• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 353
  • Last Modified:

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\login.vbs

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.
0
lbbcsg
Asked:
lbbcsg
  • 4
  • 4
1 Solution
 
Netman66Commented:
This script should be placed in :

C:\WINDOWS\SYSVOL\sysvol\{your domain here}\scripts

This will then replicate to all DCs.

The GPO running the Logon script will then simply point to login.vbs with no UNC path.

0
 
lbbcsgAuthor Commented:
When I put it in the C:\WINDOWS\SYSVOL\sysvol\domain.dom\scripts folder then go into my GPO and choose Logon Script, I have to drill down to find it, and it ends up putting in the entire path with the file name at the end.
0
 
Netman66Commented:
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\Policies\{E1E61435-DA91-4FEC-BD81-582D8543F0AE}\User\Scripts\Logon

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.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
lbbcsgAuthor Commented:
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\Policies\{E1E61435-DA91-4FEC-BD81-582D8543F0AE}\User\Scripts\Logon
C:\WINDOWS\SYSVOL\sysvol\{your domain here}\scripts

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?

0
 
Netman66Commented:
If you place the script in that location on DC1, then it should replicate to DC2.

If you have DNS configured correctly, then the client should authenticate to DC2 if DC1 is down and run the script correctly.

Is DC2 a Global Catalog?  Is it running DNS and in sync with DC1?

0
 
lbbcsgAuthor Commented:
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.
0
 
Netman66Commented:
I think you'll find that this:  The Logon script path is \\domain.dom\netlogon\login.vbs

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.

0
 
lbbcsgAuthor Commented:
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.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now