I have customized the KAV 6.0 policy on my admin kit to the settings I'd like my users to have. If I look at the enforcement tab, it shows that it is enforced for all the currently managed workstation (8 as of right now). However, what I'm finding is that the policy settings are not actually being enforced.
One of the settings is to disable the incredibly annoying notification sounds. However, I go to the workstation and find that the sounds are still enabled. Even if I synchronize workstation settings using the admin kit, the settings will not change. I can set them manually, but that defeats the purpose of the admin kit!!!
Why does it say the policy is enforced when it's really not?!
Full Version: admin kit policy not being enforced
If you change any settings you must unlock and lock this point again.
QUOTE(Helmut @ 9.01.2008 01:19) 
If you change any settings you must unlock and lock this point again.
All of my settings are unlocked... does that just mean that the end user can change settings however they want, regardless of the policy? I"m assuming that then the policy would reenforce itself and the settings would change back? Or would it have to be manually re-enforced as well?
This is one thing that was much easier with McAfee and EPo. Change a setting in the policy, save it, and it was enforced within 10 minutes. From what I can tell, after you change the policy here you have to manually push it out to the clients.
Read this FAQ.
If you don't close the LOCK signs the standard policy is enforced and your customized settings are not used!
Just close the LOCK's and your settings will be enforced and greyed-out on the clients. If not you've to check
in your policy the TAB "ENFORCEMENT" --> ADVANCED --> if setting is set to "DO NOt MODIFY LOCAL SETTINGS".
If this is set your policy is definetly enforced from the AdminKit. To speed it up you can do a right-click on your group name
and choose "Force Synchronisation".
Just close the LOCK's and your settings will be enforced and greyed-out on the clients. If not you've to check
in your policy the TAB "ENFORCEMENT" --> ADVANCED --> if setting is set to "DO NOt MODIFY LOCAL SETTINGS".
If this is set your policy is definetly enforced from the AdminKit. To speed it up you can do a right-click on your group name
and choose "Force Synchronisation".
QUOTE(defekt @ 9.01.2008 10:15)
If you don't close the LOCK signs the standard policy is enforced and your customized settings are not used!
Just close the LOCK's and your settings will be enforced and greyed-out on the clients. If not you've to check
in your policy the TAB "ENFORCEMENT" --> ADVANCED --> if setting is set to "DO NOt MODIFY LOCAL SETTINGS".
If this is set your policy is definetly enforced from the AdminKit. To speed it up you can do a right-click on your group name
and choose "Force Synchronisation".
Just close the LOCK's and your settings will be enforced and greyed-out on the clients. If not you've to check
in your policy the TAB "ENFORCEMENT" --> ADVANCED --> if setting is set to "DO NOt MODIFY LOCAL SETTINGS".
If this is set your policy is definetly enforced from the AdminKit. To speed it up you can do a right-click on your group name
and choose "Force Synchronisation".
Thanks, I think I've got it sorted out now. If the settings are "locked", will it still enforce them if I have "Do not modify local settings" selected? Or do I still have to change that setting, too. Right now, I have it set on "Modify all policy settings to the local settings at first policy application"
Unfortunately, I think the translation into English could've been a bit clearer here, maybe?
QUOTE
"Modify all policy settings to the local settings at first policy application"
This is your prob you need this setting to be set to "DO NOT MODIFY LOCAL SETTINGS" & keep LOCKS closed too !!
Later if you're more firm with the product you can use the MODIFY SETTINGS for more effective work/settings on specified clients
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.