7

I'm trying to use Group Policy Preferences to manage user connections to shared printers.

The print server is Windows Server 2003 R2 Std edition. Several printers are installed, and I've added x64 editions of all the drivers to the print server as well.

I've created a new GPO containing the printer preference settings. Printer mappings are targeted based on AD security group membership.

I log on to a Windows XP PC with the Group Policy CSEs installed and the printer maps perfectly.

I log on to a Windows 7 x64 PC and it doesn't map. If I manually connect to the shared printer, I get a prompt which asks me to confirm if I trust the server before installing the driver, and then it works perfectly.

I have domain admin rights and my UAC settings have not been changed from the default, i.e. UAC is enabled and the default level is selected.

Is the printer mapping failing because it's unable to prompt me to install the driver, or is there something else afoot?

ThatGraemeGuy
  • 15,314
  • 12
  • 51
  • 78

2 Answers2

9

OK I managed to get this working.

For Vista there is a Group Policy setting (more info here):

  • User Configuration/Policies/Admin Templates/Control Panel/Printers

Configuring the "Point and Print Restrictions" policy setting to "Disabled" will allow for silent printer driver installation, and thus allow the printer to be mapped successfully.

After struggling for the better part of this morning trying to figure out why this didn't work on Windows 7, I eventually discovered that Windows 7 and Server 2008 R2 ignore this policy setting. There is an equivalent setting under:

  • Computer Configuration/Policies/Admin Templates/Printers

This is honoured by Windows 7 and Server 2008 R2 See TechNet for more info.

ThatGraemeGuy
  • 15,314
  • 12
  • 51
  • 78
0

If you cannot find the policy under Computer Configuration, you may not be using Group Policy Management on Server 2008 R2. You'll only get the policy on Server 2003 if you have updated your ADM files to the latest.

If you are having the reverse problem with XP clients, make sure you have followed this article: http://support.microsoft.com/kb/888046

Method 1 worked for me.