these are performance counters i discovered myself. they are default counters for xp pro sp2 + .net framework 2.0:

each of these keys is located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
each line represents a separate key.

.NET CLR Data\Performance
.NET CLR Networking\Performance
.NET Data Provider for Oracle\Performance
.NET Data Provider for SqlServer\Performance
.NETFramework\Performance
ASP.NET\Performance
ASP.NET_2.0.50727\Performance
aspnet_state\Performance
ContentFilter\Performance
ContentIndex\Performance
ISAPISearch\Performance
MSDTC\Performance
PerfDisk\Performance
PerfNet\Performance
PerfOS\Performance
PerfProc\Performance
PSched\Performance
RemoteAccess\Performance
RSVP\Performance
Spooler\Performance
TapiSrv\Performance
Tcpip\Performance
TermService\Performance
WmiApRpl\Performance

please share any performance counters you know of that aren't on the list.

Edited May 9, 200620 yr by ophiel

Why bother? Just use ExCtrlst.exe from Microsoft.

GL

because this can be done silently with no required user interaction and with no need to install an external program.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\

.net framework 1.1 counter:

ASP.NET_1.1.4322\Performance

vmware counter:

VMware\Performance

Edited May 25, 200620 yr by Ophiel X

Not to sound stupid, but performance counters?

Matt

because this can be done silently with no required user interaction...

True, but on different installation they are different (for example, some are missing on nlited source). And you can create problem if you 'create' a service. There must be some check if the service exists.

...and with no need to install an external program.

You can extract ExCtrlst.exe from the .msi file. It's all that's needed.

GL

disabling performance counters for non-existant services does NOT create said service and has no negative impact at all.

besides, it is quite easy to check for existence of those services from a script if i wanted to.