Windows 2000 and Windows XP provide more flexibility with roaming profiles. By default, the client attempts to download the user's roaming profile from the server. If the client does not attempt to do this, you must ensure that the profile is set to Roaming, in order to take advantage of the support.
As a logged-on administrator, use the following steps:
For Windows 2000:
For Windows XP:
You can also copy an existing Windows user profile to the server in order to prime the roaming user profile for a user. From the User profile dialog box you opened in the previous steps, click the Copy to button. Locally cached profiles (preferences and settings) can be replicated to the Logon Server just like you would copy user folders from \Windows\Profiles for Windows 98. Make sure you are copying the profiles into the folder that the NT clients will load them from. See the next section for discussion on profile locations. If you are migrating multiple profiles from an NT server to an iSeries Logon server, then it will probably be more efficient to copy over the entire \WINNT\Profiles folder.
By default, clients with the IPLC attempt to load or store roaming profiles in the subdirectory, Profiles, of the user's home directory. You can override this behavior by changing the user Profile Path that is configured.
For Windows 2000:
For Windows XP:
The Profile path is typically specified in the following form: \\logonserver\profilesShare\profileDirectory