B
Bigby
Guest
Hi All,
I have an issue where on certain Windows 10 machines Group Policy processing slows to a crawl.
It can take anywhere from 8 minutes to 21 minutes from entering the User ID and Password until you receive the Desktop (normally, it only takes about one minute).
I have turned on Group Policy verbose logging and noticed that during a fast boot, several operations happen within 1ms and on a slow boot those same operations take a little over 1s or longer (see graphics below, both are from the same machine):
<Edit: I will upload the pics as soon as I am able. My account needs to be verified and after following the directions to do so I still cannot post with embedded pics>
Here is what I know and have tried:
- The problem started around July 8, 2019.
- The Windows 10 images are all the same, imaged via MDT/WDS and all are Windows 10 Enterprise - 1803.
- It is very random, only about 5 machines and it doesn't happen all the time to those machines.
- The Group Policies have had only minor changes and the slowness hasn't coincided with GP changes.
- The Forest Functional Level is "Windows 2008 R2".
- There is only one location (so far) that is experiencing the issue and that location has four DCs (mix of Win2k8 R2 and Win2016). No updates to the DCs have been performed since we started seeing the issue, the DCs have been rebooted within that time and we have seen the issue when the Win 10 PCs have connected to any of the DCs.
- Nothing (that we know of) has changed in the environment.
- The Win 10 machines are receiving critical updates and Defender updates automatically.
- I have used Windows Performance Reporting & Windows Performance Analyzer to gather boot traces but I haven't found a way to get it to tell me what the parameters are for a particular SVCHOST entry so I can't tell which one is the Group Policy Client (gpsvc).
- I have seen that Windows Update is running during the time when the login is slow (via Event Viewer).
Has anyone else experienced this issue? Can anyone suggest further troubleshooting steps?
Any help is appreciated!
Thanks,
--Brian
More...
I have an issue where on certain Windows 10 machines Group Policy processing slows to a crawl.
It can take anywhere from 8 minutes to 21 minutes from entering the User ID and Password until you receive the Desktop (normally, it only takes about one minute).
I have turned on Group Policy verbose logging and noticed that during a fast boot, several operations happen within 1ms and on a slow boot those same operations take a little over 1s or longer (see graphics below, both are from the same machine):
<Edit: I will upload the pics as soon as I am able. My account needs to be verified and after following the directions to do so I still cannot post with embedded pics>
Here is what I know and have tried:
- The problem started around July 8, 2019.
- The Windows 10 images are all the same, imaged via MDT/WDS and all are Windows 10 Enterprise - 1803.
- It is very random, only about 5 machines and it doesn't happen all the time to those machines.
- The Group Policies have had only minor changes and the slowness hasn't coincided with GP changes.
- The Forest Functional Level is "Windows 2008 R2".
- There is only one location (so far) that is experiencing the issue and that location has four DCs (mix of Win2k8 R2 and Win2016). No updates to the DCs have been performed since we started seeing the issue, the DCs have been rebooted within that time and we have seen the issue when the Win 10 PCs have connected to any of the DCs.
- Nothing (that we know of) has changed in the environment.
- The Win 10 machines are receiving critical updates and Defender updates automatically.
- I have used Windows Performance Reporting & Windows Performance Analyzer to gather boot traces but I haven't found a way to get it to tell me what the parameters are for a particular SVCHOST entry so I can't tell which one is the Group Policy Client (gpsvc).
- I have seen that Windows Update is running during the time when the login is slow (via Event Viewer).
Has anyone else experienced this issue? Can anyone suggest further troubleshooting steps?
Any help is appreciated!
Thanks,
--Brian
More...