[Today's post comes to us courtesy of Chris Puckett, John Bay and Damian Leibaschoff from Commercial Technical Support]
The purpose of this post is to help you complete your Windows/SBS 2003/SBS 2008 migrations to SBS 2011 Standard successfully on the first attempt. Furthermore, on subsequent posts we will cover documentation and tips to help you recover if you have encountered an issue.
If you are already experiencing a setup failure, please check the post-setup with failures section in our third post of this series SBS 2011 Standard Migration – Keys to Success – Part 3: Post Setup and Common Failures for further troubleshooting information first.
The content on this blog extends on content found here: Prepare your Source Server for Windows SBS 2011 Standard migration .
An older version of this post can be found in: http://blogs.technet.com/b/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-suc...
Understand what setup will do for you and what you need to do manually. Leverage the TechNet Migration Center .
You might find an answer to a question you have, seek advice on your migration plan, or simply see what others have encountered that you might not have considered.
This way you know what to expect. This also allows you to test the hardware and verify you have the necessary BIOS updates and drivers.
The Exchange Pre-Deployment Analyzer performs an overall topology readiness scan of your environment and provides you with a list of decisions that need to be made before you deploy Exchange Server 2010.
If there is only one DC, make sure the SYSVOL and NETLOGON shares are present. Also, check the File Replication Service event log to see if it is in Journal Wrap. The event below is an example of what to look for.
Event Type: Error
Event Source: NtFrs
Event ID: 13568
Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
If there are multiple domain controllers in the source environment, force an Active Directory replication between them in Active Directory Sites and Services and verify it is successful.
You can also run the Microsoft IT Environment Health Scanner in the source environment to uncover any AD health issues.
An unhealthy Active Directory can result in an SBS 2011 Standard migration installation failure .
Make sure the Primary group is set to something besides Domain Admins, Enterprise Admins, or Schema Admins. In the properties of the user account, click the Member Of tab, and at the bottom look for the Primary group.
Strong passwords must meet the following minimum requirements:
SBS 2011, like SBS 2008, only supports a Class C Subnet. If your SBS 2003 server is not in a Class C subnet, it can cause communication problems during SBS 2011 Standard migration setup. Please see the following post for supported network topologies in SBS 2008, this applies to SBS 2011 Std.
SBS setup tries to create a Distribution List with the SAM account name of Postmaster. If it already exists on your non-SBS or SBS 2003 source server, you need to rename it on the source server before the migration begins. This should not be very common but some third party anti-spam solutions may configure an account with that name.
If you have Exchange 2003 or Exchange 2000 recipient policies that are ONLY Mailbox Manager policies and do not define e-mail addresses (they do not have an E-mail Addresses (Policy) tab), perform the following steps to delete the policies:
If you have Exchange 2003 or Exchange 2000 policies that are BOTH E-mail Addresses and Mailbox Manager policies (they have both the Mailbox Manager Settings (Policy) tab and the E-mail Addresses (Policy) tab), perform the following steps to remove the mailbox manager portion of the policy:
If you have a deadline set for a Windows 2008 R2 update in WSUS that is past-due, your SBS 2011 Standard setup can fail when the update is automatically installed and the SBS 2011 server is rebooted. Deadlines are not automatically set in SBS 2003 nor SBS 2008 but can be set by the Admin through the native WSUS console. We recommend disabling WSUS on the source server for the duration of the migration. For this, on the source server, open IIS Manager, and stop the “ WSUS Administration ” site
Similar to the point above, your SBS 2011 Standard setup can fail if something outside of it initiates a server restart while it’s in the middle of its setup routine. Things to keep an eye out for:
If the source server is SBS 2003 or 2008, the MyBusiness OU needs to be present and contain the expected sub-containers. To verify:
This tool performs the following actions:
Always select the option to get updates upon launching this tool to make sure you are getting the latest set of health check rules.
2481235 List of rules for the Windows Small Business Server Migration Preparation Tool
2542156 SBS 2011 Standard Edition Source Tool Scan Fails
For Windows/SBS 2003:
For Windows/SBS 2008:
From now until the SBS 2011 Standard migration setup is complete, do not make any changes on the network. This is not a good time to be doing any of the following:
Time zone of Hyper-V host: _________________________________
When installing SBS 2011 Standard as a Hyper-V guest, make sure to set the time zone to the one you noted in the field above.
Expand Forest, Domains, your domain, Domain Controllers, and select the Default Domain Controllers Policy.
Click on the Settings tab and expand Computer Configuration, Policies, Windows Settings, Security Settings, Local Policies/User Rights Assignment
Find the "Log on as batch job" right, and make sure that you have an entry for BULTIN\Administrators
If you don't have that entry, do a right-click edit on top of the policy on the left pane, navigate to the location you just checked and edit the right to add the missing value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.