Re: pushprinterconnection.exe

You said you used a startup script right? Since startup scripts (versus
logon scripts) run in system context, those printers will only show up for
the system account, which obviously is bad. You have to use the following
setting in group policy (not startup scripts):

In the Group Policy Object Editor:
Computer Configuration -> Administrative Templates -> System -> Logon ->
"Run these programs at user logon"

Double-click setting, and in the resultant window, click on "enable", then
click "show"

Click "add" then enter the UNC path (\\server\scripttahtaddsprinters.vbs).
Click ok to all the windows, and be sure the policy is assigned to an OU
that your computer belongs to. If you have multiple DC's, initiate
replication between them, then go to the client desktop and type gpupdate
/force from the "run" window.

Your client will acquire the new policy. Now reboot, and log in as any user
to the computer. You should not see the printer.

If not, run the "group policy results" wizard agains the computer and verify
that it has that particular policy, and setting applied to it. I have to
re-iterate that I've used this technique many times in the past, and it has
saved me a TON of work. I am confident that if you follow the above
instructions, you will get it to work too.

-P

"arglong" <arglong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:12548DA4-9FB8-414B-8030-66D09BACCA1C@xxxxxxxxxxxxxxxx
I used a startup script and I verified that the everyone had read access.
Logged on as administrator and didn't get the assigned printers.
Something
is eluding me.....
I appreciate all your help!


"TwistedPair" wrote:

Just to verify, did you use the startup scripts, or did you use logon
scripts? Also, the location on the network that your policy points to
(the
share) . . . I know you said it wasn't a permissions issue, but just to
be
sure, have you verified that the "everyone" group has read access to it?

Suppose you log in with a privilaged user instead of a limited one . . .
Does GPO deployment work under that scenario? You're REALLY close, let
me
know ASAP.

Pair

"arglong" <arglong@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6267A174-9F9B-4253-8890-6434AA5866F3@xxxxxxxxxxxxxxxx
Twisted Pair,

Tried your script. It works when executed manually from the PC, however
when
used with GPO, PC says running scripts but does not add the printer.
We
thought it might be a permissions issue but there are no logs of GPO
failing
in the event viewer. We did have a GPO prevents the students from
making
changes but we disabled that particular GPO for the users and the GPO
for
the
printers with your script in it still didn't work. Any suggestions?

Arglong

"TwistedPair" wrote:

Mark,
In essence, it looks like the poster just wants to install printers on
his
client machines using group policy. He wants to apply the policies
per-machine, so that anyone that logs into that machine gets the
printer.
He has created an .exe that will install the printer, but needs a
policy
that will run it. Running the exe is just a means to an end, which is
getting printers installed through policy. See my post for an
alternate
method of achieving the same thing.

-Pair

"Mark Heitbrink [MVP]" <spam-only@xxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:%237nPEG8tGHA.4160@xxxxxxxxxxxxxxxxxxxxxxx
arglong schrieb:
It is frustrating because the printer management could be a
wonderful
tool if
it worked correctly. I'm glad to hear someone else is having the
same
problems.

My problem is, I can´t unterstand the problem ...
You can copy the pushprinterconnection.exe to the startup folder
inside your Policy and then just select the .exe?
You try to copy the file within the opne/close dialog, when
selecting the .exe?

- create a GPO
- go to compconf\...\scripts\startup
- open explorer navigate to the right startup folder in Sysvol
- copy .exe to this place
- back to your GPO select the exe as a startupscript

Mark
--
Mark Heitbrink - MVP Windows Server
Homepage: www.gruppenrichtlinien.de
extend GPO: www.desktopstandard.com
PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.








.

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: Deploy office 2003 to XP workstations
    ... Thats why I just posted the policy, ... XP works with a asynchronous startup behavior. ... The network driver starts to late. ... you can set "Run login scripts synchronously". ...
    (microsoft.public.windows.group_policy)
  • Re: pushprinterconnection.exe
    ... Just to verify, did you use the startup scripts, or did you use logon ... the location on the network that your policy points to (the ... Does GPO deployment work under that scenario? ...
    (microsoft.public.windows.group_policy)
  • Re: Startup Scripts not working???
    ... You mentioned you are running the scripts as startup scripts... ... as login scripts for your user accounts. ... printers, because if the two scripts run at the same time, ...
    (microsoft.public.windows.group_policy)
Loading