I am currently in the process of migration from Exchange 2003 to Exchange 2010. Right now servers coexist. I have transferred several mailboxes to Exchnage 2010 and now I'm testing it for possible problems. I have revealed one by now: after restart of CAS service, Outlook clients do not restore connection to the server: users get a popup message which requires login and password. To solve the problem Outlook must be closed and launched again. In case of restart Exchange 2003, connection restores automatically without any user interaction, and I would like go get the same behaviour with Exchange 2010.
Another moment is that popup message for Outlook 2007 users points to external CAS's DNS record. I don't think it is correct, but I can't understand how to fix it: there are not many settings for RPC-clients in EMC and Get-RpcClientAccess returns correct (internal) server name.
Any ideas? I'm ready to provide any information needed.
You may want to look into configuring your CAS Servers to use Kerberos to resolve the issue with users receiving login prompts when the CAS Server they are connected to is rebooted.
Here's a link to get you started:
1) verify internal\external url setting on EWS virtual directory
2) plz have a look on http://support.microsoft.com/kb/2634633
I have succefully solved the problem. That was Autodiscover SCP. It enables Outlook anywhere option (RPC over HTTP) automaticaly. If CAS restarted, Outlook lost connection and tried to connect via HTTP, but that type of access had not been configured in my environment yet. To solve the problem the corresponding Outlook option needed to be disabled for internal (RPC) users. Sorry, I can't post the link, but you can find appropriate topic by its name: "How do I Disable the auto configuration of Outlook Anywhere on 2007/2010 Clients?"
- Edited by Igor Kulagin 20 hours 55 minutes ago misspelling
- Marked as answer by Igor Kulagin 20 hours 55 minutes ago
I have succefully solved the problem. That was Autodiscover SCP. It enables Outlook anywhere option (RPC over HTTP) automaticaly. If CAS restarted, Outlook lost connection and tried to connect via HTTP, but that type of access had not been configured in my environment yet. To solve the problem the corresponding Outlook option needed to be disabled for internal (RPC) users. Sorry, I can't post the link, but you can find appropriate topic by its name: "How do I Disable the auto configuration of Outlook Anywhere on 2007/2010 Clients?"
- Edited by Igor Kulagin Tuesday, March 11, 2014 1:56 PM misspelling
- Marked as answer by Igor Kulagin Tuesday, March 11, 2014 1:56 PM
I have succefully solved the problem. That was Autodiscover SCP. It enables Outlook anywhere option (RPC over HTTP) automaticaly. If CAS restarted, Outlook lost connection and tried to connect via HTTP, but that type of access had not been configured in my environment yet. To solve the problem the corresponding Outlook option needed to be disabled for internal (RPC) users. Sorry, I can't post the link, but you can find appropriate topic by its name: "How do I Disable the auto configuration of Outlook Anywhere on 2007/2010 Clients?"
- Edited by Igor Kulagin Tuesday, March 11, 2014 1:56 PM misspelling
- Marked as answer by Igor Kulagin Tuesday, March 11, 2014 1:56 PM
Good to see you got this fixed.
couple of things to mention.
1 - have you set the registry key on Outlook 2007 client to represent credentials
2 - are you load balancing Exchange 2010
What was the behaviour for an Outlook 2010 client in the environment...?
Hello, Rhoderick.
I have no load balancing for Exchange and Outlook 2010 clients have the same behaviour as 2007 have. Can you give me a link with description of Outlook 2007 registry key, please?