Over a year ago I wrote an article with title “AppSense Environment Manager Policy Configurations Lost”. With the upcoming new release of AppSense Environment Manager 8.5, this article will be obsolete, ‘cause they solved it! #HipHipHooray
How did they solve it?
First of all AppSense created three triggers to check for a new config and secondly they changed the default behavior:
This means that the configuration can be updated on the endpoint at any time. When “At logon” or “At startup” are selected, the user will not actually use the configuration until a logon or startup is performed:
- Immediately: When a new AppSense EM policy configuration is applied on a computer, all the settings from the old configuration are erased because they are no longer applicable. (this is the same as the old behavior, settings might get lost here)
- At Logon: When a new AppSense EM policy configuration is applied on a computer and the user is still logged on, the user will not use that updated configuration until the next time he logs on. (This is the new default.)
- At Startup: obviously, you will have to reboot the machine and then the new policy will be applied.