Smart Upgrade can also be used to deploy non-versioned patches. One option is to deploy a Smart Update Kit document that points to a batch file, a command file, or a VB script that when executed, runs the installer for the latest Maintenance Release or Fix Pack followed by the patch zip file. Or if your clients are already running the latest release, then you can deploy a non-versioned patch by listing a "placeholder" destination version in a Smart Upgrade Kit document. See below for details and examples of these options.
You would like this option when you need to upgrade clients to the latest Maintenance Release and/or Fix Pack and then also apply a non-versioned patch. The following example would upgrade 8.5.1 Fix Pack 2 clients to 8.5.1 Fix Pack 3 and also apply a non-versioned patch.
1. Copy the following sample code into a Notepad document and replace the sample location for the "8.5 IFP3 IBM Lotus Notes Standard 8.5FP3.exe" and the "non-versioned fix example.exe" with the network location of the Webkits accessible by your end-users.
2. Save the file as a .bat or .cmd file. (In this example, we'll use the name "upgrade85FP3.cmd".)
Note: Be sure to save the file (upgrade85FP3.cmd) to a network location accessible by end-users. The location specified should match the location entered in the .bat or .cmd file.
3. In a new Smart Upgrade Kit document,
-- specify the Source Version as 8.5FP2 and the Destination Version as 8.5FP3
-- point the kit to the file created in step 1 (upgrade85FP3.cmd).
You would use this second option when you need to apply a patch to clients that have already been upgraded to the latest Maintenance Release and/or Fix Pack. For this example, let's say that the users are running Notes 8.5.1 Fix Pack 3, which currently is the latest Maintenance Release and Fix Pack.
1. In a new Smart Upgrade Kit document, specify the
Source Version as
8.5.1 FP3 and the
Destination Version as
8.5.1 FP3plus.
2. Attach the hotfix to the kit document and/or a shared network drive.
3. Once the patch is successfully applied, note that Smart Upgrade Tracking will report those successful upgrades as failures because the "Destination Version" will not be changed (e.g., to 851 FP3plus). To avoid users being prompted to upgrade again, you should disable the Smart Upgrade Kit at the end of the day. If you cannot disable the Smart Upgrade Kit, then you should include instructions for users in the "Message Section" of the kit. For example, include a message to "click 'Delay until Next Update' if your client has already been upgraded."
