1. Compares the release number of the user's Notes client to the release number specified in the Source version field of the kit document in the Smart Upgrade application. The Notes client sends a match pattern to the server including the Notes client's current version, the platform and the localization. The Install type is also sent. The server then looks for a matching kit.

2. If the server finds a match, it sends a flag back to the Notes client indicating an upgrade kit may exist.

3. The Notes client searches the Smart Upgrade application for a match for its current Notes client version, platform and localization. The Notes client also checks the install type.

Note Smart Upgrade kits utilize a Readers field; therefore, the Notes client only sees kits for the user specified in the Allowed Users and Servers field of the Smart Upgrade Kit document.

Note Specifying the upgrade kit release number in the Deploy version field of the desktop policy settings document is optional. If that field is blank, but an update kit is available, Lotus Notes Smart Upgrade skips Step 4 and uses the release number of the update kit to continue the upgrade process.

6. Users can update their clients when prompted or delay the upgrade for a specified period of time. If the user has a policy that specifies an Upgrade deadline and that date has expired, the Smart Upgrade dialog box displays an "Update Now" button that forces users to update their Notes client with no options for further delay. If the setting "Remind me every hour after upgrade deadline has passed" is set in the policy settings document, users can delay the Smart Upgrade in one hour increments before being prompted again.

Related topics

Using Notes Smart Upgrade
Adding update kits to the Smart Upgrade application
Creating a desktop policy settings document
Planning for Notes client installation and upgrade
Using the Smart Upgrade Run-As wizard

Glossary