Software Deployment

If you decide to repackage then remember to add a HKCU unique key to force an overwrite of the Current User keys.

Unless the update fixess a known issue that you have in Production or is a security update then I wouldnt even bother updating at this stage because its so new.

First of all, extract the files & see if it comes with an MSP. If not, use Wise or Install shield to create one, apply it to your source and redeploy. Or just repackage the entire app with the update, and set up the upgrade in GPO.

Its usually an extremely bad practice to package a patch as an msi to patch another msi. Worst case you could have the packages overwriting each other & get repair loops.

I would agree using an MSI as a patch isnt real smart.

Adobe however seem to reach there own heights in stupidity sometimes. They make great software but whoever is creating the packages seems to be trying to make everyones life very difficult.

Disabling admin installs, disabling per use installs may be ok for some but the odd sites requires these.

I too am doing GPO deployment on a new site and all the adobe stuff doesnt like it one little bit.

I have resorted to capturing many of their products that require patches.

When you install 7.01 update, you will find an msi file in your (Documents and Settings)\(Your account)\Loacl Settings\temp.

Just copy it to another location and patch your package .

Christophe

I know how to patch an msi with a msp update.
But how do I patch a msi with another msi ???

/Ronni Pedersen

I use GPO to deploy MSI packages.
Add this new package in the same GPO, and declare it as a update package