Move Windows SBS 2011 Standard settings and data to the Destination Server for Windows Server Essentials migration
Applies To: Windows Server 2016 Essentials, Windows Server 2012 R2 Essentials, Windows Server 2012 Essentials
Move settings and data to the Destination Server as follows:
Import Active Directory user accounts to the Windows Server Essentials Dashboard (optional)
Move the DHCP Server role from the Source Server to the router
Remove legacy Active Directory Group Policy objects (optional)
Copy data to the Destination Server
Before you copy data from the Source Server to the Destination Server, perform the following tasks:
Review the list of shared folders on the Source Server, including permissions for each folder. Create or customize the folders on the Destination Server to match the folder structure that you are migrating from the Source Server.
Review the size of each folder and ensure that the Destination Server has enough storage space.
Make the shared folders on the Source Server Read-only for all users so no writing can take place on the drive while you are copying files to the Destination Server.
To copy data from the Source Server to the Destination Server
Log on to the Destination Server as a domain administrator, and then open a command window.
At the command prompt, type the following command, and then press ENTER:
robocopy \\<SourceServerName> \<SharedSourceFolderName> \\<DestinationServerName> \<SharedDestinationFolderName> /E /B /COPY:DATSOU /LOG:C:\Copyresults.txt
Where:
- <SourceServerName> is the name of the Source Server
- <SharedSourceFolderName> is the name of the shared folder on the Source Server
- <DestinationServerName> is the name of the Destination Server,
- <SharedDestinationFolderName> is the shared folder on the Destination Server to which the data will be copied.
- Repeat the previous step for each shared folder that you are migrating from the Source Server.
Import Active Directory user accounts to the Windows Server Essentials Dashboard
By default, all user accounts created on the Source Server are automatically migrated to the Dashboard in Windows Server Essentials. However, automatic migration of an Active Directory user account will fail if some properties do not meet migration requirements. You can use the following Windows PowerShell cmdlet to import Active Directory users.
To import an Active Directory user account to the Windows Server Essentials Dashboard
Log on to the Destination Server as a domain administrator.
Open Windows PowerShell as an administrator.
Run the following cmdlet, where
[AD username]
is the name of the Active Directory user account that you want to import:
Import-WssUser SamAccountName [AD username]
Move the DHCP Server role from the Source Server to the router
If your Source Server is running the DHCP role, perform the following steps to move the DHCP role to the router.
To move the DHCP role from the Source Server to the router
Turn off the DHCP service on the Source Server, as follows:
On the Source Server, click Start, click Administrative Tools, and then click Services.
In the list of currently running services, right-click DHCP Server, and then click Properties.
For Start type, select Disabled.
Stop the service.
Turn on the DHCP Role on your router.
Follow the instructions in your router documentation to turn on the DHCP role on the router.
To ensure that IP addresses issued by the Source Server remain the same, follow the instructions in your router documentation to configure the DHCP range on the router to be the same as the DHCP range on the Source Server.
Important
If you have not set up a static IP or DHCP reservations on the router for the Destination Server, and the DHCP range is not the same as the Source Server, it is possible that the router will issue a new IP address for Destination Server. If this happens, reset the port forwarding rules of the router to forward to the new IP address of the Destination Server.
Configure the network
After you move the DHCP role to the router, configure the network settings on the Destination Server.
To configure the network
On the Destination Server, open the Dashboard.
On the Home page, click SETUP, click Set up Anywhere Access, and then choose the Click to configure Anywhere Access option.
Complete the instructions in the wizard to configure your router and domain names.
If your router does not support the UPnP framework, or if the UPnP framework is disabled, a yellow warning icon may appear next to the router name. Ensure that the following ports are open and that they are directed to the IP address of the Destination Server:
Port 80: HTTP Web traffic
Port 443: HTTPS Web traffic
Note
If you have set up an on-premises Exchange server on a second server, you must ensure port 25 (for SMTP) is also open and that it is redirected to the IP address of the on-premises Exchange server.
Remove legacy Active Directory Group Policy Objects
The Group Policy Objects (GPOs) are updated for Windows Server Essentials. They are a superset of the Windows Small Business Server 2011 GPOs. For Windows Server Essentials, a number of the Windows Small Business Server 2011 GPOs and Windows Management Instrumentation (WMI) filters must be manually deleted to prevent conflicts with the Windows Server Essentials GPOs and WMI filters.
Note
If you modified the original Windows Small Business Server 2011 Group Policy Objects, you should save copies of them in a different location, and then delete them from Windows Small Business Server 2011.
To remove old Group Policy Objects from Windows Small Business Server 2011
Log on to the Source Server with an administrator account.
Click Start, and then click Server Management.
In the navigation pane, click Advanced Management, click Group Policy Management, and then click Forest:<YourDomainName>.
Click Domains, click <YourDomainName>, and then click Group Policy Objects.
Right-click Small Business Server Auditing Policy, click Delete, and then click OK.
Repeat step 5 to delete the following GPOs that apply to your network:
Windows SBS Client Windows 7 and Windows Vista Policy
Windows SBS Client Windows XP Policy
Windows SBS CSE Policy
Windows SBS User Policy
Update Services Client Computer Policy
Update Services Common Settings Policy
Update Services Server Computer Policy
- Confirm that all of the GPOs are deleted.
To remove WMI filters from the Source Server
Log on to the Source Server with an administrator account.
Click Start, and then click Server Management.
In the navigation pane, click Features, click Group Policy Management, and then click Forest:<YourNetworkDomainName>
Click Domains, click <YourNetworkDomainName>, and then click WMI Filters.
Right-click Windows SBS Client, click Delete, and then click Yes.
Right-click Windows SBS Client Windows 7 and Windows Vista, click Delete, and then click Yes.
Right-click Windows SBS Client Windows XP, click Delete, and then click Yes.
Confirm that these three WMI filters are deleted.
Map permitted computers to user accounts
In Windows Small Business Server 2011, if a user connects to Remote Web Access, all the computers in the network are displayed. This may include computers that the user does not have permission to access. In Windows Server Essentials, a user must be explicitly assigned to a computer for it to be displayed in Remote Web Access. Each user account that is migrated from Windows Small Business Server 2011 must be mapped to one or more computers.
To map user accounts to computers
Open the Windows Server Essentials Dashboard.
In the navigation bar, click Users.
In the list of user accounts, right-click a user account, and then click View the account properties.
Click the Anywhere Access tab, and then click Allow Remote Web Access and access to web services applications.
Select Shared Folders, select Computers, select Homepage links, and then click Apply.
Click the Computer access tab, and then click the name of the computer to which you want to allow access.
Repeat steps 3, 4, 5, and 6 for each user account.
Note
You do not need to change the configuration of the client computer. It is configured automatically.
After you complete the migration, if you encounter an issue when you create the first new user account on the Destination Server, remove the user account that you added, and then create it again.