[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
Second Part: SBS 2011 Standard Migrations – Keys to Success – Part 2: The Setup Phase

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.

A. Disabling IPv6 is not necessary in SBS 2011 Standard

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.

B. Run the Migration Wizard.

Link to the Migration Wizard TechNet Documents for SBS 2003 to SBS 2011 Standard.
http://technet.microsoft.com/en-us/library/gg563798.aspx

Link to the Migration Wizard TechNet Documents for SBS 2008 to SBS 2011 Standard.
http://technet.microsoft.com/en-us/library/gg615497.aspx

If you are migrating from a non-SBS source, you will have to follow the migration document steps manually without the migration wizard.

C. Troubleshooting Moving Public Folder Replicas

http://blogs.technet.com/b/sbs/archive/2009/06/21/sbs-migrations-troubleshooting-moving-public-folder-replicas.aspx

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:
http://blogs.technet.com/b/exchange/archive/2010/05/05/3409916.aspx
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).

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

E. Install the latest critical and security updates on the new server

Including:
Windows Server 2008 R2 Service Pack 1.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=C3202CE6-4056-4059-8A1B-3A9B77CDFDDA

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
http://support.microsoft.com/default.aspx?scid=kb;en-US;2401588

F. On the SBS 2011 server, after setup is done, download and install the Windows Server Solutions Best Practices Analyzer.

G. Don’t forget to clean up old Group Policy Objects.

http://technet.microsoft.com/en-us/library/gg563794.aspx
http://technet.microsoft.com/en-us/library/gg563807.aspx

H. Check other content in the SBS Blog for other helpful information around SBS 2011 Standard

I. Check the known post installation issues:

Windows SBS 2011 Standard Known Post Installation Event Log Errors and Warnings
http://support.microsoft.com/kb/2483007

POST SETUP WITH FAILURES

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.

Common setup failures:

  • Primary Failing Task: InstallExchangeTask
    Key Error or Exception from the Log:
    Task: InstallExchangeTask: Exchange setup failed with error.
    Most Common Cause:
    See Resolution Summary
    Resolution Summary:
    Read the following article for details on causes and how to complete the setup:
    Exchange Server 2010 incorrectly changes to evaluation mode after you reinstall or repair Exchange Server 2010 in Windows SBS 2011 Standard
    http://support.microsoft.com/kb/2527626

 

  • Primary Failing Task: DcPromo_JoinDomain or DcPromo
    Key Error or Exception from the Log:
    Setup: Task DcPromo_JoinDomain failed
    Most Common Cause:
    See Resolution Summary
    Resolution Summary:
    Read the following article for details on causes and how to complete the setup:
    Completing the SBS 2011 Standard setup after a failure during the promotion to a domain controller
    http://support.microsoft.com/kb/2536941

 

  • Primary Failing Task: ConfigureSharePointTask (setup will crash with Windows SBS 2011 Setup has stopped working)
    Key Error or Exception from the Log:
    TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureSharePointTask" Task
    threw an Exception during the Run()
    call:Microsoft.WindowsServerSolutions.Common.IWorker.IISConfig.IISConfigException:
    IIS Server Administration threw an exception. See inner exception for details.
    ---> System.IO.FileLoadException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
    Error: Cannot commit configuration changes because the file has changed on disk
    Most Common Cause:
    This is a timing issue in the SBS setup. See Resolution Summary for details.
    Resolution Summary:
    Read the following article for details on how to recover from this error:
    SBS 2011 Standard Edition Setup Crashes Unexpectedly
    http://support.microsoft.com/kb/2535810

 

  • Primary Failing Task: ConfigureWSSOutgoingEmailTask
    Key Error or Exception from the Log:
    [10156] 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).
    Resolution Summary:
    There is no supported way to continue setup, the source server would need to be restored, the issue corrected and the setup re-attempted.

 

  • Primary Failing Task: None - Last task in log  MUPhase2Task
    Key Error or Exception from the Log:
    [4668] 110228.205025.4092: Task: Task ("MUPhase2Task") execution complete.
    [4668] 110228.205025.4092: TaskManagement: Exiting ProgressManager.UpdateProgress(100), not updating since the task is complete.
    [4668] 110228.205025.4172: TaskManagement: Previous Task required us to stop processing Tasks for a restart, failure, or cancel.
    [4668] 110228.205025.5842: TaskManagement: A Reboot was required. Now=True,Finished=False,Redo=True
    [4668] 110228.205025.5852: Setup: TME needs a reboot: bTMEHasMoreToDo=True bPrepareOnly=False
    [4668] 110228.205025.5852: Setup: Setting RebootPendingValue to true.
    [4668] 110228.205025.5852: Setup: Back from running the TME
    [4668] 110228.205025.5872: Setup: Setting ResultFile value to C:\Program Files\Windows Small Business Server\Data\TME\Results\TaskStatusResults634345230254462706.xml
    [4668] 110228.205025.5942: Wizard: Admin:QueryNextPage(sbssetup.mainprogress) = null
    [4208] 110228.205025.6052: Wizard: WizardChainEngine Next Clicked: Last page, so the wizard isdone, closing wizard frame and returning
    [4208] 110228.205025.6112: Setup: Setting ShowBillboards to False
    [4208] 110228.205025.6262: Wizard: sbssetup.mainprogress exited with the button: Next
    [4208] 110228.205025.6272: Wizard: TOC sbssetup.finish is NO longer on ExpectedPath
    [4208] 110228.205025.7533: Setup: We are back from the wizard after user clicked Next.
    [4208] 110228.205025.7533: Setup: Get Stage = <null>
    [4208] 110228.205025.7533: Setup: We have a reboot pending.
    [4208] 110228.205025.7553: Setup: Rebooting the box.
    [4208] 110228.205025.7653: Setup: service SPAdminV4 is stopped correctly
    [4208] 110228.205025.7923: Setup: service SPTimerV4 is stopped correctly
    [4208] 110228.205025.8923: Setup: service SPTraceV4 is stopped correctly
    [4208] 110228.205025.8933: Setup: service SPUserCodeV4 is stopped correctly
    [4208] 110228.205026.0283: Setup: service SPWriterV4 is stopped correctly
    [4208] 110228.205026.2553: Setup: service SPSearch4 is stopped correctly
    Most Common Cause:
    The server went for the reboot but the setup never resumed. This can happen due to some source environment conditions and a timing issue during the setup during certain installs. Once it happens, the setup is not completed and steps are required to finish it. This assumes that all setup tasks that have completed up until this point have worked.
    Resolution Summary:
    To complete the setup, follow the instructions on this article:
    The SBS 2008 or 2011 Standard Migration Wizard may fail to launch due to an incomplete setup
    http://support.microsoft.com/kb/2533423

 

  • Primary Failing Task: ConfigureIISTask and ConfigureWSSOutgoingEmailTask
    Key Error or Exception from the Log:
    CoreNet: Using WMI QueryString: Select * From MicrosoftDNS_Zone Where Name="contoso.com"
    [4464] 110802.002431.0928: IISConfigLib: could not get dns zone, retrying: 2
    [4464] 110802.002432.1207: Task: There was an error while configuring IIS. Here are the exception details: Microsoft.WindowsServerSolutions.Common.IWorker.IISConfig.IISConfigException: Could not find dns zone for the domain
       at Microsoft.WindowsServerSolutions.Common.IWorker.IISConfig.CIisConfigLib.GetSpecificZoneWithRetry(String zoneName)
       at Microsoft.WindowsServerSolutions.Common.IWorker.IISConfig.CIisConfigLib.CreateDnsRecord(String nameToRegister)
       at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureIISTask.Run(ITaskDataLink DataLink)

    [..]

    TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureWSSOutgoingEmailTask" Task threw an Exception during the Run() call:System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureWSSOutgoingEmailTask.AddOutboundSmtpDnsRecord()
       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:
    We've failed to find the DNS zone for the domain using WMI on the new server. The most common reason for this is that the zone on the source server is not configured as AD Integrated, and as such it does not automatically replicate to the new server as part of the process of joining the domain.
    Resolution Summary:
    There is no supported way to continue setup, the source server would need to be restored, the issue corrected and the setup re-attempted.

 

Catalog of setup errors:
Catalog of Windows Small Business Server 2011 Standard Error Messages
http://technet.microsoft.com/en-us/library/gg508783.aspx

For help troubleshooting other setup failures, please check the following post (most sections are relevant to SBS 2011 Std):
http://blogs.technet.com/b/sbs/archive/2010/08/03/the-ultimate-guide-to-sbs-2008-setup-failures.aspx