lbbcsg
asked on
Login script w/multiple DCs
I've got 2 2003 Servers. Both are DCs, GCs and DHCP servers. I've got a Visual Basic login script placed in the \\domain.dom\netlogon folder. I have a Login Script policy in GPO tied to my main OU. The Logon script path is \\domain.dom\netlogon\logi
The problem is when I shut down DC1 and log into a workstation, the login script is not being run. I need it to pull the script when logging into DC2. When DC1 is down, I can browse to that Netlogon folder and manually run the script, so it's not a rights issue. For some reason it's just not running itself when DC1 is down.
Someone please advise.
The problem is when I shut down DC1 and log into a workstation, the login script is not being run. I need it to pull the script when logging into DC2. When DC1 is down, I can browse to that Netlogon folder and manually run the script, so it's not a rights issue. For some reason it's just not running itself when DC1 is down.
Someone please advise.
ASKER
When I put it in the C:\WINDOWS\SYSVOL\sysvol\d
When you click Add for the logon script, you should be presented with a logon script name and parameters. By default, it should place the script in the GPO (policy's) folder as below - note the GUID will be different for you.
\\Domain\SysVol\Domain\Pol
As log as the script is in the policy folder it will replicate to all DCs and should be available.
You can leave it in the Scripts folder as instructed above, but you will need to drill down to it.
Either way should work for you.
\\Domain\SysVol\Domain\Pol
As log as the script is in the policy folder it will replicate to all DCs and should be available.
You can leave it in the Scripts folder as instructed above, but you will need to drill down to it.
Either way should work for you.
ASKER
Netman, thanks for the help thus far.
I know what you mean when I hit Browse and it looks in the default spot like you mention above. If I put my script in there, it still doesn't run when DC1 is down.
So far I've tried:
\\Domain\SysVol\Domain\Pol
C:\WINDOWS\SYSVOL\sysvol\{
From both spots, no script runs when DC1 is down. Yet I can browse to both locations while DC1 is down and manually run it.
Anymore ideas?
I know what you mean when I hit Browse and it looks in the default spot like you mention above. If I put my script in there, it still doesn't run when DC1 is down.
So far I've tried:
\\Domain\SysVol\Domain\Pol
C:\WINDOWS\SYSVOL\sysvol\{
From both spots, no script runs when DC1 is down. Yet I can browse to both locations while DC1 is down and manually run it.
Anymore ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The replicaiton works, I can make a change to the script on DC1, then within seconds see the change on DC2. DC2 is a GC. I will have to verify the DNS status.
I think you'll find that this: The Logon script path is \\domain.dom\netlogon\logi
Should simply refer to the script name of login.vbs in that GPO isnce it knows where to look already.
By adding the domain it likely only resolves to the other DC.
Should simply refer to the script name of login.vbs in that GPO isnce it knows where to look already.
By adding the domain it likely only resolves to the other DC.
ASKER
It came down to being a DNS issue. Once I added the 2nd DNS server IP address inside DHCP it seemed to resolve the problem.
C:\WINDOWS\SYSVOL\sysvol\{
This will then replicate to all DCs.
The GPO running the Logon script will then simply point to login.vbs with no UNC path.