Forum Discussion
External Access to Exchange 2016 while migrating from 2010 APM LTM
When you install Exchange 2016 next to 2010, after configuration, you'll actually swing the namespace over to 2016. 2016 is able to proxy 2010 requests but it's better to bring up Exchange 2016 on it's own virtual IP, especially if you're using the iApp to configure the services (the two are very different).
When you're assured your new APM/LTM config is working for the new VIP only then would you swing DNS over to the new name.
Check out the Exchange 2016 Rapid Deployment Guide and then test the configuration on a new VIP and APM policy in a staging environment before doing anything to production.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com