There are a lot of great articles which demonstrate how to use Local Update Publisher (LUP), yest there is a huge confusion on how to push software and updates. In my post I will be using Adobe Reader XI as an example. Adobe distributes it major version upgrades, for example Adobe Reader X 10.0.0 as an msi Windows installer package. Next versions 10.0.1 can be downloaded as msi again or as a Windows installer patch file .mst.
We can always push full .msi files for each subversion upgrade, but this wouldn’t be efficient. You clients will be forced to download more data, use more processing power… efficiency is a key.
First, we want to create our base product in LUP: msi file for Adobe Reader XI. I am not going to describe it as there are plenty of examples available on how to deploy msi package using LUP. Do not forget to use Adobe Customization wizard to tailor msi for your needs.
Let’s say your clients have 10.0.4 installed and you created next update for 11.0.0 superseding 10.0.4. Not all your client will have version 11.0.0 installed when Adobe release the patch: 11.0.01. Here’s what you do:
Download .msp file from Adobe’s public ftp server.
Right click to create new update and add msp file, click next:
Do not select Adobe Reader 11.0.0 as supersedes package! This is your “base” package.
Next you will see blank rules, so create the following to accaunt for both x64 and x86 Windows versions. We will need to check the following:
– check if system is x86 or x64
– check if Adobe Reader XI installed
– check what version is present
Here’s Installed rules for this:
Note: do not forget to save them as you will reuse them for a next patch such as 11.0.02
Click next to get Installable rules:
Same as before with a small adjustment. You can actually load rules created in previous step and slightly modify them to have the following:
If you notice the only thig was changed is check for file version condition. From greater or equal to we changed to less than. I am guessing you’ve already notice we are checking for file version of the main DLL file, which will change with every patch. To get this file version, simply apply this patch on a test machine manually. I’ve done that already for you; my screenshots have correct version for 11.0.01.
And this is it, just click keep accepting the default values for the rest and click finish to publish. When client which has older version than our base (in our case 11.0.0) request the update, they will first install msi update and on the next cycle (you can force it via wuauclt /detectnow) it will install .msp.
Update Feb 20, 2013:
To add rule above you should:
1. Add all 6 specified before rules.
2. Press «Group» button and choose OR.
3. Select 3 rules: processor type x64 detection, check file exist in PROGRAM_FILESX86, check .dll version in PROGRAM_FILESX86.
4. Press «Group» button and choose AND.
5. Select remained 3 rules: processor type x86 detection, check file exist in PROGRAM_FILES, check .dll version in PROGRAM_FILES.
6. Press «Group» button and choose AND.