|
|
|
|
|
|
|
|
|
|
|
|
|
|
Automating migrations to multi-user Notes clients (continued)
While I don't have experience with other third party tools, DominoPower has asked us to show you how you can get the most out of using my product, InstallPump, when automating this process.
InstallPump Version 3 has been used by hundreds of organizations to automate their Notes/Domino installations, upgrades, and administration. Working with InstallPump, you can quickly create a package to automate this seemingly difficult upgrade.
Here's an important security tip
Multi-user Notes installations require the target user to be logged onto the machine (the HKEY_CURRENT_USER section of the registry is accessed). If your security policies do not allow users to perform software installations/upgrades, you can separate your InstallPump package into to stages (first upgrading the program files and then upgrading the data files).
|
Let's go through the steps to create an automated multi-user client upgrade package with InstallPump.
My explanation of the InstallPump solution in this article is based on the following assumptions:
- An existing Lotus Notes installation (R4.5 or greater) has already been installed and configured on the local machine.
- The current Windows user has rights to perform software installations on this machine. As stated earlier, this package can be separated into two stages, if necessary.
- Ideally, an automated upgrade should require a minimal amount of (or no) user intervention.
When the InstallPump package is finally deployed on the user's machine, the user should have a fully functional and configured multi-user Lotus Notes client.
The user's Notes data directory will have been moved to the personal profile section (usually "C:\Documents and Settings\username\Local Settings\Application Data\Lotus\Notes\Data"), and subsequent persons who log onto this machine will have their data directories created in the same format.
Defining your deployment package
To define your migration package with InstallPump, create a new action by clicking the New button on the Actions tab and select action 49 (the "migrate Notes data to multi-user" action).
This action only requires one field, which is the location of the user's Notes data directory. Since this value can change on a machine-by-machine basis, let InstallPump detect where the current Notes client is installed by inserting the global variable "<NotesDataDir>". This will resolve to the current data directory on each machine, as shown in Figure A.
FIGURE A
 
Let InstallPump detect the Notes client and resolve to the current data directory on each machine. Roll over picture for a larger image.
The next action that you would add to your project would be Action 41, the installation/configuration action. The installation/configuration action contains a variety of tabs that control how the Notes/Domino software is installed on the target machine, ranging from the basic settings that define version and target directories to tabs for modifying the Notes.INI file, the local address book, Notes desktop, etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
Find unused Lotus Notes groups and clean up your address book
Have you ever wanted to get rid of old Lotus Notes groups that were cluttering up your address book, but you weren't sure if they were used? Find Unused Groups can help.
Find Unused Groups will check your ACL, mail, multi purpose and server groups to help you determine if they are used, and who uses them.
Learn how to easily clean up your address book. |
-- Advertisement --
Mark your calendar for in-depth Lotus training, May 12-14, Boston
Join experts and peers May 12-14 in Boston for educational and networking events that deliver real-world Lotus training so you can increase productivity and efficiency in your company, advance your skills, and squeeze the most from your current environment. One registration gets you into THE VIEW's Admin2010 and Lotus Developer2010.
Register by April 10 to save $200. |
|
|
|
|
|
|
|
|
|
|
