Usually this is happening When you decommission a VM with SCOM agent inside. SCOM sometimes keeps the agent record for a while and even when VM is no there anymore, the relationship that we make between in-guest object and a VM keeps the VM object alive, this is when it just attaches to All management servers resource pool, which means to any available SCOM server.
To workaround the issue, you can perform topology rebuild process in our web UI and then launch on-demand discovery of VM2Agent relationship with the following script:
- Code: Select all
$disc=get-scomdiscovery -name "veeam*VMware*VMContains*"
$RMS=get-scomclass -displayname "root*emulator" | get-scomclassinstance
$task=get-scomtask -displayname "*on demand*"
Start-SCOMTask -Task $task -Instance $RMS -Override $Override
We are still investigating different processes which could cause an object to become orphaned and hopefully we can come up with better solution. We would highly appreciate if you can tell us how the process of VM decomissioning works in your environment - are you uninstalling the SCOM agent as a part of this process?
Let me know if the issue still exists even after on-demand relationship rediscovery.