Page History
...
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. For additional information about OS metrics collection, see Configure OS metrics monitoring.
| Tip |
|---|
SQL Diagnostic Manager retains your previous settings upon upgrade if OLE automation is the default for your monitored SQL Server SQL Server instance. |
After selecting your method for OS metrics collection, click Next to continue.
...
You can open the Add Servers wizard from the SQL Diagnostic Manager Console menu by selecting 
>Manage Servers, and > Manage Servers and clicking Add in the Manage Servers window.
...
SQL Diagnostic Manager does not require OS metrics OS metrics collection. However, if you disable this feature, SQL Diagnostic Manager ceases to collect OS metrics 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.
...
- 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,
| Newtablink | ||||
|---|---|---|---|---|
|
...
In environments where cross-domain trust security is enforced, data from the 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.
...