Hey nerds, I’m trying to deploy a printer from the print management msc to a specific group policy object. The object applies to a specific OU, mydept/machine classes/desktops, and when I deploy the printer from the print manager, it says the printer has been deployed successfully to the gpo. However when I go to edit the gpo, the printer does not show up as it should.
Any thoughts? I know I have to script the pushprinterconnection.exe to the members of the OU, but the printer should still show up in the gpo edit.
The one thing I am waiting a response on is if we are using the R2 updated AD schema or not. Unfortunately I don’t think I have access to the info directly.
i write vbscripts for printer migrations and installs… i’d be happy to help if you want… otherwise, i’m guessing that your ad schema has been extended but isn’t natively r2… so the functionality is even lessened… lawlz
i write vbscripts for printer migrations and installs… i’d be happy to help if you want…
We do similar here for printer assignment- while we assign printers based on AD group membership, the actual assignment occurs when each users login script keys off off their group membership, assigning them the printer(s) specified.
We’ve done similar for migrations. We aren’t large enough to script printer installations, heh.
If you want to enable logging, type <b>–log</b> in the <b>Script Parameters</b> 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.
