Ask a question

0

Migration from SBS2011 to Server 2016 (new hardware) with separate Exchange server on existing hardware

Hi!

I am migrating from an SBS2011 to a new server hardware with server 2016. As it is not supported to migrate the Exchange Server onto the domain controller, I want to (have to) migrate to Exchange 2016 on the existing hardware of the SBS2011, of course after installing server 2016 on this machine. This will result in the loss of the old Exchange 2010 server on SBS before the new machine is active. Going through the SBS to Server 2016 Essential tutorial the Exchange migration is in the middle of the process, however I need to do this at the very end. Is there a problem with this? I am talking about 20 users, so building it up from scratch and restoring the data from pst files is an option. Is there known procedure for this scenario?

Thank you,

Oliver

---

• SBS 2011
• Exchange Server 2016

asked10/29/2018 20:21

87 views

Add Comment

2 Answer(s)

• 

  0

  Hello Oliver,

  The best way to do this is to use the new hardware to virtualize your network. The Windows Server 2016 Standard should be installed on the new hardware with the Hyper-V role added. Once that is done you create a virtual machine for the new domain controller and one for Exchange Server 2016. After that has been done you can start migrating from the old SBS 2011

  ---

  answered 10/30/2018 05:01

  Add Comment

  

  In addition to the above please read this:

  • Demystifying Windows Server 2016 Licensing in the case you are going to use Windows Server 2016 Standard with Hyper-V role for licensing details.
  • If you want to do this for free you should use Try Active Microsoft Hyper-V Server 2016 | Microsoft Evaluation Center. This version of Windows Server 2016 is without a GUI and it is Core, so no user interface. I have written about this here How to install and configure RSAT on Windows 10 and make it a management workstation that connects to a Hyper-V 2016 core server in a workgroup. So, that can be your foundation for your network. More tutorials with the subject Windows Server Essentials support | hyper v

  ---

  Reply

  replied 10/30/2018 05:33

  Your browser doesn't have Flash, Silverlight or HTML5 support.

  Reply Cancel
• 

  0

  Hi Mariette,

  The new DC is already up and running, so I would only use the VM for the Exchange Server on the DC. Do you have any concerns with this approach?

  Thanks

  Oliver 

  ---

  answered 10/30/2018 07:57

  Add Comment

  

  Hello Oliver,

  Not a good idea! You should not run Hyper-V on a Domain Controller. Your only option is to install Hyper-V server on that new hardware and create two virtual machines, one for the domain controller and one for Exchange Server 2016. Sorry for the hassle but that is the way it is.

  

  And if you do not believe me read this 7 Reasons not to Make Hyper-V a Domain Controller

  ---

  replied 10/30/2018 08:17

  

  Hi Mariette,

  Oliver is asking a very similar question to what I'm faced with.  I have new hardware running Server 2016 with the Hyper-V role installed.  We have an old server that has SBS 2011 virtualized and I'm ready to migrate.  I was reading that it's not best practices to run a domain controller in a VM.  Is this accurate? I've had situation in power outages where the host machines go down an it can cause problems if the other servers come online before the SBS 2011 DC comes online.  I was heard it was wise to have the DC as a separate machine.  Any thoughts or recommendations would be greatly appreciated.

  Thanks,

  Aaron

  ---

  replied 05/01/2019 19:46

  ---

  Reply

  replied 10/30/2018 08:10

  Your browser doesn't have Flash, Silverlight or HTML5 support.

  Reply Cancel