Home | Resource Guides | Tech Tips | Network Administration | Certification

Tech Tips › Windows NT › Users and Groups

Tech Tips / Windows NT / Users and Groups

Storing user profiles, part 1

You can impact network traffic and efficiency based on where you store different types of profiles. To avoid version problems, don't store roaming user profiles on the Netlogon share (\Winnt\System32\Repl\Import\Scripts) if you have more than one logon server.

For example, assume that you're validated by \\ServerA when you log on, and your roaming profile is copied from that server. Any changes to your user profile are saved to \\ServerA when you log off. If you're validated by \\ServerB the next time you log on, your newer user profile won't be downloaded.

However, because mandatory user profiles aren't copied back to the server upon logoff, they can be stored on the domain controller's Netlogon share. When you set a user's profile path to %Logonserver% (e.g., %Logonserver%\Filename.man), his or her profile is copied from the logon server used to validate the logon. If more than one logon server is used in your organization, use the Folder Replication service to automatically copy mandatory user profiles to all logon servers.