Bug 33797 – Deploying printers using Group Policy or Group Policy Preferences

Bug 33797 - Deploying printers using Group Policy or Group Policy Preferences


Summary:	Deploying printers using Group Policy or Group Policy Preferences

Status:	RESOLVED WONTFIX

Product:	UCS manual
Classification:	Unclassified
Component:	Print services
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	Docu maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-12-20 12:37 CET by Felix Botner
Modified:	2024-04-17 13:19 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2013-12-20 12:37:13 CET

see, Ticket 2013121621002374

we should have a howto how to deploy printers using Group Policy or Group Policy Preferences.

with GPO's:
http://blog.powershell.no/2009/11/08/deploying-printers-using-group-policy/

with GPP's:
http://blogs.technet.com/b/grouppolicy/archive/2009/06/24/gp-preferences-set-a-default-printer.aspx
http://dxpetti.com/blog/?p=181
http://blog.powershell.no/2009/03/20/group-policy-preferences/

If GPP's are used, it is important to set the option 

  "Run in logged-on user's security context (user policy option)"

otherwise to machine account tries to connect to the printer and that can screw up printer access controls.

Comment 1 Arvid Requate

2020-05-06 12:51:27 CEST

We should describe the process via GPOs, not GPPs, because the latter are "tattooing" and may be hard to support.

Comment 2 Nico Gulden

2024-04-17 13:19:10 CEST

This bug hasn't seen any update for several years. I close it.

If you still see a need for it, you can reopen the bug. Please add an argumentation about why it's important to take care of it.