mmuza
asked on
OpsMgr 2007 R2 dynamic group membership
Installation consist of scom 2007 r2 on windows 2003 r2 with one management group. About 15 management packs deployed and about 3000 agents. All in all it is working good but recently I stumble upon an issue with populating dynamic groups. Although I've excluded members (windows computer entity) from a dynamic group (either by exclude tab or by query) it doesn't seems to work.
In view members entity isn't there but I have health state view which is narrowed to that group and that computer is still showing there. By querying the db I can see that computer is still member of that group although view members doesn't shows it.
I've tried creating new groups with different kind of queries and behavior is the same. Even tried creating groups in different management packs. All the same. Waited for interval to pass, the same.
Any ideas what to look at next?
In view members entity isn't there but I have health state view which is narrowed to that group and that computer is still showing there. By querying the db I can see that computer is still member of that group although view members doesn't shows it.
I've tried creating new groups with different kind of queries and behavior is the same. Even tried creating groups in different management packs. All the same. Waited for interval to pass, the same.
Any ideas what to look at next?
Can you post your dynamic inclusion and exclusion queries/objects so I can have a look at what you've setup?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
yeah, i'd expect that query to work fine. Your state view is just windows computers in the group or something more complex?
from that blog entry did you try *just* running the powershell cmdlet Kevin mentions "remove-disabledmonitoring object" to see if that made any difference to your views? maybe there's something hinky floating around in there that never quite got deleted properly out of the database.
also in ref to the blog entry, is your exclusion a hyper-v host?
from that blog entry did you try *just* running the powershell cmdlet Kevin mentions "remove-disabledmonitoring
also in ref to the blog entry, is your exclusion a hyper-v host?
ASKER
I went through the mentioned post and issue is resolved now.
no objections.
ASKER
Technet article was the solution.