Deploying printers via GPO

[Miha]

Hi

We're moving our network printers to a new print server, so we want to use a
new feature in Win2003 R2 - deploy printers via GPO to our users.
Since they still have network printers installed that are pointing to an old
server, after deploying a GPO to point all printers to a new server, the
default printer at users is still pointing to an old server. Is it possible
to set that newly deployed printers will also be default ? Also if I deploy
more than one printer, the first one is always used as a default (if there
is no printers installed on a client side). Can this be changed?

Thank you in advance.
Regards,
Miha

 

[Florian Frommherz]

Howdie!

We're moving our network printers to a new print server, so we want to use a
new feature in Win2003 R2 - deploy printers via GPO to our users.
Since they still have network printers installed that are pointing to an old
server, after deploying a GPO to point all printers to a new server, the
default printer at users is still pointing to an old server. Is it possible
to set that newly deployed printers will also be default ? Also if I deploy
more than one printer, the first one is always used as a default (if there
is no printers installed on a client side). Can this be changed?

I'm afraid but setting a default printer is not implemented in this
feature. Don't ask me why - I'm missing this too. There also is no
option of setting a newly deployed printer as default when there are
existing ones. I haven't found a way for this, yet. You'll need to
script it.

These two articles helped me out:
http://support.microsoft.com/kb/263226
http://www.microsoft.com/technet/scriptcenter/resources/qanda/nov04/hey1117.mspx

cheers,

Florian

 

[Miha]

Thanks!

Regards,
Miha

Howdie!


I'm afraid but setting a default printer is not implemented in this
feature. Don't ask me why - I'm missing this too. There also is no option
of setting a newly deployed printer as default when there are existing
ones. I haven't found a way for this, yet. You'll need to script it.

These two articles helped me out:
http://support.microsoft.com/kb/263226
http://www.microsoft.com/technet/scriptcenter/resources/qanda/nov04/hey1117.mspx

cheers,

Florian

 

[Lanwench [MVP - Exchange]]

In

Hi

We're moving our network printers to a new print server, so we want
to use a new feature in Win2003 R2 - deploy printers via GPO to our
users. Since they still have network printers installed that are pointing
to
an old server, after deploying a GPO to point all printers to a new
server, the default printer at users is still pointing to an old
server. Is it possible to set that newly deployed printers will also
be default ? Also if I deploy more than one printer, the first one is
always used as a default (if there is no printers installed on a
client side). Can this be changed?
Thank you in advance.
Regards,
Miha

You might post in a GP group for more expert help. I personally use a more
old-fashioned method for printers (con2prt.exe in a login script - which can
both deletes add printers).

 

[Realgar]

With this program, con2prt, a normal user without admin rights, is able to
install a network printer? I've the problem with the WinXp client, where
normal users cannot add network printers..

Tnx


"Lanwench [MVP - Exchange]"

 

[Kurt]

With this program, con2prt, a normal user without admin rights, is able to
install a network printer? I've the problem with the WinXp client, where
normal users cannot add network printers..

Tnx


"Lanwench [MVP - Exchange]"

In
You might post in a GP group for more expert help. I personally use a more
old-fashioned method for printers (con2prt.exe in a login script - which
can both deletes add printers).

Any user can add a network printer that is published in the directory.

....kurt

 

[Realgar]

Yes,
when I had only my Windows 2000 environment, with clients windows 2000 and
server windows 2000 this was right. Now I'm implementing Windows Xp sp2
clients inside my network, and this clients are unable to install network
printers (intalled and shared from the windows 2000 adv srv).
When a user try to connect to a printer, the message is:
"A policy is in effect on your computer which prevents you from connecting
to this print queue. Please contact your system administrator."

Thinking that was something inside a gp, I've created a new ou with a blank
gp and inserted inside it a pc and a user, but the result is the same. Using
gp's instrument to look if some policies had been applied, everything was
"not defined".

Any idea?
I've found this kb:
http://support.microsoft.com/kb/888046/en-us
http://support.microsoft.com/kb/319939/en-us
but they don't work...
My printer server is an windows 2000 advanced server in cluster with a same
server. And the new clients are all Windows XP sp2. All pc/server are
updated with SUS.

Tnx

With this program, con2prt, a normal user without admin rights, is able
to install a network printer? I've the problem with the WinXp client,
where normal users cannot add network printers..

Tnx


"Lanwench [MVP - Exchange]"

In Miha <[email protected]> typed:
Hi

We're moving our network printers to a new print server, so we want
to use a new feature in Win2003 R2 - deploy printers via GPO to our
users. Since they still have network printers installed that are
pointing to
an old server, after deploying a GPO to point all printers to a new
server, the default printer at users is still pointing to an old
server. Is it possible to set that newly deployed printers will also
be default ? Also if I deploy more than one printer, the first one is
always used as a default (if there is no printers installed on a
client side). Can this be changed?
Thank you in advance.
Regards,
Miha
You might post in a GP group for more expert help. I personally use a
more old-fashioned method for printers (con2prt.exe in a login script -
which can both deletes add printers).

Any user can add a network printer that is published in the directory.

...kurt

 

[Mark Heitbrink [MVP]]

Hi

"A policy is in effect on your computer which prevents you from connecting
to this print queue. Please contact your system administrator."

- Create a new OU
- set "block inheritance" on that OU
- move a user to this OU
- move a computer to this OU
- logon
?

Still not working?
Delete manually:
HKLM + HKCU
\Software\Policies
\Software\Microsoft\Windows\Current Version\Policies
(you need local admin rights to do that)

If it now works, there is a problem in your existing GPO structure
or in the installation, perhaps you manipulated the hivedef.inf
ot a different kind of running a unattended setup, with selfmade
registry settings.

The creation of the OU with blocking GPO is only for troubleshooting
reason.

Mark