So I've had no end to the issues experienced when trying to utilise GPP Printer deployment and synchronous logons (Wait for Network enabled). Over the years with Windows 7 and 2008 R2 I have had numerous times where there are just completely unexplained delays in logging on where the client is stuck on "applying group policy printers". At this stage there are no corresponding entries in the Event Logs. I have enabled trace logging of the CSEs via Group Policy and monitoring the user log at this time again shows nothing. There is literally an unexplained gap in processing after applying a printer or all printers of minutes at times with no entries or explanation for the gap.
This behaviour does not change if the client has the drivers already installed. This fact is what drives me the most crazy - it's as if it's stuck installing something or doing something, but why should it have to install a thing if the drivers are there... just connect and move to the next printer!
This is a very serious problem and my opinion based on years of dealing with this BS behaviour is most likely:
- GPP Printers are just broken on Windows 7 and 2008 R2 - When I can instead utilise a VBS script which applies the same "point and print" connections to a user when logging in, INSTANTLY, but applying the exact same setting via GPP locks a client up for 30 minutes on logon what would you think?
- Something related to UAC. These problems do not seem to occur on XP. But then the issues still occur when "Elevate and don't prompt (UAC Disabled)" is enabled. Perhaps there is a prompt or something stalling the logon process.
- The requirements for correct settings and such are beyond too convoluted. There are all these settings and BS related that also need to be set for GPP Printers to work correctly usually - Allow non administrators to install drivers, disable Point and Print Restrictions etc. To be very clear it is my opinion, after having worked with GPP Printers for years now, being a Server and Windows 7 MCITP and MCSA (2012) and having done a lot of study on Group Policy to try and solve this BS that the default should be that no matter what, by DEFAULT, when a printer is scoped by GPP Printers it should ignore all other restrictions and apply.
- The printer CSE is broken or does not work correctly in a Windows 7/2008 R2 environment.
Microsoft need to investigate this issue, it is a very serious issue, whether is be an actual bug or a complete lack of a clear way to utilise this feature from them. They need to make this feature work, correctly.
I am very happy to provide MS or anyone else as much information about this issue as I can. As said I have event logs, I have trace logs I can provide. I want to work with MS to fix this issue as I believe it to be one of the biggest problems with Windows currently.