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.
Voila!
