The Configure OS Metric Collection window of the Add Servers wizard lets you select which type of operating system metrics collection you want to use or whether you do not want to collect any OS metrics from a SQL Server instance. SQL Diagnostic Manager uses OLE automation or a direct connection to the Windows Management Interface (WMI) when collecting OS metrics and service status data on clustered SQL Servers. Collect Operating System data using direct WMI is selected by default when adding a new SQL Server instance.

Select Do not collect Operating System data if you do not want to collect these statistics. For additional information about OS metrics collection, see Configure OS metrics monitoring.

After selecting your method for OS metrics collection, click Next to continue.

Access the Add Servers wizard

You can open the Add Servers wizard from the SQL Diagnostic Manager Console menu by selecting File > Manage Servers, and then clicking Add in the Manage Servers window.

Permissions necessary for direct WMI collection

It is preferred that the WMI user is a local administrator on the monitored SQL Server instance. However, if you do not want to grant administrator access, use the following steps to configure remote WMI access in Microsoft Windows:

1. Add the user account to the Performance Log Users and Distributed COM users groups.
2. Grant privileges to WMI.

You also may need to add the WMI user account to the following policies:

• Act as part of the operating system
• Log on as a batch job
• Log on as a service
• Replace a process level token

For more information about using a direct WMI connection, see the Microsoft document, .

Disabling OS metric collection

SQL Diagnostic Manager does not require OS metrics collection. However, if you disable this feature, SQL Diagnostic Manager ceases to collect OS metrics and does not raise any previously-associated alerts. You can easily enable OS metric collection at any time if you decide that you want to continue collecting these metrics.

Using direct WMI when the collection service is on a different domain than the SQL Server

In environments where cross-domain trust security is enforced, data from asynchronous collection is not returned from an untrusted domain to a trusted domain. As a result, the collection service does not receive the data.

If you select Collect Operating System data using direct WMI and the machine used for your collection service is in a different domain than your monitored SQL Server instance, you must make some configuration changes on your collection service machine. If you do not make these changes, change your OS metrics collection to Collect Operating System data using OLE automation if you want OS and disk statistics plus the auto discovery of mount points.