Select the product you need help with

Roaming profiles do not work after migration from Windows 2000 to Windows Server 2003

Article ID: 949665 - View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows XP and Windows Vista

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You have a two-way trust relationship between a Microsoft Windows 2000 domain and a Windows Server 2003 domain.
You migrate the Windows 2000 domain to the Windows Server 2003 domain.
You try to migrate users and computers together with their security identifier (SID) history.

In this scenario, roaming profiles are not loaded, and users cannot manually access their own profile.

Additionally, a message that resembles the following message may be logged in the Userenv.log folder:

USERENV(1e0.1e4) 11:33:37:076 CheckXForestLogon: checking x-forest logon, user handle = 2472
USERENV(1e0.1e4) 11:33:37:107 CheckXForestLogon: XForest logon!
USERENV(1e0.1e4) 11:33:37:107 ParseProfilePath: CheckXForestLogon returned S_FALSE, disable RUP
USERENV(1e0.1e4) 11:33:37:107 ReportError: Impersonating user.
USERENV(1e0.1e4) 11:33:37:107 CEvents::FormatString: FormatMessage failed.  Error = 317
USERENV(1e0.1e4) 11:33:37:107 LoadUserProfile: ParseProfilePath returned a directory of ...

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps:

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System
If an AllowX-ForestPolicy-and-RUP registry entry exists, go to step 6. Otherwise, go to step 4.
On the Edit menu, point to New, and then click DWORD Value.
Type AllowX-ForestPolicy-and-RUP, and then press ENTER.
Right-click AllowX-ForestPolicy-and-RUP, and then click Modify.
In the Edit DWORD Value box, type 1, and then click OK.
Exit Registry Editor.