How to map 20 printers to 300 domain joined computers through GPO?


  • Hi,

     There is one Accounting department which has 20 printers with 300 computers and currently the printer is mapped by users. What if other users (200) from another Departments (IT and Marketing) migrate to Accounting Department? We would like to create a GPO that map the 20 printers to 300 computers in the Accounting Department so any users (Accounting, IT, and Marketing) can log on and print.



    Someone suggested:

    RUNDLL32 PRINTUI.DLL,PrintUIEntry /gd /z /n"\\computername\printer name"

    but this is for 1 computer and 1 printer. What if there are 20 printers and 300 computers?

    • Edited by wawakiki Tuesday, January 12, 2016 2:24 AM
    Tuesday, January 12, 2016 2:12 AM


All replies

  • Depending on how your OU structure is setup you could map the printers for the Accounting Department via GPP.

    For instance, create a user policy to map the printers via GPP.  Then within each preference (don't know offhand if there is a "collection" option available, use Item-Level Targeting to apply the settings, only if the computer (that the user is logging into) is in the Account Department OU. 

    If you don't have separate OUs, you could create a security group to dump all of the account department systems into and then use for your ILT

    Tuesday, January 12, 2016 1:44 PM
  • Hi. Share the printer. From the Default Domain policy goto to User configuration --> Preferences--> Control Panel settings and add new shared printer. And select the shared printer. 



    Khalid Garayev

    * Please don't forget to mark as answer or Vote if it helps!

    Tuesday, January 12, 2016 7:20 PM
  • Never mind. I did a PGO with Loopback.

    Thanks for the comments.


    Wednesday, January 13, 2016 9:27 PM
  • Hi Tuan,

    I am glad that you have solved your issue.
    Appreciate your share and update.
    Best regards,

    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact

    Tuesday, January 19, 2016 9:04 AM