Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1562
  • Last Modified:

NTFRS and LSASS page fault per second threshold Active Directory 2003

I'm in the process of setting up critical threshold levels via openview management engine alerting to monitor our 2003 AD domain controller health and performance. What is the recommended setting to be considered as critical for NTFRS page fault/sec and LSASS page fault/sec. Any ideas?
0
mmoya
Asked:
mmoya
  • 2
1 Solution
 
ChiefITCommented:
There's no way of telling. Sustained issues with page faults per second may indicate an error, but there is no way to quantify what would be an error and what wouldn't.


According to Technet:
http://technet.microsoft.com/en-us/library/cc768048.aspx#XSLTsection131121120120

""Memory : Page Faults/sec. This counter gives a general idea of how many times information being requested is not where the application (and VMM) expects it to be. The information must either be retrieved from another location in memory or from the pagefile. Recall that while a sustained value may indicate trouble here, you should be more concerned with hard page faults that represent actual reads or writes to the disk. Remember that the disk access is much slower than RAM.""
0
 
ChiefITCommented:
Also note that if you have a memory leak and a real problem, you will either end up with a rebooting computer, and/or Blue Screen of Death. That's usually when people hunt down and fix the issues of page faults.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now