This document discusses Exchange Server updates and migrations. It provides guidance on updating Exchange Servers, including why updates are important, the different types of updates, and the general update process. It also outlines the general server migration process, including preparing Active Directory, installing new Exchange Servers, configuring load balancing, testing the new environment, changing DNS records, and decommissioning legacy servers. Questions are taken at the end if time allows.

1. Exchange Server
Migrations & Updates
Dave Stork
Architect @ OGD ict-
diensten
Exchange MVP
Mail: dave.stork@ogd.nl
Twitter: @dmstork
Blog: https://dirteam.com/dave
Podcast: www.theUCarchitects.com

2. Agenda
Updates & Updating
– Why?
– General process
Server migrations
– General process
Questions
– If remaining time allows

3. Updates

4. Updates
Why update?
Updates fixes bugs, improve security and add
features and capabilities.
– Regular updates
– Security updates
– Interim updates
– Hotfix
What are upgrades?
New major build (i.e. Exchange 2007 to 2013)

5. Updates
Regular Exchange Updates
Exchange 2007-2010
– Rollup Updates (RU)
– Service packs (SP)
Exchange 2013
– Cumulative updates (CU)
– Service Pack (just a support distinction)
All updates are cumulative
– You can install the latest update without requiring to install
intermediate updates
– 2013: It’s best to keep up and miss no more than 1 CU

6. Updates & Support
Mainstream Support
Security updates
Possibly new features and capabilities
Extended Support
Security updates
Out of support
No updates
Business risk

7. Updates & Support
Service Pack extends support
Where can I find this information?
– https://support.microsoft.com/en-us/lifecycle
Products Released Lifecycle Start Date Mainstream Support End
Date
Extended Support End
Date
Service Pack Support
End Date
Exchange 2010
Enterprise 11/9/2009 1/13/2015 1/14/2020 10/11/2011
Exchange 2010 SP1 8/23/2010 Not Applicable Not Applicable 1/8/2013
Exchange 2010 SP2 11/28/2011 Not Applicable Not Applicable 4/8/2014
Exchange 2010 SP3 2/12/2013 Review Note Review Note
Exchange 2010
Standard 11/9/2009 1/13/2015 1/14/2020 10/11/2011

8. Update process
Always test updates in a test/lab environment
that is comparable to the live environment
If this is not possible; wait several weeks and
watch the Exchange Team blog and/or MVP
blogs
http://blogs.technet.com/b/exchange/
Read release notes and check compatibility
with third party solutions (Antivirus, backup)
Read every release notes, also those you’ve skipped!

9. Update process
Single server
Check server health
Ensure backups are OK
– Perform a restore test
Plan a maintenance window and inform users
Reboot server
Install update
Reboot
Test
Perform additional actions and release or uninstall
update
– Uninstall not possible with SP and CU

10. Update process
Servers in a DAG
Check server health
Ensure backups are OK
– Perform a restore test
Plan a maintenance window
– inform users?
Disable server in Load Balancer
– To prevent user connections to a server while updating.
Healthchecks might not correctly detect availability

11. Update process
Servers in a DAG
Put server in maintenance mode
– 2010: built-in StartDagServerMaintenance.ps1
– 2013: MVP Michael van Horenbeeck script
– http://vanhybrid.com/tag/maintenance-mode/
Disable Antivirus (AV, and other processes)
Install update
– Test & evaluate
Stop maintenance mode
– 2010: built-in StopDagServerMaintenance.ps1
– 2013: MVP Michael van Horenbeeck script

12. Update process
Servers in a DAG
Enable AV and other processes
Perform additionional actions
Redistribute databases
– Built-in: RedistributeActiveDatabases.ps1
Enable server in load balancer
– Check when client access load is evenly distributed
Start process on other servers
– With 2013 you can wait a longer period before updating
other servers

13. Update process tip
To speed up updating, disable
Check for server certificate
revocation in Internet
Explorer.
However, a reboot is required.

14. Server migrations

15. Migrations
Check requirements
Coexistence
Topology
Resources
Third party products
Clients

16. Migrations
General process
Prepare Active Directory
Install first new Exchange server
– Install correct certificate
– Configure Internal and External URLs
– Other configuration
Install additional servers
– Repeat configuration

17. Migrations
General process
Configure load balancer
Test and evaluate
– Including backup!
Change DNS records pointing to Exchange
Migrate data
Decommission legacy Exchange

18. Prepare Active Directory
Prepare Schema & Active Directory Domain
via setup of Exchange installer
– Setup /PrepareSchema or /PrepareAD
– Note: most 2013 CU’s have AD Schema updates
Not required to perform on Exchange server
– Schema Master
Can be done before or during installation of first new Exchange
server
Check successful preparation
– https://technet.microsoft.com/en-us/library/jj937132(v=exchg.141).aspx
You cannot install new “legacy” Exchange server
after this action

19. Install first new Exchange server
New Exchange server
Microsoft recommends installing in separate AD
site (another subnet), configure and then
change IP address
Install certificate
– Certificate request made by Exchange
Configure Internal/External URI
– OWA, ECP, EWS, OAB, Outlook Anywhere

20. Install first new Exchange server
New Exchange server
Configure AutoDiscover URL
– Set-ClientAccessServer –Identity <server> –
AutoDiscoverServiceInternalUri
https://autodiscover.contoso.com/AutoDiscover/AutoDisco
ver.xml
Other (server) configuration
– Database Availability Group
– Databases
– Antivirus, backup, third party solutions
Same process for subsequent servers

21. Load Balancer
Configure your load balancer
Choose a Virtual IP (VIP)
Add real servers
Add required protocols
– HTTPS, SMTP, IMAP etc.
Healthcheck
– https://mail.contoso.com/owa/healthcheck.htm
Other options
– SSL Offloading
– Content Switching
When migrating from 2013 to 2016 you can add
2016 servers to existing 2013 VIP

22. Test and evaluate
How to test?
Change local host file to point towards Virtual IP
Move test or pilot users to new Exchange
– This is an immediate test for mailbox migration
Use OWA, Outlook etc.
Let users interact with other users not on new
Exchange
– Delegates, Access to Mailbox and Public Folders etc.
– Note changes/issues reported by pilot users

23. Change DNS
Change DNS records pointing to Exchange
Do this in a maintenance window
From old server to new server
– Or Virtual IP
Valid for Exchange 2010->2013 & 2016
When coming from Exchange 2007
– Change Exchange 2007 to other namespace, i.e. legacy
– Point “normal” URLs to new Exchange
This is a major milestone; real coexistence

24. Migrate Data
Mailboxes
Mailbox moves are online from 2007 upwards
– This means you can migrate a mailbox without locking out
the user up until the very last moment
You can suspend mailbox moves in 2010+
– After Initial Sync the suspended mailboxes will be kept in
sync
If there are issues you can resolve them and then
let the move resume
– Bad Item or Large item limit, other corruption, permissions
etc.
A 2013 MigrationBatch is a collection of mailbox-
moves

25. Migrate Data
Mailboxes
Be aware: Mailbox moves generate a lot of
transaction logs
– Monitor disk space
– Temporarily enable circular logging (risk!)
After completing a mailbox move or Migration
batch an Outlook restart is required
ActiveSync devices might have to be
reconfigured
– Remove and re-add configuration in device

26. Migrate Data
Public Folder
From legacy public folders to Modern Public Folders
(2013+)
– Prepare anytime, but cutover only after all mailboxes are on
new server
– You have to use several scripts
– https://technet.microsoft.com/en-
us/library/jj150486(v=exchg.150).aspx
– Some additional tips
– https://dirteam.com/dave/2014/06/30/migrating-legacy-
public-folders-to-exchange-2013-tips/
From 2013 to 2016
– Public Folder mailbox move

27. Decommission legacy servers
When satisfied and data is migrated
Run setup on server
– This is the only supported way to uninstall Exchange!
Setup warns when you cannot uninstall
– For instance: Arbitration mailboxes
Resolve issues and try again
Remove legacy server objects from load
balancer etc.
Remove computer account from AD and
remove hardware/VM

28. DONE!

29. Questions?
Mail: dave.stork@ogd.nl
Twitter: @dmstork
Blog: https://dirteam.com/dave
Podcast: www.theUCarchitects.com

30. Microsoft Ignite 2015 sessions
Meet Exchange Server 2016
Exchange Server Preferred Architecture
Deploying Exchange Server 2016
Exchange on IaaS: Concerns, Tradeoffs, and
Best Practices
https://channel9.msdn.com/Events/Ignite/2015