Slow Outlook 2010 startup out of company network
Hi. I have Exchange 2010 SP1 RP1 installed with 2 CAS servers in CASARRAY. Outlook Anywhere and AutoDiscover is configured correctly (checked by Exchange server remote connectivy analyzer). When a clients with migrated mailbox to Exchange 2010 run an Outlook 2010 from home, the startup of Outlook 2010 is very slow (about 40 seconds). When they run Outlook 2007 with same account configuration, the Outlook starts in 5 seconds. Debugging mode of Outlook did not show any error. Do you have any idea how to solve/troubleshoot this issue? ------- Michal Stoppl
December 21st, 2010 3:28am

Does the CAS Array host name resolve on the Internet? If it does, then it shouldn't do. That can cause the delay you are experiencing because Outlook tries to connect to the CAS Array host and you have to wait for that to time out. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2010 1:02pm

Hi. CAS Array host name is identical with mail.domain.com - we have this configuration because we had an issue with certificate in case of scenario, when the name was different. Would you clarify, why it should be different/why does it cause the delay? Outlook connects to CAS Array, which is NLB, that stands of 2 CAS servers. What is a correct configuration? We use the same hostname for both internal and external connection.
December 22nd, 2010 1:03am

Hi MStoppl. How about check the "on fast/slow networks, connect usting http first..." in the ourlook account setting? Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2010 5:26am

Hi. Gavin: I will try that, thanks. Simon: I was thinking about that again and... If casarray would be a problem, there would be a same impact to both Outlook 2007 and Outlook 2010 users (in my humble opinion) :) ------- Michal Stoppl, DiS. Please always use Mark as answer if you are satisfied with provided solution.
December 22nd, 2010 6:07am

Outlook doesn't make a connection to the CAS Array using HTTPS at all. You don't have to put the CAS Array in to your SSL certificate. If you are using the same name for both CAS Array and Outlook Anywhere then that is your problem. Microsoft do not recommend that that the name resolves externally. As I have already said, the reason for the delay is because the host name you are using resolves, therefore Outlook attempts to make a regular MAPI connection to the server. This doesn't work because the various ports are not open. It has to time out, then fail back to Outlook Anywhere. Gavin's suggestion may well work, but the issue will be setting the clients to work in that way, particularly non-domain clients, as you cannot configure that property with Autodiscover. Your best option is to change the CAS array host name, to a name that does not resolve externally. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2010 6:19am

Hi Simon, thanks for clarification. Do I understand correctly, that you recommend: Current situation: Outlook Anywhere/OWA/... on casarray: exchange.domain.com Future: CasArray: exchange.domain.local Outlook Anywhere/OWA/...: exchange.domain.com So exchange.domain.local should point to...? I have believed, that name of casarray has to be a name of NLB. Sorry, this is my first deployment :( Thanks------- Michal Stoppl, DiS. Please always use Mark as answer if you are satisfied with provided solution.
December 22nd, 2010 6:29am

The CAS Array host can point to either the IP address of the NLB or directly to a CAS server. It doesn't really matter. What I usually do is simply point the CAS array host at a CAS server to begin with (A record to the IP address, not a CNAME). Test to ensure that it is working correctly. Then implement NLB. If the NLB doesn't work, then I can change the DNS entry back. Otherwise, what you have suggested is correct. Use a host name that resolves internally. I often use outlook.example.local, rather than Exchange, as there is often a server called "Exchange" floating around somewhere. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2010 6:38am

So summary: 1) Create a DNS record casarray.domain.local, that will point to internal IP of NLB 2) Change casarray FQDN to casarray.domain.local Everything else should be a same (name of NLB exchange.domain.com, ...), I hope. I will try it out of business hours. If there is still something wrong, let me know please. Thanks.------- Michal Stoppl, DiS. Please always use Mark as answer if you are satisfied with provided solution.
December 22nd, 2010 6:47am

So summary: 1) Create a DNS record casarray.domain.local, that will point to internal IP of NLB 2) Change casarray FQDN to casarray.domain.local Everything else should be a same (name of NLB exchange.domain.com, ...), I hope. I will try it out of business hours. If there is still something wrong, let me know please. Thanks. ------- Michal Stoppl, DiS.
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2010 2:43pm

Hi. Thanks a lot for a clarification, this helped me to solve my problem. ------- Michal Stoppl, DiS.
December 23rd, 2010 6:31am

Hello, can NLB cause this sort of delay?
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2011 12:30am

NLB not. We also have CAS servers in NLB. As mentioned - the problem in our case was, that name of NLB was same as CAS array... M. ------- Michal Stoppl
March 23rd, 2011 10:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics