Data Execution Prevention (DEP) is a relatively new feature of both Intel and AMD hardware that is supported beginning with Windows Server 2003 Service Pack 1 and Windows XP Service Pack 2. DEP is a set of related hardware and software features designed to make it more difficult for malicious programs to execute sensitive code [...]

NTSMF version 2.4.6 and higher utilizes a facility that allows you to specifically exclude Performance Library DLLs that cause collection problems. Instructions to exclude specific Performance Library (Perflib) DLLs are contained in an optional configuration file named DmPerfss.cfg that is stored in the NTSMF root directory. The format of theDmPerfss.cfg file, which use a simple XML [...]

NTDS is the main source of information on Active Directory traffic to and from Domain Controllers. It contains a ton of interesting looking counters.
Unfortunately, there is not much written that documents AD performance issues and how to use these counters. This TechNet overview article is a good place to start. There are two main objects [...]

The short answer is that Intel knows what these things means, but does not publish a mapping anywhere of how these internal names correspond to external products. The closest Intel comes is this document at http://www.intel.com/design/chipsets/mature/mature.pdf, which does not mention either Family or Stepping names.
In semiconductor fabrication, “stepping” refers to the chip manufacturing process which [...]

Yes.
By design, the Performance Sentry Collection Service (dmperfss.exe) is installed to run under the built-in LocalSystem (SYSTEM) account. This built-in account, which most services use, has the authority to perform almost any internal function on the local machine. However, the LocalSystem account has no built-in facilities to access secure network resources, such as shared network [...]

Situation:
Performance Sentry Administration is used to assign Data Collection Sets (DCSs) to machines running the data collection service.  An administrator has two options when assigning data collection sets to machines: The first one is called a Registry DCS and the second a File DCS. The Registry DCS parameters are written to the Registry key: “HKEY_LOCAL_MACHINE/SOFTWARE/DemandTechnology/PerformanceSeNTry/CollectionParameters”

These [...]

Logical disk information containing “HarddiskVolume…” usually indicates an unformatted partition. Knowledge Base article (Q260834) describes the ‘HarddiskVolume’ label as a volume that has been mounted, but not assigned a drive letter. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;q260834
There is another MS KB entry that specfically discusses “HarddiskDmVolumes” names. See
http://support.microsoft.com/?kbid=274311. This KB article explains that after you convert a hard [...]

Once Performance Sentry is installed and you are able to collect and process Windows performance data on a consistent basis, it is a good idea to familiarize yourself with some of the more important data elements that you will be collecting with Performance Sentry. There are several ways to approach this.
To help you get started, [...]

OK, you asked for it. If you do not need to gather Module identification information, you can run the Performance Sentry collection service under a User Account. You can only set the Collection Service to run under a User Account manually using the Services Administrative Tool, which is illustrated below:

To function correctly, the User Account that [...]

No, to function properly the Performance Sentry collection service should be set up to run under the LocalSystem (or SYSTEM) account. The LocalSystem (or SYSTEM) account is a built-in account used by many services with an extraordinary level of privileges for accessing local system resources. These include privileges that cannot be granted to any User [...]