Outlook Anywhere

Hi All, We are migrating from Exchange 2007 environment to Exchange 2013. In our exchange 2007 environment, outlook anywhere was not enabled. As exchange 2013 uses internal outlook anywhere (RPC over https) connection, we had to enable outlook anywhere on Exchange 2007 servers. My question is after enabling outlook anywhere on Exchange 2007 servers, do we need to force outlook anywhere settings on existing configured outlook profiles or existing outlook profiles will pick up outlook anywhere settings automatically from exchange server. I read many articles around the same but nothing was conclusive, somewhere it suggests it will pick up in six hours, somewhere it suggested to do it via GPO, somewhere it suggests part of autodiscover etc. did not get a confirmed answer hence posting it on this forum.

Thanks

July 1st, 2015 7:47am

You should not have to force Outlook to retrieve Outlook Anywhere (OA) settings.  Have you configured a SRV record for Outlook to find AutoDiscover via DNS?  If not, is the AutoDiscover DNS entry pointed at Exchange 2013?  Do you have your AutoDiscoverServiceInternalURI option configured on your Exchange 2013 CAS servers and removed on your 2007 servers?   If you run 'get-outlookprovider' what do you get for results?

Let's start with that for now.

Make sure to read these Microsoft articles as well:



Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 9:31am

Hi,

The Autodiscover service uses a user's e-mail address and password to automatically configure a user's profile.

Using the e-mail address, the Autodiscover service provides Outlook Anywhere server settings to the client.

In general, when we move a mailbox from exchange 2007 to 2013 , the mailbox will connect automatically exchange 2013 after restarting outlook .

Please run the below command to check you outlookanywhere setting on exchange 2013:

Get-OutlookAnywhere | fl Identity,*host*,*auth*

Make sure the external host name points to your exchange 2013 server .

If we have any Outlook connectivity issue, we can have a test with https://testconnectivity.microsoft.com/   and see what went wrong.

For more information, please refer to the link:

https://technet.microsoft.com/en-us/library/bb124251%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Best Regards,

David

July 1st, 2015 10:28pm

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

Other recent topics Other recent topics