Printer GPO issue

[Timhi]

Hi. I created a printer deploy GPO per this guide:

http://technet.microsoft.com/en-us/library/cc722179.aspx

It uses an executable and a print server to push printers to users or computers. Here's the problem... when a user logs on, the printer GPO gets read, but it crashes the print spooler and doesn't add them. Further investigation into the log got me this:

Failed to deploy per user connection \\printserver\printer1. The remote procedure call failed.
Failed to deploy per user connection \\printserver\printer2. The RPC server is unavailable.

This doesn't happen all the time, only most of the time. Sometimes the GPO executes perfectly. I set the GPO to initiate once the network is available, so no worries about no network connection.

Anyone familiar with this problem?
Thanks!

 

[Timhi]

Ok then, how about this:
is there a way to delay a GPO from executing for a few seconds after logon? Like adding a batch file with a wait command? I'm thinking it might be trying to execute before wireless is fully initialized.

 

[Timhi]

The RPC is failing because of a print spool crash. The script gets to one of the printers and crashes the print spooler. Since the print spooler initiates the RPC call, the script fails.

I found that the printers that are causing the failure are not being listed in AD for some reason. I have 15, only 6 show up in AD. If I browse to the actual print server, they all show up... all printers are configured the same way, I can connect manually, and they are all in WINS so netbios works. Any ideas?

 

[Timhi]

Solved. The reason the printers were not in AD is because they were pruned for some reason, maybe losing connections to the printers. That was caused by a bad driver.

If anyone else has this problem, check the drivers!!!