Export (0) Print
Expand All

Move Windows SBS 2003 settings and data to the Destination Server for Windows Server 2012 Essentials migration

Published: July 9, 2012

Updated: March 1, 2013

Applies To: Windows Server 2012 Essentials

Move settings and data to the Destination Server as follows:

  1. Copy data to the Destination Server

  2. Import Active Directory user accounts to the Windows Server 2012 Essentials Dashboard (optional)

  3. Remove old logon scripts (optional)

  4. Remove legacy Active Directory Group Policy Objects (optional)

  5. Configure the network

  6. Map permitted computers to user accounts

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.

  1. Log on to the Destination Server as a domain administrator.

  2. Click Start, type cmd in the search box, and then press ENTER.

  3. 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, and <SharedDestinationFolderName> is the shared folder on the Destination Server to which the data will be copied.

  4. Repeat the previous step for each shared folder that you are migrating from the Source Server.

By default, all user accounts created on the Source Server are automatically migrated to the Dashboard in Windows Server 2012 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.

  1. Log on to the Destination Server as a domain administrator.

  2. Open Windows PowerShell as an administrator.

  3. 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]

Windows SBS 2003 uses logon scripts for tasks such as installing software and customizing desktops. Windows Server 2012 Essentials replaces the Windows SBS 2003 logon scripts with a combination of logon scripts and Group Policy Objects.

noteNote
If you modified the Windows SBS 2003 logon scripts, you should rename the scripts to preserve your customizations.

noteNote
Windows SBS 2003 logon scripts apply only to user accounts that were added by using the Add New Users Wizard.

  1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.

  2. In Active Directory Users and Computers, Expand your network, and then click Users.

  3. Right-click a user name, click Properties, and then click the Profile tab.

  4. Delete the contents of the Logon script text box, and then click OK.

  5. Repeat steps 3 and 4 for each user.

The Group Policy Objects (GPOs) are updated for Windows Server 2012 Essentials. They are a superset of the Windows SBS 2003 GPOs. For Windows Server 2012 Essentials, a number of the Windows SBS 2003 GPOs and Windows Management Instrumentation (WMI) filters must be manually deleted to prevent conflicts with the Windows Server 2012 Essentials GPOs and WMI filters.

noteNote
If you modified the original Windows SBS 2003 Group Policy Objects, you should save copies of them in a different location, and then delete them from Windows SBS 2003.

  1. Log on to the Source Server with an administrator account.

  2. Click Start, and then click Server Management.

  3. In the navigation pane, click Advanced Management, click Group Policy Management, and then click Forest:<YourDomainName>.

  4. Click Domains, click <YourDomainName>, and then click Group Policy Objects.

  5. Right-click Small Business Server Auditing Policy, click Delete, and then click OK.

  6. Repeat step 5 to delete the following GPOs that apply to your network:

    • Small Business Server Client Computer

    • Small Business Server Domain Password Policy

      We recommend you configure the password policy in Windows Server 2012 Essentials to enforce strong passwords. To configure the password policy, use the Dashboard, which writes the configuration to the default domain policy. The password policy configuration is not written to the Small Business Server Domain Password Policy Object, like it was in Windows SBS 2003.

    • Small Business Server Internet Connection Firewall

    • Small Business Server Lockout Policy

    • Small Business Server Remote Assistance Policy

    • Small Business Server Windows Firewall

    • Small Business Server Update Services Client Computer Policy

      This GPO will be present if you are migrating from Windows SBS 2003 R2.

    • Small Business Server Update Services Common Settings Policy

      This GPO will be present if you are migrating from Windows SBS 2003 R2.

    • Small Business Server Update Services Server Computer Policy

      This GPO will be present if you are migrating from Windows SBS 2003 R2.

  7. Confirm that all of the GPOs are deleted.

  1. Log on to the Source Server with an administrator account.

  2. Click Start, and then click Server Management.

  3. In the navigation pane, click Advanced Management, click Group Policy Management, and then click Forest:<YourNetworkDomainName>

  4. Click Domains, click <YourNetworkDomainName>, and then click WMI Filters.

  5. Right-click PostSP2, click Delete, and then click Yes.

  6. Right-click PreSP2, click Delete, and then click Yes.

  7. Confirm that these three WMI filters are deleted.

  1. On the Destination Server, open the Dashboard.

  2. On the Dashboard Home page, click SETUP, click Set up Anywhere Access, and then choose the Click to configure Anywhere Access option.

  3. Follow the instructions in the Set up Anywhere Access wizard to configure your router and domain name.

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

noteNote
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.

In Windows SBS 2003, 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 2012 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 SBS 2003 must be mapped to one or more computers.

  1. On the Destination Server, open the Windows Server 2012 Essentials Dashboard.

  2. In the navigation bar, click Users.

  3. In the list of user accounts, right-click a user account, and then click View the account properties.

  4. Click the Anywhere Access tab, and then click Allow Remote Web Access and access to web services applications..

  5. Click Shared Folders, click Computers, click Homepage links, and then click Apply.

  6. Click the Computer access tab, and click the name of the computer to which you want to allow access.

  7. Repeat steps 3, 4, 5, and 6 for each user account.

noteNote
You do not need to change the configuration of the client computer. It is configured automatically.

noteNote
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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft