Software Deployment

While there are several possible reasons- I would point out that creating an MSI package to push a simple registry modification is not a good idea. The system must maintain this as another installation to track (as well as checks due to the AD assignment) and if the application is reinstalled or triggers a repair- your change will very likely get "undone".

I recommend you create a simple script for this change that checks for the setting and if it is not set, sets it. Then place this in an OU assigned logon script.

Just my own suggestion- there are several ways to go about it (largely dependant upon your environment and the tools you have available).

Hope this helps!

In Robert's defence,

I seem to recall that packages MUST be MSIs in order for GPOs to push them.

One client of mine uses MSI wrappers to then execute little WiseScript EXEs.

BKelly is right, though, about not actually using MSIs to make system changes... because if something changes about a key component, the MSI will self-repair, undoing whatever you did.

If the package is to be workstation deployed then it will only install the HKCU keys for each user of the workstation as the app is accessed by the user. The app does a mini self repair in order to add the keys. If the msi has only HKCU information in it then how is this going to be triggered? You will need a shortcut to trigger the entry being installed. Thats most likely not happening and not a neat solution anyway.

I agree with bkelly that trying to change registry keys only with msi's is a hit and miss affair.

You would be better off to create a custom action in a VisualStudio mst file and add the key you want and remove the other one.