Here's kind of a parallel question to this one about my printer server saga...
Is it possible that AD can be corrupted or have something odd going on that affects printer configurations on these systems?
The initial reason we needed to look at rebuilding the print server was because during they year we'd have scattered reports about users unable to print. they try to add a printer, and it would tell them they didn't have permission to do so. Sometimes they didn't report it because the next day or the next reboot it would allow the printer to be added.
Policy refreshes on the computer wouldn't seem to matter.
The printer permissions were set for everyone to allow use to it, plus the problem seemed to "go away" only to reappear, same user, same computer.
Administrator-level users could sometimes log into the system, add the printer, then log off and the user could add the printer without problem. Other times it didn't seem to matter.
After we added the new print server as explained in the link, we instantly had two people unable to print (the two printers were not auto-migrated with the consultant's printer migration tool, I don't know if it was a resource kit util or third party). My boss added the printer to the new server and it still didn't work, with print jobs being stuck in the queue or going right through but nothing would print...again, outlined in the link.
I took a machine that was a clean install of XP and tried adding the printer, still didn't work.
Yesterday another consultant came in and rebuilt the server, 32 bit, from the ground up. Fresh install with each printer driver installed and configured from downloaded drivers, no migration or anything. We went back to the person who had the initial issue (we had to point her to the "printers-old" server), pointed it to the new "printers" server, and voila! It didn't work. The print jobs were stuck in the queue again.
I ended up having to delete the printer, reboot, on her local machine I deleted the driver from the print server settings (right click on the window for printers and faxes and in the drivers tab remove the printer driver), reboot, and as an admin re-add the printer from the printers-old server again, reboot and let her log in with her account and re-add the printer under her account. Then she could print again.
I'm trying to nail down the common links here. Two people on two machines (and more afterwards from reports) could not print immediately after the new print server was installed. That would tell me it's the print server. But we replaced the print server with a fresh install, fresh drivers, etc. version, and it still wouldn't work. Completely removing the driver from the client was required before the client machine could print to that printer at all...corrupted drivers from a print server? but I tried a client computer that had never had the driver installed before, and it too failed. Printer failure? But we had, in the initial report, two printers in that room, two different models (one a 1020 and the other a 2600 if memory serves) that refused to print. The 2600 had firmware updated and that didn't fix the problem, and while troubleshooting the issue I tried direct printing to the printer from the local client and it refused to work until I completely removed the driver from Windows and rebooted to a "clean slate".
So the only other thing I can think of at this point, short of finding a guru that eats assembler for breakfast and reads debugger output like the comic section of the paper, is that active directory is doing something strange. We are running AD 2003, and are supposed to be upgrading to AD 2008 in the near future (meaning "soon"), and our current installation was upgraded from AD 2000 a few years ago. I don't know of any issues with our AD configuration (errors in logs, etc.) but that doesn't mean there isn't something going on.
Can AD be causing something like this with printer configurations on our network? Anyone even HEAR of anything vaguely like this in your network or other people's networks?