Hello, I am attempting to migrate from Exchange 2007 SP2 to 2010 SP1. I have set the autodiscover.domain.com to the IP of the Exchange 2010 CAS Server. When an Outlook client is trying to connect to a mailbox for the first time on the Exchange 2010 server it should populate: Microsoft Exchange Server: outlook.domain.com Mailbox: user@internaldomain.com Instead it is populating the correct server (this is a Load Balanced CAS array) but for Mailbox it puts: =SMTP:user@externaldomain.com This was working when I first set it up and now is all mucked up. Yes I have tried the Remove-AutodiscoverVirtualDirectory and New-AutodiscoverVirtualDirectory multiple times and restarted IIS and restarted all exchange servers. The test Email Auto Configuration shows everything being pointed to the correct URL's. Any help would be appreciated, this has completely stopped my Exchange Migration.

Hi, This may be related to the DNS configuration on the client's network card. If the DNS server is the public DNS server, the client would always to check the and connect to external doamin, it is expected. If the client boxes not joined into domain, the outlook would not use the internaldomain.com as you want to achieve. Regards from www.windowsadmin.info

I guess redirecting the autodiscover url should resolve this issue Please refer the following article for refrence http://support.microsoft.com/kb/940726 Hope this helps. Viral R

Thank you for replies. This is for internally connected Domain Computers. Haven't even made it to external tests. I am now getting the auto population to work on computers that have never had Outlook configured on their computers and login and run outlook, it sets up correctly to the Exchange 2010 SP1 UR2 CAS Array. However, if the computer had outlook configured before and pointed to the Exchange 2007 server and I move the user mailbox to the 2010 server the Outlook Client does not pick up the new settings after restarting computer and says Outlook is offline. Also, when running the Test Email Autoconfiguration I get: Autodiscover to..."CorrecttInternalURL\autodiscover.xml" Started Autodiscover complete with HTTP Status 500 Autodiscover to..."CorrecttInternalURL\autodiscover.xml" Failed (0x80004005) I have tested and i can access the Autodiscover InternalURL from the browser. Creating a new session for implicit remoting of "Test-OutlookWebServices" command... RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https:// mail.domain.com/autodiscover/autodiscover.xml. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1013 Type : Error Message : When contacting https://mail.domain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (500) Internal Server Error. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1023 Type : Error Message : The Autodiscover service couldn't be contacted. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1013 Type : Error Message : When contacting https://mail.domain.com/ews/exchange.asmx received the error Client found response co ntent type of '', but expected 'text/xml'. The request failed with an empty response. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1025 Type : Error Message : [EXCH] Error contacting the AS service at https://mail.domain.com/ews/exchange.asmx. Elapsed time was 687 milliseconds. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1026 Type : Success Message : [EXCH] Successfully contacted the UM service at https://mail.domain.com/ews/exchange.asmx. The elapse d time was 140 milliseconds. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1013 Type : Error Message : When contacting https://mail.domain.com/EWS/Exchange.asmx received the error Client found response content type of '', but expected 'text/xml'. The request failed with an empty response. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1025 Type : Error Message : [EXPR] Error contacting the AS service at https://mail.domain.com/EWS/Exchange.asmx. Elapsed time was 218 m illiseconds. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1026 Type : Success Message : [EXPR] Successfully contacted the UM service at https://mail.domain.com/EWS/Exchange.asmx. The elapsed time was 46 milliseconds. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1113 Type : Error Message : When contacting https://mail.domain.com/ews/exchange.asmx received the error Client found response content type of '', but expected 'text/xml'. The request failed with an empty response. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1125 Type : Error Message : [Server] Error contacting the AS service at https://mail.domain.com/ews/exchange.asmx. Elapsed time was 124 milliseconds. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1126 Type : Success Message : [Server] Successfully contacted the UM service at https://mail.domain.com/ews/exchange.asmx. The el apsed time was 0 milliseconds.

Thanks but I am not getting any security warnings about certificates. All certificates are setup properly with SAN certs and all domains are included in the SAN Cert. This was working out the box and has since failed.

Update/More info: I have 3 CAS servers all with identical setups. CAS1 and CAS2 autodiscovery does not work, CAS3 does work???? They are all using the same SAN Cert. Cert is not the issue. I have pointed the Autodiscovery internal URL to both the individual server domain names (default setup) and the CAS array domain name and i get the same results so the HLB Cas Array is not the issue. I have also remove the CAS Array and just set it up as if they were stand alone CAS servers and still get the same issue. The problem is with CAS1 and CAS2 Autodiscovery. I have removed and recreated the virtual directories on them multiple times and the EWS. No help. I am still getting the issue when new Outlook clients try to connect for the first time where it puts =SMTP:user@externaldomain.com for the username, even when only pointing to the working CAS3 server Autodiscovery. So something else is also wrong with Autodiscovery. This is all for internal domain connected Windows 7 PC's using Outlook 2007 and 2010. Very frustrating. I never had a single issue with Exchange 2007 Autodiscovery, and by judging by the numerous issues mutliple people are having with Exchange 2010 Autodiscovery it looks like there may be issues with it in Exchange 2010. I have also installed UR2 for SP1, no help. I have also created the correct DNS entries in my internal DNS server. Exchange Active Sync, Outlook Web Access, Availabilty Service and Web Services are working perfectly fine. Unfortently this is my only show stopper as I can't migrate my 100 users to Exchange 2010 Mailbox as when they go to run Outlook it won't pick up the new settings for Outlook to connect to the new CAS servers. Thank you.

That is the expected behavior after KB 2412171. You need to uninstall the patch on your clients. I believe MS will release an updated patch in the next release to revert the behavior. Description of the Office Outlook 2007 update: January 11, 2011 http://support.microsoft.com/kb/2412171 http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/82d00bc2-1e9d-4dfb-8ed0-711b3e85d7cf James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Actually this is the behavior I want, I want it to use the internal domain name instead of the external SMTP domain name for the user. I figured it out though. I had to enable transparency on my Load Balancer for the MAPI Virtual Service, even thought the Kemp Load Master Exchange 2010 instrutions say to disable it. It is now populating the proper user@internaldomain username. Now that I have that figured out I am still stuck with my second issue on two of my three CAS servers. The Autodiscover Service is dead on CAS1 and CAS2. I get the below: Autodiscover to..."https://server.domain.com/autodiscover/autodiscover.xml" Started Autodiscover complete with HTTP Status 500 Autodiscover to..."https://server.domain.com/autodiscover/autodiscover.xml" Failed (0x80004005) Test-OutlookWebService -ClientAccesServer "CAS1" RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https:// cas1.domain.com/autodiscover/autodiscover.xml. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1013 Type : Error Message : When contacting https://cas1.domain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (500) Internal Server Error. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1023 Type : Error Message : The Autodiscover service couldn't be contacted. RunspaceId : 37cd000a-dbc8-4226-82b5-07baeb070676 Id : 1013 Type : Error Message : When contacting https://cas1.domain.com/ews/exchange.asmx received the error Client found response co ntent type of '', but expected 'text/xml'. The request failed with an empty response.

If you open a browser can you get to https://cas1.domain.com/autodiscover/autodiscover.xml The first thing I would do, 1. Compare the ntfs permissions with the working CAS to the non working CAS for the autodiscover.xml 2. Compare the IIS virtual directory settings particularly the authentication settings for the working CAS and non working CAS. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

yes, i can access all three servers via browser from all clients. IIS VD's are setup exactly the same. I set these 3 servers up at the same time exactly the same way. I cannot figure out why two of them have died and the 3rd has no issues at all? I don't know why recreating the IIS VD's doesnt help. I read something about reparing .net for IIS or re-installing it but I can't find that thread or how to do it.

I had to throw in the towel on this one. I tried just simply uninstalling the Client Access Role on CAS2 and it couldn't even do that. It crashed halfway thru the uninstall and everything was done after that. I cut my losses and wiped out the OS and re-installed Exchange with the recoverserver swithch (http://technet.microsoft.com/en-us/library/dd876880.aspx). After the OS re-install all Web and Autodiscover services on this CAS server worked normally again. Are there official instructions on how to re-install IIS and the CAS Role for Win 2008 R2 and Exchange 2010 SP1? I tried removing the IIS role, rebooted server, reinstalled the IIS role using the "typical" script with the Exchange install media and then removing the CAS role, on uninstall of the CAS Role is where it failed. At least the recover server process worked. So far Exchange 2010 migration has been a total nightmare. Exchange 2003 to 2007 was a breeze compared to this. thank you for the replies. -D

Thank you for your update and let us know how you resolve the issue. Based on my research, there is no specific official article about IIS reinstallation. You can remove IIS role in Server Manager and then refer to the following article to reinstall it. http://technet.microsoft.com/en-us/library/cc771209.aspx Thanks. NovakPlease 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.