After this latest round of Windows updates (on 1/11/11, in fact) my Exchange 2007 server of course rebooted. This may have had the side effect of making any changes I'd inadvertently made take effect.
Since then, the Autodiscover service in Exchange 2007 from Outlook 2007 seems to reply with the User Principal Name ([email protected] instead of [email protected]). I'm specifically seeing this from within the "Test Email AutoConfiguration" tool in Outlook (the UPN appears in the first text box labeled "E-mail") and when creating a new profile in Outlook. If I disregard the UPN and instead fill in my email address, Autodiscover works as expected and I can connect without issue.
I've confirmed using ADSI Edit that the SMTP email address is properly set for my users. I even went a bit crazy and set the UPN to the email address using ADSI Edit, to no avail. I've re-installed the Client Access role on the server in question.
Exchange server is Server 2008, 64-bit of course. Clients are mostly XP 32-bit, though the issue happens from a Windows 7 machine as well.
Output of "Test-OutlookWebServices -Identity:[email protected]" (real username, replaced domain):
Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address [email protected].
Id : 1012 Type : Warning Message : XML>Unknown Node:AutoDiscoverSMTPAddress AutoDiscoverSMTPAddress Line :http://schemas.microsoft.com/exchange/autodiscover/outlook/responses chema/2006a
Id : 1012 Type : Warning Message : XML>Object being deserialized: Microsoft.Exchange.Management.SystemCo nfigurationTasks.AutoDiscoverUser
Id : 1012 Type : Warning Message : XML>Element
Id : 1012 Type : Warning Message : XML>Unknown Element:System.Xml.XmlElement Line:8(8) [email protected]
Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://cppmail02v.CPCH.ci. central-point.or.us/Autodiscover/Autodiscover.xml.
Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://exchange01.active.directory.domain/EWS/Exchange.asmx. The elapsed time was 15 milliseconds.
Id : 1015 Type : Information Message : [EXCH]-The OAB is not configured for this user.
Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://exchange01.active.directory.domain/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds.
Id : 1016 Type : Information Message : [EXPR]-The AS is not configured for this user.
Id : 1015 Type : Information Message : [EXPR]-The OAB is not configured for this user.
Id : 1014 Type : Information Message : [EXPR]-The UM is not configured for this user.
Id : 1013 Type : Error Message : When contacting https://exchange01.active.directory.domain/Rpc received the error The remote server returned an error: (404) Not Found .
Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://exchange01.active.directory.domain/Rpc. The elapsed time was 0 millisecon ds.
Id : 1006 Type : Success Message : The Autodiscover service was tested successfully.
Id : 1021 Type : Information Message : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors.
A lot of people had problems with the original version of this update http://support.microsoft.com/kb/2412171 It seemed that the best option was to uninstall it.
From the cached version of http://blogs.office.com/b/microsoft-outlook/archive/2011/01/13/fixes-for-issues-with-december-update-for-outlook-2007-have-been-released.aspx
janegilring 15 Jan 2011 11:23 AM Ive experienced problems with Autodiscover when setting up new Outlook-profiles after installing this update. Instead of pre-populating the E-mail address field with the user s primary SMTP-address, the user`s UPN was used. This of course caused Autodiscover to fail since the UPN was not an alias on the mailboxes.
After uninstalling the latest Outlook 2007 update the issue was resolved, and the primary SMTP-address was pre-populated.
I`ve also experienced the issue with Outlook 2010, removing the latest hotfix package resolved the issue.
The affected updates:
Description of the Outlook 2010 hotfix package: December 14, 2010
support.microsoft.com/.../2459115
Description of the Office Outlook 2007 update: January 11, 2011
support.microsoft.com/.../2412171
The Outlook 2007 update are released to Windows Update/WSUS, while the Outlook 2010 hotfix package must be requested afaik.
Is this a known issue, and is it due to be fixed in upcoming updates?
To Uninstall:
Uninstall KB2412171 on your client. This fixes the problem. To my knowledge, MS has yet to address this problem. Extremely frustrating...
I've just done a little experiment on a virtual machine (I didn't have Exchange 2007 handy, so it was Exchange 2010, but I don't believe there's going to be much difference) and it's confirmed my suspicions.
The value comes from the E-mail field on the General tab of Active Directory Users and Computers, so if you change that field to something else, the Outlook AutoDiscover value should change to reflect that.
This may be a simple answer but if I'm not mistaken , the email address that Autodiscover uses (and the address that populates the email address field on the General tab of the user object properties) is the email address that's set as the Primary SMTP address. Is the UPN set as the Primary SMTP address for this user? Could that be what's causing the problem?