J’essaie de analyse which group policies are inflating the bootup time.
What’s the best way to do so?
Something like gpresult including timestamps/periods would be really helpfull!
Source : [Server Fault](Archived MSDN and TechNet Blogs | Microsoft Learn](Archived MSDN and TechNet Blogs | Microsoft Learn)
One technique is documented here:
How to enable GPO logging on windows 7 /2008 R2
It is similar to the User Environment Debug Logging in Windows XP/2003.
Click Start , click Run , type regedit , and then click OK .
Locate and then click le suivant registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion
On the Edit menu, point to New , and then click Key .
Type Diagnostics , and then press ENTER.
Right-click the Diagnostics subkey, point to New , and then click DWORD Value .
Type GPSvcDebugLevel , and then press ENTER.
Right-click GPSvcDebugLevel , and then click Modify .
In the Value data box, type 0x30002 , and then click OK .
Exit Registry Editor.
At a command prompt, type le suivant command, and then press ENTER:
gpupdate /force
View the Gpsvc.log file in le suivant folder:
%windir%\debug\usermode
Si vous are wondering what the hex numbers are on the left, those are thread id’s.
Si vous have multiple domain controllers and a distributed network, pay attention to le domaine controller that the GPO is processed from. It’s not unusual to pull a GPO from a domain controller that is different from le domaine controller that performed authentication, or a domain controller on the other side of the planet.
J’ai also found that Microsoft Network Monitor 3.4 provides useful information. Typically you would be able to observe each GPO as it is being processed, with a timestamp.