SBS 2003 to SBS 2011 Migration Issues
**SBS 2003 to SBS 2011 migration issues that you can call 1-800-Microsoft (or your local Microsoft support) and will get support and hotfixes included at no charge.
**
There are certain migration issues that can be fixed by calling into Microsoft Support. Because these are known issues they will not be charged.
Windows Small Business Server group policies cannot be configured.:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2645313
You will see the following in your setup log:
The SBSsetup.log that is located at c:\program files\windows small business server\logs will display the following error:
111205.091758.3837: Task: Running Task(ConfigureGP) with Type(Microsoft.WindowsServerSolutions.ClientDeployment.Tasks.GPOTask) and Assembly(ClientTasks.dll).
[4944] 111205.091758.4472: Task: Beginning of task ClientDeployment.GPOTask
[4944] 111205.091758.4677: Task: no Subkey
[4944] 111205.091758.4736: Task: no Subkey
[4944] 111205.091801.1181: Task: ClientDeployment.GPOTask failed with C:\Program Files\Windows Small Business Server\Bin\GPOTask.exe /config:C:\Users\administrator.JOHNBAY-MIG\AppData\Local\Temp\tmpAE02.tmp
[4944] 111205.091801.1191: Task: Finish of task ClientDeployment.GPOTask
[4944] 111205.091801.1191: Task: In Task ConfigureGP: Windows Small Business Server group policies cannot be configured.
[4944] 111205.091801.1201: Setup: Task ConfigureGP failed.
Small Business Server setup attempts to create several group policies. The setup tries to create the polices on the SBS 2011 server. If the sysvol folder is not shared on the SBS 2011 server then the polciy creation tasks will fail. The issue will occur if during the installation process, you receive a pop up message indicating that Active Directory Replication is taking longer than expected and you choose to not wait.
The SBS 2008 or 2011 Standard Migration Wizard may fail to launch due to an incomplete setup:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2533423
After running the SBS 2008 or 2011 Standard setup in join domain/migration mode, you launch the Migration Wizard (“Migrate to Windows SBS” link in the console) and the wizard crashes.
The MigrationWizard.log in “c:\program files\Windows Small Business Server\Logs” will have content similar to this:
Setup: Unhandled exception: System.TypeInitializationException: The type initializer for 'Microsoft.WindowsServerSolutions.Setup.MigrationWizard.SystemData' threw an exception. ---> System.Collections.Generic.KeyNotFoundException: StringKeyDictionary missing key: 'JoinDomainServer'.
at Microsoft.WindowsServerSolutions.Common.StringKeyDictionary`1.get_Item(String key)
at Microsoft.WindowsServerSolutions.Setup.MigrationWizard.SystemData.ReadSourceServerName()
at Microsoft.WindowsServerSolutions.Setup.MigrationWizard.SystemData..ctor()
at Microsoft.WindowsServerSolutions.Setup.MigrationWizard.SystemData..cctor()
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Setup.MigrationWizard.Program.Main()
Due to a timing condition, the SBS Setup may not resume after the server restarts following the installation of updates. Once that happens, the server boots into a desktop and no errors are displayed. The server seems to be functional although a number of configuration tasks are missing.
If you try the install again, you may not see this another time. It can be due to saying yes to updates (so don't say yes during the install).
Contact Microsoft for a script to complete the install.
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/default.aspx?scid=kb;en-us;2527626
This one occurs for various reasons. I've seen permission errors in the mail store cause Exchange not to install and then someone fixes the permissions and then manually installs Exchange. But by doing so, you will find that it's not activated and is in eval mode. If you end up in this condition, follow that KB.
SBS 2011 Standard Edition Setup Crashes Unexpectedly:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2535810
Due to a timing condition, the SBS Setup may not resume after the server restarts following the installation of updates. Once that happens, the server boots into a desktop and no errors are displayed. The server seems to be functional although a number of configuration tasks are missing.
If you try the install again, you may not see this another time. It can be due to saying yes to updates (so don't say yes during the install).
The sbssetup.log file that is located at c:\program files\windows small business server\logs will contain the following error:
[4624] 110318.160407.0793: 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
If you don't want to start over, you can call 1-800-Microsoft for a script to complete the install.
SBS 2011 Migration Installation May Crash Because of User Rights:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2643832
4728] 111109.222532.5628: Task: Running Task(ConfigureSharePointDatabaseTask) with Type(Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointDatabaseTask) and Assembly(IWorkerConfig.dll).
[4728] 111109.222532.8724: TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureSharePointDatabaseTask" 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)
The setup process runs a task named ConfigureSharePointDatabaseTask that is responsible for configuring SharePoint on the SBS 2011 server. The task runs using a COM+ application named WSSCONFIG. The WSSCONFIG application runs under the security context of the account used for the migration. The account must have the logon as a Batch security privilege. If the migration account does not have the logon as a batch security right or has been denied logon as a batch the task will fail and SBS setup will crash.
This occurs because your com+ permissions are incorrect. If you end up this condition, call Microsoft for a hotfix to put you back into proper migration path.
For other support issues not listed above please review
http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx and http://blogs.technet.com/b/sbs/archive/2011/07/11/sbs-2011-standard-migration-keys-to-success-part-3-post-setup-and-common-failures.aspx and http://blogs.technet.com/b/sbs/archive/2010/08/03/the-ultimate-guide-to-sbs-2008-setup-failures.aspx
and post in the SBS forum - http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/threads