changing Outlook Anywhere internal URL disconnects XP clients

Good morning,

I am supposed to change the internal Outlook Anywhere hostname for an Exchange installation:

recent internal hostname: webmail.contoso.com
future internal hostname: webmail.contoso.local

The external hostname for OA is not set, because OA should not be available from external. 

Now I made a test changing the internal hostname as follows:

  • generate a new Exchange certificate with subject name "webmail.contoso.local"
  • Set-OutlookAnywhere -InternalHostname webmail.contoso.local -InternalClientsRequireSSL:$True

Afterwards I made some tests on several clients:

  • Windows 7: working fine, it takes some time but Outlook updates its profile to the new internal OA name and connects to the mailbox
  • Windows XP: Outlook profile is not updated automatically, if I update it manually, Outlook hangs when starting and still tries to establish 1 connection to the old OA internal hostname

Does anyone of you have an idea how to solve this? I appreciate your suggestions, thank you very much. :-)

Sebastian

March 31st, 2015 2:06am

Hello,

Have you updated the host name on the certificate from webmail.contoso.com to webmail.contoso.local?

Run Connection Status on both Windows 7 and Windows XP and see if they connect to different DC. If so, check the DC replication issue.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 8:25am

Hi Simon,

thanks for your suggestions. The certificate host name was updated to webmail.contoso.local before changing the OA hostname.

I also checked the connection status. The problem also occurs when the clients contact the same DC. For the DCs i checked the replication with repadmin and dcdiag an I cannot find any issues.

Thank you

March 31st, 2015 8:27am

Hi,

the problem was that Outlook 2007 on Windows XP did not automatically update the profile. So I put a GPO with the appropriate administrative template to set the OA hostname, after this it works now!

Sebastian

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 7:11am

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

Other recent topics Other recent topics