This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 93%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENC%3C/text%3E%3C/svg%3E)
So I have about 100 shared computers on a domain each with 5 active users, we are moving from prntserver01 to 02. Maybe user 1 uses printer 1,2,5 ,and user 2 uses 1,2,4, user 3 uses 1,3,4,5. etc. I Have found PowerShell commands, I can add a printer to that computer, but How do I add it to the user? also, how does PowerShell handle the printer exploit fix?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 11%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHL%3C/text%3E%3C/svg%3E)
Hi,@Neal Cleary.Welcome Microsoft Q&A. For the problem of PowerShell PowerShell, it is recommended that you ask questions in Github.
I am trying to make a PowerShell script to help me move Printer accounts from the old print server to a new one. How would a group policy help me know that user 1 on computer 1 uses printers 1,2,5 yet on computer 2 users 1 2 5 and 3?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 44%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGR%3C/text%3E%3C/svg%3E)
Group Policy doesn't help you know who users which printer. But you can create a group for each printer and let it automatically install over Group Policy.
If the Printers aren't managed in the first place why bother managing them now. If the users installed them before manually let them install them again from the new print server.
Otherwise as I said, use a Logonscript to get the connected printers (Get-Printer), filter the printers from the old print server, and use Add-Printer to re-add them with the new print server.
PowerShell doesn't handle the printer exploit itself. Users can't install printer drivers without Administrative Rights. If you new print server has new printer drivers then admin rights are required. This is Windows not PowerShell.
Thats also why I suggest to use GPO in combination with Printer Restrictions so you can allow driver installs from your print server without admin rights.
Why not use GPO and Printer Restrictions?
Otherwise use a logon script in user context to add the printer to the user.