Hello Brent,
If I understand correctly this can be done with users still having access to the server and Exchange....correct?
If the new Exchange Server 2016 has been installed and configured it acts as a downstream proxy for any connection you make to the Exchange Server 2016. At step 10 of Migrate Exchange Server 2010 from SBS 2011 to a new Exchange Server 2016 on Windows Server 2016 I explain how to configure DNS and at that step all traffic at port 443 and 25 for mail.yourdomain.com should be routed to the new Exchange Server 2016. Even if all mailboxes are still on the Exchange Server 2010 the Exchange Server 2016 will act as a proxy and route that traffic to the old 2010 server. Even during the time you are migrating mailboxes nobody will notice anything if all is configured properly. Maybe only for a very short moment users will notice 'something' when that particular mailbox is migrated. The only time you can run into issues is when you need to migrate Public Folders, that is a kind of a cutover situation where users can see a short disconnection of the Public Folders. Exchange Server 2016 has the ability to act as a upstream and downstream proxy, the Exchange Server 2010 cannot act as an upstream proxy. Best practice is always to connect to the highest version of Exchange Server in your network.
I understand that the migration between SBS 2011 and Server 2016 has to be finished first before tackling the Exchange part of this migration...is this correct?
No, you can also start with the Exchange Server migration. That can even be done with only the SBS 2011 DC in place and no other DC around yet. It depends a bit on how much time you have and if the mailbox store on the SBS 2011 is huge I would start with the Exchange migration first.
Can one have the new server running Server 2016 (as a file server) and the old SBS 2011 Server running the Exchange part of things ? If so how long can this continue or is there no time limit ?
You can install the new Windows Server 2016 as a member server (file server) for as long as you want. You can even make the Windows Server 2016 a replica DC but not yet migrate FSMO roles and keep it that way as long as you wish. The trigger for the 21 days is when you move the FSMO roles to the new DC.
...at what point in the process ie: at what step in the tutorial, does one have to simply power through and get the migration finished else users will be left without an active server?
Really, there is no such point. I would relax and take your time. Best part of the migration is probably the way I migrate files and folders with DFSR. You create the replication partners and walk away...it sits in the background and does the work for you.
I would always take enough time. Specially when this is new for you. Don't rush anything and if you don't know ask me!
Easy to use migration kit
Migration kit for migrating from one source (for example SBS
2011) to a new Windows Server environment built on the latest technology.
This kit is ideal if you want to perform the migration of your old
server yourself. The kit contains everything to ultimately run your
infrastructure on more modern operating systems like Windows Server
2016/2019, Exchange Server 2016/2019 or Office 365. Success guaranteed!
IT pro collection for IT consultants and
engineers
The migration kit that you are currently viewing is part of the
IT Pro Collection. The IT Pro Collections contain all migration
kits that we have written. See
here
for an overview of all migration kits and manuals. If you perform
multiple migrations for clients, you are an IT Consultant, the IT
Pro Collections are the most obvious choice. Success guaranteed!
All our migration kits and IT Pro Collections are backed with awesome
support. In our store, you can choose to purchase support as part of
your initial purchase or you can get ad hoc support by creating a support
ticket
here. Don't
want to do it yourself? Migration support is also available through
consulting service,
contact us.
answered 01/25/2018 12:56