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

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
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 How to back up and restore the registry in Windows XP and Windows Vista
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 2003domain.
  • 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 = 2472USERENV(1e0.1e4) 11:33:37:107 CheckXForestLogon: XForest logon!USERENV(1e0.1e4) 11:33:37:107 ParseProfilePath: CheckXForestLogon returned S_FALSE, disable RUPUSERENV(1e0.1e4) 11:33:37:107 ReportError: Impersonating user.USERENV(1e0.1e4) 11:33:37:107 CEvents::FormatString: FormatMessage failed.  Error = 317USERENV(1e0.1e4) 11:33:37:107 LoadUserProfile: ParseProfilePath returned a directory of ...
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:
  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.

Article ID: 949665 - Last Review: 01/15/2015 18:48:27 - Revision: 2.0

Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86)

  • kbnosurvey kbarchive kbtshoot kbprb KB949665
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)