Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Logon script replication
A logon script is always downloaded from the server that validates a user's logon request. For users with accounts on Windows Server 2003 family domains that have one or more ___domain controllers, any one of the ___domain controllers can authorize a user's logon attempt. In order for logon scripts to always work for users, logon scripts must exist for all user accounts in a ___domain, on every ___domain controller in that ___domain.
Windows Server 2003, Standard Edition, ___domain controllers and servers use File Replication Service (FRS) to replicate system policy and logon scripts to every ___domain controller in a ___domain. When you make a change to a logon script stored in the SYSVOL share of a ___domain controller, FRS replicates this change to the SYSVOL shares of all other ___domain controllers in the ___domain. If the administrator manages scripts for a ___domain using Active Directory Users and Computers, then the logon scripts are typically located in the %systemroot%\SYSVOL\sysvol\domain_name\Scripts folder. The system will look for scripts in the netlogon share of the ___domain controller that authenticates the user.
If the administrator uses Group Policy to manage logon scripts on a standalone system, then the user logon scripts are typically located in the %systemroot%\System32\GroupPolicy\User\Scripts\Logon directory.
For specific information on how to configure the logon script path for a user in a ___domain, see Assign a logon script to a user in the Active Directory.
For background information about replication, see Understanding Sites and Replication and Replication overview.
For instructions about configuring replication, see Configure Replication Between Sites.