[Today’s post comes to us courtesy of Chris Puckett, John Bay and Damian Leibaschoff from Commercial Technical Support]
This is the third post of this series and covers common issues that you might encounter after completing the SBS setup. Furthermore, it covers common failures for which you can recover from or identify the root cause to prevent them in the future.
If you think you want to disable IPv6 in SBS 2011 Standard, or any Vista/Windows 2008/Windows7/Windows 2008 R2 product for that matter, you must do so in the registry. Unchecking IPv6 in the properties of the NIC will cause you grief. For more information on how to do this, read here.
Link to the Migration Wizard TechNet Documents for SBS 2003 to SBS 2011 Standard.
Link to the Migration Wizard TechNet Documents for SBS 2008 to SBS 2011 Standard.
If you are migrating from a non-SBS source, you will have to follow the migration document steps manually without the migration wizard.
If you are migrating from SBS 2008 and you had previously migrated from SBS 2003 or had Exchange 2003 in the organization, please check the following post as replication might not work until the legacy servers container is removed:
Please note that this can also cause issues with Mail Enabled Public Folders after a successful migration from SBS 2003 to SBS 2011 Standard. The same resolution should be applied after completing the next step (remove the last legacy exchange server from an organization).
Before you are ready to demote and remove the source SBS 2003 server from the network, make sure you follow the steps to Remove the Last Legacy Exchange Server from an Organization BEFORE you uninstall Exchange 2003 from the SBS 2003 server. The steps are located here.
Before you are ready to demote and remove the source SBS 2008 server from the network, make sure you follow the steps to Uninstall Exchange Server 2007 BEFORE you remove the SBS 2008 server. The steps are located here.
Windows Server 2008 R2 Service Pack 1.
And the following Post-Sp1 hotfix:
2401588 Remote procedure call service crashes on a computer that is running Windows Server 2003 SP2, Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2
Windows SBS 2011 Standard Known Post Installation Event Log Errors and Warnings
It is important to note that most failures are fatal, there are a few scenarios where the SBS setup can be manually completed or resumed. Most setup failures will have a directly correlation with an existing condition on the source domain and if common, should be covered in our previous blog posts on this series. If your failure is not documented here, you will have to restore the source server from backup, correct/isolate the source of the failure, and re-start the process.
· Completing the SBS 2011 Standard setup after a failure during the promotion to a domain controller
· The SBS 2008 or 2011 Standard Migration Wizard may fail to launch due to an incomplete setup
· SBS 2011 Standard Edition Setup Crashes Unexpectedly
· Exchange Server 2010 incorrectly changes to evaluation mode after you reinstall or repair Exchange Server 2010 in Windows SBS 2011 Standard
· Catalog of Windows Small Business Server 2011 Standard Error Messages
· Primary Failing Task: ConfigureWSSOutgoingEmailTask
Key Error or Exception from the Log:
 110707.151411.3108: TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureWSSOutgoingEmailTask" Task threw an Exception during the Run() call:System.Runtime.InteropServices.COMException (0x8000401A): The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.EnterpriseServices.Thunk.Proxy.CoCreateObject(Type serverType, Boolean bQuerySCInfo, Boolean& bIsAnotherProcess, String& uri)
at ystem.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType)
at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object props, Boolean bNewObj)
at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureWSSOutgoingEmailTask.Run(ITaskDataLink dataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink)
at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName)
Most Common Cause:
See item U in http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
Other causes include problems with group policy replication (missing policies on new server).
There is no supported way to continue setup, the source server would need to be restored, the issue corrected and the setup re-attempted.
· For help troubleshooting other setup failures, please check the following post (most sections are relevant to SBS 2011 Std):