Forum Discussion
Exchange 2010 to 2013 upgrade with F5
We currently have Exchange 2010 running with our F5's serving SMTP and MAPI connections to our clients.
We are upgrading to Exchange 2013 which now uses Outlook Anywhere instead of MAPI or RPC over HTTP.
This will mean re-configuring the F5 iApp template but I don't really want to break our current implementation.
Can I create a separate iApp for Exchange 2013 and then just point our DNS entry to the new VS once I am happy it is working?
- Lee_Sutcliffe
Nacreous
Hi, nothing wrong with this approach, if you don't have a separate test/development environment, it is a prudent way to ensure you don't break your current configuration. It also makes roll back straight forward.
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