#Outlook 2010 and exchange 2016 compatibility Pc
I tried modifying the host record of the pc but when i try to open the mailbox it says “cannot stat micrsoft outlook, set of folders cannot be opened attempt to log on to msft exchange has failed” Is there anyway to test the DNS changes without actually making the change in dns and have a user whos mailbox still resides in 2010, use 2013 CAS ? Get-OutlookAnywhere | Set-OutlookAnywhere -ExternalHostname -InternalHostname -ExternalClientsRequireSsl $true -InternalClientsRequireSsl $true -DefaultAuthenticationMethod NTLM
#Outlook 2010 and exchange 2016 compatibility pro
If Outlook Anywhere was already enabled and configured, it needs to be checked to confirm that the correct authentication settings are in place to allow Exchange 2013 to proxy connections to Exchange 2010 for users who have not yet been moved to Exchange 2013.įor the Exchange Server Pro organization the servers are configured as follows: If Outlook Anywhere was not previously used in your Exchange 2010 organization it needs to be enabled and configured. If you have a large/complex environment you can use my mail flow heat map script for this.ĭuring co-existence all Outlook connections to mailboxes are via the Exchange 2013 Client Access servers using RPC-over-HTTPS (Outlook Anywhere), even internal connections. Verify that mail flow between existing servers is healthy.Test Exchange Web Services by doing free/busy lookups.Launch Outlook for a new test user and verify that Autodiscover works correctly.Review the Exchange 2010 server event logs for any unusual errors.Confirm that backups for Exchange 2010 are functioning correctly.Either use a different mailbox policy for the test user you use for ExRCA, or use a mobile device to perform the testing instead. Note that the ActiveSync test may fail on the final step if your ActiveSync mailbox policy does not allow non-provisionable devices.Use the ExRCA tools to test external access.Run Test-ExchangeServerHealth.ps1 to perform a health check of the servers.This avoids potential support confusion if a service is cutover to Exchange 2013, is found to be not working, and then it is unknown whether the service was already faulty or whether it was the cutover that caused the fault to occur. Before any migration or cutover of services it pays to verify that the current Exchange Server 2010 environment is in good health.