piideleteJune asked a question.
I am curious to see how others do this.
If you have a vCenter server with 4 hosts and you point the SIM at the vCenter and it pulls back the 4 hosts details. You install snow agents on the guests running on those hosts and SLM links everything nicely.
Now if you do the same for Hyper-V and point the SIM at a VMM that has 4 full blown Windows servers running the Hyper-V role you get the VMM and the Hosts reporting in to the DCC section of SLM. You then also install the agent on the Hosts as they are windows servers and the guests running on them too.
This leads you to get duplicates of the Hosts as Search for Computers lists both them as coming from the SIM and the Agents. SLM doesn't link them all together in the searches or reports and only does this in the DCC view.
Is there a best practice like not installing the agent on the Hosts or is this a Ideas Board for SLM to handle this quite normal situation better?
Hey Joe
Ever get anything back re this? Also having this same issue.
Rely on just the SIM and loose all the agent details or loose all the datacentre relationships seem to be the only choices
No others commented on this and didn't get around to logging it as an issue, so suggest we both do so as it seems a flaw in the product when Hyper-V is used.