Article ID: 314886 - View products that this article applies to.
This article was previously published under Q314886
This article describes some issues that administrators must plan for if users have roaming user profiles and can log on interchangeably to Windows-based computers.
Hard-Coded Paths for User ProfilesIf the Windows XP installation is an upgrade, the existing profile location is the %SystemRoot%\Profiles folder, and this folder continues to be used. If the Windows XP installation is a new installation, a Documents and Settings folder is created on the same volume as the Windows XP installation, to hold locally cached versions of user profiles.
Some programs use hard-coded paths to specify where a local or roaming user's cached profile is stored on the local computer. If a user roams between Windows-based computers, unexpected behavior can occur if a program is hard-coded to look for the user's locally cached profile in the %SystemRoot%\Profiles folder.
For example, if you log on to a new Windows XP installation, a program might not find a user's profile if the program looks for the profile in the same place that it previously looked. If a program has problems with users who roam between operating systems, the program may be using hard-coded paths.
To identify the path to a user's locally cached profile, type set at a command prompt, and then press ENTER.
System and Group Policies Applied to the UserWindows XP policy settings are located in a different area of the registry. Windows XP components look for those settings in that different location, and the components use those settings to configure the user's environment. If the user roams to a Windows XP-based computer, Group Policy places the settings from any group policy objects (GPOs) that apply to the user in the following registry location:
HKEY_CURRENT_USER\Software\PoliciesIn itself, this arrangement does not present a problem. However, the size of the user's profile is increased by the extra registry values that are mandated by having both types of policy. The administrator who sets policies in Windows operating systems must be aware of this behavior.
Article ID: 314886 - Last Review: December 1, 2007 - Revision: 1.4