Hi, I have been doing a weekly SQL query to try and find any high number of events I get in my SCOM environment.
One of the events I have stumbled across is 31901 (The registry probe could not connect to the registry of the computer <name>) which comes from the Collect Registry Probe Module Events
I have read a couple of previous suggestions on the forum and upon checking I found two different scenarios. For a couple of servers I checked the health and it looked like they had RPC issues. A restart got rid of these problems.
However the ones left seem to have something in common. They relate to hosts referring to SQL instances/clusters. So the logging computer is the host and the probe cannot to the registry of the virtual computer. In other words the computers that cant be connected to are all agentless and show as managed by the logging computer under Agentless Managed
If I log onto the host with my SCOM action account and run something like reg query against the virtual instance I get ERROR: The network path was not found. I can ping the instance fine though. I dont really understand how these instances work but I presume they dont have services or a registry as such. Therefore is this normal or is there any way I can get rid of the events? I dont really want to get rid of the rule itself as it did help me find a couple of RPC issues. I could override for that host if this is normal and how it should work.