No announcement yet.

deploying prts with R2 gpo

  • Filter
  • Time
  • Show
Clear All
new posts

  • deploying prts with R2 gpo

    I've upgraded one of my two Dc's to win2003 R2. The other one is W2003 sp1.
    The new printer management console looks and works fine, but when it comes to deploy the printers using GPO it's not working.
    I've linked the printers to the only existing OU policy (user settings section), with no visible effects. Linking them to default domain GPO didn't help.
    The deployed printers are installed locally at the upgraded server.

    Am I missing anything ?


  • #2
    Re: deploying prts with R2 gpo

    enable this feature, you must use a utility called PushPrinterConnections.exe.
    The PushPrinterConnections.exe utility is only needed on computers running Windows 2000, Windows XP, and Windows Server 2003 R2 client computers.

    In order for the PushPrinterConnections.exe utility to work, you must update your Active Directory schema with the Windows Server 2003 R2 changes.

    First, add the PushPrinterConnections.exe utility to a machine startup script (for per-machine connections) or to a user logon script (for per-user connections). The utility reads the settings made by the GPO containing the printer setting and adds the printer connection.
    It is a good idea to use the same GPO for both the printer connection settings and the PushPrinterConnections.exe computer startup or user logon script. This ensures that only users (or computers) that receive the printer connection settings will run the PushPrinterConnections.exe utility.

    MS Note: Only per-user printer connections are supported on computers running Windows 2000. Either Windows XP or Windows Server 2003 is required for per-machine printer connections.

    To install printers to groups of users or computers by using Group Policy
    1. In the Print Management tree, under the appropriate print server, click Printers.
    2. In the results pane, right-click the printer you want to deploy, and then click Deploy with Group Policy.
    3. In the Deploy with Group Policy dialog box, click Browse, and then choose a Group Policy object.
    4. Click OK.
    5. To assign the printer connection setting to the GPO, do one or both of the following:
    • As a per-user setting, select the The users that this GPO applies to (per user) check box.
    • As a per-machine setting, select the The computers that this GPO applies to (per machine) check box.
    6. Click Add.
    7. Repeat steps 3 to 6 to add the printer connection setting to another GPO.
    8. Click OK.

    To use the PushPrinterConnections.exe file
    1. Using Group Policy Management console (Gpmc.msc), right-click the GPO with your printer connections settings and click Edit.
    2. In the Group Policy Object Editor tree, navigate to one following locations:
    • If the printer connections are deployed per-machine, go to Computer Configuration, Windows Settings, Scripts (Startup/Shutdown).
    • If the printer connections are deployed per-user, go to User Configuration, Windows Settings, Scripts (Logon/Logoff).
    3. Right-click Startup or Logon, and then click Properties.
    4. In the Logon Properties or Startup Properties dialog box, click Show Files.
    5. Copy the PushPrinterConnections.exe file to this location and then close the window.
    6. In the Logon Properties or Startup Properties dialog box, click Add.
    7. Type PushPrinterConnections.exe in the Script Name box.
    8. If you want to enable logging, type –log in the Script Parameters box. Log files are written to %windir%\Temp\PpcMachine.log (for per-computer connections) and %temp%\PpcUser.log (for per-user connections) on the computer on which the policy is applied.

    For per-computer connections, the printer connections will be added when the client computer restarts. For per-user connections, the printer connections will be added when the user logs on.

    If you remove the printer connection settings from the GPO, the PushPrinterConnections.exe will remove the corresponding printers from the client computer on the next restart or user logon.

    For more Information, Download R2 Detailed Help File (or use the one you have on your server) from

    Good Luck
    Yaniv Feldman
    Microsoft Security Regional Director
    Microsoft Management Expert


    • #3

      I really aprecciate your help