dlaporte 14 Posted March 6, 2015 Share Posted March 6, 2015 I have been testing different policy changes and have been duplicating the default "Eset Security Product for windows..." when I do this. I have noticed that when I do this and then update a specific client with the changes it gets some of the old and some of the new policies. I checked and made sure that the client pc was only assigned to the new (duplicated) policy. I then created a policy from scratch (well from choosing "new") I Had ZERO issues with ANY of the settings I chose on the client PC. Link to comment Share on other sites More sharing options...
Administrators Marcos 4,707 Posted March 7, 2015 Administrators Share Posted March 7, 2015 Whed editing a policy, do you keep "Apply" or "Force" to the left of settings that do not take effect on clients you apply the policy on? Link to comment Share on other sites More sharing options...
dlaporte 14 Posted March 9, 2015 Author Share Posted March 9, 2015 apply? Should I be choosing force? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,707 Posted March 9, 2015 Administrators Share Posted March 9, 2015 Try selecting "Force" and see if it makes a difference. Link to comment Share on other sites More sharing options...
Recommended Posts