User guide

the account exists in the local administrators group.

Please see the Performance Advisor: WMI or Registry Access KB article for more information and

configuration details about using pass-through authentication on Windows Vista and higher:

Important: SQL Server authentication can be used for any watched Event Manager SQL Server

connection using a connection's "Monitoring Service Connection Properties" context menu

item. This can eliminate the need for pass-through authentication if SQL Sentry's performance

monitoring isn't being utilized to collect Windows performance counters from the target servers,

and if you aren't monitoring the server with Performance Monitor or Event Manager Windows

Task Scheduler.

If performance monitoring is required either via SQL Sentry Performance Advisor or you need to

watch a Windows Task Scheduler, pass-through authentication may still be required.

9.4 Least Privilege General Performance Monitoring

For an overview of the performance monitoring features available with SQL Sentry Event Manager

please see the Schedule Performance Monitoring topic in the SQL Sentry User Guide. It is possible to

collect performance counter data in SQL Sentry Event Manager without Windows Administrator

privileges.

First, you will need to add the SQL Sentry Monitoring Service account to the Performance Monitor

security group of the machine on which the Monitoring Service is installed. Next, for the service to be

able to access the performance counters of your watched connections remotely you will need to grant

the service account read access to certain registry keys. On each machine that you wish to collect

performance counters, follow the steps below.

1. Navigate to the winreg key located at the following path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

2. Right click on the winreg key and select Permissions. Add the SQL Sentry Monitoring Service

account.

3. Restart Windows

NOTE: For general information on editing the Windows Registry see Microsoft KB article 256986.