Implementing the %SERVERNAME% Environment Variable In ProfilesLast reviewed: April 24, 1996Article ID: Q138083 |
The information in this article applies to:
SUMMARYThis article describes how to implement the %SERVERNAME% environment variable in the user profile path of the Windows NT User Manager. This environment variable must be set on the workstation computer, not the domain controller.
MORE INFORMATIONWhen you have configured a user's profile path in User Manager, the entry looks similar to this:
UserProfiles User Profile Path: \\%SERVERNAME%\profiles\user1.usrThe %SERVERNAME% variable provides load balancing and performance improvements. As Administrator, you can spread the load of processing user profiles to another server by setting the SERVERNAME environment variable to the name that is located close to the workstation. When a user logs into the domain, they are directed to \\%SERVERNAME%, where %SERVERNAME% has been set to the name of a server, for example, "Server1". The profile server should be close to the client's computer (not located across a slow link) to expedite log on. For example, on all workstations in Phoenix, set the variable to a Server name that is located in Phoenix. On workstations in Seattle, set the variable to a Server name that is located in Seattle. That way, when a user is in Phoenix, his or her logon script is executed on a controller in Phoenix. When that user visits Seattle, his or her logon script is executed on a controller in Seattle.
Setting the Environment Variable On Workstation Using A ServerWARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
|
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |