Jan 19, 2017 - Windows Management Framework 5.1 includes updates to Windows PowerShell, Windows PowerShell Desired State Configuration (DSC),. New Windows Server 2012 R2 Standard in the environment. Added print services to it and added five HP printers to it and shared them. Also deployed the printers via group policy. Clients are running Windows 7 Pro x64. The group policy fails to install the printers (error 0x00000002). We get the same error when trying to manually add the printer from the client side. From Event Viewer: Group Policy was unable to add per computer connection. Error code 0x2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server. Any ideas on troubleshooting this? JMcKenzie, I would pick one client and start by removing the print driver for the printer you are trying to install. To delete drivers on a client you should use the built-in PrintUI-program. Running the following command will take you to the appropriate setting: printui.exe /s /t2 You can then delete the driver for the printer you are installing. Try to reinstall/redistribute the printer and make sure it succeeds. ![]() Saifee masjid namaz azan al. If the issue persists I recommend deleting the following registry-key and restarting the Printer Spooler-service: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager PendingFileRenameOperations Also make sure a valid Windows 7 print driver is installed on the server so it can hand it out to the Windows 7 clients. Cheers, Curt Winter Certified Microsoft Professional Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied. If you found my post helpful, please mark it as the answer. Curt, Thanks for your ideas. Gratis download font shin go pro.ttf. One of the printers is an HP LJ 4700. When I run the printui.exe executable it doesn't show any drivers for that printer model on the client machines. The other four printers that I'm trying to add currently use our existing Windows Server 2008 R2 server. So, those drivers do exist on the clients. When I try to delete them, printui.exe tells me that it can't because they are in use. There is no registry key PendingFileRenameOperations in the couple of clients I've checked. The server is sharing Type 4 - User Mode, PCL6 Class Drivers for the various printers. Best regards, -John McKenzie.
0 Comments
Leave a Reply. |