V
V
Vadim Choporov2016-12-02 17:05:24
Browsers
Vadim Choporov, 2016-12-02 17:05:24

How to use 2 Exchange accounts in 1 browser??

Good afternoon.
I have a corporate Exchange 2010 server. I allow OWA connections. I connect through the browser, I log in - everything is ok. But if 2-3 users work on 1 computer, each with their own mailbox, a problem arises:
after 1 has finished working with the box, clicks exit - it seems to exit, and even transfers to a page with the text "exit completed successfully". But then? when we try to enter the main page again, to enter the second user, instead of offering to enter credentials, it automatically transfers to the box from which we successfully exited before. Restarting the browser, clearing the cache, deleting history (including saved passwords) does absolutely nothing. After a n-th amount of time, it asks for login again, only the value of n is quite large, I was able to log in under another user only after 2 days))
Tell me, maybe somewhere in the server settings there is a setting for the user's session retention time when idle, or something similar? Or something else to pay attention to?
PS. The situation is the same both through the Internet and in LAN. Browsers tried Firefox and Chrome.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
S
Saboteur, 2016-12-02
@saboteur_kiev

In a normal way, different users on the same computer should have different accounts.
So do it.
As a last resort, a bicycle, launching at least a browser from another account.

E
Ethril, 2016-12-02
@Ethril

At logon in OWA there is a daw private computer/shared computer. In shared remembers something like for 15 minutes.

A
akelsey, 2016-12-06
@akelsey

When you click Sign Out in OWA, all sessions are terminated, all cookies are neutralized.
When the browser is directly connected to Exchange OWA, everything works correctly (it would be strange to expect a different behavior from Microsoft).
In your case, it looks like someone is caching information between the browser and the mailer, I suspect a corporate proxy server with aggressive caching, such as Squid.
In this case, you need to correctly register local resources in the autoconfiguration script, or distribute them to users through GPO, in extreme cases, add exceptions to IE by hand (for the duration of the test, it is better to disable the proxy altogether).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question