[Today’s post comes to us courtesy of Chris Puckett, John Bay and Damian Leibaschoff from Commercial Technical Support]
First Part: SBS 2011 Standard Migrations – Keys to Success
This is the second post of the series. During the actual setup of the SBS 2011 Standard server you may encounter a number of situations that can be prevented or addressed on the fly. This post tries to cover them and provide viable options to allow the setup to continue.
If you are already experiencing a setup failure, please check the post-setup with failures section in our third post of this series for further troubleshooting information first.
The SBS setup will try to disable them automatically but it might not work on all cases, so ideally disable them from the BIOS before starting the process.
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:
· Changing passwords
· Installing Software
· Removing Domain Controllers
· Changing out the network hardware
· Restoring servers
· Rebooting domain controllers
· Re-wiring the network
You may get an error “Verify that the Source Server Name is Correct” while trying to install SBS into an existing domain
· Check for Time Mismatch (Date, Time and Time Zone) on both source and new server.
· Check DCOM setting on the source server (Use DcomCnfg.msc)
· Check the Credentials being used.
Active Directory replication is taking longer than expected. You can choose whether to continue waiting.
If you choose not to wait, the migration may fail. Unless you are sure that replication is working correctly, it is recommended that you continue waiting.
Do you want to wait for the replication to finish? (Yes/No)
Most Common Cause:
You will only get this dialog after the SBS setup has waited for 25 minutes and the new server has not been able to properly contact the source DC to initialize the file replication service (FRS), this is preventing the new server from becoming a domain controller. Clicking No on this dialog will almost certainly mean a failed setup. The source server is most likely in journal wrap or having FRS issues.
Correct the FRS issues on the source server, do not reboot the new server or close down the setup, leave the popup dialog open while you troubleshoot, once the FRS issues are corrected on the source server, you can open a command prompt on the new server by using Shift-F10 and restart the Netlogon and FRS services, then confirm that SYSVOL and NETLOGON are shared on the new server by using NET SHARE, only then you should click Yes to continue waiting, after 5 minutes the setup will go on.