Notes Client Deployment 

Table of Contents | Previous Page | Next Page

---

Lotus Notes 8.5 provides the following choices for deploying the client:

• Manual installation: This is usually done from the CD or from files placed in the network.
• Smart Upgrade: This is a feature that uses policy and settings documents to help push out upgrade to users who would then get a notification to upgrade their Lotus Notes client.
• Upgrade by mail: This is a feature that sends an e-mail notification to specified users to upgrade their Notes clients and, optionally, their mail file templates.
• Administrative installation: This is a feature of the Microsoft Windows Installer that copies the installation kit to a file server that users access through a network connection. Users launch the installation program from the file server to install Lotus Notes client locally on their client machines.

Note: You can use administrative installation to copy the installation files to a network file server, and then use upgrade-by-mail or Lotus Notes Smart Upgrade to notify users.

The table below compares the different deployment options.

Deployment Options	Advantages	Disadvantages
Manual Installation / Upgrade	-Easily back up files before upgrading	-Time consuming -Administrator might have to visit each workstation
Smart upgrade	-Can establish a deadline in which users must upgrade their Notes client -Can be customized with transforms to create a silent, automated installation, a shared installation, and so on	-Not capable of upgrading pre-Release 6 clients
Upgrade by Mail	-Capable of upgrading pre-Release 6 clients. -Can be customized with transforms to create a silent, automated installation, a shared installation, and so on Mail template can also be upgraded at the time of client upgrade	-Administrator cannot determine when upgrade occurs
Administrative Installation / Upgrade	-Uses the command line option /A to create an administrative image of the Lotus Notes 8 installation on a network file server -Can be customized with transforms to create a silent, automated installation, a shared installation, and so on	-Requires the Windows Installer service, which is part of the Windows XP and Vista

Manual Installation

The most simple way to install the Notes Client is manually by using either a CD or a package downloaded from the Passport Advantage website.
The steps for the manual installation and configuration are the same as the Notes 8.0 Client are shown below.

Client Installation on Windows

After you have downloaded the Notes Client web kit from the Passport Advantage website, you double-click on it to uncompress it in your defaulttemp folder, but you can specify another folder if you wish. Once this process is complete, it automatically launches the setup which brings you to the following screen:


You click Next and at the next screen, you select the option where you accept the terms in the license agreement:


You click Next and at the next screen, you enter the User Name, Organization, and the type of installation for your client (Single User or Multi-User):


After your selections, you click Next and at the next screen, you choose the locations for the program and data folders.


Click Next and at the next screen, you select the different options you wish to install with your Notes Client.


Once your options selected, click Next and at the following screen, you choose which defaults you wish for Notes:


Once you click Install, the next screens show the progress of the installation:


Once everything is complete and no errors have been encountered, you end up with the following screen:


Your Notes Client is now ready to be configured (first installation) or upgraded (existing installation).

Client Installation on Linux

As of today, there are two types of Notes 8.5 Client packages available for Linux:

• Debian (.deb): The Debian package is used on the operating system called Debian GNU/Linux or Debian for short. IBM created this Notes Client package specifically for the Ubuntu 8.04 LTS Desktop Edition.
• RPM Package Manager (.rpm): The RPM Package Manager is the one mostly used by all Linux distributions. This RPM package was specifically created for Red Hat Enterprise Linux (RHEL) 5.2 Desktop and SUSE Linux Enterprise Desktop (SLED) 10 XGL.

There is no single user installation option available. The only type of client installation available on Linux is 'multi-user' mode, meaning that it creates one directory structure for the binaries, and one directory structure for the data directory under the user's home directory:

• Default directory for the binaries: /opt/ibm/lotus/notes --- one per workstation
• Default directory for the data : /home//lotus/notes/data --- one per use

Also, there is no Domino Administration Client or Designer Client available on Linux.
The following sections explain how to install the Notes 8.5 client code for the supported Linux distributions:

• Ubuntu 8.04 LTS Desktop Edition (Debian package)
• Red Hat Enterprise Linux (RHEL) 5.2 Desktop (RPM package)
• SUSE Linux Enterprise Desktop (SLED) 10 XGL.(RPM Package)

Important Note: The Notes Client configuration steps, screens and dialogs are all the same as the Notes 8.0 client regardless of the operating system. The following sections only show the code installation.

Client installation on Ubuntu with Debian package

This section describes the client installation on Ubuntu 8.04 LTS Desktop Edition (Debian package).
When you download the Notes 8.5 Client RPM Package from Passeport Advantage, it comes as a TAR file, which is the equivalent of a ZIP file in Windows. First, you must decompress the TAR file

1. Open a terminal window
2. Copy the TAR file in a temporary directory
3. Go to the temporary directory
4. type the following command

tar -xvf .tar 

As a result, you should see the following five Debian files:

• ibm_lotus_cae-8.5.i586.deb
• ibm_lotus_activities-8.5.i586.deb
• ibm_lotus_notes-8.5.i586.deb
• ibm_lotus_sametime-8.5.i586.deb
• ibm_lotus_symphony-8.5.i586.deb

To install the Notes 8.5 client code, the steps are the following:

• Open a terminal window
• Go to the temporary directory where the Debian files are present
• Change to the user 'root' with the following command

	su

	Enter the password of the 'root' user

• To launch the installation, type the following command

	dpkg -i .deb

To respect the dependencies of the different Debian files, you must start by installing the Notes 8.5 package:

	

   dpkg -i ibm_lotus_notes-8.5.i586.deb 

If you try to install any other Debian package, your will get errors like the following:


Once this package is installed, the order of the other packages has no importance:

• dpkg -i ibm_lotus_activities-8.5.i586.deb
• dpkg -i ibm_lotus_cae-8.5.i586.deb
• dpkg -i ibm_lotus_sametime-8.5.i586.deb
• dpkg -i ibm_lotus_symphony-8.5.i586.deb

Here's how it would look like in a terminal screen:

Client installation on Red Hat Enterprise Linux with RPM Package

This section covers the client installation on Red Hat Enterprise Linux (RHEL) 5.2 Desktop and SUSE Linux Enterprise Desktop (SLED) 10 XGL (RPM package).

When you download the Notes 8.5 Client RPM Package from Passeport Advantage, it comes as a TAR file, which is the equivalent of a ZIP file in Windows. First, you must decompress the TAR file

1. Open a terminal window
2. Copy the TAR file in a temporary directory
3. Go to the temporary directory
4. Type the following command

	tar -xvf .tar

As a result, you should see the following five RPM files:

• ibm_lotus_cae-8.5.i586.rpm
• ibm_lotus_activities-8.5.i586.rpm
• ibm_lotus_notes-8.5.i586.rpm
• ibm_lotus_sametime-8.5.i586.rpm
• ibm_lotus_symphony-8.5.i586.rpm

To install the Notes 8.5 client code, the steps are the following:

• Open a terminal window
• Go to the temporary directory where the RPM files are present
• Change to the user 'root' with the following command

	su

	Enter the password of the 'root' user

• To launch the installation, type the following command

	rpm -ivh *.rpm (First installation)

	rpm -Uvh *.rpm (Upgrade existing installation)

You should see a progress bar similar to the screen below (at the bottom):


Once the installation is completed, it should look like the following screen:


Once the installation is complete, you should see the Notes and Symphony icons in the Application Browser below:

Multi User Installation

The multi-user installation allows multiple users to use the same Notes Client on a single workstation without sharing the same data directory. While sharing the same executables, each user has their own data directory and personal files within their own user home directory. Depending on how the operating system security is configured, one user cannot access the other users' home directory, thus their Notes data directory.

This type of installation is not available for the Domino Administrator and the Domino Designer clients. It is required if you are using or deploying the Notes Roaming User feature. While the user might have a single-user installation on his own workstation, if he's configured as a roaming user and he wishes to use a workstation at another location, he must use one with a Notes Client installed as multi-user.

NEW: In Notes 8.5.1, the multi-user installation is supported and recommended in a Citrix environment. For more details, see the topicConfiguring custom data directories for multi-user install or upgrade on Windows or Citrix in the Domino 8.5.1 Administrator Help

When installing a Notes Client in multi-user mode, you must choose the option at the following screen:


Then you choose where you wish to install the program files.


Note that you are note prompted to pick and choose the data directory location because this is created automatically under the user's home directory when a user logs in and launches the Notes Client from the desktop icon.

If a new user connects to the shared workstation and launches the Notes Client, it goes into the configuration steps and the user must answer all the prompts, just like when you first configure a Notes Client in a single-user installation.

Notes Client Configuration for all platforms

For all platforms, the Notes Client configuration steps are all the same.
When you first launch the Notes Client, you get the splash screen as follow:


Then you get to the following configuration information screen. You click Next.


At the User Information screen, you enter the user's first and last name, and the name of the Domino server in hierarchical format.
Note: In order for the server name to resolve automatically, your DNS must be able to resolve the first part of the server name (for example, ITSO_Server). Otherwise, you will have to provide a protocol and a fully qualified host name, that will create a connection document in the user's personal address book.


You will get prompted with a user password corresponding to the name entered above. Then, the client connects to the server and authenticates to it. If the credentials provided are valid, the next screen appears.


You can either specify which optional services you wish to configure or click Finish.
Your client is now configured and should automatically launch, and bring you to the Getting Started page.

Automating Deployment

Depending on the size of your enterprise, you may need to provide a deployment method for hundreds or even thousands of users. In this instance, being able to automate the deployment saves you both time and resources. Below are a few resources to help with automating your deployment:

• IBM Redpaper, Distributing Notes Clients Automatically , REDP-3693
• Lotus Domino Administrator 8.5 Help topic, Automating client installation using a silent install
• Lotus Domino Administrator 8.5 Help topic, Setting up client installation and installation methods
• Lotus Domino Administrator 8.5 Help topic, Providing a batch file for installing the clients

You may choose to use a third-party tool in automating your deployment. However, be aware that IBM Lotus would assist you as much as possible to make your deployment successful, but does not support the third-party tool.

For network installation, it is recommended to expand the web kit file first. Otherwise the client will have to do it, which will take more time.

Silent Install

This section explains how to set up a Notes Client without user intervention using a scriptable setup.

Although there is no way to avoid configuring the client altogether, much of the configuration can be achieved behind the scenes so that you have limited user intervention through a process called "Scriptable Setup."

The scriptable setup option uses a setting in the Notes.ini file to provide information to the client setup wizard. During installation, the wizard displays only the panels that users need to set up the Notes client. The Notes.ini parameter, ConfigFile= points to a text (.TXT) file that contains the parameters that the wizard needs.

For example:

ConfigFile=C:\Program Files\Lotus\Notes\Data\setup.txt

The wizard reads the text file and completes the setup. The user is able to bypass the wizard screens for parameters that have been provided by the text file.

The settings and parameters that you can use in the text file are listed in the Administrator Help file.

All or only some of these parameters can be used. Depending upon which parameters are used dictates which of the setup screens the user may be presented with.

What follows is an example of a text file that would simply prompt the user for their password upon initial login. Based on the parameters in this example text file, setup would be complete once the user's password has been entered and the client has completed creating the Bookmark.nsf, Names.nsf, and so on.

Example for the file setup.txt:

Username=User Name/Acme
KeyfileName=c:\Program Files\Lotus\Notes\Data\username.id
Domino.Name=servername/Acme
Domino.Address=servername.acme.com
Domino.Port=TCPIP
Domino.Server=1
AdditionalServices=0
AdditionalServices.NetworkDial=0
Replication.Threshold=1
Replication.Schedule=1

Important Information for Roaming User Setup

The scriptable setup option uses a setting in the NOTES.INI file to provide information to the client setup wizard. During installation, the wizard displays only the panels that users need to set up the Notes client. However, there are some important items to be aware of when using this a Scriptable Client Setup for a client that is intended for a Roaming User.

Important differences apply to the use/value of variables for roaming users. For details please read

• IBM Technote #1206817 - http://http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21206817| - Additional Considerations When Using a Scriptable Client Setup for a Roaming Notes User"
• Notes Client Help Topic titled "Scriptable Client Setup for Roaming Users"

Smart Upgrade

The Smart Upgrade is a feature introduced in Release 6 that allows administrators to upgrade Lotus Notes workstations without visiting every desktop. You can use it to upgrade clients from release 6.x or later to release 8.5.

The IBM Redpaper “Understanding the Lotus Notes Smart Upgrade, REDP-4180“ explains this feature in more details. http://www.redbooks.ibm.com/abstracts/redp4180.html

The benefits of using the Smart Upgrade are the following:

• The cost of the client upgrade phase is reduced and as a result.
• It makes a clients deployment phase much shorter, thus the mixed environment will be for shorter time
• An administrator can monitor the process
• Starting from release 7.0.2 you can upgrade users who have only the User rights to Operating system
• You can use this facility to deploy small patches and Fix Packs as well.

Requirements

To use Smart Upgrade successfully you need to meet the following requirements:

• Domino 6.5.x server or above
• Domino 6.5.x clients or above
• Domino Policies (Organizational or Explicit) deployed with Desktop Settings
• A Smart Upgrade Kit Database that is configured in the Server Configuration document
• Smart Kit Document that defines a path for installation

Tip: If You run a pre 6.x release you may still use the Run As utility to upgrade users who have limited access to the OS, but you need to use the Upgrade by Mail function of Lotus Notes.

How to set up Smart Upgrade

You should specify the Desktop Settings of your policy to the version of Lotus Notes you wish to upgrade. For example, we want all users to upgrade to “Release 8.5 FP1”

Desktop Settings – Smart Upgrade tab:

• Deploy version: make sure to use the format “Release 8.5 FP1“
• The Upgrade deadline: you should determine a date by which users need to modify their clients.

If you want to notify users that have missed the deadline, and need to upgrade their clients as soon as possible, check “Remind me every hour after the “Upgrade deadline” has passed:” - This will prompt users every hour, after a passed deadline.

• Mail-in database for the Smart Upgrade Tracking reports – specify an address where all reports about client upgrades will be sent.
• The Remove Smart Upgrade Tracking files after a specified number of days – If you want reports to be automatically removed, select “Yes”, and specify a number of days after which reports will be automatically removed (default value is 365). If you want to keep them forever and remove them manually select “No”.

Smart Upgrade database

If you configure the Smart Upgrade kit to upgrade pre 8.x client to 8.5 clients, select Notes Basic, even if you want upgrade to the Notes 8.5 Standard client. In terms of the Lotus/Domino 8.5 old C++ client is Basic, that's why you need to select Basic one. Later when you perform upgrade from 8 or 8.5 client to the newer version, select a necessary client (basic or standard)

Basics tab

Section Basics:

• The Kit Description - Type any text here to identify this smart upgrade kit for you.
• Enable this kit for use:
• Enabled (checked) kit – makes it available to users,
• Disabled (unchecked) - will prompt users.

Section This Smart Upgrade kit can be used to update the following version of the Lotus Notes:

• Source configuration:
• Notes Standard – Select it if you upgrade 8 or 85 Standard clients
• Notes Basic – Select it if you upgrade from pre 8 release, or you upgrade 8.0 or 8.5 Basic clients upgrade options
• Source version - The Type version you want to upgrade, it should be EXACTLY as in Help->About the Lotus Notes. For example, the “Release 7.0.3” or “Release 8.0.2 FP1”. You can use “*” asteric if you want to upgrade all versions.

Tip: if you have many different versions deployed, use “*” and select the full the Lotus Notes installation. Later when the majority of users will be on one or two versions, you can supply the incremental installer, which is much smaller, and it will upgrade a client much faster. For example for moving from the Release 8.5 to Release 8.5.1 use the incremental installer.

• Operating system - Windows, Linux or Macintosh. In the Operating System field. Starting from release the 85 Lotus Smart upgrade supports the Linux clients’ upgrade.
• Localization - select you a localised source client, for example if you want to upgrade the Finnish clients to the Finnish 85 client, select Finnish. Or if you use an English client, select English.
• Release 6.5.4/6.05 or previous - select “Yes”, if a source version is lower than 6.5.4/6.05, or “No” if the source version is newer. Before 6.5.4 there were no difference between full and client’s only installations. Now you can upgrade single clients with the client’s only installation, and people who use an administrator and the Designer with another installation.

Section “After Applying this kit, the client will run this version of the Lotus Notes”:

• Destination version - type a version here, exactly the same as in the Desktop Settings of a policy document.

The Client’s software will lookup first such a policy document to which version it should upgrade, then it will try to find the corresponding Upgrade kit in Smart Kit database, so it is very important.

• Restart the Lotus Notes after update: check it if you want the Notes to start after a client is upgraded to a new version.

Section “Location of update kit”:

Location:

• On a shared network drive
• Attached to this note
• Shared network drive & attached kit

If you upgrade clients from the pre 8 release , it is better to supply a path to the network installation. You can select a path to setup.exe or .msi file (in case you upgrade Windows clients. If you upgrade Linux/Macintosh clients, select a full path to the Macintosh or Linux installations.

• “Optional arguments for the shared network drive kit” - you can supply the additional arguments to install program here.

For example, if you choose, the .msi file, you can supply /qb! which means q-quite, b-a display progress bar, !-a hide cancel button, you may find other options for the msiexec.exe in a link attached to this post.

Section “Optional message to end users (appears in update prompt):

• Message text - Any user’s text you wish to appear to users. You may put the estimated time that this upgrade may take as well.

The Administration Tab

Section Administration:

• Allowed Users & Servers - An empty field means all users can see this kit. You may limit it to only several users, they specify their names here.

Tip: Use the SmartUpgrade together with the Seamless Mail Upgrade, which will convert a mail file of a user immediately after a client is upgraded to the Lotus Notes 8.5.

Notes Smart Upgrade for Notes Clients running on Linux

Starting with Notes 8.5, you can now upgrade Notes Clients running on Linux desktops using RPM (SuSe, RedHat) or DEB (Ubuntu) packages.

When configuring for Lotus Notes 8.5 and greater on Linux client users using Smart Upgrade, you must configure Smart Upgrade using a specific procedure.

As mentioned in the introduction, Notes installation on a Linux client uses an RPM or a DEB install package, based on your Linux platform. If you are using an RPM or DEB kit, you must uninstall your existing Notes client using the ISMP uninstaller supplied with your installed release. If you have a pre-Notes 8.5 release installed and then start the process of upgrading to Notes 8.5 with an RPM or DEB kit, you may encounter problems.

IMPORTANT: An upgrade kit is different than a full kit, as some files mentioned below like smartupgrade.sh appears only in the upgrade kit.

For 8.5 and greater, these scenarios are available:

• For 8.5 users who want to upgrade to 8.5.1 or greater using Smart Upgrade, follow the steps below in the section "Configuring Lotus Notes 8.5 Smart Upgrade on Linux". The file smartupgrade.sh in webkit tar file can be used as a sample script to write your own setup.sh or rename smartupgrade.sh to setup.sh directly.
• For 8.5.1 users who want to upgrade to newer builds using Smart Upgrade, use the webkit tar directly or create your own smartupgrade.sh script and tar file to customize the Smart Upgrade behavior.

Configuring Lotus Notes Smart Upgrade on Linux

When configuring for Lotus Notes SmartUpgrade for Linux client users, you must configure for SmartUpgrade using a specific procedure.

Prior to installing Notes 8.5 on Linux, you must uninstall your existing Notes client using the ISMP uninstaller supplied with your release.

Smart Upgrade for RPM-style install kits is similar to that for ISMP; the difference is the
content of the update kit. An update kit for RPM contains several RPM packages and a setup.sh shell script .

You must also create and attach an update kit to the SmartUpgrade database, as below.

1. Create a Smart Upgrade database.
2. Create an update kit.
3. Open the Smart Upgrade database, click “New Kit”, complete the form fields, and attach the update kit to the kit document, or designate a shared network drive in the kit document.
4. Click Save & Close.

How to use Smart Upgrade for Notes Client on Linux

Smart Upgrade for Notes users on Linux using an RPM or DEB kit is similar to the pre-Notes 8.5 ISMP method; the difference being the content of the update kit. An update kit for RPM/DEB contains several packages and a required shell script. In 8.5, this script was called setup.sh as in 8.5.1, the name was changed to smartupgrade.sh.

Steps to create and attach an update kit to the Smart Upgrade database

1. Create a Smart Upgrade database.
2. Create a Smart Upgrade kit (tar file).
3. Open the Smart Upgrade database, click New Kit, complete the form fields, and attach the update kit to the kit document, or designate a shared network drive in the kit document.
4. Click Save & Close.

The update kit is a tar file that contains several RPM and DEB packages and a shell script (smartupgrade.sh). During the upgrade process, Notes downloads and decompress the tar package, and then finds and executes the script . The script must include which RPM or DEB packages are to be upgraded.

No other file named setup.sh or smartupgrade.sh must be present in the kit folder or sub-folders.

You can create a new folder and put the tar file into it.

Create a new folder, for example notes85standard_linux, and then copy these RPM packages to that folder.

1. ibm_lotus_notes-8.5.i586.rpm
2. ibm_lotus_sametime-8.5.i586.rpm
3. ibm_lotus_activities-8.5.i586.rpm
4. ibm_lotus_cae-8.5.i586.rpm
5. ibm_lotus_symphony-8.5.i586.rpm

Create a script named smartupgrade.sh in this folder.

SUSE / RedHat: In your smartupgrade.sh file, make sure that all the RPM packages to upgrade are listed in a single line (no line break) in order to avoid dependency issues.

Ubuntu: In your setup.sh file, list each DEB package to upgrade in its own line (not a single line) and list ibm_lotus_notes-8.5.i586.deb first.

Package the folder, for example notes85standard_linux, as a tar file.

Limitations

The following limitations apply:

• Smart Upgrade can not be used to deploy Cumulative Client Hotfixes (CCH) . Attempting to install a CCH will cause the Lotus Notes client to no longer start as expected. Once you launch the client, and enter your password, the following error occurs:
  “File does not exist: Files\IBM\Lotus\Notes\notes.exe”
• Smart Upgrade from a shared network drive is not supported for a non-admin Notes account on Windows Vista if UAC is enabled. For details please refer to IBM Technote 1403215
• On MacOS, Smart Upgrade can not be used to upgrade from Release 7.0.x or 8.5 Standard Client to 8.5 / 8.5.1. For details please refer to IBM Technote 1327065

More Information

More information is provided in the following resources

• The Lotus Education On Demand: the Lotus Domino/Notes 6 Smart Upgrade Tutorial
• The IBM Redpaper “Understanding the Lotus Notes Smart Upgrade, REDP-4180“
• IBM Technote 1312864 - How to configure the Smart Upgrade Tracking Database
• Microsoft Windows installer tool command line options

Upgrade by mail

Upgrade by Mail is still available in Domino 8.5, it was introduced in early versions of Lotus Notes, before Seamless upgrade was introduced.

Tip: Use Upgrade by Mail if you are upgrading from pre 6.x release, for clients that does not have SmartUpgrade functionality or for some reasons you want to upgrade particular users without SmartUpgrade.

The idea of Upgrade by Mail is that we send to user special form, that is has a button which will trigger upgrade of client and mailfile template. The benefit of this method this this will arrive to user as a regular email.

To send user a Upgrade by Mail notification, open Domino Directory, select users to whom you would like to send a message and choose “Send Upgrade Notification” from Action Bar menu.

In Basics tab of this for select whether you want upgrade Lotus Notes from “Lotus Notes 6 or higher” or “Lotus Notes version that is pre 6.x release”

You may also include additional text for users in any local language.

If you want to receive notification after mail file upgrade, select “Notify me when users complete mail conversion” to “Yes”, else select to “No”.

In a “Client Versions” you should select to which version this will apply. The number you enter is Version Number of Lotus Notes Release.

Lotus Notes 85 is 359 build number, Lotus Notes 802 is 323. If you want to upgrade release 802 clients, you should enter number that is greater than 323, for example 324.

In Software Distribution tab you need to enter full UNC path to installation of new Lotus Notes 85 client. In a Notes Install Kit Path provide full path to the installation.

Tip: avoid using network drive letter, better use UNC pathes, as well try not to use spaces in pathes, as this may cause additional problems to OS.

In a Mail Template Information section, fill the mail conversion information.

Old design template name for your mail file, will the template name exactly as it appears in Design tab “Inherit design from”.

New mail template file name: type filename of new template, for example “mail85.ntf”

Ignore 200 category limit. Select “Yes”, some old releases had a limitation of opening databases with more than 200 folders, Lotus Notes 85 has much higher limits.

Mail file to be used by IMAP mail client, check this field if you want to enable this mailfile for IMAP access.

Upgrade folder custom design – check this field if you want upgrade all folders to design of Inbox.

Prompt user before upgrading custom folders – check “Yes” if you want user to decide whether (s)he want to upgrade folders to new Inbox design.

When user receives Mail Upgrade Notification, two buttons will appear in message. One which upgrades a client software and the second which converts mailfile to new template.

Another option to automatically upgrade design of mail file, after client upgrade is SeamLess upgrade.

For more information, consult the Technote 1164125 – How to perform a silent upgrade by mail (http://www.ibm.com/support/docview.wss?rs=203&uid=swg21164125)

Seamless Mail Upgrade

Seamless mail upgrade, which uses a desktop settings document assigned to a master policy document, only works at the time that a user upgrades his client.

In the Desktop Settings document, you can choose to upgrade the user's mail template based on the version of the user's Notes client. After the client has completed the upgrade, it will retrieve policy settings from the user's mail server. If it recognizes that the user has a policy document assigned to him or her that contains the Seamless Mail Upgrade Desktop Settings document, then it will automatically upgrade the user's mail template to the version specified in the Desktop Settings document.

Here are some possible reasons seamless mail upgrade could fail for some users:

1. The user's mail server does not contain the policy document necessary for Seamless Mail Upgrade because either the NAMES.NSF has not been replicated or it has not been refreshed on the server. The user's mail server could be using a cached copy of the NAMES.NSF, which does not have the policy documents.
2. The policy document may be too restrictive as far as the organizational hierarchies are concerned. For instance, you may have an organizational policy document for an organizational unit (OU) that a user you want to upgrade is not a member of. Make sure that the users you want to upgrade are members of the organization or organizational unit that your policy targets.
3. The upgraded version of the user's Notes Client does not match the version specified in the Desktop settings document.
4. The version of the mail template that you want the users to upgrade to is not available on the users' mail servers.
5. The user may have an old NOTES.INI file left from an older installation of the Notes client.
6. The user did not setup his or her location document correctly (correct mail server & user ID) before the upgrade of the client. The location document must point to the user's correct home mail server.
7. The user may have a setup profile, which overrides policy documents.

Seamless mail upgrade only works at the time that the Notes client is upgraded, but you can re-initiate seamless mail upgrade by modifying the Notes 6.x client's NOTES.INI. Seamless mail upgrade writes the information relating to the upgrade to your client NOTES.INI.

Resetting the following NOTES.INI variables on your Notes client and relaunching the client should force seamless mail upgrade to activate (Note: it is highly recommended that you make a backup copy of your NOTES.INI before making any changes):

mailsetup=0

mailsetupfolder=0 (or mailupgradefolder=0, in Notes 7.0 and higher clients)

setup=1

It is mainly the setup variable which will re-trigger the Seamless mail upgrade

---

Table of Contents | Previous Page | Next Page