Hello community,
For some employees, we have the problem that the total GPO processing take an extremely long time.
The processing of the GPO components (Group Policy Environment, Registry, Services, ...) takes up to 21 seconds (screenshot at the bottom of the post).
The screenshot is taken from Group Policy Result Wizard.
This error is reproducible (while running gpupdate) and also occurs if the user uses a different domain controller.
The error does not happen to everyone - not even with users and computers that are in the same AD OU.
To log the error, I have already created the registry entry GPSvcDebugLevel.
https://social.technet.microsoft.com/wiki/contents/articles/4506.group-policy-debug-log-settings.aspx
I have added an excerpt from the log file when processing the “Group Policy Envorinment” (gpsvc.log).
Here you can see that step takes just under 21 seconds.
GPSVC(1ed0.2dc8) 09:03:47:804 LogExtSessionStatus: Successfully logged Extension Session data
GPSVC(1ed0.2dc8) 09:03:47:817 ProcessGPOList: lpGPOInfo->lpGPInfoHandle->dwExtnCount is 2 for Group Policy Environment.
GPSVC(1ed0.2dc8) 09:04:09:000 IsSecureCachingDisabled: secureCachingState = 2.
In order to expand the log additionally, I configured further logs via GPO.
Computer Configuration> Administrative Templates> System> Group Policy> Logging and tracing
Here I have set and activated the event logging to Informational, Warning and Errors for all available settings.
In this log (computer.log) you can see that these steps are the time-consuming steps.
2021-06-17 09: 03: 47.825 [pid = 0x1ed0, tid = 0x2dc8] Licensing subsystem initialized.
2021-06-17 09: 03: 51.927 [pid = 0x1ed0, tid = 0x2dc8] User information initialized.
2021-06-17 09: 04: 08.960 [pid = 0x1ed0, tid = 0x2dc8] Variable% ComSpec% = "C: \ WINDOWS \ system32 \ cmd.exe"
What else can I do to narrow down the error or to fix it?
Attachments:
106536-computer.log
106555-gpsvc.log