Previous to Windows 7/ Server 2008 R2, regular users could only install OS included or digitally signed print drivers. Anything else would require an administrator account to perform the installation. You could create a deployment package via SMS/SCCM or KBox but deploying via GPO is so much easier. I have 2 Canon Image Runners (fiery) whose drivers require administrative rights to install.

To set this up I first created a new GPO that I will assign to my internal user OUs. Under User Configuration navigate to \Policies\Administrative Templates\Control Panel\Printers and modify the Point and Print Restrictions policy item. Set it to enabled and change the 2 options dealing with driver installation to “Do not show warning or elevation prompt.”

Now go to your print server or open the print management console. Find the printer you want to deploy to your users, right-click and select deploy with group policy. Browse to find the GPO you just created, select “The users that this GPO applies to (per user), and click Add, then OK.  While you can also deploy to machines, this keeps things simple since our driver installation GPO settings target the user.

You will see confirmation that the printer deployed and if you refresh your GPO you will see the printer(s) you deployed under Printer Connections. Link the GPO to the proper OUs, force replication on your DCs, issue a gpupdate to your desktops and like magic the printer and driver will just appear on your clients. No log off or reboot required. Best of all they won’t see any prompts for the installation of the driver.

Reference:

TechNet

I came across a thread in the TechNet forums discussing printer queue naming best practices. One of the Microsoft Printing Team members chimed in to explain how they do it internally in Microsoft.

At Microsoft the printer names are associated only with locations + A, B, C and CLR if it’s color.

Possible examples: Sales-A-CLR or Bldg3_Flr2_West-A

They then include more detail in the location field and device brand, model, PCL/PS, etc in the comments field. This way the queue (name) is not married to a specific printer type. When they physically replace a printer they only have to change the driver and port name, then update the comments. A very clean and simple way to do it.

When the user searches for network printers using AD they will see:

NAME (this is the share name of the print queue)

LOCATION (text has been entered in the location field of the print queue)

MODEL (driver in use on the print queue – very misleading unless 1:1 always in place)

SERVER NAME (the print server where the print queue resides)

COMMENTS (text has been entered in the comment field of the print queue)

Reference:

Technet Forums