On some machines,
AeXMetricProv.exe consumes high CPU usage. This behavior is most prevelant on, but not limited to, Domain Controllers.
This condition occurs on machines with excessively busy NT Event Logs. Domain Controllers are most likely to experience this issue because their NT Event Logs, the
Security log in particular, are typically busier than other Windows machines.
If any NT Event rules are enabled in a Monitor Policy, the Monitor Agent will then read all NT Events which occur on a machine. This architecture is not typically problematic unless the NT Event Logs are excessively busy (e.g. thousands of events per minute).
This is a known issue and has been submitted to development.
There is no direct resolution to this behavior at this time. This article will be updated when this issue has been resolved in a future release.
To aleviate the CPU consumption, separate all Domain Controllers (and other machines with excessivley busy NT Event Logs) from the existing Monitor Policies. Clone the existing enabled policies, remove all NT Event based rules, and apply the policies to only the effected machines. This will allow all other monitoring to occur except for NT Event monitoring which will resolve the high CPU consumption of the Monitor Agent.
Monitor Solution for Servers SP4 7.0.7416
ID: ETK 1998414
Etrack (Symantec) database
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Currently server is down.
Didn't find the article you were looking for? Try these resources.