Why do my group memberships for Windows Computers have machines that don’t belong there?

Here is a little tip if you find that your Windows Computer Groups (and state views scoped by groups) contain computers that should not be there.


Have you noticed that you have state views or Windows Computer Groups that contain servers that you don't expect?  Like Exchange Servers in your SQL Computers Group?  Or SQL Servers in your Exchange 2007 computer group?  Or maybe Hyper-V host servers in a LOT of your groups?  If so – you are probably running Hyper-V, and using the Hyper-V MP version 6.0.6633.0.

Have a look at the below example:  My SQL Management Pack “Computers” view – contains domain controllers, exchange servers… even XP clients… plus it also includes the Hyper-V host (VS3).




This can wreak havoc on your management group…. because we use groups of Windows Computers for Overrides, and for scoping console views. 


The good news is – there is a very simple workaround:  There is a relationship in this MP that we need to disable.  This relationship attempts to associate the Windows Computer objects of a guest to its host – however it doesn't work properly, and isn't necessary.


Open Authoring in the console.  Select “Object Discoveries”.  Scope to “Hyper-V Virtual Machine”.  Find the discovery named: “Hyper-V 2008 Guest Computer Relationship Discovery”




Create an override for this – “for all objects of class:  Root Management Server”.  Set this discovery to disabled.


Now that that is disabled – we need to run a little cleanup on aisle 7.  We have a nifty little cmdlet in the OpsMgr command shell – named remove-disabledmonitoringobject.  This cmdlet will basically remove any discovered objects – for any situation where they are explicitly disabled with an override on a discovery.  Since that is what we just did (disabled a discovery) this will quickly delete any discovered relationships which previously existed.




Now – when I look at my state views scoped to SQL Computers group – I only see SQL servers, AND – the Hyper-V host.  We don't want the Hyper-V host tho…..  apparently the cmdlet cleanup doesn't take care of those.  To resolve that membership – I generally bounce the HealthService on the Hyper-V hosts, and then the HealthService on the RMS, and in a few minutes they will be gone.





Comments (16)

  1. Kevin Holman says:

    Hey Tim –

    That is interesting – did you run the remove-disabledmoniotingobject?  Did this crash with an error after a long time – or did it complete and return to the command shell prompt?

  2. Kevin Holman says:

    By the way – this is all fixed in SCVMM 2008 R2 SP1.  It is ready for integration without issue.

  3. Kevin Holman says:

    It’s possible VMM does this – I will look into it.  What version have you implemented – the MP’s?

  4. Thanks for a great post Sir!!

  5. Kevin Holman says:

    Guys – I will try to find out whats happening here – but I have very limited resources available.  I strongly recommend that you post a newsgroup posting here on this issue:


    Also – you can file a bug at

    Both of those will help raise awareness for this issue.

  6. Kevin Holman says:

    Interesting.  It is possible yours are also there due to some other issue – do you have and monitor Vmware in this environment?  Did you bounce the healthservice on the RMS and Hyper-V hosts?  

    Some have reported having to uninstall the agent from the Hyper-V host – and delete it from the console, then reinstall it – to get this group membership to go away.  I havent seen that personally.

  7. Mark Verbaas says:


    Once again a great post and tip. Executed the steps right away to clean up the SQL Computer View.

    Keep it up!



  8. Tim Humphrey says:


    Thanks for the post this is something that has puzzled me for a while.  However, I performed the steps outlined in your post yesterday but I still see the Hyper-V hosts and all of the VM guests in the state views for SQL, IIS and Sharepoint. Anything else I should try?



  9. Tim Humphrey says:


    I did run the remove-disabledmonitoringobject cmdlet.  It ran for about a minute and then returned the to the shell prompt.


  10. Tim Humphrey says:

    I do not have or monitor any VMWare in this environment.  I did bounce the health service on the RMS and Hyper-V hosts.  I’ll try to remove the agent from the Hyper-V host and reinstall and see if that clears it up.

  11. Tim Humphrey says:


    I was seeing the same behavior in my Dev environment.  So I pulled the SCOM agents from the Hyper-V hosts in Dev and ran the powershell cmd.  I then rebooted both my RMS and MS and found that those computers still showed up in the IIS, SQL, and Sharepoint groups in the Authoring section.  I do have VMM 2008 R2 and I have performed the SCOM integration.  Thoughts?


  12. Tim Humphrey says:


    SCVMM 2008 R2 and the SCVMM MP version 2.0.4271.0

  13. Gee says:

    Hi Kevin,

    I also encountered same problem as Tim. I’ve tried step given by you but still not resolved. I also monitor SCVMM 2008 R2 and the SCVMM MP version 2.1.4271.0.

    It appear non related agent in SQL Server, MOSS and Forefront server.

    Do you have email ID for me to send out the attachment.

  14. Raphael Burri says:


    SCVMM integration unfortunately creates very similar and confusing results as it discovers VMM_to_HyperV and HyperV_to_guest relationships. Unlike the Hyper-V management pack that relationship discovery isn’t done inside the MP but through connectors. VMM writes those directly to OpsMgr’s repository.

    When VMM and OpsMgr are integrated, those relationships are automatically created.

    To my knowledge there is no way to control what exactly the integration connector writes to OpsMgr and what not.

  15. Hi Kevin

    I've disabled the Hyper-V –  Virtual Machine relationship discovery in Hyper-V MP as in your article

    but relationship was removed for only for the standalone Hyper-V hosts we have. All other hyper-v hosts that are part of a cluster the relationship it is not removed.

    I've ran many times remove-disabledmonitoringobject but reults is still the same.

    We have SCOM 2007 R2 CU5 and VMM 2008 R2 SP1. We have 4 Hyper-v clusters and 6 standalone Hyper-V hosts.

    Any ideas how to disable the relationship for those hosts that are in a cluster also?

  16. Hi Kevin I've fixed my issue:

    1. Manually uninstall all SCOM agents on all nodes part of a cluster.

    2. Remove the cluster name from agentless monitoring. If you can do it trough the SCOM console follow this article rickjury.blogspot.com/…/operations-manager-scom-2007-how-to.html

    4. Delete the nodes from Agent Managed views in Administration pane.

    3. Run Remove-DisabledMonitoringObject command in SCOM PowerShell. Wait 20-30 min.

    4. Install SCOM agents on all nodes.

    5. Add cluster name to Agentless monitoring.

Skip to main content