Hello, guys.

I've been running into a problem lately. We are currently trying to automate the printer-installation in our company by using VBScripts.

Right now I have a OU set up with several computers that are in the same room and will therefore get the same printers. First we are placing a vbs.-file on these PCs by using a Group Policy on this OU. This script runs on Startup and works perfectly well. It places the file into the folder C:\Scripts (if the folder doesn't exist, it creates it).

The problem is the other GPO, which is being applied to all users in our company and runs on logon. It's supposed to look in the folder C:\Scripts and run our .vbs-file in there (If the computer isn't in the OU it obviously won't find anything and will not run any script). The problem is, it doesn't do that. If I run the script manually, it installs the printers. So the problem has to be with the GPO, right?

This is the path I have given for the script in the GPO: C:\Scripts\printer.vbs

I highly suspect this path doesn't work, though I don't know how to make it work.

I'd appreciate any help, thank you.

Greetings, TheRobidog

• Edited by TheRobidog Tuesday, February 04, 2014 9:57 AM

> This is the path I have given for the script in the GPO: > C:\Scripts\printer.vbs   Give this a try: Script name "%systemroot%\system32\cscript.exe", Parameters "%systemdrive%\Scripts\printer.vbs". And of course, check the GPO eventlog for script events.   And of course, run "gpresult /h report.html" and check report.html - is your logon script listed here?  

I've tried your solution but it still doesn't work.

I've also looked in the eventlog and the report file. The GPO isn't listed in either of them.

This means it isn't applied correctly, right? I don't have any filters on it, so I'm quite confused right now.

PS: We're using Windows Server 2003 and Windows 7 Clients.

• Edited by TheRobidog Tuesday, February 04, 2014 12:51 PM

> This means it isn't applied correctly, right? I don't have any filters > on it, so I'm quite confused right now.   Partially right. If the GPO is not listed, it isn't even recognized as "linked" at all - not regarding filters or anything. It is NOT linked to an OU within the scope of management of your users.   Where is the GPO with the logon script linked? What objects are in this OU - users or computers?  

It's linked to a OU containing all the groups (which contain all user, obviously) in our company. Inheritance is activated, so that can't be the problem. It doesn't contain any computers. They are in another OU.

Is the scope of the policy set to the default "Authenticated Users" ? Or are there specific objects specified ?

  > It's linked to a OU containing all the groups (which contain all user, > obviously) in our company. Inheritance is activated, so that can't be > the problem. It doesn't contain any computers. They are in another OU.   So you linked to a OU where groups are? Where then are the user accounts themselves? GPOs do NOT apply to groups - they MUST be linked to the OU where the user account resides...