tecivo BLOG

My IT notes, 'How To...' guides, Microsoft, SharePoint, Citrix, AppSense, Apple, technology & gadgets and more!

Tag: AppSense (page 1 of 2)

How to…Stop install wizard running every time the AppSense Management Console is opened

If you’re using a mandatory or local profile (that’s deleted at logoff) you’ve probably noticed that the AppSense Management Console always runs through the install wizard when you open it whereas if you leave your local profile on the server or use a roaming profile this wouldn’t happen.

AMC wizard

This happens when a couple of related keys don’t exist in the users registry:

HKCU\Software\AppSense Ltd\AppSense Management Console (64 Bit) n.n.n.n
HCKU\Software\AppSense Technologies\Deployment

AMC registry 8.3  AMC registry 8.4

To stop the install wizard running every time you open the Management Console add these keys to your Default profile or ntuser.man mandatory profile. (check your registry to ensure you use the appropriate version number).


How to…Updating AppSense Environment Manager configuration during active user sessions

A former colleague directed me to this blog posting which explains the use of AppSense Environment Manager engineering key ‘PreventUnapplyOnConfigChange’

I’d never heard of it before but soon found it detailed in AppSense Tech-Note TN-150931 (login required).

Adding this registry value solves the problem facing AppSense Administrators when making changes in a busy operational environment as it means that EM configuration files can be updated while a user is logged in with causing any problems – something that’s especially useful in the early stages of a deployment when changes are carried out all the time.

One of the headaches of managing AppSense Environment Manager environments is scheduling the deployment of configuration updates. Generally you’d only update the endpoint at restart so you ensure you don’t effect any active users. However there are a couple of obvious problems with this:

  1. any new computer start up actions added will need a second device restart before they apply
  2. you may not have control of how often endpoints are restarted so changes could take days or weeks to deploy

So if you have an environment that’s subject to constant change you’d have to consider deploying on a schedule and clearly that’s an issue if you’re working with a 24/7 operation.

Changing the EM configuration when the user is logged on can affect their session – settings configured by EM can be removed mid-session causing functional issues for the user and potentially opening security holes.

The ‘PreventUnapplyOnConfigChange’ registry setting prevents this behaviour which means that configuration updates can be applied to an endpoint while the user is logged on not taking effect until next logon.

Create the following registry value appropriate for the version of Environment Manager you have:

Environment Manager Version 8.0.x.x

HKLM\Software\AppSense Technologies\Environment Manager

Environment Manager 8.1.x.x

HKLM\Software\AppSense\Environment Manager
Registry Value Name: PreventUnapplyOnConfigChange
Registry Value Type: REG_DWORD
Registry Value Data: 1

Needless to say adding a Computer Startup  Set Value action is a simple way to get the setting deployed.
A value of 0 is the same as default behaviour if the key is not created i.e. EM actions are unapplied on config change

Note the limitations highlighted by AppSense if you’re using a persistent profile:

“If using a local or roaming profiles, using this Engineering Key would lead to these actions being applied permanently for any users logged on when a new configuration is deployed. In these circumstances, it would be preferable to only deploy configurations at computer startup (if there are actions which need to be unapplied).Self-Heal actions are currently unapplied regardless of this setting”

Thanks to Darren Randall at HP Enterprise Services for bringing Geert De Keyser’s blog entry to my attention which led me to the AppSense Tech-Note.


How To…Test AppSense Environment Manager configurations without having to deploy updates from the Management Server

Sometimes it’s helpful to test changes to your Environment Manager on the fly and its a pain to either mess about creating temporary Deployment Groups on the Management Server or worse rolling out configuration updates to all managed end-points.

It’s actually quite straight forward to edit a configuration file directly on your end-point.

From a PC or Server where you have the Environment Manager Console installed simply access the end-point C$ share and open configuration.aemp directly – you can make the changes and save directly back to the end-point where changes will immediately be applied ready for testing.

To roll back you can either take a copy of the file before editing or grab the previous version from another end-point and copy across.

On Windows Server 2003 you’ll find the file at

C:\Documents and Settings\All Users\Application Data\AppSense\Environment Manager\configuration.aemp

On Windows Server 2008 you’ll find it at

C:\programdata\AppSense\Environment Manager\configuration.aemp

You can do the same with Application Manager but you’ll need to restart the AM service after saving the changes

C:\programdata\AppSense\Application Manager\Configurationconfig.aemp


Older posts

© 2017 tecivo BLOG

Theme by Anders NorenUp ↑