When migrating from an in-house Exchange to Smarsh Hosted Services Exchange, you may encounter issues with Outlook still trying to retrieve Autodiscover configuration from local Active Directory.
- public DNS is configured correctly;
inOutlook users get a password prompt for their old server (it may come up after prompting the user for Smarsh Hosted Services Exchange server or when the user is trying to access out of office assistant settings);
- users cannot send folder sharing invitations;
- running Autodiscover test in the user’s Outlook shows links to the old server;
- a common fix to put a record for the Autodiscover server into the
hostsfile does not work (read the Knowledge Base article on How To Find And Modify Entries In The HOSTS File for more information).
1. Adding Registry values for Outlook to exclude SCP object check
If you have users on the in-house Exchange server that are not supposed to be migrated to Smarsh Hosted Services at all, this can sometimes result in
Note: Public Autodiscover DNS record should be pointing to Smarsh Hosted Services.
Important: Back up the registry first and be careful when making any changes to it as any incorrect action may result in the OS crash.
The fix is to create the following Registry keys on necessary machines:
Open regedit: to do so, click the Start button and then in the Start Menu, either in the Run box or in the Search box, type regedit and press Enter.
Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover (x.0 corresponds to the Outlook version: 16.0 = Outlook 2016, 15.0 = Outlook 2013, 14.0 = Outlook 2010, 12.0 = Outlook 2007) and create these DWORD values to excude all checks before ExcludeHttpRedirect which is used in Smarsh Hosted Services:
For Outlook 2010 version 14.0.7140.5001 and later versions, please also add the following DWORD:
For Outlook 2016 version 16.0.6741.2017 and later versions, please also add the following DWORD:
Note: You may also need to add the same DWORD values to the following registry path: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\x.0\Outlook\AutoDiscover
You can also export this set of records into a .reg file and import it to Registry on another affected machine.
Run the following cmdlets:
Set-WebServicesVirtualDirectory -Identity yourservername\EWS* -InternalUrl https://ExchangeProxyServer/EWS/Exchange.asmx
Set-WebServicesVirtualDirectory -Identity yourservername\EWS* -ExternalUrl https://ExchangeProxyServer/EWS/Exchange.asmx
Note: if you have more than 1 server running, use a full EWS path to the necessary instance instead of EWS*. For example: -identity "yourservername\EWS (Default Web Site)"
The Exchange Proxy Server settings can be found under Home > Exchange Servers & Settings > Exchange Proxy Setting.
Run the following cmdlet:
Set-ClientAccessServer –Identity yourservername –AutoDiscoverServiceInternalUri https://ExchangeProxyServer/Autodiscover/Autodiscover.xml
3. Fixing the local DNS records
If you have a local DNS server and a
Go back to top
4. Redirecting to Smarsh Hosted Services Autodiscover server in IIS
If a password prompt for the old server pops up and the Test Email Autoconfiguration utility shows the local server's URLs, that means the Autodiscover settings were pulled directly from AD. To fix that, navigate to IIS manager > Default Web Site > Autodiscover > Properties (or IIS manager > Default Web Site > Autodiscover > HTTP Redirect) and set the page to redirect to https://ExchangeProxyServer/autodiscover (you can try https://ExchangeProxyServer/autodiscover/autodiscover.aspx as well)..