My problem is exactly this same as described here: • I have few Windows 2008 R2 (no SP1) servers in remote offices, mostly in Domain Controller, and many of them have problems installing ANY printer drivers. • following errors show up in Event Log when adding printer driver under Print and Document Services/Print Management/Print Services/ /Drivers OR trying any other way to install drivers: EventID 215: Installing printer driver - failed, error code 0x57, HRESULT 0x80070057.

See the event user data for context information. EventID 215: Installing printer driver Canon iR C2380/2550 PCL6 failed, error code 0x0, HRESULT 0x80070057.

See the event user data for context information. EventID 215: Installing printer driver Canon iR C2380/2550 PCL6 failed, error code 0x490, HRESULT 0x80070057.

See the event user data for context information. • in this particular server case this is problem with Canon iRC 2380i printer with Canon Generic PCL6 Driver, but it seems to apply to any driver and any printer (tried different drivers, different versions, PCL, postscript, etc) • I'm using 64 bit drivers that should be working on this platform. Any help will be appreciated. I found a possible fix on what I first thought would be an unrelated site.

You can use the Print Management snap-in to automatically detect all the printers that are located on the same subnet as the computer on which you are running Print Management, install the appropriate printer drivers, set up the queues, and share the prin.

The problem they described was replacing a previously unsigned print driver package with a new one. Tomabo Mp4 Downloader Pro License Key. It kept failing with the same 0x80070057 error that we were seeing on some user machines using HP's UPD for x64 Windows 7 PC's.

We dumped the output from pnputil to a file, found the OEM package assisted with HP and then deleted it as described in the article. As soon as we did that, the point and print option cleanly installed the driver without a problem.

I'm not sure how this manifests itself, as we've got a standard image and we're ghosting it - but as a fix, this seemed to work well. While its not much help, I have the same printer model installed on the same windows revision without problems. Since you have the same problem on several machines at once then it would seem likely it's caused by active directory or a group policy. Try taking a look at the security on HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Print. You should have: system full control administrators full control users read access TrustedInstaller Full access The same goes for HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Ports except that its: creator owner special permissions system full control administrators full control users read access The symptoms are odd enough that I would suspect that this will qualify for a free incident with MS. Unless you've been installing any special thinprint type apps. Thanks, last night I've discovered that printer install ok on a server that is not a Domain Controller (funny enough we have ~10 remote offices where DCs works as print servers;) - so I started thinking what's the difference between DC and standard server?

The only answer is GPO. I've been comparing GPOs on DC and normal system, but can't see anything that would lead to my problems. Also I've checked registry permissions as you advised - there are this same on DC and standard box, and this same as yours.

I wonder what else can impact driver installation.:/ – May 25 '11 at 7:08. I had the same issue described in the OP when trying to add any print drivers to a 2008 R2 domain controller, but fixed it in a different way. I found that running the command 'net localgroup Users' on my domain controller returned no members. To fix, I ran the following two commands: net localgroup Users Interactive /add net localgroup Users 'Authenticated Users' /add I found this solution under Method 2 on a MS knowledge base article to fix another symptom the server was exhibiting: Hope this helps someone else as it took me ages to get to the solution.