Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Lotus Notes > Notes client provisioning and install > How to deploy non-versioned patches via Smart Upgrade
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Feature comparison of IBM Notes 9.0 & IBM iNotes 9.0

body br p This article provides a sidebyside listing of new features available in both or in either IBM Notes 9.0 and IBM iNotes 9.0. For more details on the features listed and additional related information, refer to the content linked below: Help topic: What's New in IBM Notes 9.0 ...

Table of requirements for new features in IBM Notes 9.x Social Edition

Table listing new features in IBM Notes 9.0 and the requirements for each feature. Each row indicates the minimum server version, ODS, and template required for the feature to work, and also whether it requires Notes Standard Configuration or Notes Basic Configuration.

Managed Replicas Explained

The purpose of this article is to explain the managed replica feature introduced in Notes 8.5.2.

How to deploy non-versioned patches via Smart Upgrade

Smart Upgrade can also be used to deploy nonversioned 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 ...

Tips for avoiding common Notes 8.5.1 install and upgrade issues

Tips from the IBM Lotus SWAT team for avoiding common Notes 8.5.1 install and upgrade issues
Learning Center articleHow to deploy non-versioned patches via Smart Upgrade
Added by ~James Bubamaroopsi | Edited by ~Wendy Quethipilyynds on August 3, 2012 | Version 16
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: smartupgrade, smart upgrade, hotfix, patch
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.

Option 1: Deploying a non-versioned patch via Smart Upgrade while also upgrading clients to the latest Maintenance Release and/or Fix Pack

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.

\\sample.network.locationedit.com\8.5 IFP3 IBM Lotus Notes Standard 8.5FP3.exe
ECHO %ERRORLEVEL%
IF %ERRORLEVEL%==0 GOTO NextKit
GOTO End
:NextKit
\\sample.network.locationedit.com\non-versioned fix example.exe
:End

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).

Option 2: Deploying a non-versioned patch via Smart Upgrade to clients previously upgraded to the latest Maintenance Release and/or Fix Pack

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."



  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (16)Aug 3, 2012, 6:34:19 PM~Wendy Quethipilyynds  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility