Install printers based on the active directory organizational unit by
pushing a machine startup script.
This idea would work perfectly as our active directory is for the most part
organized by a computers physical location in a school. A machine startup
script which can be found in the group policy editor under Computer
Configuration\Windows Settings\Scripts\Startup is different from a login
script as it is run on the target machine before a user even logs into a
computer. After creating a GPO with my printer installation script set as a
startup script I linked the GPO to a test OU where I began my testing.
Unfortunately, this setup didn't seem to want to work. When the computers in
the OU would boot up I would receive a message stating the access was denied
to add the printer. I knew that the problem was not with permissions
accessing the scrip. The access denied message is coming from the local
machine. It appears the "Domain Computers" account doesn't have enough
access to create the printers. I have added the "domain computers" to the
local "Power Users" account, but I still get the same error.
The script I am running uses:
I use the above in a cmd file to create a local TCP/IP Port then I install a
local Pinter and driver. Then I map it to the local TCP/IP port.
There is no print sever anywhere.
I basically want to create an OU called "Printer Installs", and I want to
move machines into this OU. By doing so, the machines would get the printer
installed via computer startup scripts through group policies. This
procedure would be useful, because we image massive number of workstations.
However, I believe, I am limited by Microsoft.
I have even considered using the loopback feature of group policies, but you
still have to login to the machine for the script to run.
Any how, I am wondering if there is something I am missing. Any directions
or help would be appreciated.