One of my customers is unable to deploy the Operations Manager agent to a portion of their estate for various complex reasons, and are exploring some alternative ways of using Operations Manager to manage both Windows and Linux, one of those options being using Agentless monitoring. Windows Operating System monitoring is disabled by default for the Agentless monitored servers though.
In order to enable monitoring, you will need to enable the discovery for the Windows Server Computers class for the Agentless Computers group. To do this, navigate to Discoveries, and scope your view to Windows Server. You should see only one discovery here (Discover Windows Server Computers)
Create an override for a Group:
Search for the Agentless Managed Computer Group (do not select the Agentless Exception Monitoring group)
Check the Enabled box (even if it is enabled by default)
Save into the appropriate MP, and wait about 10 minutes. You should now start seeing monitors populate in the health explorer.
And you will see some perf counters available in the Performance view
A few notes:
- Your default action account will still need local admin rights on the servers monitored agentless in order to read the event logs, performance counters, etc
- Ping needs to be available between the gateway/management server and the agentless monitored device
- Unlike agent-managed computers, there is no caching of data. If connectivity is lost, there will be gaps in reporting data. You also won’t receive heartbeat failures, only failed to ping alerts.
- There is a recommended limit of 60 agentless monitored servers per management group, and no more than 10 per management server/gateway – so this can’t be used to monitor the entire estate, but can help create some visibility.