In the Deployment Health Checks there is a warning if you have a policy targeted against a manual or automatic group.
Why is this considered a bad thing to do?
Also you right-click and subscribe a node to a csutom site it creates one of these an open policy action that it is indeed complaining about. If this is really a bad thing then shouldn’t that be changed somehow to activate the subscription to that custom site in the manner that would be consistant with the BKM?
Policy Action Not Targeted By Property - It’s statement is: There are open Policy actions targeting computers using Computer Lists or Computer Names. Policy actions remain open until they are manually stopped and should be targeted at a group of computers using retrieved properties instead of individual computers. The following policy actions should be stopped or re-issued.
Typically what I see under here is when we have added a computer directly to a custom group via the right-click method… but also shows when a group is used for targeting which also occurs often.
When deploying your actions, on the ‘Target’ tab, you need to be deploying actions using the second radio option which is labeled ‘All Computer with the Property Values Listed Below’. If you target sets of computers using the first or third radio options (even if you drill down to a group of computers) it will trigger the Policy Action Not Targeted By Property check.
When you right-click on computers to add them to Groups, this creates manual groups. Manual groups creation leads to a lot of actions building up and this will trigger the health check about large numbers of open actions. It is better to use automatic groups.