Re: GPO for assigning printers

1. Network printers, by default, are per user, not per computer. So, connecting a (user) printer in a Startup Script won't do anything useful.

2. If your domain is using the Windows Server 2003 R2 Functional Level, you can deploy printers to computers, which really means deploying to any user that logs on to the computer. You can specify the printers to deploy using the Print Management Console or via GP Editor.

3. Although network printer connections are per user, you can use the PrintUI command to deploy printers to all users on a computer. See http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm. Although you could do this in a Startup Script, the printer connection is persistent, so you only have to execute the command once per printer per computer, not every time the computer starts, so using it in a Startup Script is somewhat overkill.


--
Bruce Sanderson
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Kermitdafwog" <Kermitdafwog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C55B937C-3184-48C0-9F4D-D35D209A8FC4@xxxxxxxxxxxxxxxx
Hi!

Scenrio -
We have just set up a new IT suite consisting of 5 PCs and one network printer
We want the printer to install on the PCs automatically and install on any
PCs added to that room (the computer account will be moved to the correct OU
when joining to the domain). We dont want the printer to be mapped when user
log on to other IT suites

My Solution (probably wrong!)

II created and editted a GPO linked to that OU
I created a PrinUI add printer script to create the new printer and added
into startup scripts under the computer configuration and put the script in
the Netlogon share (and also into the Startup folder of the script under
c:\windows\sysvol\etc)

When i log in as the admin or a test user i dont get the printer mapped.
the script defintiely works as when i run it, it installs without error and
when the computer is starting up you see the script run...we see a dialog box
saying "connecting to printer..."

Where am I going wrong?
I added the same script into the User config of the policy and the printer
mapped....how is this is as there are any user accoutns in this OU?

Any help would be graefully received

cheers
Kermit

.

Relevant Pages

  • Re: connecting to printers at PC startup
    ... I want to use a group policy to have PCs automatically connecting to specified printerwhen the PCs start up. ... The startup script gets executed - I am sure of this because if I make any mistakes in the script a warning message will pop up. ... You can't do it in a startup script as you have found out - the reason for that is that connecting to a shared printer is done on a 'per user' basis (try it: log in as a user, ...
    (microsoft.public.windows.server.active_directory)
  • Re: connecting to printers at PC startup
    ... I want to use a group policy to have PCs automatically connecting to ... The startup script gets executed - I am sure ... node's startup script to user node's logon script. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Xcopy not working in startup script
    ... This is a basic batch file script that I am ... deploying through group policy in the startup script to copy ... it works fine on it's own, but when deployed through group policy it ... the permissions of the computer object elsewhere in the domain. ...
    (microsoft.public.windows.server.general)
  • Re: Ooooopppps. Rights not right...
    ... Use a log in script to call a compiled file stored on a share. ... > because the classid is for per machine instead of per user. ... > you have create two user classes, one is called student; ... > Put this bat file to the computer startup script in the local group policy. ...
    (microsoft.public.windows.server.general)
  • Re: Power Management GPO?
    ... I suspect that the power management subsystem might not be started when the startup scripts runs or the SYSTEM context can't modify it, but I have some ideas about this and will do some testing later on today to work it out. ... I created a GPO and put the batch file in first as a startup script and when that didn't work I tried it as a logon script. ... A normal user can't change the power settings so a logon script like this won't work either. ... I can't remember if all power setting are per machine, but if some are per machine and some are per user then you could split it up into 2 scripts, one startup script and one logon script. ...
    (microsoft.public.windows.group_policy)
Loading