This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 10%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
I have configured a Windows Client as an agentless computer (actually a Windows 10 client). Its discovered and goes green in SCOM as a Windows Computer.
Only ping is enabled at this point.
I'm trying to enable an alert rule targeting Windows Computer, disabled by default and enabled to above computer using an Override.
However, it doesn't seem to get enabled.
Is this possible using agentless or do I have to install an actual agent on the client computer?
Sorry, target was "Windows Computers"
Amyway, I did get it to work eventually. But I didn't have success with my Override strangely enough.
However, probably not going to use Agentless anyhow since it poses some other problems (like not showing the Event description for the alert in a proper way).
Hi,
this should be possible of course, but it also depends on the MP you are using and how the rule has been created/configured/targeted. Did you create the rule or is it defined within a vendor MP?
Did you also cover this one:
Agentless Monitoring in Operations Manager
and in particular
Agentless management of a computer will not work if the agentless-managed computer and its proxy communicate through a firewall. A management server will not collect descriptions for events or publishers that are present on an agentless managed computer but are not present on the proxy agent.
Regards,
Stoyan
Just a custom rule targeting Windows Computer in a newly created blank MP
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 31%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
It really depends on what the rule does and how it does it, so you'll have to be more specific than "a custom rule" ;)
What you need to understand here is that for agentless monitoring, all the workflows are running from the Management Server.
Which mean the only workflows that can work are the ones that are capable of connecting remotely to the monitored agent.
For example, a performance collection rule should work since the datasource is connecting to wmi, so as long as the proper permissions are granted and the proper network ports are opened it will work just as fine remotely as locally.
It shows up when I just targeted All Windows Computers. Will look into why it didn't work with the Override
Hi,
You can also check the events in the Operations Manager event log on your management server(s), maybe you will find a clue there.
Regards,
Stoyan