SBS 2003 to SBS 2011 – Run the Migration Preparation Tool on the Source Server Failed (X) on Schema Update:
http://social.microsoft.com/Forums/en-US/partnerwinserversbs/thread/9ac51388-e647-4ba0-afda-2ec5e508036a

So during the migration from SBS 2003 to SBS 2011 the migration tool failed on the schema update…

Suggested actions include:

Based on the research, we found this issue maybe caused by the factors below:

1. The value for the SYSVOL setting under the NETLOGON\Parameters section of the registry is not populated or refers to an invalid location.

2. The reparse point between %windir%\sysvol\sysvol\domain and %windir%\sysvol\sysvol\<FQDN> is invalid.

3. The Default Domain or Default Domain Controller policies are missing from the SYSVOL folder or were not defined with the default GUID number.

I would like to provide some suggestions below to narrow down this issue:

Suggestion 1: Verify the SYSVOL registry key exists and points to the current sysvol path

===========================

1. Press the Windows + R keys.

2. Type REGEDIT in the RUN field and click OK.

3. Locate the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

Value Name: SYSVOL

Value Type: REG_SZ

Value Data: <path to current sysvol location>

4. A typical registry value for a SYSVOL folder located in the default path is C:\Windows\SYSVOL\sysvol.

5. If the SYSVOL registry setting or its value is missing, manually add or correct it in REGEDIT or run:

reg add HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters /V SysVol /T REG_SZ /D “<valid drive letter:>\<valid parent folder>\sysvol\sysvol” /F

Suggestion 2: Verify the file system junction is correct

===========================

There are two reparse points in the SYSVOL tree which must be correctly defined.

A DIR command against the path “<drive>:\windows\sysvol\sysvol\domain” (where “domain” is the literal word “domain”) is not sufficient to validate the reparse path. Instead the LINKD command-line tool must be used. LINKD is available as part of the Windows Server 2003 Resource Kit Tools.

Windows Server 2003 Resource Kit Tools

http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

The LINKD syntax to validate the reparse points for a SYSVOL located at C:\Windows\SYSVOL in the CONTOSO.COM domain is:

linkd %systemroot%\sysvol\sysvol\contoso.com

AND

linkd %systemroot%\sysvol\Staging Areas\contoso.com

If those commands fail to return a valid reparse point (i.e. return a blank value or invalid path), the reparse point must be redefined. The LINKD syntax to define the reparse points for a SYVOL located at C:\Windows\SYSVOL in the CONTOSO.COM domain would be:

linkd c:\windows\sysvol\sysvol\contoso.com c:\windows\sysvol\domain

AND

linkd c:\windows\\sysvol\Staging Areas\contoso.com c:\windows\sysvol\staging\domain

Suggestion 3: Verify the Default Domain and Domain Controllers policies exist in the SYSVOL folder and have the correct GUID

====================================

From the console of the infrastructure master where you are running ADPREP /DOMAINPREP verify that:

· The SYSVOL contains two subdirectories, POLICIES and SCRIPTS.

· Default Domain and Default Domain Controllers policies exist under the POLICIES folder.

· The Default Domain policy has been defined with the GUID “{31B2F340-016D-11D2-945F-00C04FB984F9}”.

· The Default Domain Controllers policy has been defined with the GUID “{6AC1786C-016F-11D2-945F-00C04fB984F9}”.

If the SYSVOL folder is empty, or the POLICIES and SCRIPTS folders are missing, resolve that condition.

If the Default Domain or Domain Controller policies exist but lack the default 31B.. and 6AC… GUIDs, recreate them with DCGPOFIX.

 

One Response to SBS 2003 to SBS 2011 – Run the Migration Preparation Tool on the Source Server Failed (X) on Schema Update

  1. Teyah says:

    Home run! Great slugging with that aswenr!