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

If you're new here, you may want to subscribe to our RSS feed. Thanks for visiting!

After migrating your server from windows 2000 to windows 2003 your roaming profiles may not work.This tutorial will explain how to fix this problem

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 …

To resolve this problem, follow these steps

1.Click Start, click Run, type regedit, and then click OK.

2.Locate and then click the following Subkey

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System

3.If an AllowX-ForestPolicy-and-RUP registry entry exists, go to step 6. Otherwise, go to step 4.

4.On the Edit menu, point to New, and then click DWORD Value.

5.Type AllowX-ForestPolicy-and-RUP, and then press ENTER.

6.Right-click AllowX-ForestPolicy-and-RUP, and then click Modify.

7.In the Edit DWORD Value box, type 1, and then click OK.

8.Exit Registry Editor.