10/13/2009 5513 views
Hi All,

I use Active Setup to install my MS Word toolbar (it is a MSI) to all users those who do not have admin rights to the box via LANDesk or SMS silently. It works fine in physical desktops, also in Citrix environment for the first time.

But, if I upgrade my MS Word toolbar from say 1.0 to 1.1, then the 1.1 files or dlls gets updated in Citrix, not the HKCU keys.

I end up with 1.0 HKCU old keys.

How to make sure Active Setup runs for per user in Citrix and their HKCU is upgraded when I upgrade my toolbar application.

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Are you publishing the application only or a desktop?
Answered 10/13/2009 by: timmsie
Fourth Degree Brown Belt


Be sure to increment by one your Active Setup, Version in HKLM i.e. 1,0 to 2,0
Answered 10/14/2009 by: dj_xest
5th Degree Black Belt

As dj_xest suggested you need to check for the value for the version key in the Active setup registry hive if you are using the same Active setup registry hive for both the versions.
Answered 10/14/2009 by: slb
Purple Belt

I am not publishing the desktop everytime I upgrade my MS Word toolbar app. Just publish application. I do increment Active Setup 'Version' reg entry value which gets triggered when the non-admin user log on after I upgrade the app in physical desktops.

But the same AS is not getting triggered in Citrix.
Answered 10/14/2009 by: athirukk
Senior Yellow Belt

That's your problem. Active setup doesn't get run when a published app is run. you can prove this by publishing the desktop and trying it.

I had the same problem and had to add the current user keys to the package and let the citrix shadow keys deal with it.
Answered 10/14/2009 by: timmsie
Fourth Degree Brown Belt

So it means, we can use 'citrix shadow keys' to fix the HKCU issue. I dont know much about this 'shadow key' implementation in Citrix, Can you please explain or point me to a source where I can get more information on Shadow key?

Is this something needs to be handled in the app code or in installshield or in citrix?
Answered 10/14/2009 by: athirukk
Senior Yellow Belt

Shadow keys

Basically when you install an app on a citrix server/terminal server as long as it's in install mode (you can do this manually by typing Change user /install from a command line and then change user /execute once the install is finished but it will go into install mode if you install the app from Add/Remove Programs). It will "watch" the install and any user settings will be copied to users who run the app.

So instead of using active setup to install your HKCU keys just add them directly to your package.

Probably not the best explaination but hopefully you get the jist
Answered 10/14/2009 by: timmsie
Fourth Degree Brown Belt

Thanks for your suggestions timmsie.
Actually we tried using " change user /install" and " change user /execute" as suggested, but still facing following issue.

1. Fresh or first time install of the MSI does populates the HKCU. No issues.
2. The application is designed in such a way to retain the few HKCU keys (say User Preferences) value while Upgrading the application.
3. At the same time, during Upgrade, few other reg keys in HKCU are modified based on command line values passed while silently installing (upgrading).

The issue is the HKCU values are NOT updated with next version values, it remains same as old version app values, but files are updated, I can see new functionalities in the toolbar. Only HKCU is an issue. May be I am mixing something here, but this is what I experienced so far.
Answered 10/14/2009 by: athirukk
Senior Yellow Belt

before we can analyze the problem here. you will need to get a grasp of citrix/terminal server repackaging which is very different from your standard desktop (xp) packaging.

Shadow Keys
It is particularly important to consider these keys when adding or rebuilding servers in your
environment. Remember that when you install an application the shadow keys will be updated with a
current timestamp. That timestamp will be newer than the timestamp in your user’s profiles. This
means that when the user’s logon they will receive the new shadow key entries, wiping out their own
customizations. This is obviously not desirable in any environment. The simplest solution is to put in
place a process whereby before installing any applications you set the time on the server to a
standardised date in the past e.g. 1/1/1970. This will ensure that your shadow keys are always older than
the keys stored in the users’ profiles.
Answered 10/14/2009 by: cygan
Fifth Degree Brown Belt