How I worked with Bob to improve Group Policy logon times by 15-30 seconds.
Let me jump to the end of the story: I didn’t really do anything here.
Bob did all the hard work. I did POINT Bob in the right direction though and get him thinking about the problem.
Bob came to me with the following query: “We played with deploying printers via GP and ultimately decided not to. However, despite removing the deployed printers from GP, every machine still goes through the “Applying Group Policy Printers policy” step even though there are no printers deployed that way and I can’t figure out how to get rid of it… On some machines, it’s just a few seconds delay, but on others, it’s upwards of 30 seconds and I’d really like to get rid of it. Any ideas?”
I THOUGHT Bob was talking about Group Policy Preferences Printers. But he wasn’t. He was talking about “Deployed Printers.”
This is totally different, and honestly, one of the parts of GP which isn’t my favorite.
Bob found the golden ticket all on his own. Here’s what Bob replied:
“I figured it out from this article:
The relevant info was:
While you ‘re in adsiedit, highlight the GPO node itself, “properties”, look for the attribute “gPCUserExtensionNames”. This is an array of an array of GUIDs.
Copy the entry to notepad, identify a block in square brackets (“[]”) that starts with the GUID {8A28E2C5-8D06-49A4-A08C-632DAA493E17} and remove the whole square brackets block. Then, look simply for the GUID {180F39F3-CF17-4C68-8410-94B71452A22D} (shouldn’be present, but better be careful) and remove just the GUID.
This cleans up the AD part of your GPO and afterwards, deployed printers will not be processed anymore during user gpo refresh.”
Logins are now 15-30 seconds faster.
Thanx for the help! ?
”
So the moral of the story is.. if you’ve ever tried “Deployed Printers” and then.. well, stopped… then this could be something that helps you out if logon times have increased.
Comments (0)