technomoney

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-04-11
14:37
2109 views
Cannot Apply Group Policy
I'm trying to push out a simple / test group policy to one of my test boxes. However, its not working. I get the error when viewing the device in ZCC.
I'm not sure what to look for since "null" isn't very helpful. Any ideas? ZCM11 with Adaptive Agent 11.0.0.41501
The action [NULL] (ID:grouppolicy) failed due to the reason : grouppolicy, however the action is set to continue on failure.
I'm not sure what to look for since "null" isn't very helpful. Any ideas? ZCM11 with Adaptive Agent 11.0.0.41501
2 Replies
technomoney

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-04-11
15:24
Re: Cannot Apply Group Policy
I should also add the agent reports the policy as "successful".
Highlighted
theflyingcorpse

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-04-11
19:21
Re: Cannot Apply Group Policy
Are there any previous versions of the policy inthe system(delete older versions)
Run the 3 commands below, between - and #
- zac cc # Clear cache
- zac ref # Refresh
- zac pr # Policy refresh, forces update to all policies
It should force an update of the policy. If you still get the error aftwards, I'd look into removing its relationship,doing the above commands again to see if the same error occurs again. If they do, its another policy causing it. If it does not occur, try to recreate the policy to see if the error persists.
Good luck!
Run the 3 commands below, between - and #
- zac cc # Clear cache
- zac ref # Refresh
- zac pr # Policy refresh, forces update to all policies
It should force an update of the policy. If you still get the error aftwards, I'd look into removing its relationship,doing the above commands again to see if the same error occurs again. If they do, its another policy causing it. If it does not occur, try to recreate the policy to see if the error persists.
Good luck!