{"id":62024,"date":"2020-07-30T13:07:43","date_gmt":"2020-07-30T13:07:43","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=62024"},"modified":"2025-11-27T05:11:54","modified_gmt":"2025-11-27T05:11:54","slug":"migrate-sbs-2011-server-2016","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/migrate-sbs-2011-server-2016\/","title":{"rendered":"How to Migrate SBS 2011 to Server 2016 (Exchange 2016)?"},"content":{"rendered":"

SBS 2011 migration to a new server, such as Windows server 2016, requires you to prepare the SBS 2011 and new server 2016 for migration. Assuming you already have created and set up the new server 2016, you can proceed and migrate everything, such as Domain Controller (DC), DNS, AD, files, folders, DHCP, users, shares, security groups, and permissions from SBS 2011 to Windows Server 2016. That too, without any loss of data or need to re-create user profiles.<\/p>

Steps to Migrate SBS 2011 to Windows Server 2016<\/h2>

Below, we have discussed all the steps to migrate SBS 2011 with Exchange 2010 to Exchange 2016 on the new Windows server 2016 & also mentioned the steps to migrate mailboxes by using the Exchange Management Shell (EMS), Exchange Admin Center (EAC), or by using Exchange Migration tool such as Stellar Migrator for Exchange. <\/strong>It helps avoid the risk of data loss during mailbox migration from SBS 2011 to Server 2016.<\/p>

Step 1: Prepare SBS 2011 for Migration<\/h3>

First, check the SBS 2011 server and spend some time to find out anything that might cause a problem during the migration. After that start with a System State backup by opening the command prompt as administrator and then entering the following command,<\/p>

wbadmin start systemstatebackup –backuptarget:=D:<\/code><\/pre>
D is the external drive letter.<\/p>
When prompted, type Y<\/strong> and press ‘Enter’. This may take a while to complete. A backup will help you restore the server in case something goes wrong during the migration process.<\/p>
Step 2: Raise SBS Domain Functional Level<\/h3>
Next, you need to migrate the SYSVOL replication from NTFRS to DFSR. For more details, visit this Microsoft page<\/a>.<\/p>
Then by using the following command in Command Prompt, you need to find the current Global state,<\/p>
dfsrmig \/getglobalstate<\/code><\/pre>
The command is used to check the global state. Use the following command to begin,<\/p>
dfsrmig \/setglobalstate 1<\/code><\/pre>
After a minute or two, execute the following command again,<\/p>
dfsrmig \/getglobalstate<\/code><\/pre>
If it displays the Current DFSR global state: ‘Prepared’, execute the following command,<\/p>
dfsrmig \/setglobalstate 2<\/code><\/pre>
And then check the status with,<\/p>
dfsrmig \/getglobalstate<\/code><\/pre>
If it displays the global state as ‘Redirected’, then run this command to check the status of the migration,<\/p>
dfsrmig \/getmigrationstate<\/code><\/pre>
If the output displays, “Migration has reached a consistent state on all Domain Controllers<\/em>,” it indicates everything has worked, as it should be. Finally, run the following command to complete the SBS preparation for migration.<\/p>
dfsrmig \/setglobalstate 3<\/code><\/pre>
Step 3: Install Server 2016 and Join the Domain<\/h3>
Now that we have prepared SBS 2011 for migration, it is time to prepare the new Windows Server 2016 to start the migration process.<\/p>
Step 4: Promote Exchange Server 2016 as Domain Controller<\/h3>
Now, you need to promote the Server 2016 as Domain Controller (DC). To do so, you can use the following PowerShell commands,<\/p>
$currentDomain = Read-Host -Prompt \"Enter your internal domain name:\"<\/code><\/pre>
$cred = Get-Credential -Message \"Enter Domain Administrator Credential.\"<\/code><\/pre>
Install-ADDSDomainController -NoGlobalCatalog:$false -CreateDnsDelegation:$false -CriticalReplicationOnly:$false -DatabasePath \"C:\\Windows\\NTDS\" -DomainName $currentDomain -InstallDns:$true -LogPath \"C:\\Windows\\NTDS\" -NoRebootOnCompletion:$true -SysvolPath \"C:\\Windows\\SYSVOL\" -credential $cred -Force:$true -Confirm:$false -SafeModeAdministratorPassword (ConvertTo-SecureString 'ntADRSM0deP@ssword!!' -AsPlainText -Force)<\/code><\/pre>
You will see a prompt where you must enter the internal domain name and credentials to finish the task.<\/p>
\n
NOTE:<\/em><\/strong> Do not transfer the FSMO roles right now. We will do that later.<\/em><\/p>\n<\/blockquote>
Step 5: Install Required Additional Roles and Features<\/h3>
Now you need to install the following roles to run on Server 2016 DC.<\/p>