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

Article translations Article translations
Article ID: 949665 - View products that this article applies to.
Expand all | Collapse all


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:
  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.
  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.


Article ID: 949665 - Last Review: March 5, 2008 - Revision: 1.0
  • Microsoft Windows 2000 Server
kbtshoot kbprb KB949665

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from