Topics on this page include:
Overview & General Information
Notes 8.5.1 Client Architecture
- Built on Eclipse and Lotus Expeditor
- One of many products on one client platform
- Same extensions can work with other products (e.g., Lotus Sametime and Lotus Symphony)
- Diagrams shown below depict the client architecture with and without embedded applications.
One Client; Two Configurations
Lotus Notes 8.5.x client is a single client that can run in two modes: Standard Configuration or Basic Configuration. Notes Standard Configuration (or Notes Standard) makes use of Java-based Eclipse technology to enhance existing Notes functionality (mail, calendar, contacts) and provide new features such as sidebars. Eclipse architecture allows the integration of other applications, such as Productivity Tools and Composite Applications, into Notes. Notes Basic Configuration (or Notes Basic) is very similar in experience to the Notes 7 client. It is available for cases in which the client machine's memory is too low to run Notes Standard.
Program & Data Directory Structure
One Program directory + new "framework" subdirectory
- C++ code files are stored in C:\Program Files\IBM\Lotus\Notes Note: This default path is configurable during initial or clean installs only; it cannot be changed during upgrades.
- Information for Notes Standard files is stored in C:\Program Files\IBM\Lotus\Notes\framework
One Data directory + new "workspace" subdirectory
- C++ code data files are stored in C:\Program Files\IBM\Lotus\Notes\Data Note: This default path is configurable during initial or clean installs only; it cannot be changed during upgrades.
- Information for Notes Standard files is stored in C:\Program Files\IBM\Lotus\Notes\Data\workspace
Back to top
Key Upgrade Considerations
Automate & Standardize
- Relocate client code on the desktop. If data was in a non-standard location consider moving it to recommended location for multi-user install. For users who will frequently change machines consider a roaming user deployment.
- Setting or resetting mail quotas
- Updating configuration settings
- Enforcing consistency (i.e. install choices, bookmarks, preferences, certification schemes and hierarchies, etc.)
- Better load balancing users across the new environment
- Policies to improve consistency of the environment
Clean, Tighten & Fix
- Remove extraneous applications from the desktop.
- Clean up notes.ini settings that are no longer required, hard-coded IP addresses of servers in address book, etc
- Fix known deployment issues before doing the upgrade
- Run maintenance on local system databases
- Defragment user workstations before (and possibly also after) the upgrade
Follow Recommended & Supported Upgrade Order
In terms of the overall Notes/Domino upgrade, the following order is recommended and supported by IBM:
- Domino servers
- Notes clients
Specifically for Notes clients (upgrade or initial install), the following order is considered ideal:
- multi-user installation
- seamless setup on first startup
- user ID fetched from ID Vault
- if a migration step is needed, leverage startup utility with script
- initial user settings/data populated through roaming user for secondary machines
- notes settings driven through Domino policy
- install MUI, if needed, before installing Fix Pack
- install latest Fix Pack
Back to top
Recommended Features, Functionality & Best Practices
|This section highlights recommend features and functionality in Notes and Domino that result in "best practices". For a more inclusive list of options available during each phase of a Notes deployment, see the attached quick reference list: Notes851_Deployment_QuickReference.pdf |
Multi-user installs are recommended over single-user installs.
who is it ideal for?
Mostly everyone. Multi-user installations are considered ideal and recommended for the majority or "general" population of Notes users. The only exception being those who need to use Domino Designer or Domino Administrator clients, both of which are available only for single-user installs.
some specific benefits are...
new to 8.5.1
- leverage operating system multi-user profiles
- leverage user-independent settings
- administrators have lock-down control of installed programs (installed in read-only directory)
- allow multiple Notes users to use the same computer while keeping their work stored securely in their own personal data directory.
-- You can now configure a customized data directory during Notes multi-user install or upgrade on Windows or Citrix. For details see the Admin Guide topic: Configuring a customized data directory when installing or upgrading Notes multi-user on a Windows or Citrix platform
. is it possible to migrate single-user installations to multi-user installations?
Currently, this must be done in several steps. You must first uninstall the single user client, then migrate the data from single-user data location to the multi-user data location and , finally, install the multi-user client. Looking forward, Notes Software Architects are looking into creating a standalone utility to provide the base steps required to migrate data.
Admin Guide topic: Upgrading a Notes single user install to multi-user
See technote 1318037
for a caveat with Multi-user setup and UseBasicNotes parameter.
Deploy Notes Standard clients
|Unless hardware is inadequate you should plan to use the standard client. For those cases where basic client is needed you should install the Standard client and configure the installer to launch the basic client (INI variable or use the "-sa" or "-basic" switch in the shortcut)|
Technote: Features not available in the "basic" configuration of Notes (#1358519)
Domino ID Vault
Establish a standardized settings list for deployments. Notes.ini configuration settings are best managed and configured through a Domino policy pushed down to Notes clients than the "old" way of configuring them through the Installer using Transform file.
Choose policies over Installer for pushing out notes.ini settings
The use of policies is preferred and recommended over embedding notes.ini settings in the Installer. However, settings may be needed before Notes is first launched in which case the Installer should be used.
If you decide to use the Installer, consider rolling out the notes.ini with minimal active settings in the Installer and then enable settings for particular users via policies after the upgrade
Admin Guide topic: Creating a customized add-on installer
Replicate notes.ini settings via roaming user functionality
Enable Roaming User functionality to push notes.ini settings replicated after an upgrade. Doing this will allow you to delete user notes.ini settings locally and then all roaming functionality to restore them upon next launch.
uninstall before upgrading
is it required to uninstall Notes before upgrading?
Technically, no. It is not required to uninstall gold versions of Notes before upgrading to (installing) a later release.
is it a good idea to do so?
Perhaps, yes. Feedback from customers and business partners in the Notes 8.5.1 client deployment focus group indicates that uninstalling Notes before upgrading yields better results.
what are the benefits?
Specific benefits of removing and reinstalling Notes during an upgrade include:
--provides a "clean-up" opportunity; delete residual or old files no longer in use or needed.
--provides an opportunity to standardize settings and configuration through a fresh install
limit user intervention during install & setup
Use a "Scriptable Setup" (or Setup Response file) to limit user intervention during both the install and the initial setup of Notes. During the install, the wizard displays only the panels that users need to set up the Notes client.
how it works
The notes.ini parameter ConfigFile= points to a text file that contains the parameters that the wizard needs. For example, the .txt file will include settings for username,mail servers, replication schedule, and additional services.
benefit to admin
another opportunity to standardize notes configurations
benefit to users
less information user is required to know to complete client install and setup
on initial launch, user will see only (1st) the Notes splash screen, (2nd) the password prompt, and (3rd) the desktop.
Admin Guide topic: Setting up Notes with scriptable Setup
Admin Guide topic: Customizing Notes install using the tuner
Back to top
Notes Upgrade & Deployment Phases
PHASE 1: Plan the Deployment
- Set realistic goals about the time frame in which deployments can be accomplished.
- Take an inventory of the applications that must be tested with the new version of Notes; Factor in time to the overall deployment to test these applications and allot time to respond to any issues.
- Develop a plan to carefully pilot the client. Collect feedback from the pilot to help create a realistic deployment roll-out plan.
- Develop a plan for training and communicating upgrade information to end-users. Goal is to ensure you have user acceptance and that they are prepared for new client.
- Develop a training and support plan for help desk staff
- Review system requirements
- Review what maintenance deliverables will be available near your planned deployment.
- Plan to follow the recommended upgrade order: servers first, clients second, templates third.
PHASE 2: Download & Customize Install Kit
- Download the multi-user Notes client kit for required language. Notes Standard clients are pre-packaged in English, French, German, and Japanese. Multilingual User Interface (MUI) packs are required to prepare clients in other languages.
- Customize which features to install, add, or remove.
- Edit the install manifest to control which features are available and what the user sees on the installation panel
- If settings must be run before the user initially launches Notes, you can configure a transform file to accomplish this. Otherwise, rely on recommended best practices of policies and/or scriptable setup options described in this document.
- Admin Guide topic: Automating Notes installation using a silent install
- Remove default components not used by your company
- Add custom plug-ins used by your company
- Set run-time settings for notes.ini, Domino policies, and plugin_customization.ini.
- Whenever possible, use Domino policies to manage notes.ini settings. Dynamic policies can be used with Notes/Domino 8.5 and later releases. Policies must be changed only when moving from previous releases
- Admin Guide topic: Customizing Notes using a plugin_customization.ini file
- Configure Notes "Scriptable Setup"
- Pre-populate cross certificates in deploy.nsf
- You can prevent users from having to respond to cross-certificate prompts by pre-populating the deploy.nsf with admin-generated cross certificates.
- Admin-generated certificates will be copied to user's address book at first launch.
- Admin Guide topic: Customizing an install kit to set certifier and trust defaults
PHASE 3: Build & Test Deployment Package
- Use a "push" tool to automate the deployment
- Consider uninstalling earlier clients for a reportedly smoother experience and the added benefit of being able to change the location of install directories
- Code scripting to shut down client if not already shut down and also reboot the machine before starting the install
- Use verbose install logging for the pilot
- Run maintenance on local databases & defragment machine
PHASE 4: Pilot Upgraded Client
- Determine pilot length & ideal participants
- At minimum, you should allow a month for customer feedback but preferably longer if possible.
- At least 100 users distributed 80% in main site, 20% in remote site, preferably not all IT users.
- Target diverse roles such as technical, power user, assistants, specific application users; consider a separate pilot for Notes Citrix users
- Determine feedback required from pilot users and success criteria.
- Look for user feedback on issues with the new release.
- Make sure to check Release Notes for known issues, etc.
- Use pilot experience to estimate support cost to final rollout
- Collect ADC fault statistics
- Certify that custom apps work with new release
PHASE 5: Roll Out the Deployment
- Plan the roll-out based on bandwidth
-- Consider how many desktops must be upgraded and plan your roll out based on network bandwidth as well as your IT support capabilities.
-- In case of low WAN bandwidth, consider alternatives such as LAN storage devices or Smart Upgrade Govenor
- Provide 'plan of support' to help desk staff
-- Use the feedback and lessons learned during the pilot to determine how much deskside support may be needed.
- Monitor the deployment
-- Throughout the deployment, monitor the progress by using the tracking features of the tool in use.
- Push out initial policy settings
-- Using Domino Administrator 8.5.1 or 8.5, configure hierarchical policy settings document to control the desktop configuration, which will be automatically detected at first client launch so no explicit install action is required.
- Update mail templates
-- After the server and client have been upgraded, then mail templates should be upgraded.
- Update folder designs
-- Folder design is not automatically updated with a template change; it must be explicitly set via a Desktop policy.
-- Prior to updating folder design, have users empty their Trash folders
PHASE 6: Manage the Desktop
- Apply the latest Fix Pack
- Use Policies to manage desktops.
- If necessary, modify desktops by re-running the Installer in Modify mode.
- Use the new Add-On Installer toolkit to build installers for 3rd-party apps
- As needed, deploy new widgets via the Widget Catalog
- Use Sametime-provided Add-On Installer to upgrade Sametime to a higher level.
Back to top
Maintaining Notes Clients
Upgrade to the latest Maintenance Release & Fix Pack
Upgrading Notes to the latest Maintenance Release and the latest Fix Pack is considered a better choice than applying a hotfix for the following reasons: Maintenance Releases and Fix Packs are IBM recommended maintenance deliverables for Notes/Domino that are planned, scheduled, well-tested, and manageable.
Whereas individual/combo hotfixes are (1) limited by eligibility, (2) intended for only the most critical issues, (3) minimally tested by IBM, and (4) requires extensive testing by customers in their environment.
You can track the schedule for Maintenance Releases & Fix Packs on the Upcoming Releases
page at developerWorks: Lotus.
For more information about the differences between Maintenance Releases, Fix Packs and Cumulative Client Hotfixes, refer to Technote #1368141
Uninstall hotfixes, Fix Packs, and CCHs prior to upgrading to or uinstalling Notes 8.5 Fix Pack 1 or earlier releases (Technote #1395383)
- If you are uninstalling a Notes release 8.5.1 or higher, or if you are upgrading from any Notes release to 8.5.1 or higher, it is not necessary to first uninstall any hotfix, CCH or Fix Pack.
- If you are uninstalling a Notes release prior to 8.5.1, or if you are upgrading Notes to any release prior to 8.5.1, then it is necessary to first uninstall any hotfix, CCH, or Fix Pack.
Install MUI packs first, then Notes fixes (Technote #1404436)
- If you plan to install a Multilingual User Interface (MUI) pack to Notes versions prior to 8.5.1, it is recommended that you do so before applying any fixes. If you install in the opposite order, you may encounter and error and then the MUI pack installer will fail:
Notes launch issues occur after specific hotfixes are uninstalled or updated (Technote #1408723)
- Several 8.5.x hotfixes were built and distributed containing an issue with the XPD component of Notes. When installed, the Notes client is placed into a state where later uninstalling or updating the hotfix will cause the client to not launch.
Back to top
To provide feedback on this content, please send an email to firstname.lastname@example.org
Previous | Table of Contents | Next