Windows 10: How does Windows deploy printers via GPO? What is GP actually doing?

What does Windows actually do when it deploys printers via GPO? What is this process and how is it being done? Can we log this process to see where it might be failing? I've looked all over the internet for this and can't find a straight answer. There MUST be a way to troubleshoot issues with deploying printers via GPO, or a way to log this process.For context - Yes I know about PrintNightmare. The drivers are not the issue, the drivers are already on the computers. I confirmed this by navigating to the print server via UNC path and clicking on the printer object itself, it will inst

:)

 

Windows 10 GPO Printer Add issues

A total shot in the dark since this is a very specific issue to our environment, but here it goes...

A little background on this issue, my school district is moving to windows 10. We partially deployed Windows 10 LTSB to some of the labs in the district. We are seeing sporadic issues with our Group Policies deploying printers. We have below 50% success rate with printers actually installing on the Windows 10 client machines.

Thinking it was an issue with LTSB, we downloaded and installed Windows 10 Education version 1709 on a test VM and joined it to the domain. I then applied GPO’s from 4 different servers. 3 Physical Server 2012 R2 servers and the original problem Server 2012 R2 VM Server.

What I found was the same inconsistency after rebooting the Win 10 Edu Test VM. I am getting the same Event 513. See below:





I am 100% sure the naming is right because I can manually add the same printer using the \\SERVER\FerLib path. All printers that fail to add have the Event 513. I am also going to post this on other forums.

We are only seeing this on student accounts which are domain guest accounts, meaning their profiles are non-permanent. We do not have the option to turn them into regular users per district policy. If you need more info that I omitted please let me know. We are getting desperate.

Thanks!

 

I loathe printers and HP rant

That old printer on network: the installation progress was like this. I just need to find its IP address on the LAN and Windows asked what kind of printer it was. I found the brand on the list of hardware and selected it. That was all that needed to be done.

As for the Brother printer. Obviously, I needed to let it connect to the wireless network and then it simply showed up on my Win 10 laptop. I didn't need to do anything.

 

Network Printers deployed via GPO to computer randomly stop showing for users

We have had printers deployed via GPO from a print server for several years now. We push the policy to computer not user, so no matter who logins the printer will be there. Suddenly we are having computers randomly not show the printers at the client.
We are all win10 clients on a 08 domain level with a 2012 print server. We are using the generic HP PCL 6 driver, have had no issues until about August when printers randomly show and dont show for user. ex: user A logs on printer shows, may work for muliple
logins and may not. Relogin, reboot of client all have varying effects. We checked our policies, Auth Users have Read, DomainComputers have Read. We have gone through logs and finding typical errors that lead no where. Any others out there have recent issues
with GPO deployed printers?