Design a policy for testing and modifying existing applications into the new Domino 7 environment. Generally, Notes/Domino 5 and 6 applications work fine in the Domino 7 environment, but we still recommend that you check all of your mission-critical applications in case of incompatibility. Create a schedule to test and if necessary modify existing applications.
Test and modify applications for the new environment. * Apply the new application design for the new environment. ***
Test and modify the applications as you planned in the previous phase. Apply the modified design for Domino 7 in a production environment as you planned in the previous phase.
Chapter 2. Preparing for your upgrade
We cover each phase outlined in Table 2-1 on page 14 in greater detail in the following sections of this chapter. All of the upgrade planning phases have a close dependency on each other, and while these dependencies might be different in each project, it is always true that some of the upgrade tasks do not happen until the previous task has finished. Figure 2-1 shows a brief example of an upgrade project.

Preparation

Production

Develop a policy

Server Client
Transition planning Transition planning

Testing

Upgrade operations Upgrade operations
(develop migration tools)

Application

Transition planning

Testing and modifying

Applying the new design
Figure 2-1 Rough schedules for upgrade projects
In an upgrade project, you must create a work breakdown structure (WBS) at the beginning of the project. Figure 2-2 on page 17 shows an example of a WBS in an upgrade project. In this sample project, the WBS has planned for servers, clients, and applications. Note that this is just a sample scenario and you must plan enough time for each stage appropriate for your environment.

TaskNo.

A A A A A A A A A A A A A A A A A B B B B B B B B B B B B B B B B B B B B B B B B B B B B 5
Total Planning current servey client choice new features planning Failover / Disaster Recovery deciding project goal Prepare software and hardware System Design Basic design Servers Topology Security System Administration Daily Schedule Server Monitoring User and group administration Desktop and clint management Additional configuration/preparation Upgrade servers Build a test plan for upgrade Build a solution for mixed-environment Create pilot environment Test in a pilot environment Build deitaled schedule Build a rollback plan Upgrade directory Upgrade administration server Upgrade hub servers Upgrade mail servers Upgrade application servers Upgrade clients Build a detailed upgrade plan Test client upgrade procedure Test client in a pilot environment Build a plan to configure clients Build a plan to upgrade mail template Test template upgrade procedure Upgrade clients Upgrade mail templates Application Transition current servey prioritrize Priority A test and modify Priority B test and modify Switch to new design for server Switch to new design for client

http://www.ibm.com/developerworks/lotus/products/notesdomino/
With an understanding these basic issues, we take a closer look at how we consider each resource when we perform an upgrade.
2.4 Defining the basic outlines of a new environment
While understanding system requirements and considering the performance for a new environment are very important, there are several more issues that the administrator should consider. In this section, we demonstrate in detail how to plan and design your new environment. Defining basic upgrade policies and determining your upgrade goal, determining how you implement your Domino 7 server, and how you administrate these environments are the major points to consider in the upgrade project.

2.4.1 Basic policies

At the beginning of an upgrade project, the administrator or system planning division must decide the basic policies and strategies for performing the upgrade. The upgrade project sometimes involves more than upgrade itself, for example, changing the type of clients and building fail-over and disaster recovery solutions. Furthermore, it is also common to change server platforms or perform server consolidation. We provide an additional section at the end of this chapter to address these issues briefly. Refer to 2.8, Other considerations for the upgrade project on page 61 if necessary.

Client choice

The Domino 7 server can be accessed by the Notes client, Domino Web Access, POP3, or IMAP/SMTP client. If Microsoft Outlook is installed on the client machine, you can also access the Domino server using Domino Access for Microsoft Outlook. Each client offers its particular advantages, as well as potential disadvantages. You must consider carefully any loss of functionality resulting from a client change, because this will be noticeable to your users and potentially result in additional support calls. Table 2-9 on page 31 is the brief table presenting both the advantages and disadvantages. Although the character of these clients is totally different and it cannot be exhaustively described in a small chart, this is a good starting point for considering a client change. We recommend that you test the clients yourself and decide which client is the most appropriate for your future environment.
Table 2-9 Brief advantages and disadvantages of each messaging client Client types Notes client Advantages Easily integrated into Domino environment (for example, easy to create workflow). Many merits as a dedicated client for Domino, including local replication, rich text editing, preview pane, type ahead addressing, short cut keys, and more. Domino Web Access Notes mail-like interface. Can be used from any supported browser from any location. Easily integrated into portal. Disadvantages Need to install on each client machine. Need to configure roaming service if you want to use from another client machine.

Check what third-party application tools you currently use and check whether they are supported in Domino 7. Check the performance.
Check the available disk size. Read Known limitations, problems, and workarounds in Release Notes before upgrade. Check that you have decided which type of clients to use.
Server configuration and system management. Check if you have new servers. Define the schedule for each servers daily and weekly operation. Backup operation. Check how to monitor new servers. If you have new servers at the time of the upgrade, you must decide how to configure these servers before the upgrade operation. Define the schedule for server tasks, agents, backup, and periodical restart. Consider how you will backup your database. Consider the schedule, backup software, and so on. You can usually use the same monitoring as you are using now, but check whether it will work in Domino 7 and consider temporary coexistence.
To do 5 Check for the user administration.
Explanation You can usually use the same way as you are doing now. However, check whether it will work in Domino 7 and consider temporary coexistence.
Domino Web Access, if used. 1 Client hardware. Check the latest Release Notes for hardware requirements. It is best to test the response time from the least powerful client, and because most of the Domino Web Access functionality takes place on the client side, it depends heavily on the client hardware. Check the latest Release Notes for supported Web browsers. It is very important to check the Domino Web Access functionality. It is very difficult to customize Domino Web Access, and although it looks like the Notes client, it is a browser-based application. It might be a problem to recognize these limitations after you upgrade the environment. Read them before, and provide these limitations to users if necessary. With Domino Web Access, it is very important to consider the HTTP topology, including reverse and forward proxy. The response time might be affected if there are some proxies in the HTTP topology. You can reduce network traffic if you use GZIP compression. However, some of the proxies dislike GZIP compression, and we recommend that you check this in the production network environment. Domino Offline Services is a good solution for providing offline access to Web application users. Domino Offline Services works well, especially for Domino Web Access, but we recommend that you check the Release Notes for its known limitations. You should also check whether you use local archiving. You can use either Domino PKI or S/MIME. You can choose a default page of Domino Web Access in the Server Configuration document. If you do nothing before users begin to use it, it shows the default welcome page. We recommend considering this before use. When you send Internet mail, there are two types of messages, plain text, and MIME/HTML. You can select whether to force users to use text or make the format selectable by users. If you have not used an Internet password, you must set the initial password and notify users.

Restriction: In order to enable message disclaimers in a mixed environment, all your Domino servers must be running Domino Directory 7 to interpret the mail policy related to message disclaimers. In addition, your SMTP servers that have been configured to add disclaimers need to run on Domino 7 and the Domino Directory 7 design. Follow these steps to configure message disclaimers on your Domino server: 1. Open the Domino Server Configuration document and select the Router/SMTP tab. Select the Message Disclaimers tab to enable message disclaimers, enable disclaimers on S/MIME signed or encrypted messages, and define the level of logging option. See Figure 3-9.
Figure 3-9 Enabling Message Disclaimers from the Server Configuration document
Note: If you enable the option to add a disclaimer to S/MIME signed or encrypted messages, recipients might not be able to read your encrypted message or validate the signature. If disclaimers are added at the server level, the SMTP task will modify the body of this message and invalidate the signature. When disclaimers are added directly from the Notes client, the SMTP task will not modify the body to add a disclaimer. When the message disclaimer is added from the Notes client, the message is marked as containing the disclaimer information and will bypass server checking. We recommend enabling the Notes client to add a disclaimer through a mail policy document and let the server only add a disclaimer if it has not been added by the Notes client.
2. Message disclaimers can only be added by the Notes client if you create a mail policy with disclaimer information and enable it in the Server Configuration document for your SMTP server, as shown in Figure 3-10. Reference the Lotus Domino 7 Administrator Help for detailed information about creating a mail policy that enables message disclaimers.
Figure 3-10 Mail policy for a specific user
Tip: To ensure that message disclaimers function on the Notes client, you need to ensure that the Notes users Location document and the users Person document in the Domino Directory contain an Internet name. In addition, the home mail server and mail file location must be correct in the users Location document.
New Domino server mail rules
Domino server mail rules are used to control incoming messages received by SMTP or the Notes mail.box. Two new types of server mail rules have been introduced in Domino 7: Support for $DNSWLsite and $DNSBLsites tags. If you decide to tag these messages processed by SMTP, rather than silently skipping or rejecting them, you can define subsequent rules to handle them in a specific manner (for example, journeying, redirecting to a database, or changing routing). See Figure 3-11.

StdR7Disc

DOCLBM7.NTF

StdR7DocLibMS

DOCLBS7.NTF

StdSmartSuiteR7DocLib

DOCLBW7.NTF

StdR7WebDocLib

DOLADMIN.NTF
Domino Offline Services Admin 1.0

DOLRES.NTF

Domino Offline Services Resource Template 1.0

DOMADMIN.NTF DOMCFG5.NTF

StdAdminDatabase StdR5DominoWebServerConfi guration DominoChangeControl

Yes Yes

DOMCHANGE.NTF
DOMLOG.NTF DSGNSYN.NTF DSPA.NTF
Domino Web Server Log Template DesignSynopsis Server.Planner: Analyst

DSPD.NTF

Server.Planner: Decision Maker

DSPV.NTF

Server Planner: Vendor Domino Web Access (7)

Server.Planner: Vendor

DWA7.NTF
New design for Domino 7 (formerly called iNotes).
EVENTS4.NTF HEADLINE.NTF ICL.NTF
Monitoring Configuration Subscriptions Issued Certificates List Mail (IMAP) iNotes Web Access (R5)
StdR4Events StdNotesHeadlines5.0 Issued Certificates List
Yes No No No design change for system > Notes Domino 6.51.

IMAPCL5.NTF INOTES5.NTF

StdR50IMail iNotes5
No No No design change for system > Notes Domino 6.52. No design change for system > Notes Domino 6.54. No design change for system > Notes Domino 6.54.

INOTES6.NTF

Domino Web Access (6)

iNotes6

IWAREDIR.NTF
Domino Web Access Redirect Personal Journal Lotus Notes/Domino Fault Reports Lotus Notes/Domino Smart Upgrade Tracking Reports Notes Log Notes Log Analysis Extended Mail (6) Extended Mail (7)

DWAREDIRECT

JOURNAL6.NTF LNDFR.NTF
Std7Journal Lotus Notes/Domino Fault Reports Lotus Notes/Domino Smart Upgrade Tracking Reports

LNDSUTR.NTF

LOG.NTF LOGA4.NTF MAIL6EX.NTF MAIL7EX.NTF
StdNotesLog StdR4LogAnalysis ExtR6Mail ExtR7Mail

Yes Yes N/A

New template.
MAIL6.NTF MAIL7.NTF MAILBOX.NTF MAILJRN.NTF MTSTORE.NTF
Mail (6) Mail (R7) Mail Router Mailbox Mail Journaling Domino MailTracker Store News Articles NNTP Discussion NNTP Cross-Post NT/Migration Users Passwords Personal Address Book Personal Web Navigator
StdR6Mail StdR7Mail StdNotesMailbox StdMailJournaling MailTrackerStore

X X X X X X X

N/A Yes Yes No
NNTPCL6.NTF NNTPDI50.NTF NNTPOST.NTF NTSYNC45.NTF
StdR7NNTPClient StdR5.0NNTPDisc StdR46NNTPPostBox StdNotesNewUserPasswords

X X X X

Yes No No N/A
PERNAMES.NTF PERWEB50.NTF
StdR4PersonalAddressBook StdR50PersonalWebNavigator
Yes No No design change for system > Notes Domino 6.54.
PHONEBOOK.NTF PHONEBOOK7.NTF POLCYSYN.NTF PUBNAMES.NTF PUBWEB50.NTF REPORTS.NTF
PhoneBook PhoneBook Policy Synopsis Domino Directory Server Web Navigator Message Tracking Reports Resource Reservations Resource Reservations (7)
StdPhonebook StdR7Phonebook StdPolicySynopsis StdR4PublicAddressBook StdR50WebNavigator StdReportsDatabase

X X X X X X X X X X

N/A N/A No Yes No No Design change for system > Notes Domino 6.04.

RESRC60.NTF RESRC7.NTF

StdR60ResourceReservation StdR7ResourceReservation
N/A N/A New implementation with dedicated server task.

N D 6 X X X X X

N D 7 X X X X
Template change No Yes No Yes N/A
SCHEMA.NTF SMUPGRADE.NTF SRCHSITE.NTF STATREP5.NTF TEAMRM6.NTF TEAMRM7.NTF USERLICENSES.NTF
Domino LDAP Schema Smart Upgrade Kit Search Site Monitoring Results TeamRoom (6) TeamRoom (7) Domino User Licence Tracking User Registration Queue Domino Web Administrator
StdDominoLDAPSchema StdNotesKits StdNotesSearchSite StdR5StatReport StdR6TeamRoom StdR7TeamRoom StdLicenseTracking

N/A No

New file.

USERREG.NTF

StdUserRegistrationQueue

WEBADMIN.NTF

StdWebAdminDatabase
Tip: Using the Lotus Domino Administrator client, you can easily list all the template available on your Domino server. At the server console, issue:

sh directory ntf

This produces the following output:
DbName Version Logged ---Modified Time---C:\Lotus\Domino\Data\webadmin.ntf V6 N/A 11/16/2005 05:00:55 AM C:\Lotus\Domino\Data\userreg.ntf V6 N/A 11/16/2005 05:00:55 AM C:\Lotus\Domino\Data\userlicenses.ntf V6 N/A 11/16/2005 05:00:54 AM C:\Lotus\Domino\Data\teamrm6.ntf V4 N/A 11/16/2005 05:00:54 AM C:\Lotus\Domino\Data\statrep5.ntf V6 N/A 11/16/2005 05:00:54 AM C:\Lotus\Domino\Data\srchsite.ntf V4 N/A 11/16/2005 05:00:53 AM C:\Lotus\Domino\Data\smupgrade.ntf V6 N/A 11/16/2005 05:00:53 AM C:\Lotus\Domino\Data\schema.ntf V4 N/A 11/16/2005 05:00:53 AM C:\Lotus\Domino\Data\resrc60.ntf V4 N/A 11/16/2005 05:00:52 AM
3.4 Upgrading the Domino Directory
Now that you have considered which sequence to follow for executing the upgrade, we focus on the details involved with upgrading the Domino Directory. First, we highlight new features of the Domino Directory for Domino 7 and discuss how and why these can benefit your environment. We also describe the actions you should take to proactively and safely upgrade both your Domino Directory and your Domino servers.

An empty mail.box opens, as shown in the following example:
Mbx Note ID State Size Count From
If necessary, you can force the delivery of messages in the mail.box file. Additionally, you can issue a route command to delivery the messages to a specific destination server using the following command:
route <destination server address>
Alternatively, you can check the mail.box status using the Messaging tab of the Domino Administrator 7 client, as shown in Figure 3-42.
Figure 3-42 View of Messaging tab from the Domino Administrator 7 client
As soon you clear the mail.box files from your server, shut down the Domino server to avoid any new incoming mail. From a server console command, type what is shown in Example 3-6.
Example 3-6 Shutting down the Domino server to avoid new incoming mail quit 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 12/03/2005 05:01:51 05:01:51 05:01:51 05:01:51 05:01:51 05:01:51 05:01:51 05:01:51 05:01:52 05:01:52 05:01:52 05:01:52 05:01:52 05:01:53 05:01:53 05:01:54 05:01:57 05:01:57 05:02:03 05:02:20 PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM PM RDEBUG Server: Waiting for all tasks to complete DOMWS Convert AddIn Terminating Router: Shutdown is in progress Router: Done freeing transfer queues (1) AMgr: Executive '1' shutting down. Process id '3964' Schedule Manager shutdown complete Calendar Connector shutdown Mail Router shutdown Administration Process shutdown DOMWS Convert AddIn Termination Complete Agent Manager shutdown complete Event Monitor shutdown Database Replicator shutdown Index update process shutdown Domino Off-Line Services HTTP extension unloaded. HTTP Server: Shutdown RDEBUG Server: All tasks have completed RDEBUG Server: Shutdown Stats agent shutdown Server shutdown complete
After your server is down, on a Windows 32-bit platform, disable Windows services to avoid a server restart if you restart your operating system. On a UNIX platform, disable any cron jobs that would be used to start the Domino server automatically with an operating system restart.
To ensure that you had a clean shutdown, you can also invoke Notes System Diagnostics (NSD) to clear any shared memory segments and remaining Domino tasks using the command shown in Example 3-7.
Example 3-7 Notes System Diagnostics F:\ND70_installation\Data>f:\ND70_installation\binaries\nsd -kill ERROR (0): no active processes found for this instance Host Name : Dom6upgradeND7 User Name : Domino7 Date : Sat Dec 03 17:28:Windows Dir : C:\WINDOWS Arguments : f:\ND70_installation\binaries\nsd -kill NSD Version : Release 6.54 ERROR (0): nothing to report: no active processes found for this instance
Started at: Sat Dec 03 17:28:Ended at: Sat Dec 03 17:28:53 2005
Generated Messages: ERROR (0): no active processes found for this instance ERROR (0): nothing to report: no active processes found for this instance

3.7.1 Windows Domino server: Running Domino as a service
If you disabled Domino to start as a Windows service, the first time you start your Domino server on a Win32 platform, you need to explicitly enable the Domino Windows services to start each time you restart your Windows operating system. Alternatively, if you launch the Domino server directly from the Windows desktop, you will be asked to select the subsequent method for starting the Domino server. See Figure 3-51.
Figure 3-51 Domino as a Windows service

3.7.2 Linux server (x86)

By default, the Linux kernel limits the number of file descriptors that a process can use and open. The default setting is 1024, which is quite restrictive for Domino, and prevents scaling above a few Notes clients. The Linux administrator can increase this setting, but this depends on how you launch your Domino server.
Launching Domino for Linux from a login session
If you are launching your Domino server from a simple login session, you need to modify the /etc/security/limits.conf file to add or modify the following lines:
DominoUser soft notfile 20000 DominoUser hard nofile 49152
In this example, DominoUser is the user running the Domino server. The soft setting represents the default file descriptor limit, and hard equals the maximum value possible for this specific user. To make these values functional while your are using a login session, you need to add the following line to the right pam.d login file (see Table 3-16 on page 135):
session required /lib/security/pam_limits.so
Table 3-16 Login file to modify to match your login session method Login method used telnet rlogin ssh Pam file to modify /etc/pam.d/login /etc/pam.d/rlogin /etc/pam.d.ssd
After performing these changes, you need to log in as the Domino user before launching the Domino server.
Launching Domino with an automated script
If you start your Domino server by invoking a script, you need to add the following line at the beginning of your startup script:

ulimit -n 2000

At the same time, we suggest adding the modifications described in Launching Domino for Linux from a login session on page 134 just in case you want or need to start the Domino server from a login session.
Implementation of the Tunekrnl program
To support large-scale Domino environments, a new program called Tunekrnl is automatically invoked by Domino at its startup. This adds some kernel parameters, as defined in Table 3-17. As a Linux or Domino administrator, you do not need to modify anything other than the files indicated earlier. Tunekrnl runs with root authority and sets a few values to the /proc file system. This is why if you relaunch Domino without restarting the Linux server, these values will not be updated. An exception has been made for /proc/<pid>/mapped_base (on SUSE Linux Enterprise Server), which is updated each time Domino starts.

Figure 3-55 Validating the installation settings
11.When the installation is complete, restart your upgrade process, as described in 3.6.4, Actions to take before restarting your server on page 127.

3.7.6 Directory services

Often in a large organization, you use several directories for user authentication. In this chapter, we mainly focus on the Domino Directory, which is the primary directory for your Domino infrastructure, but you also need to consider the remaining directory services that you use internally.

Directory Assistance

Directory Assistance (based on the DA50.NTF template) has changed significantly since Domino 6. You can update its design structure on your directory server and let the updated design replicate over your server infrastructure seamlessly. Because Directory Assistance is a very small database used as a reference to other directories, there is not any performance impact when the design gets upgraded.
Extended Directory Catalog
Extended Directory Catalog is based on the PUBNAMES.NTF template and is used to aggregate Domino Directories from other domains or locations. You might want to upgrade its design during the server upgrade. To upgrade your Extended Directory Catalog (EDC), use the replica design approach, although we recommend performing this operation during off-hours. Indeed, EDC is often a large database with large view indexes that can take significant time to update. Perform the following steps: 1. Disable the replication of your EDC from the master server where you aggregate directory information. 2. From the Domino Administrator 7 client, select File Database Replace Design and select the same template that you used to replace the design of your Domino Directory. 3. When the new design has been pushed to the EDC, you can enable replication of this directory.
Condensed Directory Catalog
There have been no design changes to the Condensed Directory Catalog since Domino 6.5.1 (DIRCAT5.NTF). Therefore, if you run this server release or later, you do not need to do anything. For an earlier release in the Domino 6.0.x code stream, you might want to use the same method used for the Directory Assistance database.

Mail settings documents and policy lock-down
The mail settings document is new to Release 7 and extends the fuctionality of policies, enabling administrators set mail file and calendar preferences. Administrators also have options to lock-down a policy. Policy lock-down prevents end users from changing any preferences the administrator specifies (Figure 4-4). Policy lock-down is available in all the policy settings documents. Keep in mind that mail policies and policy lock-down will only work on a Release 7 Notes client. If your users are on a Lotus Notes 6.x client, these settings will not have any adverse effects; they just simply will not apply.
Figure 4-4 Mail Settings document
Table 4-4 on page 158 provides a policy compatibility chart.
Table 4-2 Policy compatibility chart Policy settings document Archiving Desktop Registration Mail Security Setup X X X Release 6 X X X N/A Release 6 and lock Release 7 X X X X X X Release 7 and lock X X N/A X X X
Tip: Setup profiles are still supported and continue to be backward compatible. Remember that the user setup profiles take precedence over policies, and you cannot use both. If you have a setup profile in place for a user, you cannot combine them with policies. Remove all setup profiles before you deploy policies.

Security settings policy

There have been several enhancements made to the security settings policy document. Note the following new features, fields located in the security settings document, and their expected behavior on Release 6.x and 7.x clients: Custom passwords policy The custom password policy section of the security settings document is new to Domino 6.5.4. This section, which is also available in Release 7, will not work in Notes clients prior to Notes 6.5.4. Keys and Certificate tab User Public Key Requirements (Figure 4-5)
Figure 4-5 Domino 7 Server document: Key strength and certificate expiration settings
Certificate Expiration Settings
Pushing down NOTES.INI parameters and Location document settings
Beginning in Domino 7, Lotus has documented instructions about how you can push down NOTES.INI parameters and Location document settings to Lotus Notes clients by customizing a desktop settings document. These settings will also successfully get pushed down on a Lotus Notes 6.x client.
4.5.2 Resource Reservations database
There have been significant enhancements and increased functionality of processing room and resource reservations. Special consideration for coexistence in a mixed environment is critical when replicating the Release 7 Resource Reservations database to a pre-Notes/Domino 7 server. Domino 7 consolidates the functionality previously combined in the template, router, and schedule manager task into a new Rooms and Resources Manager (RnRMgr) task. Note: Resource Reservations databases (RRDB) based on a 6.x or earlier design do not function properly on Domino 7 servers. Overbooking of rooms and resources can easily occur if you attempt to use a pre-Domino 7 RRDB on a 7.0 server. Replace the design of the Resource Reservation template (RESRC7.NTF) immediately. In Releases 7.0.2 and later, this is done automatically at server startup. The Resource Reservations database must have a Release 7 design, and you need to replace the design of this database immediately following your upgrade. For each Resource Reservations database, the Administration Server setting, located on the Advanced tab of the access control list, needs to be set as soon as possible. This setting must be the same as the server setting for any preexisting rooms or resources in the database. If the value is different, autoprocessing of requests for new rooms or resources might experience sporadic delays due to conflicting data in the Domino Directory. Tip: Room and resource reservations will not be processed unless the RnRMgr task is loaded on the server where the Resource Reservations database resides. To ensure that the RnRMgr task is loaded on server startup or restart, add it to the ServerTasks= line of the servers NOTES.INI file if it is not already there. To manually load the task, use the load rnrmgr console command. The new Resource Reservations design and architecture also now allows for multiple replicas of this database on multiple servers and is cluster-aware. There are several considerations to take note of when creating replicas of this database.

Table 5-4 Notes client upgrade options Upgrade option Manual upgrade Advantage Easily back up files before upgrading. Disadvantage Time-consuming. Administrator has to visit each workstation or leave the installations and configuration up to the end user. Administrators are unable to determine when upgrades occur. Does not work on pre-Release 6 clients.

Upgrade by mail

This upgrade is capable of upgrading pre-Release 6 clients (R4.6 and later). Lots of automation. Set upgrade deadlines.
5.2.1 Client installation options
The Lotus Notes client, Designer client, and Administrator client are all bundled on the installation CD. During the installation, a user will be presented with the option to install the Notes client or all three clients on their machine. You can also download the Lotus Notes client files from the IBM Passport Advantage Web site. If you install using a downloaded Web kit, you have the option to download the Notes client only or all three client (Notes, Administrator, and Designer).
5.2.2 Manual installation
The manual installation changed very little from Release 6.x to Release 7. We briefly describe what to expect from a manual installation of the Notes client: 1. If you are installing from a downloaded installation file from the Web, double-click the executable, and you will be first prompted to select a location for the extracted files, as shown in Figure 5-1. By default, the location to save the files will be the TEMP environment variable the user set on their machine. For the package with all three clients, you need 190 MB of free space.
Figure 5-1 Install Shield Wizard: Location to Save Files (Web kit): Dialog box 1
2. You are prompted with the window shown in Figure 5-2. Click Next.
Figure 5-2 Welcome window: Dialog box 2
3. Read and accept the license agreement, as shown in Figure 5-3.
Figure 5-3 License Agreement: Dialog box 3
4. You are prompted for customer information, as shown in Figure 5-4. Notes retrieves the same information from the client currently installed. You can modify it as needed. Click Next.
Figure 5-4 Customer Information: Dialog box 4
5. In the next installation dialog box, provide the installation path, as shown in Figure 5-5. The installation path defaults where the Notes clients are currently installed, and the Change button might be unavailable. This information is from the \HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes registry key. If you want to install the Notes client to a different path, we recommend that you uninstall the previous client before installing the new version.
Figure 5-5 Installation Path Selection: Dialog box 5
6. Select which features to install, as shown in Figure 5-6. By default, the installation selects the minimum recommended files for the Note client installation. Select the Domino Designer and Domino Administrator clients here if you need to install all three clients. You can highlight some features for a feature description or select each client to check how much hard drive space is required for each client. Click Next.

Figure 6-6 Minimal NSD configuration from your Server document
If you disabled NSD file generation, you will be warned when the Fault Report is generated that NSD is not configured, as shown in Figure 6-7. Disabling NSD file generation will impair the functionality of the automatic diagnostic data collection tool and Fault Analyzer.
Because NSD information is missing, any real crash information cannot be extracted and finally prevents the automatic diagnostic data collection tool (and Fault Analyzer) from working well.
Figure 6-7 Importance of NSD information when you use automatic diagnostic data collection
Tip: When using Fault Recovery in conjunction with administrator notification, you can attach the NSD file generated by the server crash to the server restart notification. To accomplish this, you need to add the following setting to the Domino servers NOTES.INI file:

FR_Attach_NSD=1

Keep in mind that in this case the entire NSD file will be attached to the server restart notification, without any limitation on its size, while the same information will be also available into the Fault Report database. If you want to limit the size of the attachment, you can specify a value in KB for the FR_Attach_NSD=100 parameter; in this case, only the first 100 KB will be sent. In Domino 7, the server restart notification contains additional information to that available in Domino 6, such as the name of the server, the Domino server version, the operating system, faulty process, and call stack. However, you can revert to the Domino 6 restart notification format by adding the following setting to the servers NOTES.INI file:
ADC_USE_OLD_EMAIL_FORMAT=1
This parameter needs to be set for each server on which you want to use the older format.
Enhanced design for the Fault Report database (LNDFR.NTF)
The design of the Lotus Notes/Domino Fault Reports database has been enhanced to offer additional options and support the use of Fault Analyzer. Enhancements include a threaded view, parent/children documents for crashes that occur with the same call stack, and an improved frameset for navigation. Figure 6-8 on page 227 shows a side-by-side design comparison for the Lotus/Domino Fault Reports database.
Figure 6-8 Quick side-by-side design comparison for Lotus/Domino Fault Reports database
Important: Remember to upgrade the design of your database, especially if you have disabled the design task or removed any template inheritance. By default, the template file name is LNDFR.NTF and the template name is Lotus Notes/Domino Fault Reports.
6.2 Introduction to Fault Analyzer
Fault Analyzer, introduced in Domino 7, is a server task that runs against your Domino Fault Reports database to analyze the available reports and determine whether a relationship exists between the reported crashes. The Fault Analyzer defines a percentage of convergence between all the failures stored in the Fault Reports mail-database, a key factor in identifying the source of related crashes and determining whether crashes occurring at different layers in the Domino processing have the same cause.

Desktop: Administrators can use desktop policy settings to update the user's desktop environment or to reinforce setup policy settings. For example, if a change is made to any of the policy settings, the next time users authenticate with their home server, the desktop policy settings restore the default settings or distribute new settings specified in the desktop policy settings document. Mail: Administrators can use mail policy settings to set and enforce client settings and preferences for mail and for calendar and scheduling. Mail archiving: Administrators can use archive policy settings to control mail archiving. Archive settings control where archiving is performed and specify archive criteria. Security: Administrators can use security settings to set up administration execution control lists (ECLs) and define password-management options, including the synchronization of Internet and Notes passwords. Each of these policy settings documents defines a set of defaults that apply to the users and groups to which the policy is assigned. After a policy is in place, it is possible for administrators to easily change a setting, and it will automatically apply to those users to whom the policy is assigned.
A.1.2 Organizational and explicit policies
There are two types of policies: organizational and explicit. It is important to understand the differences between the types; otherwise, it might lead to an improper implementation of these policies. In addition, there are exceptions that you can apply to these policies.

Organizational policies

An organizational policy automatically applies to all users registered in a particular organizational unit. For example, if an administrator wants to see default settings distributed to all users at the fictional ITSO Acme company registered in Sales/Acme, the administrator simply creates an organizational policy named */Sales/Acme. Then, when that same administrator uses the Sales/Acme certifier ID to register a user, that user automatically receives the settings in the corresponding organizational policy. If a user is moved within the hierarchical structure (for example, because the user transfers from the sales department to the marketing department), the organizational policy for the corresponding certifier ID is automatically assigned to the user. For example, if the administrator moves the user from Sales/Acme to Marketing/Acme, all settings defined in the desktop, archiving, and security policy settings documents associated with the */Marketing/Acme organizational policy are assigned to the user. The new policy settings become effective the first time users authenticate with their home server.