This will result in autodiscover returning the on-premises configuration instead of the new one pointing to Office 365 or the Exchange forest.
Before the new version, what you might easily do is overrule the autodiscover configuration and define a manual setup to connect to Office 365 or a new Exchange forest. You could define an account with manual settings—that’s all it took. It was a labor-intensive job, but it was technically doable.
With Outlook 2016 it becomes a lot harder. It involves either cleaning up the on-premises Active Directory with all the potential problems associated with it, or overruling the autodiscover in the registry of every single device.
Keeping It Simple
DeploymentPro offers a solution to this problem for this. DeploymentPro allows you to connect to Office 365 or an Exchange on-premises forest without any issues, overruling or reconfiguration.
With the power of the cloud combined with automation, DeploymentPro eliminates the need for you to visit every desktop physically and remote sessions with employees. It is a cost-effective way to manage your desktop regardless of size, version, geographic location, or status. Find out more about DeploymentPro now so you are fully prepared to handle your next migration to Outlook 2016.