I have Exchange 2010 environment 2 CAS/HUB NLB nodes and 2 MBX nodes. After one user migration from exchange 2003 everything works for him exept autodiscover. For anyone else everythink works without problems. Account autoconfiguration test gives error: Autodiscover to https://XXX.XXX.XXX/autodiscover/autodiscover.xml FAILED (0x800C8203) Command: test-outlookwebservices -identity:username RunspaceId : 4d9e472a-fdd6-4e2e-a684-48bc5b434aa6 Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://xxx xxx.xxx/Autodiscover/Autodiscover.xml. RunspaceId : 4d9e472a-fdd6-4e2e-a684-48bc5b434aa6 Id : 1006 Type : Information Message : Contacted the Autodiscover service at https://xxx.xxx.xxx/Autodiscover/Autodiscover.xml. RunspaceId : 4d9e472a-fdd6-4e2e-a684-48bc5b434aa6 Id : 1023 Type : Error Message : Autodiscover returned the error: 603:The Active Directory user wasn't found. Maybe someone had similar problem or has idea where to look. Thanks

Hi, Did you create a legacy record when you installed Exchange 2010? It sounds like the autodiscover is still looking at the exchange 2003 server and the user doesn't exist on that server. /MartinExchange is a passion not just a collaboration software.

Quote: “one user migration from exchange 2003 everything works for him exept autodiscover. For anyone else everythink works without problems” According to above, AutoDiscover functionality is fine on the exchange server Please check the difference between the problematic machine and the working machine, including outlook version, OS version and service pack version Please recreate the mail profile of the problematic user on the working user’s machine, see if the issue still appears. It can narrow down the cause to either workstation or user object If the issue still occurs on the working machine, please check the following info on the problematic account: · Please compare the settings of the mailbox between the working user and the problematic user by using “Get-Mailbox” cmdlet · Please compare the settings of the user object between the working user and the problematic user by using “Get-User” cmdlet · Please compare the security settings of user object between the working user and the problematic user by using ADSI EditorJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

James, I did't find any differences. Only that this "bad" user belongs to Domain admins and organization management groups. I've tryed to add "good" user to same groups, but autodiscover works for him.

Does the bad user works with outlook and owa besides autodiscover feature? Anything else that doesn't work with this user? Any related info in event viewer about this user? Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

So, the issue still appears if the mail profile of the problematic user has been recreated on the working user’s machine, right? Please backup the data of the problematic mailbox into PST file, disconnect the mailbox, and enable the problematic user with a new mailbox. Then, monitor the resultJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Good suggestion James, it can be any type of corruption with the mailbox Haven't seen them too often but it happens some times Any update on the issue?Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

How's the issue currently? Any update?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Sorry for not responding so long time. I found onemore thing. Thru OWA interface everything works nice, but if i click question mark (right upper corner) then about in new window I see that "Exchange mailbox address:" is in old exchange. Maybe anyone has suggestions how to fix it?

Hi, The design of OWA will be very different, so you can easily see what Exchange version the OWA is running on. The new is yellow from the start and the 2003 is blue as far as i remember. I am sorry if i missed you question, but the part where "Exchange mailbox address:" is in old exchange lead me to the answer above. /MartinExchange is a passion not just a collaboration software.

Today i've tryed to remove mailbox (not account) and recreate it. It doesn't help. One more thing. In Outlook "Test e-mail AutoConfiguration" error is the same like for doesn't existing user: Autodiscover to https://xxx/autodiscover/autodiscover.xml Failed (0x800C8203)

Has anyone ever come accross a solution to this problem. I have an existing exchange 2010 user with the same issues. Autodiscovery doesn't work only for this specific user. We run a test e-mail auto configuration from Outlook 2010. The result we get is that "autoconfiguration was unable to determine your settings" and "autodiscover.xml failed (0x800C8203). When we run that test on the same computer with any different user, the test is successfull. I enabled diagnostic logging for autodiscovery on exchange 2010 server. Everytime we run the test-email auto configuration from outlook we get an Event 1201 MSExchange Autodiscover in the event viewer stating "Error Response with the ErrCode:603, Message: The active directory user wasn't found". Clearly this user is in AD and we have no other authentication issues with this account. I also noticed in Outlook under this user, regardless of where he logs on, he is unable to download global address book. I have tried everything from disabling and reenabling mailbox account, looking at AD Attributes, looking at exchange properties for users etc. I can get this user connected to exchange when I manually setup outlook instead of using autodiscovery which fails. The 3 things I noticed that were not working for this user are the GAB, the Online Archive and the Autoconfigure ability. I can't find any differences between a working user and this specific user as far as AD attributes go.

Got it fixed. Disconnected mailbox for user, deleted user account from AD, restored AD user account, reconnected Mailbox. All is well. Just like Magic.

A workaround if you do not want to reprovision the AD account is to do the Autodiscover XML locally for the user. You could hard code your autodiscover settings locally and follow this approach: http://support.microsoft.com/kb/2028193 I had 4 users with this autodiscover error and therefore couldnt perform other vital functions either (FreeBusy, and the same exact errors: FROM the client: autodiscover.xml failed (0x800C8203) // From the Shell: 603:The Active Directory user wasn't found. This isnt a mailbox issue. The local autodiscover XML could easily be created with all of our URL VDIR settings found when performing the outlook autodiscover test. It would be helpful for someone to identify the root cause of the 603 error from the AD/Exchange team. This is a user object specific issue.

Has anyone else found any info on this? I too am having the same error, and recreating the user account is not an option.