Category Archives: Sbsmigration

SBS 2011 migration issues

SBS 2003 to SBS 2011 migration issues – TechNet Articles – Home – TechNet Wiki:
http://social.technet.microsoft.com/wiki/contents/articles/7919.sbs-2003-to-sbs-2011-migration-issues.aspx

The issues noted on this page have scripts that can be obtained for free from Microsoft to complete a migration without having to roll all the way back.


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

Decommissioning a CA on a SBS 2003

How to decommission a Windows enterprise certification authority and how to remove all related objects from Windows Server 2003 and from Windows Server 2000:
http://support.microsoft.com/kb/889250/en-us?sd=rss&spid=1167

If you have a SBS 2003 where you or SOMEONE has added the CA role (as it’s not default), you need to remove it before you demote the SBS 2003 from the network.


Book mark that KB in case you need it.

Completing the SBS 2011 Standard setup after a failure during the promotion to a domain controller:

Completing the SBS 2011 Standard setup after a failure during the promotion to a domain controller:
http://support.microsoft.com/kb/2536941


That KB came out earlier but it’s time to review it again. 


My first advice to anyone doing a SBS migration is to say no to updates during the install.


Repeat after me.


Just SAY NO.


When looking in the DcPromo.log, always search for “[ERROR]” from top to bottom, once you find the line, for example: “04/08/2011 10:19:41 [ERROR] Failed to install to Directory Service (5)”, then concentrate on the error code in the (), on this case 5, which translates to ACCESS_DENIED.


I find that the error logs read best from bottom to top.  The errors normally pop out well from the bottom rather than from the top.  Now in a dcpromo log you won’t have all the logs of updates you did during the install, but the SBSsetup log sure does.

What’s the biggest blocker in migrations?

What’s the biggest blocker in migrations?


Journal wrap.


What is journal wrap?  And why do we care about journal wrap in SBS?  Normally we don’t.  We are a single DC minding our own business and don’t need to replicate with ANYONE. 


http://blogs.technet.com/b/instan/archive/2009/07/14/what-happens-in-a-journal-wrap.aspx


So us little single DCs go along our merry way and because we don’t talk to another DC we don’t need to have our AD journal …or database…fully functional.  As long as we’re not sharing information with another DC we can be DEAD WRONG in our databases and it doesn’t matter….until the date we need to migrate.  Then it matters.  So our single DCs are over in the corner chattering away being DEAD WRONG about the state of affairs.


The impact of this on an affected DC is that FRS will not set the IsSysvolReady registry key to indicate to the Netlogon service that all is well, Sysvol will therefore not be shared out and the DC will not be able to authenticate users fully until the Journal Wrap condition has been resolved.


Now you’d think that with the inability to get to the sysvol folder that our DCs would freak out but amazingly enough they don’t.  You can be in this journal wrap state on a single DC and you won’t see issues with two exceptions.


If you drill down to the NtFrs folder you’ll see an error message….


Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date:  12/25/2007
Time:  2:43:19 PM
User:  N/A
Computer: KIKIBITZFINAL
Description:
The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR.
 
 Replica set name is    : “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
 Replica root path is   : “c:\windows\sysvol\domain”
 Replica root volume is : “\\.\C:”
 A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
 
 [1] Volume “\\.\C:” has been formatted.
 [2] The NTFS USN journal on volume “\\.\C:” has been deleted.
 [3] The NTFS USN journal on volume “\\.\C:” has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
 [4] File Replication Service was not running on this computer for a long time.
 [5] File Replication Service could not keep up with the rate of Disk IO activity on “\\.\C:”.
 Setting the “Enable Journal Wrap Automatic Restore” registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
 [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run “net stop ntfrs” followed by “net start ntfrs” to restart the File Replication Service.
 [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
 
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
Click on Start, Run and type regedit.
 
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
   “System\CurrentControlSet\Services\NtFrs\Parameters”
Double click on the value name
   “Enable Journal Wrap Automatic Restore”
and update the value.  
[to 1]
 
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.


This is the one time you can follow the event error exactly and it will fix your issue (see http://msmvps.com/blogs/bradley/archive/2009/11/27/burflags-and-journal-wrap.aspx for more details.


The second way is running the www.sbsbpa.com and you’ll see it flagged as well



But unless you do either one of the two, the SBS box chugs along just fine….. until along comes either a temp Domain controller (in the case of the www.sbsmigration.com swing to a temp DC method) or in the case of the Microsoft method where you join the SBS 2008 to the domain via the migration install method.  Suddenly that second DC starts talking to the first and the first DC says “I’m right, you need to follow me!”  and the second DC says “Huh?  You are crazy you have no idea what you are talking about, I’m not going to follow you!” and the two refuse to talk to each other… or to use the proper technical terms, they don’t replicate.


So you go to migrate and you don’t.  It’s that simple.  Fix the journal wrap with that registry key and then the SBS 2003 will allow the replication of it’s info to the other DC.


So how do they get into journal wrap condition you ask?  While there are many reasons there’s ONE reason in particular that has probably burned us more than any other issue. 


Running out of room on the C drive.


Every SBS 2003 that you ran out of room on the C drive and lost licenses, probably has a journal wrap problem.


Every SBS 2003 that someone used to print out gobs of color photos and the print spooler would explode and use up all the free room, probably has a journal wrap problem.


Every SBS 2003 that had a small c drive and you got close to running out of room on the C drive, probably has a journal wrap problem.


So think back to every SBS box that ran out of room on the C drive.


Now go run the www.sbsbpa.com on it and fix your journal wrap problem.

Migration from SBS 2003: Planning and source server/domain health check:

Microsoft Advisory Services Engagement Scenario – Migration from SBS 2003: Planning and source server/domain health check:
http://support.microsoft.com/default.aspx?scid=kb;en-us;982905

Now before you read this and freak out that Microsoft advisory services are going to start stepping in between you and your customer and start doing migrations…  read this KB.  See how it’s setting the scope for the MS side of what support incidents you may need/hit… and more importantly what the steps are to ensure a proper healthy AD BEFORE you begin the migration.


Should the customer request assistance with bringing the current environment to a healthy state beyond the time allotted to such task in this offering (60 minutes), separate, break-fix Support Incidents will need to be opened to address each subordinate issue. Further, should any issues arise while performing agreed upon scoped tasks in Migration or New Installation scenarios, a maximum of thirty (30) minutes will be spent troubleshooting. This troubleshooting will be considered billed within the current advisory case. If the issue is not resolved in these thirty (30) minutes, a new, break-fix Support Incident will need to be opened at the customer’s cost to address the problem. The Advisory Support Engineer may work the Support Incident at their discretion.


Take a look at this specific engagement checklist and how it lays out what tasks you should do –


Tasks



Collapse this tableExpand this table
Task Name Estimate (Minutes) Estimate (hours)
Collection of source environment information Note: This is a discussion that will help understand the current environment. It might creep into some of the other tasks. 30 0.50
Review of event viewer events. Note: High level overview, looking for errors that could cause problems during the migration. 30 0.50
Collection and Analysis of DCDIAG and NETDIAG output (Installation of Support Tools required) Note: No time should be spent in installing tools, that is part of the pre-reqs. 15 0.25
Collection and Analysis of SBS 2003 BPA output (Installation of BPA required) Note: No time should be spent in installing tools, that is part of the pre-reqs. 15 0.25
Collection and Analysis of IT Environment health scanner output (Installation of Tool required) Note: No time should be spent in installing tools, that is part of the pre-reqs. 15 0.25
Collection and Analysis of Exchange 2003 Best Practice Analyzer output (health and pre-migration check) (Installation of Tool required) Note: No time should be spent in installing tools, that is part of the pre-reqs. 30 0.50
Discussion of environment health and action plan. Note: Discussion about the findings and repair steps if needed. 30 0.50
Corrective actions as needed as per time scoping for the scenario, Problem resolution cases would need to be created at the customer’s expense if needed. Note: Time allotted for minor actions to correct issues detected that could prevent a good migration. Any large issues would need their own problem resolution support case. 60 1
Verification of Administrator’s account group membership and primary group settings. Note: Checklist of known issues that might not be checked by the toolset used. 10 0.16
Verification of strong password Note: Checklist of known issues that might not be checked by the toolset used. 10 0.16
Verification of WSUS and WSUS policies being disabled (if present) Note: Checklist of known issues that might not be checked by the toolset used. 10 0.16
Verification of SBS 2003 network subnet. (Must be a Class C, private subnet). Note: Checklist of known issues that might not be checked by the toolset used. 10 0.16
Apply hotfix 939820 on source server. Note: Checklist of known issues that might not be checked by the toolset used. 30 0.50
Raise functional levels of domain and forest Note: Required step on source server. 15 0.25
Running of the Migration Source Server preparation tool, confirm the version being used matches the SBS 2008 media. Note: Required step on source server. 30 0.5
Walkthrough of the Answer File creation wizard, creation of proposed answer file. Note: Required step for migration. 30 0.5
Source Exchange server mailbox optimization suggestions Note: This is a discussion on some of the options to optimize exchange, this should not include any actions, just sharing of documentation. Mostly documented in the migration guide. 15 0.25
Discussion on timeline for the actual migration setup. 15 0.25
Creation of System State Backup. Note: Do not skip this step, if customer does it on their own, we need to verify it completed correctly. 30 0.50
Total 430 7.16

 


Bottom line read over that KB and see how your pre-migration checklist compares.  Are you doing all of those steps?


If you aren’t, why are you not doing them?

When you are in the step of the migration where you are mucking out the old 2k3 group policies…

When you are in the step of the migration where you are mucking out the old 2k3 group policies…


Small Business Server Update services Client Computer Policy

Small Business Server Update Services Common Settings Policy

Small Business Server Update Services Server Computer Policy

Is not the same as …..

Those are the new WSUS policies.  So if you never had an R2/WSUS box before, don’t touch those.

 


 

The Official SBS Blog : SBS 2008 Migrations from SBS 2003 – Keys to Success:

The Official SBS Blog : SBS 2008 Migrations from SBS 2003 – Keys to Success:
http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx


How the SBSBPA differes from the EBS Prep tools recommended in that post:


SBS BPA checks the health specifically for SBS 2003. 



In that list the only item that is specifically going to cause me issues is the Exchange functional level.


In the EBS Health scan tool, the main difference is that the EBS health tool checks for AD replication issus that the SBSBPA may not catch.  Then it checks DHCP, DNS, etc but it’s checking general health of the network in potential replication issues.



Thus it’s wise to run BOTH tools when preparing for SBS 2008 migrations.


And one of the first steps that BOTH tools tell you to do in order to migrate to Exchange 2007 is to flip the Exchange server to Native mode.



 How To Convert from Mixed Mode to Native Mode in Exchange:
http://support.microsoft.com/default.aspx?scid=kb;en-us;327779

  1. Start Exchange System Manager. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
  2. Right-click the organization, and then click Properties.
  3. Click the General tab, and then click Change Mode under Change Operations Mode. Click Yes if you are sure that you want to permanently switch the organization’s mode to native mode.