Printer Deployment through GPO

When adding pushprinterconnections.exe to the Logon Script, you can also add a logging parameter (i.e. -log) that will capture the output of the process and save it as a file on the remote workstation.

For user-based GPOs:
C:\Documents and Settings\%USERNAME%\Local Settings\Temp\ppcUser.log

For computer-based Printer GPOs:
C:\Windows\Temp\ppcMachine.log

Examining that log file will almost certainly reveal the problem.

For me the problem was "access denied", and after a lot of testing we found that it was only failing for users who were NOT members of the Local Administrators group. However, if someone who was a member of the local administrators group logged onto the machine, the non-admin magically got the printer afterwards when they logged in. I suspect it has something to do with non-admins not being able to install the printer driver onto the local machine - so in the end we had to temporarily make everyone a local administrator for a single logon immediately after the printer was first deployed on the network.