NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

September 14, 2009

This is the tenth installment in a series of posts about the new features and options in AppSense Version 8 Service Pack 2.  (If you have not yet downloaded this latest release, you can read more info and download it from here )

AppSense Environment Manager 8.0 SP2 includes an automatic refresh of items which use the following registry keys, or subkeys:

control panel\accessibility\stickykeys
control panel\appearance
control panel\colors
control panel\cursors
control panel\desktop
control panel\international
control panel\keyboard
control panel\mouse
keyboard layout
software\microsoft\plus!
software\microsoft\windows\currentversion\policies\explorer
software\microsoft\windows\currentversion\policies\system\wallpaper
software\microsoft\windows\currentversion\themes

These registry keys are all refreshed by using the SystemParametersInfo win32 function to individually set known items.

In addition, any change to the desktop folders causes an icon refresh to be sent and AppSense Environment Manager also broadcasts a system wide policy update message.

Refreshes are sent after all other actions have taken place.

A broadcast message for environment variables is sent whenever Environment Manager updates any variables. Environment Manager listens for broadcasts from other programs, such as VBScripts, to pick up any environment variable changes from within them.

Tip: If the key you are setting requires a refresh but is not in the list above, try setting a dummy value that matches one of the above registry keys. This forces a refresh.

P:S
As this is an ever growing blog topic, the previous posts on the other new features we have detailed can be found below:

NEW FEATURE No. 1 – AppSense Environment Manager 8.0 Service Pack 2 – Run As

NEW FEATURE No. 2 – AppSense Environment Manager 8.0 Service Pack 2 – Connect As

NEW FEATURE No. 3 – AppSense Environment Manager 8.0 Service Pack 2 – Improved compression and data handling protocol

NEW FEATURE No. 4 – AppSense Environment Manager 8.0 Service Pack 2 – Manipulation of files in Personalization Analysis

NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

NEW FEATURE No. 6 – AppSense Environment Manager 8.0 Service Pack 2 – Group SID Refresh

NEW FEATURE No. 7 – AppSense Environment Manager 8.0 Service Pack 2 – Trigger Action Time Audit Event

NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

NEW FEATURE No. 9 – AppSense Environment Manager 8.0 Service Pack 2 – New Application Categories in the User Interface

NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

NEW FEATURE No. 11 – AppSense Environment Manager 8.0 Service Pack 2 – Registry Hive Exclusions


NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

September 7, 2009

This is the eigth installment in a series of posts about the new features and options in AppSense Version 8 Service Pack 2.  (If you have not yet downloaded this latest release, you can read more info and download it from here )

AppSense Environment Manager 8.0 Service Pack 2 introduces a new option – Stop If Fails.

In order to emulate functionality from earlier versions of Environment Manager, the Stop If Fails option can be utilized to prevent subsequent processing of child nodes. This does not alter the existing behavior of other actions and parallel nodes.

Note: By default, any action or condition that fails automatically stops the processing of subsequent child actions or child conditions.

On upgrading from a 7.x Environment Manager configuration, all rules are converted to reusable conditions and Stop If Fails is applied to each condition where referenced in the main configuration body.

Note: Stop If Fails is not available from within either reusable nodes or reusable conditions. Copying or moving nodes or conditions that contain the Stop If Fails option to reusable nodes or reusable conditions results in those Stop If Fails options being removed. However, Stop If Fails can still be applied to the reusable node when referenced from within the main body of the configuration.

P:S
As this is an ever growing blog topic, the previous posts on the other new features we have detailed can be found below:

NEW FEATURE No. 1 – AppSense Environment Manager 8.0 Service Pack 2 – Run As

NEW FEATURE No. 2 – AppSense Environment Manager 8.0 Service Pack 2 – Connect As

NEW FEATURE No. 3 – AppSense Environment Manager 8.0 Service Pack 2 – Improved compression and data handling protocol

NEW FEATURE No. 4 – AppSense Environment Manager 8.0 Service Pack 2 – Manipulation of files in Personalization Analysis

NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

NEW FEATURE No. 6 – AppSense Environment Manager 8.0 Service Pack 2 – Group SID Refresh

NEW FEATURE No. 7 – AppSense Environment Manager 8.0 Service Pack 2 – Trigger Action Time Audit Event

NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

NEW FEATURE No. 9 – AppSense Environment Manager 8.0 Service Pack 2 – New Application Categories in the User Interface

NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

NEW FEATURE No. 11 – AppSense Environment Manager 8.0 Service Pack 2 – Registry Hive Exclusions





NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

August 28, 2009

This is the fifth installment in a series of posts about the new features and options in AppSense Version 8 Service Pack 2.  (If you have not yet downloaded this latest release, you can read more info and download it from here )

AppSense Environment Manager 8.0 Service Pack 2 introduces a new condition – Run Once.

When the Run Once condition is utilized on a specific trigger, the condition ensures that any child actions or conditions only run once during that logged on session.

This condition is available only from trigger nodes that run more than once per session, and therefore excludes the following:

  • Computer | Startup
  • Computer | Shutdown
  • User | Logon
  • User | Logoff

Each Run Once condition uses its own unique internal variable to monitor when the condition is satisfied. This enables any number of conditions to be utilized but only once within the current session. So, for example, you could pop up a ‘maintenance’  warning message only the first time a specific application is launched within that session.

Tip It is possible to change the Run Once condition to become a ‘Run More than Once’ condition by editing an existing Run Once condition and selecting ‘Ctrl‐Alt‐Right Click’ in the dialog to bring up a new counter spin control. Altering the counter value from ‘1’ to the desired number will change the action to a ‘Run More than Once’ action.

P:S
As this is an ever growing blog topic, the previous posts on the other new features we have detailed can be found below:

NEW FEATURE No. 1 – AppSense Environment Manager 8.0 Service Pack 2 – Run As

NEW FEATURE No. 2 – AppSense Environment Manager 8.0 Service Pack 2 – Connect As

NEW FEATURE No. 3 – AppSense Environment Manager 8.0 Service Pack 2 – Improved compression and data handling protocol

NEW FEATURE No. 4 – AppSense Environment Manager 8.0 Service Pack 2 – Manipulation of files in Personalization Analysis

NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

NEW FEATURE No. 6 – AppSense Environment Manager 8.0 Service Pack 2 – Group SID Refresh

NEW FEATURE No. 7 – AppSense Environment Manager 8.0 Service Pack 2 – Trigger Action Time Audit Event

NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

NEW FEATURE No. 9 – AppSense Environment Manager 8.0 Service Pack 2 – New Application Categories in the User Interface

NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

NEW FEATURE No. 11 – AppSense Environment Manager 8.0 Service Pack 2 – Registry Hive Exclusions