

Lowercase full domain name: contoso.local For more information about SIDs, see Security identifiers.Īccount Name : the name of the account that requested the “modify registry value” operation.Īccount Domain : subject’s domain or computer name. When a SID has been used as the unique identifier for a user or group, it cannot ever be used again to identify another user or group. The system uses the SID in the access token to identify the user in all subsequent interactions with Windows security. Each time a user logs on, the system retrieves the SID for that user from the database and places it in the access token for that user. Each account has a unique SID that is issued by an authority, such as an Active Directory domain controller, and stored in a security database. Note A security identifier (SID) is a unique value of variable length used to identify a trustee (security principal). If the SID cannot be resolved, you will see the source data in the event. Event Viewer automatically tries to resolve SIDs and show the account name.

Note: It may also be necessary to gather logs from remote computers with which the computer being analyzed was communicating, if the cause of delay is suspected to be network-related.This event generates when a registry key value was modified. To see these long events in the procmon log do the following: Look for queries that take a long time to complete that will mean a thread is stuck, occupied or tied up.

When examining the ProcMon logs, what to look for?ĪutoProtect queries file information frequently to get file attributes, size, and times. To restore AutoProtect to its normal altitude: Save the Log as Native Process Monitor Format (PML) You can verify that the SRTSP altitude has been changed by running the FLTMC command-ĥ. In regedit, change the following value Key : Also note that Tamper Protection may need to be disabled to make registry changes.ġ. Please note that very large amounts of data will be collected: if possible capture only the events that occur during the slow-down. If disabling AutoProtect resolves a performance-based issue, then gather a ProcMon log when AutoProtect is disabled and a second log when AutoProtect is enabled.
