{"id":2345,"date":"2018-11-28T11:44:13","date_gmt":"2018-11-28T16:44:13","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=2345"},"modified":"2018-11-28T11:44:13","modified_gmt":"2018-11-28T16:44:13","slug":"exchange-2016-migration-process","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2018\/11\/exchange-2016-migration-process\/","title":{"rendered":"Exchange 2016 Migration Process"},"content":{"rendered":"

 <\/p>\n

<\/h4>\n

\"\"<\/a><\/h4>\n

 <\/p>\n

Exchange 2016 Migration Process<\/h4>\n

It has been an exciting year of migrations to our new Exchange platform and now that we\u2019re reaching the tail end (under 500 accounts\/domain) we wanted to make sure everyone was up to speed about how the migration will work. While we have done everything to make it completely seamless and non-intrusive for the users (most will just continue working without even noticing anything) we still manage every single migration as if it were our own personal email. Carefully.<\/p>\n

Here are some steps that are involved in every migration.<\/p>\n

Step 1: Let us know that you want to migrate at least 5 days in advance<\/h4>\n

It takes a little bit of coordination for every migration project and we want to make sure we treat each migration with white gloves \u2013 if we can address issues or potential issues ahead of time and have someone present that you can dial directly, we can minimize problems. Once you know you\u2019re ready to go, let us know at least 5 days in advance and we\u2019ll guide you through the process. After all, you\u2019re paying us, don\u2019t DIY it and chance getting lost Googling for a solution to a random issue that we\u2019ve probably encountered thousands of times.<\/p>\n

Step 2: Pick a URL for OWA<\/h4>\n

Everything at ExchangeDefender is branded for you and each organization comes with it\u2019s own domain for Autodiscover, owa, etc. Anything under 16 characters goes and is typically going to be https:\/\/YOUR-ORG-HERE.xd.email<\/p>\n

Step 3: Make DNS modifications to lower domain TTL<\/h4>\n

At least 3 days in advance you\u2019ll want to contact your ISP or domain registrar (where your domain is hosted) and \u201clower the domain TTL to 5 minutes\u201d \u2013 what this means is that you want your DNS to only be cached for 5 minutes. Most DNS servers have the setting at 3 or 1 days so we need to bring this way down so that Outlook clients can switch to the new servers quickly instead of waiting for days.<\/p>\n

Step 4: Make backups<\/h4>\n

You should be making backups all the time but a migration is a great time to do so just because everyone will be in their email aware of the migration. If you rely heavily on Public Folders you\u2019ll have to export that data and add it to the new technology in 2016, Shared Mailboxes. There are millions of reasons to do so from productivity to better reliability and better management.<\/p>\n

Always backup.<\/p>\n

Step 5: Actual Migration<\/h4>\n

Best part of the migration is that after the Autodiscover change in your DNS everything is pretty much on autopilot. Email will be moved by our team on the backend to the right servers automatically. Outlook clients will automatically reconnect to the new servers and most won\u2019t even notice any difference except for better speed and more reliability.<\/p>\n

Step 6: Cleanup<\/h4>\n

The last step is where we look at odds and ends: random Microsoft stuff that used to work before but now it\u2019s suddenly broken. We\u2019ve all been here with users, we\u2019ve all dealt with \u201cunique business case scenarios for xyz\u201d and so on \u2013 again, we want to make sure everyone is happy with 2016 and productive right away and that means being on top of all the issues right away.<\/p>\n

Knock on wood, our migrations process has had enough reps and tests that it\u2019s very fluid and predictable now. While the cutover to the new 2016 platform is pretty much instantaneous, and mail is synced up on the backend, it can take about an hour or so depending on the mailbox for all the data to move and the search index to update. But what you get with 2016 is the most stable, trouble-free, platform we\u2019ve ever offered.<\/h4>\n

Looking forward to seeing you on 2016.<\/h4>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,8],"tags":[51,52,112,113],"class_list":["post-2345","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-hosted-services","tag-email","tag-email-security","tag-microsoft-exchange","tag-migrations"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2345","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=2345"}],"version-history":[{"count":9,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2345\/revisions"}],"predecessor-version":[{"id":2355,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2345\/revisions\/2355"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=2345"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=2345"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=2345"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}