Re: Assigning a Computer a Printer

From: Eric Voskuil (voskuil_at_online.autoprof.com)
Date: 03/25/04 

Date: Wed, 24 Mar 2004 22:34:50 -0500

You can't assign shared printers from a startup script (computer policy),
since there is no user context and printers are mapped to user profiles - as
you discovered.

You can use the logon script (user policy), assuming your users have
permissions to install printers and drivers (they would by default). You
should be able to either user loopback policy, a WMI filter (XP/2003), or
write custom script code to determine computer grouping.

Our Policy Maker printers extension does this all with the typical
point-and-click nature of true Group Policy settings, runs with elevated
permissions, and implements each shared (or TCP/IP) printer connection as a
policy. Since each PM policy setting can be independently filtered using
any combinations of 25 filter categories, you could them simply assign all
of the printers in one GPO, filter each printer according to the physical
location, and assign the GPO to all users.

Regards,

Eric Voskuil
http://www.autoprof.com/policy

"ad newb" <anonymous@discussions.microsoft.com> wrote in message
news:3EA1D09B-0B34-44BE-877E-B84B3CED7827@microsoft.com...
> I've been able to use a wsh script to install a printer using a GP. Is
there any way I can add a printer so that it is specific for that computer
no matter what user logs on. We have people that will be logging on to
different PC's in different departments and I want them to have access to
whatever printer that department uses. Currently if a user in Sales logs
onto a computer in Marketing the GP will map to the printer that is located
in Sales. I've tried assigning the WSH script to the Computer configuration
startup settings in the GP but it does not work since mapped printers are
stored in the user's persnoal profile. Any help would be appreciated.

Relevant Pages

  • Re: pushprinterconnection.exe
    ... setting in group policy (not startup scripts): ... In the Group Policy Object Editor: ... Logged on as administrator and didn't get the assigned printers. ... Does GPO deployment work under that scenario? ...
    (microsoft.public.windows.group_policy)
  • Re: pushprinterconnection.exe
    ... setting in group policy (not startup scripts): ... In the Group Policy Object Editor: ... Logged on as administrator and didn't get the assigned printers. ... Does GPO deployment work under that scenario? ...
    (microsoft.public.windows.group_policy)
  • Re: pushprinterconnection.exe
    ... You said you used a startup script right? ... Since startup scripts (versus ... In the Group Policy Object Editor: ... Logged on as administrator and didn't get the assigned printers. ...
    (microsoft.public.windows.group_policy)
  • Re: pushprinterconnection.exe
    ... The exe must reside on there. ... If you are creating a USER policy then set the GPO to disable COMPUTER ... Logged on as administrator and didn't get the assigned printers. ... Does GPO deployment work under that scenario? ...
    (microsoft.public.windows.group_policy)
  • Re: Logon script in Group Policy not working.
    ... Seems like your script doesn't run at all, ... Maybe your policy isn't applied at all. ... permissions to add network printers and a correct path. ... MCSA Windows 2003 server ...
    (microsoft.public.windows.terminal_services)