Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Logon Script via GPO Question 2

Status
Not open for further replies.
Oct 23, 2007
21
US
We have twelve locations, each requiring a different script. Rather than writing a long script with IF/THEN clauses, we just use twelve different batch files and specify them in the User's Profile in A/D.

We now want to have Group Policy execute the Logon Script. My question is about the location of the script files. I see that as you drill into the properties of the logon script file in Group Policy, it is looking under Policies at a folder that has a long HEX folder name with sub-folders under that. I can see that if I place a batch file there, it will replicate to other servers. So, I am confident that the files will be replicated and users will run them.

I would prefer to put the twelve batch files into one location and then point the Group Policy object to the specific file. Can I do this? If so, where to I put those files?

My alternative is to put each individual script file into the appropriate policy folder and then point the Group Policy object to the file. That just seems more difficult to manage.

Thanks in advance for any suggestions...
 
You can put the batch files or scripts in any share the user in question has read access to. When setting up the GP to run the file, simply put the full UNC path to the file. Something like \\myserver\scripts\login.bat




"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
When I deal with Logon scripts I use the NETLOGON directory created by default.

The UNC to access this directory is:
\\<domainName>.local\ or \\<domainName>.com\
Depending on how you have your Domain setup.

Although leaving the scripts in the GUID is another acceptable way to do this.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top