Upgrade

Lotus Notes 6
Lotus software
Lotus Notes 6
Upgrade Guide
Upgrade Guide
Part No. CT1L4NA
G210-1426-00
Printed in USA
Disclaimer
THIS DOCUMENTATION IS PROVIDED FOR REFERENCE PURPOSES ONLY. WHILE EFFORTS
WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION
CONTAINED IN THIS DOCUMENTATION, THIS DOCUMENTATION IS PROVIDED “AS IS”
WITHOUT ANY WARRANTY WHATSOEVER AND TO THE MAXIMUM EXTENT PERMITTED
IBM DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION THE
IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A
PARTICULAR PURPOSE, WITH RESPECT TO THE SAME. IBM SHALL NOT BE RESPONSIBLE FOR
ANY DAMAGES, INCLUDING WITHOUT LIMITATION, DIRECT, INDIRECT, CONSEQUENTIAL
OR INCIDENTAL DAMAGES, ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO,
THIS DOCUMENTATION OR ANY OTHER DOCUMENTATION. NOTWITHSTANDING
ANYTHING TO THE CONTRARY, NOTHING CONTAINED IN THIS DOCUMENTATION OR ANY
OTHER DOCUMENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING
ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR
ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT
GOVERNING THE USE OF THIS SOFTWARE.
Copyright
Under the copyright laws, neither the documentation nor the software may be copied, photocopied,
reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or
in part, without the prior written consent of IBM, except in the manner described in the documenta-
tion or the applicable licensing agreement governing the use of the software.
© Copyright IBM Corporation 1985, 2002
All rights reserved.
Lotus Software
IBM Software Group
One Rogers Street
Cambridge, MA 02142
US Government Users Restricted Rights — Use, duplication or disclosure restricted by GS ADP
Schedule Contract with IBM Corp.
List of Trademarks
1-2-3, cc:Mail, Domino, Domino Designer, Freelance Graphics, iNotes, Lotus, Lotus Discovery Server,
Lotus Enterprise Integrator, Lotus Mobile Notes, Lotus Notes, Lotus Organizer, LotusScript, Notes,
QuickPlace, Sametime, SmartSuite, and Word Pro are trademarks or registered trademarks of Lotus
Development Corporation and/or IBM Corporation in the United States, other countries, or both.
AIX, AS/400, DB2, IBM, iSeries, MQSeries, Netfinity, OfficeVision, OS/2, OS/390, OS/400, S/390,
Tivoli, and WebSphere are registered trademarks of International Business Machines Corporation in
the United States, other countries, or both. Pentium is a trademark of Intel Corporation in the United
States, other countries, or both. Microsoft, Windows, and Windows NT are registerd trademarks of
Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark
of The Open Group in the United States and other countries. Java and all Java-based trademarks and
logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.
All other trademarks are the property of their respective owners.
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Removing NNTP documents from the

Domino Directory . . . . . . . . . . . . . . . . 2-29
Upgrading to Notes/Domino 6
Domino 5 registration servers and the
1 Planning the Move to Lotus Certification Log . . . . . . . . . . . . . . . . . 2-30
Notes/Domino 6 . . . . . . . . . . . . . . . . . . . 1-1 Obsolete NOTES.INI settings . . . . . . . . . . . . 2-32
Upgrading to Lotus Notes/Lotus Domino mail messaging changes since
Domino 6 . . . . . . . . . . . . . . . . . . . . . . . 1-1 Lotus Domino 4.6 . . . . . . . . . . . . . . . . 2-33
Preparing to upgrade to Lotus
3 Upgrading the Domino
Notes/Domino 6 . . . . . . . . . . . . . . . . . . 1-2
Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Planning the upgrade . . . . . . . . . . . . . . . . . . . 1-3
Using the Domino Directory template in a
The upgrade roadmap . . . . . . . . . . . . . . . . . 1-13 mixed-release environment . . . . . . . . . . 3-4
New Domino server and Domino Customized Address Books or Directories . . . 3-5
Administrator client features . . . . . . . 1-16
Condensed Directory Catalogs and
Domino server and Domino upgraded Domino servers . . . . . . . . . . 3-5
Administrator client enhancements . . . 1-26
LDAP service and Domino Administration
Interoperability issues . . . . . . . . . . . . . . . . . 1-38 servers . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
2 Upgrading Domino Servers . . . . . 2-1 Domino Directory changes since Lotus
Upgrading a Domino server to Domino 6 . . . . 2-1 Domino 4.6 . . . . . . . . . . . . . . . . . . . . . . 3-7
Before you upgrade a Domino server . . . . . . . 2-2 Increased UniqueNameKey (UNK) table
size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Preparing to upgrade a clustered Domino
server . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 4 Upgrading Notes Clients . . . . . . . . 4-1
Upgrading to Lotus Domino 6 . . . . . . . . . . . 2-10 Upgrading Notes clients . . . . . . . . . . . . . . . . . 4-1
Post-upgrade tasks for Domino Before you upgrade the Notes client . . . . . . . . 4-3
Administration servers . . . . . . . . . . . . 2-12 Using Upgrade-by-mail . . . . . . . . . . . . . . . . . 4-3
Post-upgrade tasks for Domino 5 mail Using IBM Lotus Notes Smart Upgrade . . . . . 4-7
servers . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Upgrading shared installation . . . . . . . . . . . 4-14
Configuring Domino 5 SMTP inbound
relay controls . . . . . . . . . . . . . . . . . . . 2-27 Deploying Notes client settings with
policies . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Post-upgrade tasks for Domino servers . . . . 2-28
Lotus Notes client changes since Notes 4.6 . . 4-16
iii
5 Upgrading Notes Mail Files . . . . . . 5-1 9 Certifying Users and Servers
Upgrading Notes mail files . . . . . . . . . . . . . . 5-1 in Flat Organizations . . . . . . . . . . . . . . 9-1
Upgrading mail files with the mail Converting flat names to hierarchical
conversion utility . . . . . . . . . . . . . . . . . 5-3 names . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Using seamless mail upgrade . . . . . . . . . . . . . 5-6 Converting flat server names to

hierarchical server names . . . . . . . . . . . 9-6
Upgrading iNotes Web Access clients . . . . . . 5-9
How the Domino Administration Process
Upgrading to the Notes 6 folder design . . . . 5-10 converts a flat server name to
6 Upgrading Databases and hierarchical . . . . . . . . . . . . . . . . . . . . . . 9-6
Applications . . . . . . . . . . . . . . . . . . . . . . . 6-1 Converting flat Notes user names to
Upgrading databases and applications . . . . . . 6-1 hierarchical . . . . . . . . . . . . . . . . . . . . . 9-11
Upgrading databases to Lotus How the Domino Administration Process

Notes/Domino 6 . . . . . . . . . . . . . . . . . . 6-2 converts flat Notes user names to
hierarchical . . . . . . . . . . . . . . . . . . . . . 9-12
Application design changes since Lotus
Notes/Domino 4.6 . . . . . . . . . . . . . . . 6-12 Flat names . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Using default Web templates with older Communication with organizations that
browsers . . . . . . . . . . . . . . . . . . . . . . . 6-16 use flat names . . . . . . . . . . . . . . . . . . . 9-14
Creating flat ID files . . . . . . . . . . . . . . . . . . . 9-16
7 Upgrading Search . . . . . . . . . . . . . . . 7-1
Ways to recertify IDs with a flat certifier
Upgrading search . . . . . . . . . . . . . . . . . . . . . . 7-1
ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Changes in search . . . . . . . . . . . . . . . . . . . . . 7-2 Results of recertification . . . . . . . . . . . . . . . . 9-19
Updating server indexes . . . . . . . . . . . . . . . . 7-2 Ways to rename flat user IDs . . . . . . . . . . . . 9-20
Search interoperability issues . . . . . . . . . . . . . 7-2
Migrating to Notes/Domino 6
Search Site and Lotus Notes/Domino 6 . . . . . 7-3
10 Overview of Domino
Domain Search and Domino 4.6 servers . . . . . 7-4
Upgrade Services . . . . . . . . . . . . . . . . 10-1
8 Upgrading Security . . . . . . . . . . . . . 8-1 Using this guide . . . . . . . . . . . . . . . . . . . . . . 10-1
Upgrading security . . . . . . . . . . . . . . . . . . . . 8-1 Overview of Domino Upgrade Services . . . . 10-1
Notes 6 ID files and earlier Lotus Notes
Installing the Domino Administrator and
client releases . . . . . . . . . . . . . . . . . . . . 8-1
Domino Upgrade Services . . . . . . . . . . 10-3
X.509 certificates and interoperability . . . . . . . 8-2
Importing users from a foreign directory . . . 10-3
Internet/intranet authentication in a
Adding users to a ‘migration’ group . . . . . 10-12
mixed-release environment . . . . . . . . . . 8-2
Setting migration options . . . . . . . . . . . . . . 10-12
Making root certificates available to clients
using SSL or S/MIME . . . . . . . . . . . . . . 8-3 Registering users and migrating
messaging data . . . . . . . . . . . . . . . . . 10-17
Verifying that a migration was successful . 10-24
iv Upgrade Guide
11 Migrating Users from cc:Mail . . 11-1 Customizing Microsoft Mail migration
settings . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Migrating cc:Mail users . . . . . . . . . . . . . . . . 11-1
Specifying advanced options for migrating
Supported cc:Mail versions . . . . . . . . . . . . . 11-2 Microsoft Mail users . . . . . . . . . . . . . 12-10
Notes equivalents for migrated cc:Mail
Registering users and completing the
information . . . . . . . . . . . . . . . . . . . . . 11-2
migration from Microsoft Mail . . . . . 12-12
Notes equivalents for migrated Organizer
Migrating additional Microsoft Mail
information . . . . . . . . . . . . . . . . . . . . . 11-4
messages after registration . . . . . . . . 12-13
Preparing to migrate cc:Mail users . . . . . . . . 11-5
13 Migrating Users from
Migrating Organizer information . . . . . . . . 11-14
Microsoft Exchange . . . . . . . . . . . . . . 13-1
Preparing to migrate Organizer Migrating Microsoft Exchange users . . . . . . 13-1
information . . . . . . . . . . . . . . . . . . . . 11-18
Notes equivalents for migrated Microsoft
Importing the cc:Mail post office directory . 11-20 Exchange data . . . . . . . . . . . . . . . . . . . 13-1
Customizing cc:Mail migration settings . . . 11-22 Preparing to migrate Exchange users . . . . . . 13-4
Setting migration options for cc:Mail . . . . . 11-23 Importing the Microsoft Exchange
Specifying advanced settings for directory . . . . . . . . . . . . . . . . . . . . . . . 13-5
migrating cc:Mail users . . . . . . . . . . . 11-24 Registering users and completing the
Mapping cc:Mail gateways to Notes migration from Exchange . . . . . . . . . . 13-8
domains . . . . . . . . . . . . . . . . . . . . . . 11-30
14 Migrating Users from a
Registering users and completing the Windows NT Domain List . . . . . . . . . 14-1
cc:Mail migration . . . . . . . . . . . . . . . 11-34
Migrating Windows NT users . . . . . . . . . . . 14-1
Migrating additional cc:Mail messages
after registration . . . . . . . . . . . . . . . . 11-37 Preparing to import users from
Windows NT . . . . . . . . . . . . . . . . . . . 14-2
Ensuring compatibility with the cc:Mail
MTA . . . . . . . . . . . . . . . . . . . . . . . . . 11-38 Specifying the Windows NT domain to
import from . . . . . . . . . . . . . . . . . . . . 14-3
Importing Windows NT users into the
Microsoft Mail . . . . . . . . . . . . . . . . . . . . 12-1 Notes registration queue . . . . . . . . . . . 14-4
Migrating Microsoft Mail users . . . . . . . . . . 12-1 Setting migration options for Windows
Notes equivalents for migrated Microsoft NT users . . . . . . . . . . . . . . . . . . . . . . . 14-4
Mail data . . . . . . . . . . . . . . . . . . . . . . 12-2 Specifying advanced options for
Understanding how the migration tool importing Windows NT users . . . . . . . 14-5
parses Microsoft Mail name formats . . 12-2 Registering users and completing the
Preparing to migrate Microsoft Mail users . . 12-5 migration from Windows NT . . . . . . . 14-8
Importing the Microsoft Mail Postoffice
Address List . . . . . . . . . . . . . . . . . . . . 12-7
Contents v
15 Migrating Users from an Search base, LDAP filters, and containers . . . 17-2
LDIF File . . . . . . . . . . . . . . . . . . . . . . . . . 15-1 Preparing to migrate Active Directory
Migrating users from an LDIF file users and groups . . . . . . . . . . . . . . . . 17-3
. . . . . . . . 15-1
What is LDIF? . . . . . . . . . . . . . . . . . . . . . . . 15-2 18 Migrating Entries from an
Understanding how Notes uses
LDAP Directory Server . . . . . . . . . . . 18-1
information in the LDIF file . . . . . . . . 15-2 Migrating entries from an LDAP directory
server . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Preparing to import an LDIF file . . . . . . . . . 15-5
Specifying advanced LDAP migration
Specifying the LDIF file to migrate from . . . . 15-7
options . . . . . . . . . . . . . . . . . . . . . . . . 18-9
Setting options for importing users from
an LDIF file . . . . . . . . . . . . . . . . . . . . . 15-8 Index . . . . . . . . . . . . . . . . . . . . . . . . . . .Index-1
Registering users migrated from an LDIF
file . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Adding imported users as directory
entries only . . . . . . . . . . . . . . . . . . . . 15-10
16 Migrating Personal Mail Data . . 16-1

Migrating personal mail data . . . . . . . . . . . . 16-1
Messaging data migrated by the user
upgrade wizards . . . . . . . . . . . . . . . . . 16-2
Before running the upgrade wizard . . . . . . . 16-4
Installing the upgrade wizard . . . . . . . . . . . 16-5
Sending users an upgrade notification
message . . . . . . . . . . . . . . . . . . . . . . . 16-7
Running the upgrade wizard . . . . . . . . . . . . 16-8
Converting message archives . . . . . . . . . . . 16-11
Overview of migrating personal address
book information . . . . . . . . . . . . . . . 16-16
After the upgrade wizard finishes
processing . . . . . . . . . . . . . . . . . . . . . 16-21

Microsoft Active Directory . . . . . . . . 17-1
Migrating Microsoft Active Directory
users and groups . . . . . . . . . . . . . . . . 17-1
Importing Active Directory names and
passwords into the Domino
Directory . . . . . . . . . . . . . . . . . . . . . . . 17-2
vi Upgrade Guide
Preface
The documentation for IBM Lotus Notes, IBM Lotus Domino, and IBM
Lotus Domino Designer is available online in Help databases and, with the
exception of the Notes client documentation, in print format.
License information
Any information or reference related to license terms in this document is
provided to you for your information. However, your use of Notes and
Domino, and any other IBM program referenced in this document, is solely
subject to the terms and conditions of the IBM International Program
License Agreement (IPLA) and related License Information (LI) document
accompanying each such program. You may not rely on this document
should there be any questions concerning your right to use Notes and
Domino. Please refer to the IPLA and LI for Notes and Domino that is
located in the file LICENSE.TXT.
System requirements
Information about the system requirements for Lotus Notes and Domino is
listed in the Release Notes.
Printed documentation and PDF files

The same documentation for Domino, and Domino Designer that is avail-
able in online Help is also available in printed books and PDF files.
You can order printed books from the IBM Publications Center at
www.ibm.com/shop/publications/order.
You can download PDF files from the IBM Publications Center and from
the Documentation Library at the Lotus Developer Domain at
www-10.lotus.com/ldd.
Related information
In addition to the documentation that is available with the product, other
information about Notes and Domino is available on the Web sites listed
here.
• IBM Redbooks are available at www.redbooks.ibm.com.
vii
• A technical journal, discussion forums, demos, and other information is
available on the Lotus Developer Domain site at
www-10.lotus.com/ldd.
Table of conventions
This table lists conventions used in the Notes and Domino documentation.
Convention Description
italics Variables and book titles are shown in italic type.
monospaced type Code examples and console commands are
shown in monospaced type.
file names File names are shown in uppercase, for example
NAMES.NSF.
hyphens in menu names Hyphens are used between menu names, to show
(File - Database - Open) the sequence of menus.
Structure of Notes and Domino documentation

This section describes the documentation for Notes, Domino, and Domino
Designer. The online Help databases are available with the software
products. Print documentation can be downloaded from the Web or
purchased separately.
Release Notes
The Release Notes describe new features and enhancements, platform
requirements, known issues, and documentation updates for Lotus Notes 6,
Lotus Domino 6, and Lotus Domino Designer 6. The Release Notes are
available online in the Release Notes database (README.NSF). You can
also download them as a PDF file.
Documentation for the Notes client

The Lotus Notes 6 Help database (HELP6_CLIENT.NSF) contains the
documentation for Notes users. This database describes user tasks such as
sending mail, using the Personal Address Book, using the Calendar and
Scheduling features, using the To Do list, and searching for information.
Documentation for Domino administration

The following table describes the books that comprise the Domino Admin-
istration documentation set. The information in these books is also found
online in the Lotus Domino Administrator 6 Help database
(HELP6_ADMIN.NSF).
The book Installing Domino Servers ships with Domino. The other books are
available for purchase, or for free download as PDF files.
viii Upgrade Guide

Title Description
Upgrade Guide Describes how to upgrade existing Domino servers and
Notes clients to Notes and Domino 6. Also describes how
to move users from other messaging and directory
systems to Notes and Domino 6.
Installing Domino Describes how to plan a Domino installation; how to
Servers configure Domino to work with network protocols such
as Novell SPX, TCP/IP, and NetBIOS; how to install
servers; and how to install and begin using Domino
Administrator and the Web Administrator.
Administering the Describes how to register and manage users and groups,
Domino System, and how to register and manage servers including
Volumes 1 and 2 managing directories, connections, mail, replication,
security, calendars and scheduling, activity logging,
databases, and system monitoring. This book also
describes how to use Domino in a service provider
environment, how to use Domino Off-Line Services, and
how to use IBM Tivoli Analyzer for Lotus Domino.
Administering Domino Describes how to set up, manage, and troubleshoot
Clusters Domino clusters.
Documentation for Domino Designer

The following table describes the books that comprise the Domino Designer
documentation set. The information in these books is also found online in
the Lotus Domino Designer 6 Help database (HELP6_DESIGNER.NSF)
with one exception: Domino Enterprise Connection Services (DECS) Installation
and User Guide is available online in a separate database, DECS User Guide
Template (DECSDOC6.NSF). The printed documentation set also includes
Domino Objects posters.
In addition to the books listed here, the Domino Designer Templates Guide is
available for download in NSF or PDF format. This guide presents an
in-depth look at three commonly used Designer templates: TeamRoom,
Discussion, and Documentation Library.
Title Description
Application Development with Explains how to create all the design elements
Domino Designer used in building Domino applications, how to
share information with other applications, and
how to customize and manage applications.
Domino Designer Programming Introduces programming in Domino Designer and
Guide, describes the formula language.
Volume 1: Overview and
Formula Language
continued
Preface ix
Title Description
Domino Designer Programming Describes the LotusScript/COM/OLE classes for
Guide, access to databases and other Domino structures.
Volumes 2A and 2B:
LotusScript/COM/OLE Classes
Domino Designer Programming Provides reference information on using the Java
Guide, and CORBA classes to provide access to databases
Volume 3: Java/CORBA Classes and other Domino structures.
Domino Designer Programming Describes the XML and JSP interfaces for access to
Guide, databases and other Domino structures.
Volume 4: XML Domino DTD
and JSP Tags
LotusScript Language Guide Describes the LotusScript programming language.
Domino Enterprise Connection Describes how to use Domino Enterprise
Services (DECS) Installation Connection Services (DECS) to access enterprise
and User Guide data in real time.
Lotus Connectors and Describes how to configure Lotus Connectors for
Connectivity Guide use with either DECS or IBM Lotus Enterprise
Integrator for Domino (LEI). It also describes how
to test connectivity between DECS or LEI and an
external system, such as DB2, Oracle, or Sybase.
Lastly, it describes usage and feature options for
all of the base connection types that are supplied
with LEI and DECS. This online documentation
file name is LCCON6.NSF.
Lotus Connector LotusScript Describes how to use the LC LSX to
Extensions Guide programmatically perform Lotus
Connector-related tasks outside of, or in
conjunction with, either LEI or DECS. This online
documentation file name is LSXLC6.NSF.
IBM Lotus Enterprise Describes installation, configuration, and
Integrator for Domino (LEI) migration information and instructions for LEI.
Installation Guide The online documentation file names are
LEIIG.NSF and LEIIG.PDF. This document is for
LEI customers only and is supplied with LEI, not
with Domino.
IBM Lotus Enterprise Provides information and instructions for using
Integrator for Domino (LEI) LEI and its activities. The online documentation
Activities and User Guide file names are LEIDOC.NSF and LEIDOC.PDF.
This document is for LEI customers only and is
supplied with LEI, not with Domino.
x Upgrade Guide
Chapter 1
Planning the Move to Lotus Notes/Domino 6
This guide covers two areas: upgrading and migration. Upgrading is the
process of moving from earlier releases of IBM® Lotus® Domino™ and
Lotus Notes® to Lotus Notes/Domino 6 — including upgrading the
software, working in a mixed-release environment, and upgrading your
infrastructure. Migration is the process of moving from other mail
systems, such as Microsoft® Exchange, to Lotus Notes/Domino 6.
Upgrading to Lotus Notes/Lotus Domino 6

Most organizations do not move to Lotus Notes/Domino 6 all at once;
rather, they phase in Lotus Notes/Domino 6. There is a period of time in
which the old systems (including earlier releases and other mailgroup-
ware products) coexist with Lotus Notes/Domino 6. Lotus created Lotus
Notes/Domino 6 with this coexistence phase in mind — key system
databases, such as the Domino Directory and the Administration
Requests database, were designed for backward compatibility. In
addition, features such as native Simple Message Transfer Protocol
(SMTP) and Multipurpose Internet Mail Extensions (MIME) support in
the Domino router do not require infrastructure changes. Existing routing
paths and addressing work as they did in Domino 4.6 or Domino 5.
To help you structure your upgrade process and rollout, see the follow-
ing information:
• Preparing to upgrade to Lotus Notes/Domino 6
• Planning the upgrade
• The upgrade roadmap
• New Domino server and Domino Administrator client features
• Domino server and Domino Administrator client enhancements
• Interoperability issues
Using this guide

This guide is intended to be read by everyone involved in the upgrade
process, and especially by the upgrade team. While end users probably
do not need to read the guide, some information in it may be useful to
1-1
them. Consider creating a short list of useful upgrade information and
distributing it to your end users.
This guide contains information on planning your upgrade, the steps
necessary for each part of the upgrade, information on operating in a
mixed release environment and a summary of new Domino server and
Administrator client features and enhancements that help your organiza-
tion be more productive.
Note For new Lotus Domino Designer and Lotus Notes features, see the
“What’s New” topics in the Lotus Domino Designer 6 Help and the
Lotus Notes 6 Help databases.
Preparing to upgrade to Lotus Notes/Domino 6

Before upgrading to Lotus Notes/Domino 6, be sure to read the Release
Notes, available as a database (README.NSF) for downloading or
viewing at http://www.lotus.com/ldd/doc. The Release Notes contain
critical technical information, documentation, interoperability issues, and
updates that were not available in time to be included in the rest of the
documentation.
To prepare for upgrading to Lotus Notes/Domino 6, consider the follow-
ing issues that affect upgrading.
Operating system changes

Lotus Notes 6 and the Domino 6 Administrator support the following
operating systems:
• Microsoft Windows® 95, Windows 98, Windows NT®4, Windows
2000, and Windows XP Professional
• Macintosh PowerPC systems
Organizations running Microsoft Windows 3.1, IBM OS/2® Warp, or
UNIX systems, which were supported by Lotus Notes 4.6, can continue
to run Lotus Notes 4.6 or move to a Lotus Notes 6 supported platform.
Lotus Domino Designer 6 supports the following operating systems:
Microsoft Windows 95, Windows 98, Windows NT4, Windows 2000, and
Windows XP Professional.
Lotus Domino 6 supports the following operating systems:
• HP-UX
• IBM AIX®
• Microsoft Windows NT 4.0 and Windows 2000 Intel
1-2 Upgrade Guide

• Sun™ Solaris® and Sun SPARC®
• Linux
Organizations running Lotus Domino on NetWare, which is supported
by Lotus Domino 4.6, can continue to run Lotus Domino 4.6 or move to a
Lotus Domino 6 supported platform.
Hardware requirements
Be sure to consult the Release Notes for hardware requirements for Lotus
Notes/Domino 6. You may need to add capacity to servers or worksta-
tions to run Lotus Notes/Domino 6. In addition, features such as transac-
tion logging have additional requirements such as separate drives.
Supported upgrade path

To upgrade to Lotus Notes/Domino 6, your Notes/Domino system
should be running Domino 4.6 or later. Upgrade a Domino 4.6 system to
the latest Maintenance Release (MR) 4.6.7a before upgrading to Lotus
Notes/Domino 6.
If you have designs or templates created prior to Notes/Domino 4.6 in
your organization, such as a Notes/Domino 4.5 Names and Address
Book or Notes/Domino 4.5 mail files, you must upgrade these designs to
at least Notes/Domino 4.6 before upgrading to Notes/Domino 6.
Note To replicate the Domino 6 Domino Directory to Domino 4.6
servers, you must upgrade Domino 4.6 servers to Domino 4.6.7a.
Planning the upgrade

The upgrade of a Domino system needs to be an organized process to
minimize work and to avoid disrupting users. Upgrades of single servers
(that is, a server that is not part of a cluster), for example, should take
place at times when few users are connected — such as weekends or late
at night.
Track your procedures, difficulties, solutions, and questions so that you
can refer to this information in later upgrade stages. Use a Notes
database or a Domino Web site to provide “best practices” for upgrading
the rest of your organization.
Upgrade to Lotus Notes/Domino 6 in the following order:
• Domino Administration server and Domino Directory or Public
Address Book (4.6)
• Domino Administrator client
• Hub servers
Planning the Move to Lotus Notes/Domino 6 1-3

• Mail servers
• Application servers
• Notes clients
• Applications and databases
By upgrading servers before clients, and servers and clients before appli-
cations, you minimize disruption to users and to business activities.
Users don’t see Lotus Notes/Domino 6 features until their clients can
utilize them; conversely, users don’t attempt to take advantage of Lotus
Notes/Domino 6 features until their servers can handle them. In
addition, this order allows administrators to become accustomed to the
new Domino Administrator client before assisting users with upgrading.
Domino Administration server and Domino Directory or Public

Address Book
Upgrade your first server and the Domino Directory at the same time.
If the Domino Directory resides on a designated administration server,
upgrade the administration server, then when prompted to upgrade the
Domino 4.6 Public Address Book or the Domino 5 Domino Directory, do
so. Otherwise, whichever server you choose to upgrade first, make sure
to also upgrade the Public Address Book or Domino Directory to the
Domino 6 design.
The Domino 6 Domino Directory template is backward compatible. After
you upgrade to the Domino 6 Domino Directory, you can replicate the
directory design to Domino 4.6 and Domino 5 servers. However, to
administer the Domino 6 Domino Directory, upgrade or install the
Domino 6 Administrator client.
For more information about Domino Directory and Domino server
upgrades, see the chapters “Upgrading the Domino Directory” and
“Upgrading Domino Servers.”
Domino Administrator client

Install the Lotus Domino 6 server and any Lotus Notes 6 clients —
including the Domino Administrator — on separate machines. This is a
change from Lotus Domino 4.6, in which installing a server automatically
installed the Domino Administrator on the same machine. When you
install a Domino 6 server, the Setup program does not install the Domino
Administrator or NOTES.EXE.
For more information about upgrading the Domino Administrator client,
see the chapter “Upgrading Domino Servers.”
1-4 Upgrade Guide

Hub servers
Hub servers handle significant mail and replication traffic and benefit
greatly from the improved performance and administration in Lotus
Domino 6. When you take a hub server off-line to upgrade it, be aware of
the disruption it may cause to your network. Though users may not
access a hub server directly, they can be affected when you take a hub
server off-line.
At the same time you upgrade the hub servers for your organization,
upgrade the administration clients that administer your Domino servers.
Mail servers
After upgrading your hub servers, use the knowledge gained from that
process when you upgrade your organization’s mail servers. Lotus
Domino 6 includes numerous performance enhancements and new
features to make your mail infrastructure faster, more powerful, and
more reliable. Users benefit from increased performance and features
such as native network compression, improved Internet Message Access
Protocol (IMAP), and soft deletions. Upgrading mail servers takes longer
than upgrading hubs and involves more people, but the experience
gained from working with the hubs should streamline this process.
Wait to upgrade users’ mail files to the Domino 6 mail template until
Notes users move to Lotus Notes 6. For your users who access mail only
from POP (Post Office Protocol) or IMAP (Internet Message Access Proto-
col) clients such as Microsoft Outlook® and Netscape® Communicator,
you can upgrade their mail files to the Domino 6 template immediately.
If you are upgrading Domino 4.6 mail servers to Lotus Domino 6, you
have several options from which to choose.
To help you in planning your Domino 4.6 mail server upgrades, see the
topic “Domino mail server upgrade scenarios” later in this chapter.
Application servers
Your applications, and the servers they run on, are often the heart of
your business, so upgrade them after your team is thoroughly familiar
with the procedures, issues, and techniques required for moving to Lotus
Notes/Domino 6. Carefully test your applications on Lotus Domino 6
before upgrading your production environment — while complete back-
ward compatibility is the goal for Lotus Domino 6, issues may arise with
applications that use undocumented features or workarounds. Consider
whether to upgrade the format of your applications to Domino 6 —
gaining performance improvements, backup and transaction logging
capabilities, or whether to leave them in Domino 4.6 or Domino 5 format,
so Domino 4.6 or Domino 5 clients and servers can create replicas from
them.

Notes clients
Roll out Lotus Notes 6 to users after upgrading the servers those users
access. Lotus Notes 6 upgrades Notes 4.6 and Notes 5 clients automati-
cally. For Notes 4.6 clients, Lotus Notes 6 creates a set of bookmarks
based on a user’s workspace and upgrades the design of the Personal
Address Book. Lotus Notes 4.6 users may need training on how to use
the new Notes user interface, though the similarity between the new user
interface and Web browsers eases the transition.
Lotus Notes 5 users will find the Lotus Notes 6 user interface familiar,
though some new features, like the Welcome Page wizard to help you
customize your Welcome page, are available.
For more information, see the chapter “Upgrading Notes Clients.”
Applications and databases

After you upgrade Domino servers and Notes clients, begin upgrading
applications and databases. This involves replacing the designs of
standard databases (such as mail files, discussion databases, and
document libraries) with Notes/Domino 6 templates. Because Notes 5
and earlier clients cannot use Notes/Domino 6 features, make sure your
users have upgraded before implementing the new templates or features
in your databases and applications.
Database format does not replicate, so you can upgrade a replica to the
new format on Lotus Domino 6 and let it replicate with a Domino 4.6 or
Domino 5 replica on Domino 4.6 or Domino 5 server. However, after you
upgrade a database, new replicas and copies of that database use the
Domino 6 format by default. During the time your infrastructure has
mixed releases, you may want to keep some databases in Domino 4.6 or
Domino 5 format. After your system has completed its transition to Lotus
Notes/Domino 6, though, upgrade any remaining Domino 4.6 or
Domino 5 databases to gain the performance and reliability enhance-
ments that the new format offers.
Before you upgrade applications and databases, test them in a Lotus
Notes/Domino 6 environment. See the topic “Testing applications before
upgrading” later in this chapter. For more information about upgrading
databases, see the chapter “Upgrading Databases and Applications.”
How Lotus Domino 6 replaces the Domino 4.6 MTA

When you enable a Domino 6 server to send messages over SMTP
outside the local Internet domain (configured in the Server Configuration
document), the server does not require Foreign SMTP Domain and SMTP
Connection documents because the server can connect by TCP and route
mail by SMTP. However, if you have existing SMTP Connection
1-6 Upgrade Guide

documents, Lotus Domino 6 follows the Foreign SMTP Domain and
SMTP Connection documents for SMTP mail routing.
The server can use a relay host as needed and can make connections
using DNS or using a hosts file. The server uses the router to route mail
over SMTP and to perform conversion between Notes format messages
and MIME format messages. Thus, the Domino 6 server replaces the
outbound services of the MTA.
When you enable a Domino 6 server to listen for inbound SMTP connec-
tions (configured in the Server document), the server performs the same
functions as the inbound MTA services. Inbound messages are stored in
MAIL.BOX and transferred or delivered by the router. MIME messages
are stored in that format and routed over either Notes RPC or SMTP to
their destination. If needed, the router converts between MIME and
Notes format messages.
Domino 4.6 mail server upgrade scenarios

Organizations upgrading from Lotus Domino 4.6 to Lotus Domino 6
should consider when to upgrade the Domino 4.6 MTA servers to
Domino 6 mail servers. Domino introduced Native SMTP in Lotus
Domino 5, eliminating the need for the SMTP MTA. Lotus Domino 6 has
three major changes that affect this decision:
• The Domino 6 router sends, routes, and delivers MIME messages
over both SMTP and Notes RPC
• The Domino 6 database format stores MIME messages natively
• Notes 6 clients can create, read, and send MIME messages over both
SMTP and Notes RPC
When considering upgrading the MTAs to Lotus Domino 6, you have a
number of options:
• Leave the Domino 4.6 MTAs in place until the rest of your system is
upgraded
• Replace the Domino 4.6 MTAs with Domino 6 mail servers before
upgrading the rest of your system
• Rework your messaging infrastructure to eliminating the need for
separate SMTP servers because all Domino 6 servers can route
Internet mail
• Use a mixed strategy
For a Domino 4.6 to Domino 6 upgrade example, see the topic “Replacing
Domino 4.6 MTAs with Domino 6 mail servers” later in this chapter.

Leave your Domino 4.6 MTA servers in place
This scenario leaves your Domino 4.6 MTA servers in place until you
have upgraded all other Domino servers and Notes clients to Lotus
Notes/Domino 6. This option ensures a known level of functionality for
Internet message traffic during the upgrade process, but does not allow
your organization to use the new Internet mail features of the Domino 6
server. For example, Notes 6 clients cannot send native MIME to Internet
recipients with this strategy — their Domino 6 mail server must convert
the native MIME to Notes format and then transfer it to the Domino 4.6
MTA. This increases load on the mail server and could cause some loss of
message fidelity.
Replace all Domino 4.6 MTAs with Domino 6 mail servers first
The Domino 6 mail servers perform the same tasks as Domino 4.6 MTAs,
with greater performance, stability, and message fidelity. Your organiza-
tion can use Domino 6 features such as restrictions to prevent spamming
and control maximum message size. Notes 6 and Internet clients can use
native MIME seamlessly.
If you upgrade your Domino 4.6 MTA servers to Lotus Domino 6 before
upgrading the rest of your Domino system, the Domino 6 mail servers
store MIME messages in MIME format, but must convert the messages to
Notes format, to an attachment containing the MIME message, or to both
a Notes format message and an attachment, when transferring the
message to a Domino 4.6 server.
For more information, see the chapter “Upgrading Domino Servers.”
As you change your infrastructure to Lotus Domino 6, the Domino 6 mail
servers can route MIME messages to other Domino 6 mail servers, which
can deliver the messages or perform the conversion for Domino 4.6
servers.
Replace all Domino 4.6 MTAs with Domino 6 mail servers during
system upgrade
This strategy is similar to upgrading MTAs before upgrading the rest of
your system, but allows you to select when to begin conversion on hub
servers or spoke servers. For example, if you use a Domino POP3 server
to host mail for a large number of POP3 clients, you might wait to
upgrade your MTAs until you upgrade the POP3 server to prevent any
need for conversion by the POP3 server or its hub. In addition, if your
hub servers are near capacity, but your spoke servers have extra
capacity, you might wait to upgrade the MTA servers until the spoke
servers have been upgraded to prevent placing the conversion load on
the hubs.
1-8 Upgrade Guide

Rework the messaging infrastructure to implement a distributed
infrastructure
In a Domino 4.6-style Internet messaging infrastructure, all Internet mail
messages route through one or more dedicated MTA servers. In Lotus
Domino 6, dedicated MTA servers are no longer necessary as all Domino
6 servers can route Internet mail, including performing any necessary
conversions. If you want to move from a Domino 4.6 “gateway” architec-
ture to a more distributed Internet mail routing infrastructure, note the
following issues:
• When you enable a distributed infrastructure, where messages no
longer route through a few SMTP servers, but rather use the Domino
6 router to transfer Internet mail, consider the possible conversion
load from Notes clients. If a Notes client sends a message to Internet
recipients in Notes message format, the Domino 6 mail server
converts that message to MIME and routes it. If your mail servers are
near capacity, this conversion load may place an unacceptable strain
on them. However, spreading conversion across all mail servers,
instead of concentrating it on a few MTA servers, is often a
performance improvement for organizations. Depending on your
system, you may want to wait until you begin converting Notes
clients to Lotus Notes 6 to rework your messaging architecture.
Because Notes 6 clients can send and read MIME, the conversion
load on the mail servers is less.
• Enabling SMTP routing on all mail servers in your organization does
not require the mail servers to have direct Internet access. You can
use a relay host for mail routing beyond your local Internet domain
and for security purposes. The relay host can be a Domino 6 mail
server, a Domino 4.6 MTA, or a third-party product.
• If you enable direct Internet access for all mail servers, make sure
they are correctly configured and properly registered with the
InterNIC. For security reasons, many systems do not accept
connections or mail from servers that are improperly configured or
not registered.
Use a mixed MTA upgrade strategy

Some organizations will use a combined strategy depending on their
needs and infrastructure. For example, a multinational organization may
immediately upgrade its MTA servers in one part of the world and wait
until the Domino system is at Lotus Domino 6 to upgrade in another. Use
these scenarios and the needs of your organization to determine the
optimal upgrade strategy.

Replacing Domino 4.6 MTAs with Domino 6 mail servers
To illustrate replacing Domino 4.6 MTAs with Domino 6 mail servers,
consider an infrastructure with three Domino servers: MTA1, Hub-E, and
Hub-W. MTA1 is the SMTP server for the organization, and Hub-E and
Hub-W are hub servers that route mail to a number of spoke servers. If
you upgrade MTA1 to Lotus Domino 6 and leave the hubs at Lotus
Domino 4.6, MTA1 performs all necessary message conversion, as it did
when the server was at Lotus Domino 4.6. When you upgrade Hub-E
and Hub-W to Lotus Domino 6, MTA1 routes Internet messages to the
hubs in MIME, and the hubs perform message conversion for Domino 4.6
spokes. As you upgrade spoke servers to Lotus Domino 6, the hub
servers perform fewer conversions. However, the spoke servers must
convert messages for their Notes 4.6 clients. Finally, when you upgrade
the Notes clients to Lotus Notes 6, MIME messages can be routed from
MTA1 to the destination client without conversion.
This upgrade process spreads the conversion load over more servers as
the process progresses — from one server (MTA1) initially to many
servers (the spokes) towards the end. It is important to consider the
performance and capabilities of the hubs and spoke servers — for
example, the spokes might not have enough spare performance to handle
the conversion load, which might necessitate a different upgrade
strategy.
Domino 6 SMTP routing attempts to locate the Internet Address for a
Notes user either within the message (if the message is created by a
Notes 6, IMAP, or POP client) or within the $Users view in the Domino
Directory. For best performance, populate the Internet Address field in
your organization’s Person documents (if the Short Name field does not
already contain an Internet address for each user) with the administra-
tion tool for Internet addresses. Also, register new users with a Domino 6
Administrator to ensure that each user has a valid Internet address.
For more information, see the chapter “Upgrading Domino Servers.”
Note You can add the variable MailConvertMIMEOnTransfer=1 to the
Domino server’s NOTES.INI file to force the server to convert inbound
mail from the Internet from MIME to the format specified in each
recipient’s Person document in the Domino Directory. This setting causes
the router on the Domino 6 server to mimic the functionality of the
Domino 4.6 SMTP/MIME Message Transfer Agent. If you do not set this
variable, the Domino 6 router forwards the native MIME messages to the
next hop servers. Any necessary conversion takes place on transfer to a
Domino 4.6 server or on delivery to the user’s mail file.
1-10 Upgrade Guide

Testing applications before upgrading
Lotus Notes/Domino 4.6 and Notes/Domino 5 applications should func-
tion unchanged under Lotus Notes/Domino 6. However, it is essential
that you test important applications in a lab environment before upgrad-
ing mission-critical production applications to Lotus Notes/Domino 6 in
a production setting. Sophisticated applications require careful testing
because potential issues may be subtle or not easily evaluated.
Create a list of the key features and functions in your applications and
evaluate their functionality under Lotus Notes/Domino 6. Apply any
Notes/Domino 6 templates and the Notes/Domino 6 format to applica-
tions. Be careful to document and test the following:
• Custom changes you have made to standard templates.
Notes/Domino 6 templates may incorporate the functionality you
added, making custom changes unnecessary, or may have changed
how the feature you are using works.
• Reuse of template code. If you duplicated standard template code,
such as LotusScript® or @commands, in your applications, be aware
that changes in how this code functions in templates will also be
reflected in how your application works.
• Use of undocumented features or settings. You may have used
features, commands, or items in Notes that are undocumented and
unsupported. While these items may have worked in earlier releases,
they might not in Lotus Notes/Domino 6.
• Creative workarounds. You may have implemented coding or design
changes to overcome a limitation in earlier releases. These
workarounds may no longer be necessary in Lotus Notes/Domino 6,
or functionality changes could change how the workarounds operate.
Be certain to test your applications thoroughly under conditions that
mirror production use of the applications. Document your test proce-
dures and results, and make them available to your upgrade team. If you
document best practices as part of your upgrade process, incorporate the
test procedures and results into your documentation.
Steps for documenting applications

Documenting applications organizes essential information about the
application before you begin testing. If you have not already documented
your application, complete these steps.
1. (Optional) Create a database to store testing information. This helps
you keep track of progress, especially if you have many applications
to test. If other people need to use this database at several sites,
create a design template that they can use.

2. Document the type of application and its purpose. For example,
determine whether this is a discussion, mail-in, or IBM Lotus
Workflow™ application. If it is a mail-in application, document the
name that the Domino Directory uses. If it is a Lotus Workflow
application, document the databases that this application uses.
3. Document any external databases or files that this application uses.
For example, determine whether this application accesses data stored
in an external database or file using @DbCommand or @DbLookup.
4. Document any Notes databases that this application references. If the
application references databases created with system templates —
for example, the Domino Directory — document whether the formu-
las in the application reference hidden views. Many system design
templates are changed in Lotus Notes/Domino 6. Therefore certain
views may no longer exist. To prevent problems, do not design appli-
cations that rely on hidden views in system design templates.
5. Document any Notes API programs that this application uses or any
API programs that modify this application.
6. Document any external OLE applications that this application uses.
7. Document the servers that this application replicates with.
8. Repeat Steps 2 through 7 for every application you need to
document.
Use a test environment

A test environment is an ideal place to experiment with new
Notes/Domino 6 features and functionality — it provides real-world
conditions without risk to your applications or impact on your business.
Before rolling out a new Notes/Domino 6 feature set or code, use it in
your test environment to prove its stability and that it functions as
intended. Notes/Domino 6 features are generally not available to earlier
clients, so evaluate their usability and impact on earlier releases before
rolling them out to your applications and users.
Back up key applications before upgrading them. If there are problems
during the upgrade, or if you encounter issues after upgrading, you can
replace the application with the backed-up version.
Note After upgrading the design of an application, you must rebuild
the views in that database. You can do this by opening the database in a
Notes client and pressing CTRL+SHIFT+F9, or at the Domino server
console, type the command:
load updall databaseName.nsf -r
and press ENTER.
1-12 Upgrade Guide

Steps for testing applications
Your testing strategy may vary depending on the number of applications
your organization needs to test.
1. If you have not done so already, install Lotus Domino Designer on
your workstation.
2. Create documents using each form in the application, including
hidden forms. Make sure that you can enter information into each
field in the form, that buttons work correctly, and that the text on the
form displays correctly.
3. Open in each view the documents you just created. Make sure that
they display correctly and that formulas calculate correctly. Make
sure hidden views work correctly.
4. Display the documents you just created. Make sure that they display
correctly and that formulas calculate correctly.
5. If the application uses external databases or files, modify data in the
external database or file and make sure the application updates the
formulas correctly.
6. If the application uses formulas that reference hidden views in
system databases — for example, the Domino Directory — make
sure these formulas work correctly.
7. If the application uses external OLE applications, create forms that
use the OLE application and launch the objects.
8. Test any agents to make sure they work correctly.
9. Check the security of the database. For example, check the access
control list; encryption keys; roles; and the readers and authors access.
10. If the application uses selective replication formulas, test these
formulas to make sure they work correctly. For example, check the
replica database to make sure the documents you selected replicated
properly.
11. Repeat Steps 2 through 11 for every application you need to test.
The upgrade roadmap

The following task list includes typical tasks for upgrading an existing
Lotus Notes/Domino system to Lotus Notes/Domino 6. Upgrading a
mission-critical system requires careful planning. As you perform the
tasks, track the problems that arise and their solutions, then compile
them into a “best practices” database or Web site that you can share with
your organization. Note that you may not find all of the following tasks
applicable to your organization.

1. Review the Lotus Domino Administrator 6 Help and the Release Notes
to familiarize yourself with changes and to determine which new
features you want to implement.
For more information about changes and new features, see the topics
“New Domino server and Domino Administrator client features”
and “Domino server and Domino Administrator client
enhancements” later in this chapter.
2. Create a prioritized list of all servers and clients, then create a
schedule for upgrading them.
For more information about planning your upgrade, see the topic
“Planning the upgrade” earlier in this chapter.
3. Identify servers and clients that need upgraded hardware, operating
system software, and network software. Refer to the Release Notes for
the latest system and platform requirements.
4. Obtain approval for any necessary hardware and software. Before
you upgrade the servers or clients, install the new hardware or
software. You may want to consider consolidation of servers and
functionality.
5. Determine the distribution method for Lotus Domino 6 server and
Lotus Notes 6 client software. Remote site coordinators require
server software. If users upgrade their own clients, the users require
client software.
6. Determine the method for upgrading Notes clients and mail file
templates. You have several options for upgrading both the client
and mail file template, including Upgrade-by-mail.
For more information about Upgrade-by-mail and other options, see
the chapter “Upgrading a Notes Client.”
7. Create an upgrade schedule. The schedule includes a list of upgrade
tasks, who will complete the tasks, and when the tasks will be
completed.
8. Set up a testing environment that includes Domino 6 and Domino 4.6
or Domino 5 servers and clients. Use the environment to test your
custom applications and new features that you want to implement.
Separate the test environment for your current Lotus Notes/Domino
production environment to avoid potential problems.
9. Create an application testing plan. This plan includes which
applications to test and designates testers.
For more information about testing applications, see the topic
“Testing applications before upgrading” earlier in this chapter.
1-14 Upgrade Guide

10. Test applications in the test environment to ensure that they function
properly. Review system templates that you customized to
determine whether or not the customizations are necessary in Lotus
Notes/Domino 6. Test the Domino Directory for authentication and
access to existing applications.
11. Create a list of applications that you want to upgrade. Use the
information found during testing to create this list.
12. When you complete your testing, notify your organization’s Domino
administrators and database managers of your upgrade plans.
13. Upgrade the first Domino server, Domino Directory or Public
Address Book, and the Domino Administrator client.
For more information about upgrading Domino servers, see the
chapter “Upgrading Domino Servers.”
14. Replicate the Domino 6 Domino Directory throughout your domain.
The Domino 6 directory design is compatible with both Domino 4.6
and Domino 5 servers.
For more information about upgrading the Domino Directory, see
the chapter “Upgrading the Domino Directory.”
15. Upgrade the remaining servers in your domain. Use your server
upgrade order in your upgrade schedule. At this time, make sure to
monitor servers and to troubleshoot any problems that arise.
16. Notify users of the Notes client upgrade.
17. Upgrade Notes clients. Use the order you specified in the upgrade
schedule. Make sure to monitor clients and to troubleshoot any
problems that arise.
For more information about upgrading Notes clients, see the chapter
“Upgrading Notes Clients.”
18. Notify users of the mail file template upgrade.
19. Upgrade mail file templates. Make sure to monitor the mail
databases and to troubleshoot any problems that arise.
For more information about upgrading mail file templates, see the
chapter “Upgrading Notes Mail Files.”
20. Upgrade the applications identified in your testing. This includes
upgrading the database format to the Domino 6 format and
rebuilding views.
For more information about upgrading applications, see the chapter
“Upgrading Databases and Applications.”
21. Implement new features.

New Domino server and Domino Administrator client features
The following tables list new features of the Lotus Domino 6 server and
Domino Administrator client and where you can find more information
about these features.
For information about Lotus Domino Designer 6 and Lotus Notes 6
features, see the topic “What’s New” in Lotus Domino Designer 6 Help
and Lotus Notes 6 Help. Or, go to http://www.lotus.com/ldd/doc to
download or view the Help databases.
For information about enhancements to the Lotus Domino 6 server and
Domino Administrator client, see the topic “Domino 6 server and
Domino Administrator client enhancements.”
Administration
New feature Description For more information
Server The Server Controller runs on a See the topic “The Server
Controller Domino server machine and Controller and the Domino
and Domino controls the server. The Domino Console” in the book
Console Console is a new console you can Administering the Domino
use to communicate with a Server System or in the Domino
Controller. The Domino Console can Administrator 6 Help.
run on any client or server platform
except Macintosh.
Roaming Stores user information on mail See the topic “Roaming
user servers or on designated roaming users” in the book
servers. By storing user information Administering the Domino
on a server, users can access their System or in the Domino
files from almost any Notes client. Administrator 6 Help.
IBM Lotus Upgrades and deploys Lotus Notes See the topic “Using IBM
Notes Smart 6 clients with incremental installers Lotus Notes Smart
Upgrade downloaded from Upgrade” in the chapter
www.lotus.com/ldd/ “Upgrading Lotus Notes
smartupgrade. Clients” or in the Domino
Administrator 6 Help.
continued
1-16 Upgrade Guide

Policies Establish and maintain standard See the following topics:
settings and configurations. Policies • Policies
can also automate redundant
• Creating an archive
administrative tasks. Policy policy settings document
documents include:
• Creating a desktop
• Archive settings document to policy settings document
create and to modify a set of rules
that define how documents are • Creating a registration
policy settings document
selected and archived
• Creating a security
• Desktop settings document to
policy settings document
dynamically update desktop
settings and configurations for • Creating a setup policy
users, including custom Welcome settings document
pages in the book Administering
• Registration settings document to the Domino System or in the
register users with the same Domino Administrator 6
settings Help.
• Setup settings document to define
first-time user setup
configurations
• Security settings document to
manage passwords and adminis-
ter Execution Control Lists (ECLs)
Domino Synchronizes Person and Group See the topic “Setting up
Active documents in the Domino Directory Domino Active Directory
Directory with user and group accounts in the synchronization” in the
synchroniz- Microsoft Active® Directory. book Administering the
ation Domino System or in the
(ADSync) Domino Administrator 6
Help.
License Monitors the number of Lotus Notes See the topic “License
tracking users in a domain to determine how Tracking” in the book
many client licenses you have. Administering the Domino
System or in the Domino
Command Provides help for most server tasks See the topic “Domino
line help when you add “/?“ or “-?“ to a server commands” in the
LOAD or TELL command. book Administering the
Domino System or in the
Domino Administrator 6
Help.
continued

Server Captures detailed information about See the topic “Activity
Activity Notes sessions, databases, and logging” in the book
Logging passthru activity, as well as mail, Administering the Domino
replication, agent, POP3, SMTP, System or in the Domino
HTTP, IMAP, and LDAP activity. Administrator 6 Help.
Activity logging collects more data
and gives you more control over
data collection than the Domino
billing functionality.
Administration Process and Requests

New Numerous new administration See the topic
administration requests including: “Administration process
requests • Roaming user requests requests” in the book
• Service provider (hosted Administering the Domino
organizations) requests System or in the Domino
• System monitoring requests
• LDAP-related requests
Database management
LZ1 Replaces Huffman compression See the book Application
compression for file attachments. LZ1 Development with Domino
for attachments compression is optional. It saves Designer or the Domino
space by compressing Designer 6 Help.
attachments more efficiently
than Huffman compression.
Indirect (IND) Text file that lists databases for See the topic “Compacting
files the compact, fixup, and updall databases, rebuilding views,
tasks, all of which support the and fixing corrupt databases
IND file as a parameter. with an indirect file” in the
chapter “Upgrading
databases and applications”
or in the Domino
1-18 Upgrade Guide

Domino Directory and LDAP schema
Central Implements Configuration See the topic “Using a
Directory Directories, which are selective central directory
Architecture replicas of a primary Domino architecture in a Domino
Directory that contain only domain” in the book
documents related to Domino Administering the Domino
Server configuration. Servers System or in the Domino
with Configuration Directories Administrator 6 Help.
look up user and group
information in remote primary
Domino Directories on
designated directory servers.
Extended ACLs Refines the ACL and restricts See the topic “Extended
(xACLs) user access to specific portions of ACL” in the book
a Domino Directory or Extended Administering the Domino
Directory Catalog. Also enforces System or in the Domino
database security for Notes client Administrator 6 Help.
name lookups and for
anonymous LDAP search access.
Directory Specifying more than one value See the topic “Directory
Assistance in the Hostname field in an assistance and failover for
failover for LDAP Directory Assistance a remote LDAP directory”
remote LDAP document allows Directory in the book Administering
directories Assistance to fail over to another the Domino System or in the
LDAP server if the first specified Domino Administrator 6
server is unavailable. Help.
New statistics These include: See the topic “Monitoring
related to • Database.DARReloadCount directory assistance” in the
directory book Administering the
• Database.DARefreshServer
assistance InfoCount Domino System or in the
• Database.DAFailoverCount Help.
Activity logging Allows you to determine who is See the topic “LDAP
for the LDAP reading or writing objects in the activity logging” in the
service directory. book Administering the
Domino System or in the
Help.
continued

Custom LDAP Override the built-in search See the topic “Configuring
filters used for filters used by Directory search filters in a Directory
directory Assistance when searching an Assistance document for a
assistance to a LDAP directory. Custom LDAP remote LDAP directory” in
remote LDAP filters can be used for mail the book Administering the
directory address lookups, client Domino System or in the
authentication credentials Domino Administrator 6
lookups, and group Help.
authorization lookups.
Domino Upgrade Services

LDAP Domino Migrates person and group See the topic “Migrating
Upgrade Service entries from an entries from an LDAP
LDAP-compliant external directory server” in the
directory to a Domino chapter “Migrating Entries
Directory. from an LDAP Directory
Server” or in the Domino
Microsoft Active Migrates users and groups See the topic “Migrating
Directory from an Active Directory to a Microsoft Active Directory
Domino Domino Directory. users and groups” in the
Upgrade Service chapter “Migrating Users
from Microsoft Active
Directory” or in the Domino
Microsoft Creates a Notes mail account See the topic “Migrating
Outlook Express in Outlook Express to which personal mail data” in the
upgrade wizard users can migrate personal chapter “Migrating Personal
mail and address book Mail Data” or in the Domino
contacts to Lotus Notes 6 mail Administrator 6 Help.
and the Personal Address
Book (PAB).
1-20 Upgrade Guide

Installation and Setup
Multi-user Enables multiple Lotus Notes See the topic “Multi-User
installation users to share one machine. Each installations” in the book
user has his own personal data Administering the Domino
files stored in separate data System or in the Domino
directories. This installation option Administrator 6 Help.
is available for only the Lotus
Notes client.
Multi-version Installs more than one Domino
UNIX server on the same UNIX machine.
installation
UNIX Four new UNIX installation See the topic “Installing
installation options were added: Domino on UNIX
options • Install template files - you can systems” in the book
choose whether or not to install Installing Domino Servers
the Domino 6 system templates or in the Domino
• Create /opt/lotus soft link
during installation - you can
create a soft link to the
/opt/lotus location if you chose
an installation location other
than /opt/lotus
• Install Service Provider - you
can setup a service provider
server after installation of a
Domino Enterprise server
• Add data directories only - you
can add data directories to an
existing Domino installation
Domino Java™ Provides uniform functionality See the topic “The
setup and appearance for server Domino Server Setup
configuration across all Domino program” in the book
platforms. Installing Domino Servers
or in the Domino
Remote Domino Enables you to perform a remote See the topic “Using the
setup server setup without using HTTP. Domino Server Setup
program remotely” in
the book Installing
Domino Servers or in the
Help.
continued

Domino server Allows you to record and playback See the topics “Creating
setup profiles Domino Server Setup program a server setup profile”
settings so that you can quickly and “Using a server
configure either locally or setup profile” in the
remotely standard types of servers, book Installing Domino
such as mail servers. Servers or in the Domino
Internet Site Contain configuration settings for See the topic “Internet
documents the Internet protocol that you Site documents” in the
specify for the protocol server. book Administering the
These documents include: Domino System or in the
• Web Site document for the Domino Administrator 6
HTTP protocol Help.
• IMAP Site document
• POP3 Site document
• SMTP Inbound Site document
• Directory Site document for
LDAPservers
• IIOP Site document
• Global Web Settings document
defines the same Web rules as
the Web site document for all
Web sites in the Server\Internet
Sites view
Internet site Provides a single view for the See the topic
view in the configuration information for all “Converting from Web
Domino Internet protocol server tasks. This Server Configurations to
Directory view replaces the Domino 5 Web Internet Sites view” in
Configurations view. the book Administering
the Domino System or in
the Domino
Messaging
iNotes Web Provides Notes users with See the topic “iNotes Web
Access™ browser-based access to Notes Access” in the book
mail, calendar, and scheduling Administering the Domino
features. iNotes Web Access users System or in the Domino
can send and receive mail, view Administrator 6 Help.
their calendars, invite people to
meetings, create To Do lists, keep
a notebook, and work off-line.
continued
1-22 Upgrade Guide

Server mail Filter messages based on specified See the topic “Setting server
rules criteria and perform defined mail rules” in the book
actions on those messages. Administering the Domino
Anti-relay Restrict internal hosts from See the topic “Preventing
restrictions relaying and specify relay access unauthorized SMTP hosts
for authenticated external hosts from using Domino as a
(for example, POP3 clients relay” in the book
connecting through an external Administering the Domino
ISP). System or in the Domino
DNS Checks whether or not an SMTP See the topic “Enabling DNS
Blacklist connection originated from hosts blacklist filters for SMTP
filters listed on DNS Blacklist sites. connec-
tions” in the book
Administering the Domino
Mail file Allows you to set quota controls See the topic “Using quotas to
quota for the mail router and to enable manage the size of user mail
management automatic notification to users files” in the book
who exceed the warning thresh- Administering the Domino
old or quota limit imposed on System or in the Domino
their mail files. It can also Administrator 6 Help.
withhold mail from users who
exceed their quota limit.
Mail Works with server mail rules to See the topic “Mail
message examine messages and to save journaling” in the book
journaling copies of messages to a Notes Administering the Domino
journal database for later System or in the Domino
retrieval. Administrator 6 Help.

Networking
Native Speeds up data transmission either See the topic “Compressing
network between a Lotus Notes client and a network data on a server
compression Lotus Domino server or between port” in the book
two Lotus Domino servers. Administering the Domino
AutoDialer Lets you link two Connection See the topic “Creating a
for documents to enable a server with Network Dialup connection”
coordinating a dialup Internet connection to in the book Administering the
dialup ISP connect automatically in Domino System or in the
connections anticipation of a scheduled Domino Administrator 6
between replication or mail transfer Help.
servers initiated by another server.
Security
Certificate Allows the revocation See the topic “Domino server-based
Revocation List status of a certificate to be certification authority” in the book
(CRL) for the verified before trusting it. Administering the Domino System or
Internet CA in the Domino Administrator 6
Help.
Synchronize Uses a security settings See the topic “Managing Internet
Internet document to synchronize passwords” in the book
passwords Internet and Notes ID Administering the Domino System or
with Notes ID passwords. in the Domino Administrator 6
passwords Help.
SSL session Allows for the See the topic “SSL session
resumption cryptographic work of resumption” in the book
authenticating over SSL Administering the Domino System or
to occur only on the first in the Domino Administrator 6
connection, with all Help.
subsequent connections
reusing the existing
keying information.
Server Grants different See the topic “Restricting
administration administration rights to administrator access” in the book
delegation different administrators Administering the Domino System or
of the same server. in the Domino Administrator 6
Help.
1-24 Upgrade Guide

Service provider (xSP)
Server Activity Enables xSPs to program- See the topic “Using activity
Logging for matically access logging for billing at hosted
xSPs LOG.NSF. organizations” in the book
Administering the Domino System or
in the Domino Administrator 6
Help.
System monitoring and maintenance

Automatic Shuts down and restarts a server See the topic “Fault
fault recovery automatically without recovery” in the book
administrator intervention. Administering the Domino
Available for Windows NT and System or in the Domino
UNIX platforms. Administrator 6 Help.
IBM Tivoli® Includes Server Health See the topic “IBM Tivoli
Analyzer for Monitoring, which offers Analyzer for Lotus
Lotus Domino real-time assessment and Domino tool” in the book
recommendations for server Administering the Domino
performance, and Activity System or in the Domino
Trends, which provides data Administrator 6 Help.
collection, data exploration, and
resource balancing. This tool
requires a separate license to use.
Web server
New HTTP These include: See the topic “Setting up
protocol security • Maximum URL length protocol security for the
options Web server” in the book
• Maximum number of URL
path segments Administering the Domino
• Maximum number of request Administrator 6 Help.
headers
• Maximum size of request
headers
• Maximum size of request
content
continued

WebDAV A set of extensions to HTTP 1.1 See the topic “Setting up
(Web-based that allows you to WebDAV” in the book
Distributed collaboratively edit and manage Administering the Domino
Authoring and files stored as design elements in System or in the Domino
Versioning) Domino databases on remote Administrator 6 Help.
support Web servers using
WebDAV-enabled clients.
New Web users These include: See the topic “Storing Web
preferences • Time zone user preferences in
cookies” in the book
• Date/time format
• Number format System or in the Domino
These settings are stored in Administrator 6 Help.
cookies, so that users can
maintain these preferences
throughout their sessions.
Domino server and Domino Administrator client enhancements

The following tables list enhancements to existing Domino server and
Domino Administrator client features and where you can find more
information about them.
For more information about Lotus Domino 6 server and Domino
Administrator client features, see the topic “New Domino server and
Domino Administrator client features” earlier in this chapter.
Administration
Enhancement For more information
You can specify the NOTES.INI file See the topic “Improving UNIX server
location when starting the Domino performance” in the book Administering
server on UNIX platforms. the Domino System or in the Domino
1-26 Upgrade Guide

Administration Process and Requests
You can specify extended administration See the topic “Using an extended
servers to process Domino Directory administration server” in the
administration requests for more than one book Administering the Domino
administration server per Domino Directory. System or in the Domino
The administration process supports See the topic “Administration
secondary Domino Directories for Process support of secondary
maintaining user names and groups that Domino Directories” in the book
you do not want to store in NAMES.NSF. Administering the Domino System
or in the Domino Administrator 6
Help.
You can access the Administration Request See the topic “Managing
database by clicking Server - Analysis - Administration Process requests”
Administration Requests. Available views in the book Administering the
are listed alphabetically. New buttons make Domino System or in the Domino
managing requests easier. For example, use Administrator 6 Help.
“Approve Selected Requests” to approve
multiple selected requests at once.
Domino clusters
The Cluster Administrator is now a server thread. See the topic “The cluster
It automatically starts the Cluster Replicator and components” in the book
the Cluster Database Directory Manager. You no Administering Domino
longer need to include CLREPL and CLDBDIR in Clusters or in the Domino
the NOTES.INI ServerTasks setting. When you Administrator 6 Help.
upgrade cluster servers to Domino 6, Domino
removes CLREPL and CLDBDIR from the
ServerTasks setting.
To run more than one Cluster Replicator, you can See the topic “Using
edit the Configurations Settings document or make multiple Cluster
an entry in the NOTES.INI file. Replicators” in the book
Administering Domino
Clusters or in the Domino
The server availability index now gives you a See the topic “The server
more accurate indication of the availability of each availability index” in the
server in a cluster. You should not use the book Administering Domino
NOTES.INI setting Server_Transinfo_Normalize Clusters or in the Domino
on Domino 6 servers. Administrator 6 Help.
continued

You can use the Domino 6 Server Monitor to See the topic “Monitoring
monitor all servers in a cluster at the same time. all the servers in a cluster
at the same time” in the
book Administering Domino
Clusters or in the Domino
By default, cluster replication now ignores See the topic “Obeying
database size quotas. This assures that replicas can database size quotas
be identical when users fail over. To make cluster during cluster replication”
replication obey database size quotas, you can edit in the book Administering
the Configurations Settings document or make an Domino Clusters or in the
entry in the NOTES.INI file. Domino Administrator 6
Help.
Many activities are cluster-aware or let you See the following topics:
perform procedures on as many servers as you • Using Advanced Notes
want at the same time. For example: user registration with
• When you register users, you can create replica the Domino
mail files for them on multiple cluster servers. Administrator
• When you register users or upgrade users for • Setting up roaming in a
roaming, you can create replicas of roaming files cluster
on multiple cluster servers. • Creating replicas in a
• When you replicate databases, you can create cluster
replicas of as many databases as you want on as • Deleting a user name
many cluster servers as you want all with one with the Domino
procedure. Administrator
• When you delete databases, you can delete • Redistributing replicas
replicas on other cluster servers.
• Moving a user’s mail file
• When you delete user names, you can delete all and roaming files from
replicas of the users’ mail files. the Domino Administra-
• When you move databases, you can move them tor or the Web
to as many cluster servers as you want. Administrator
• When you move users’ mail files from a cluster in the book Administering
to a server that is not in a cluster, you can delet Domino Clusters or in the
all replicas of the mail files from the cluster. Domino Administrator 6
Help.
1-28 Upgrade Guide

Domino Directory and LDAP Schema
You can use a remote LDAP directory or See the topic “Directory assistance
a secondary Domino Directory to and client authentication” in the
authenticate IMAP, POP3, and LDAP book Administering the Domino
clients. Previously this capability was System or in the Domino
only available for Web (HTTP) client Administrator 6 Help.
authentication.
You can specify secondary Domino See the topic “Administration
Directories for maintaining user names Process support of secondary
and groups that you do not want to store Domino Directories” in the book
in NAMES.NSF. Administering the Domino System or
Help.
You can store groups used in database See the topic “Directory assistance
ACLs in a secondary Domino Directory, and group lookups for database
in addition to a server’s primary Domino authorization” in the book
Directory. Previously you could store Administering the Domino System or
such groups only in a remote LDAP in the Domino Administrator 6
directory only in addition to the primary Help.
Domino Directory.
Directory Assistance can now use cluster See the topic “Using Directory
failover to fail over to an alternate replica Assistance in a cluster” in the book
of a Domino Directory. Administering the Domino System or
Help.
You have more control over how a server See the topic “Directory assistance
uses a secondary Domino Directory services” in the book Administering
configured in a directory assistance the Domino System or in the Domino
database. For example, you can disable Administrator 6 Help.
the directory for LDAP use. Previously
this control was available for only a
remote LDAP directory/
Lotus Domino 6 can serve up directories See the topic “How directory
through LDAP, NAMELookup, or both. assistance works” in the book
Help.
continued

The LDAP service schema now supports See the topic “The Domino LDAP
the following: schema” in the book Administering
• LDAP RFCs 2252, 2256, 2798, 2247, the Domino System or in the Domino
2739, 2079, and 1274 Administrator 6 Help.
• True object class inheritance
• namingContext operational attribute
defined in LDAP standard RFC 2251
• Automatic schema maintenance
process
• Arbitrary distinguished names
You can use the LDAP Schema database See the topic “Domino LDAP
template, SCHEMA.NSF, as a tool for Schema database” in the book
maintaining and extending the schema. Administering the Domino System or
Help.
There are additional LDAP service See the topic “Customizing the
configuration settings available on the LDAP service configuration” in the
Configurations Settings document, some book Administering the Domino
of which were previously controlled System or in the Domino
through the NOTES.INI file. The LDAP Administrator 6 Help.
service detects changes to these settings
automatically so that restarting the
LDAP service is unnecessary.
A directory indexer created by the See the topic “Indexer tasks: Update
database indexer (Update task) keeps and Updall” in the book
Domino Directory view indexes Administering the Domino System or
up-to-date. in the Domino Administrator 6
Help.
Domino Off-Line Services (DOLS)

You can take directory catalog databases See the topic “Allowing users to
off-line. take the Domino diretory offline” in
the book Administering the Domino
You can encrypt a subscription. See the topic “Configuring the
DOLS subscription” in the book
Help.
continued
1-30 Upgrade Guide

You can load customized subscriptions See the topic “Reducing DOLS
onto the DOLS Client Pre-Installer CD. download time with the client
installation CD” in the book
Help.
The “Allow per-user shared subscription See the topic “Configuring the
data” option enables a subscription to DOLS subscription” in the book
share files with other off-line Administering the Domino System or
subscriptions as long as the user has both in the Domino Administrator 6
files installed. Help.
You can deselect the “Full Text Index See the topic “Configuring the
subscription after sync” and “Compact DOLS subscription” in the book
subscription after sync” options to Administering the Domino System or
prevent compaction and full-text indexing in the Domino Administrator 6
of DOLS subscriptions. Help.
The “Push subscription settings\Push See the topic “Configuring the
subscription settings to iNotes Sync DOLS subscription” in the book
Manager” option in the Off-line Administering the Domino System or
Subscription Configuration Profile in the Domino Administrator 6
document pushes settings off-line to Help.
users, so users no longer need to reinstall
a subscription to update their settings.
The “Read only subscription See the topic “Configuring the
setting\Make schedule read only” option DOLS subscription” in the book
in the Off-line Subscription Configuration Administering the Domino System or
Profile document prevents users from in the Domino Administrator 6
modifying the synchronization schedule Help.
settings.
The “Use passthru server to connect to See the topic “Configuring the
destination server” option enables a DOLS subscription” in the book
subscription to use a passthru server to Administering the Domino System or
connect to the Domino server that hosts in the Domino Administrator 6
the subscription. Help.
continued

The “Use optional TCPIP address to See the topic “Configuring the
connect to destination server” option DOLS subscription” in the book
provides an optional or secondary Administering the Domino System or
TCP/IP address configuration to access in the Domino Administrator 6
the Domino server hosting a subscription. Help.
The “Always overwrite ID” option See the topic “Creating a DOLS
enables the Domino server to overwrite Offline Security Policy document”
the user’s off-line ID each time the user in the book Administering the
installs a subscription to keep IDs Domino System or in the Domino
up-to-date and consistent. Administrator 6 Help.
DOLS supports the Lotus Notes See the topics “Configuring the
multi-user and roaming user DOLS subscription” and “Creating
configuration. a DOLS Offline Security Policy
document” in the book
Help.
Keyboard shortcuts are available for See the topic “Web Control
nearly every option in the Web Control instructions for DOLS users” in the
and iNotes Sync Manager. book Administering the Domino
Messaging
IMAP service support for NAMESPACE See the topic “Configuring the IMAP
command enables IMAP mail users service to allow shared access to
access to designated public mail folders mail files” in the book Administering
and other users’ mail files to which they the Domino System or in the Domino
have delegated access. Administrator 6 Help.
You can run a report in the Mail Tracking See the topic “Tools for mail
Reports database with Author level monitoring” in the book
access. Running reports in this database Administering the Domino System or
previously required Manager level in the Domino Administrator 6
access. Help.
continued
1-32 Upgrade Guide

Shared mail has been enhanced with the See “Shared mail overview” in the
following changes: book Administering the Domino
• You can configure multiple shared System or in the Domino
mail databases and directories. Administrator 6 Help.
• You can associate user mail with more
than one shared mail database.
• There is a new Shared Mail tab on the
Server document.
• Lotus Domino 6 automatically creates
a shared mail database when you
install the server.
The “Verify that local domain recipients See the topic “Restricting users from
exist in the Domino Directory” option for receiving Internet mail” in the book
the SMTP listener task ensures that each Administering the Domino System or
user specified in the RCPT command is in the Domino Administrator 6
found in a configured directory. Help.
Networking
Support for the IPv6 standard for TCP/IP See the topic “IPv6 and Lotus
networks replaces support for the IPv4 standard. Domino” in the book
System or Installing Domino
Servers. Or see the Domino
The Domino SNMP Agent is now installed with See the topic “The Domino
the Domino server and includes several SNMP Agent” in the book
enhancements: Administering the Domino
• Configuration options are now set in the System or in the Domino
SNMP tab of the Server Configuration Settings Administrator 6 Help.
document in the Domino Directory, not in the
separat LSNMPCFG.NSF database.
• Partitioned servers are recognized automat -
cally. The file LNSNMP.INI is used if it’s
available, but it is not required, except for
partitioned server start functionality.
• Domino SNMP is available for the Linux
platform if prerequisite SMUX protocol (RFC
1227) support is available, for example, by
employing a properly configured UCD-SNMP
or NET-SNMP Master SNMP Agent.
continued

• The Domino MIB now contains comments that See the topic “The Domino
indicate which Domino statistic, if any, an SNMP Agent” in the book
object is derived from. Administering the Domino
• Most queries for objects derived from statistics System or in the Domino
use the current value of the statistic, not a Administrator 6 Help.
cached value.
• For efficiency, caching is still employed for the
lnAllStatsTable and for table row discovery.
• Over 200 objects have been added to the
Domino MIB.
• All known syntax errors have been corrected
in the Domino MIB.
Platform-specific steps are needed to configure
the agent, even if it was previously installed and
configured for Domino 4.6 or 5.
Search
A new version of the full-text search See the topic “Domain Search” in the
engine provides improved performance book Administering the Domino
and resource utilization as well as System or in the Domino
increased capacity for indexing. Administrator 6 Help.
Security
The new Domino Certificate Authority (CA) See the topic “Domino server-
for processing Notes and Internet certificate based certification authority” in
requests separates the role of CA the book Administering the
administrator from that of the registration Domino System or in the Domino
authority administrator. Administrator 6 Help.
You can dynamically deploy new or updated See the topic “Deploying and
Administrator ECLs to client workstations. updating workstation ECLs” in
the book Administering the
Domino System or in the Domino
continued
1-34 Upgrade Guide

Internet (HTTP) password restrictions for See the topic “Password
users configured in the Domino Directory Options dialog box” in the
allow you to: book Administering the Domino
• Set an expiration period on an Internet System or in the Domino
password Administrator 6 Help.
• Set a grace period for resetting Internet
passwords
• Require users to change Internet
passwords immediately
• Lockout Internet access for users requiring
password
• Determine Internet password quality and
length
SSL security settings for an Internet protocol See the topic “Internet Site
are obtained from a Site document rather documents” in the book
than a Server document. The Site document Administering the Domino
contains new options that control the System or in the Domino
Certificate Revocation Lists (CRLs), which do Administrator 6 Help.
not appear in the Server document.
New rules for agent security appear in the See the topic “Setting agent
Server Record in the Domino Directory. preferences for the Web
Navigator” in the book
Administering the Domino System
or in the Domino Administrator
6 Help.
The following security fields on the Security See the topic “Setting up Notes
tab of the Server document, which previously user, Domino server, and
applied only to Notes client access, now Internet user access to a Domino
apply to all Internet protocols in addition to server” in the book
the Notes client: Administering the Domino System
• Only allow server access to users listed in or in the Domino Administrator
the Directory 6 Help.
• Access server
• Not access server
The key string <ECLOwner> added to the See the topic “Administration
Administration ECL enables the current user ECL <ECLOwner> key” in the
to modify the ECL during client ECL refresh. book Administering the Domino
continued

The Domino Administrator client now logs See the topic “Collecting
the results of the Execution Security Alert information for a new
(ESA) dialog boxes, ESA details, and ECL administration ECL” in the book
modifications in the client log (LOG.NSF) in Administering the Domino System
Miscellaneous Events. or in the Domino Administrator
6 Help.
You can create Certification Revocation Lists See the topic “Domino
(CRLs). server-based certification
authority” in the book
System monitoring and maintenance

You can monitor events on your system See the topic “Event generators” in
using Event Generators. the book Administering the Domino
You can define Event Handlers to log an See the topic “Event handlers” in the
event, to notify you when an event book Administering the Domino
occurs, to forward an event for System or in the Domino
additional processing, or to prevent an Administrator 6 Help.
event from being logged.
You can monitor platform statistics. See the topic “Creating statistic
Predefined statistics counters have been profiles” in the book Administering
added to monitor networking, logical the Domino System or in the Domino
disk, memory, paging file, platform, Administrator 6 Help.
process, and system statistics for all
platforms.
You can create performance statistic See the topic “Creating statistic
profiles that you can monitor using profiles” in the book Administering
charts to display the statistics in real time the Domino System or in the Domino
or historically. Administrator 6 Help.
You can set console text, color, and See the topic “Customizing the
highlight attributes for both the remote appearance of the Domino server
server and local console, making it easier console and Domino Administrator
to read and interpret the system message console” in the book Administering
and information that appear on your the Domino System or in the Domino
system. Administrator 6 Help.
continued
1-36 Upgrade Guide

The Domino Server Monitor includes See the topic “Domino server
server profiles that let you monitor a monitor” in the book Administering
subset of servers and monitor only the the Domino System or in the Domino
tasks or processes specific to those Administrator 6 Help.
servers.
You can change Web user names with See the topic “Rename Selected
the Domino Administrator. Notes People dialog box” in the
book Administering the Domino
You can find server names, user names, See the following topics:
and groups in a domain by making an • Finding a server name in the
administration request. domain with the Domino Admin-
istrator or the Web Administrator
• Finding a user name in the
domain with the Domino Admin-
istrator or the Web Administrator
• Finding a group name in the
domain with the Domino Admin-
istrator or Web Administrator
in the book Administering the Domino
Enhanced server activity logging See the topic “Activity logging” in
captures detailed information about the book Administering the Domino
Notes sessions, databases, passthru System or in the Domino
servers, and scheduled agent activities, Administrator 6 Help.
as well as POP3, SMTP, HTTP, IMAP,
and LDAP activity.
With transaction logging for views, you See the topic “View logging” in the
no longer have to rebuild views after a book Administering the Domino
server crash. System or in the Domino
Web server
Enhancements For more information
By default, cookie logging is enabled as See the topic “The Domino Web
part of the new HTTP server task on server log (DOMLOG.NSF)” in the
Windows NT and Windows 2000 book Administering the Domino
platforms. Data provided by cookie System or in the Domino
logging appears in the text logs. Administrator 6 Help.
continued

Enhancements For more information
The HTTP response header is a new Web See the topic “Web Site Rules
site rule type in the Domino Directory document” in the book Administering
Server\Internet Sites view. This rule type the Domino System or in the Domino
adds an Expires header or custom header Administrator 6 Help.
to HTTP responses that match specified
URL patterns and response codes.
You can use single sign-on (SSO) for Web See the topic “Multi-server
browsers to sign on to a Domino or session-based name-and-password
WebSphere server once, then have access authentication for Web users (single
to any SSO-enabled Domino or sign-on)” in the book Administering
WebSphere server in your domain the Domino System or in the Domino
without signing on again. Administrator 6 Help.
Additionally, SSO allows multiple Web
SSO Configuration documents in a
Domino Directory or domain.
Interoperability issues
Typically, upgrade processes include a period of time in which you must
maintain a mixed-release environment. Until the upgrade is completed
you might have a mix of Lotus Domino 6 and Domino 5 or Domino 4.6
servers in production. More likely you might have Lotus Domino 6
servers and Lotus Notes 4.6 or Notes 5 clients and applications. The
following are known interoperability issues and general guidelines to
help you manage a mixed-release environment.
Server
• The Domino Administrator can administer an environment that
includes Notes/Domino 4.6 or Notes/Domino 5 and Domino 6.
However, because the Domino Administrator takes advantage of
new Domino 6 features, there are some limitations in a mixed
environment.
• Server bookmarks
If the Directory server (set in the Administration Preferences by
choosing File - Preferences - Administration Preferences) is not a
Lotus Domino 6 or 5 server, the Domino Administrator can
retrieve only 64K of server names for the server bookmarks. To
avoid this limitation, designate a Domino 6 server as the Directory
server.
1-38 Upgrade Guide

• User registration
User registration with the Domino Administrator does not
function properly if the registration server does not use the new
Domino Directory template.
• Server monitoring
When monitoring Domino 4.6 servers, the Domino Administrator
cannot report the status of individual tasks, such as the router. The
Domino Administrator reports only whether or not the server is
responding.
• Replication schedule
The replication schedule display does not work with Domino 4.6
servers.
• ACL management tools
The ACL management tools on the Files tab of the Domino
Administrator do not work with databases on Domino 4.6 servers.
• In previous releases of Lotus Notes/Domino, you configured Setup
Profiles to set workstation defaults. In Lotus Notes/Domino 6, you
use policies to configure the workstation defaults. Implementing
policies is optional. Lotus Notes/Domino 6 continues to support
Setup Profiles. However, if you choose to implement policies, be
aware of the following:
• Archive and registration settings documents have limited support
on Lotus Notes 5 and earlier clients, while the setup, desktop, and
security settings documents are supported only by Lotus Notes 6
clients.
• Setup Profiles in a Person document override policies.
• Setup Profiles continue to work in Lotus Notes/Domino 6, but are
not easily located in the Domino Directory.
For more information about policies, see the book Administering the
Domino System.
• The Domino 6 Web administrator template can be used to administer
only Lotus Domino 6 servers. Earlier releases of the Web
administrator template cannot administer a Lotus Domino 6 server.
• Domino 6 supports a new IP standard, IPv6. To connect Domino 4.6
or Domino 5 servers to an IPv6-enabled Domino server, create an old
A-type record in the Lotus Domino 6 server’s DNS.
For more information about IPv6, see either Administering the Domino
System or Installing Domino Servers.

• In a Domino 6 environment, you can implement either Internet site
documents or Server documents, but not both. If you select the
“Loads Internet configuration from Server/Internet Sites
documents” on the Basics tab of the Server document, then Internet
site documents will take precedence over your Server documents. If
you implement Internet site documents for one protocol, you must
implement the documents for each protocol that you use.
Implementing Internet Site documents for the POP3, IMAP, and
SMTP protocols overrides any server document settings that you
have set for those protocols.
In the mixed-release environment, you can use both Internet site
documents and Server documents to manage your environment. You
cannot use Internet site documents to configure your Domino 5 or
earlier servers.
• If you plan to create a cluster that includes some Domino 6 servers
and some Domino Release 5 or Release 4.6 servers, keep the
following in mind:
• Because the Cluster Replicator always replicates the template
design between replicas, a user’s mail replicas should all use the
same mail template — the Domino 6 mail template, the Domino
Release 5 mail template, or the Domino Release 4.6 mail template.
• If you move a user’s mail file from a Domino 6 or a Domino
Release 5 server to a Domino 4.6 server, free time information for
the user is not removed from CLUBUSY.NSF. Remove this
information from CLUBUSY.NSF so that cluster servers do not
have the wrong information for the user.
• If you are using an extended ACL in a database on a Domino 6
server in a cluster, it is best to include only Domino 6 servers in
the cluster. Otherwise, the replicas of the database can become
unsynchronized. When you use an extended ACL in a database,
changes you make to a replica on a Domino Release 5 or Release
4.6 server do not replicate to Domino 6 servers. In addition,
Domino 6 servers replicate to Domino 5 or Release 4.6 servers only
those changes allowed by the extended ACL.
• The Internet Cluster Manager (ICM) directs client requests to any
Domino Web server in the cluster. However, only Domino 6 and
Domino Release 5 Web servers generate URLs that include
references to the ICM. When a user selects one of these URLs, the
ICM balances the workload by redirecting the user to the most
available server. If the ICM redirects a user to a Domino Release
4.6 Web server, the server will not generate URLs that reference
the ICM. As the user moves between Web pages, the user
continues to access Web pages on the Domino Release 4.6 server
1-40 Upgrade Guide

only. To take advantage of the ICM at that point, the user must
select or enter a URL that contains a reference to the ICM.
Domino Directory and LDAP Schema

• The Domino Directory database templates are backward compatible,
and you can replicate the Domino 6 design to your Domino 4.6 and
Domino 5 servers. However, note the following precautions:
• Before you upgrade the Domino 4.6 Name and Address Book
(NAB) or Domino 5 Domino Directory to the Domino 6 design,
create a backup of the NAB or Domino Directory.
• To administer the Domino 6 Domino Directory, use a Domino 6
Administrator client.
• The Domino 6 Domino Directory template includes a number of
new field names that increased the size of the UniqueNameKey
(UNK) table. Domino 4.6 databases are limited to 64K, which the
Domino 6 Domino Directory template exceeds. Upgrade your
Domino 4.6 servers to Domino 4.6.7a to avoid problems with the
Domino Directory database size.
For more information about the Domino Directory and
UniqueNameKey table, see the chapter “Upgrading the Domino
Directory.”
• If a Domino 5 server and a Domino 6 server in the same domain both
run the LDAP service, LDAP users connecting to the Domino 5
server can search for an LDAP entry created on the Domino 6 server
that is not defined by the Domino 5 schema.
• If you implement Extended ACLs (xACLs), note the following:
• You must use a Notes 6 client to set Extended ACLs, and you
must set the Extended ACLs on a directory database on a Domino
6 server.
• You can use Extended ACLs in a mixed-release environment. To
replicate changes from a Domino 5 server to a Domino 6 server,
the Domino 6 server must pull the changes from the Domino 5
server.
• During Domino 6 to Domino 5 replication, the Domino 6 server
only replicates to the Domino 5 server the database contents that
the Extended ACLs allows the Domino 5 server to access.
• Lotus Domino 5 and earlier releases do not enforce Extended ACL
rules.

• After you upgrade your Domino 4.6 Public Address Book to the
Domino 6 Domino Directory design, you must upgrade your
Domino servers running LDAP to at least Domino 4.6.3 so they can
properly handle LDAP queries and return correct information. The
Domino Directory uses the Internet Address field to answer LDAP
queries. Lotus Notes/Domino 4.6 releases earlier than 4.6.3 do not
handle this change.
• You can implement the new Central Directory feature in a
mixed-release environment. Domino 6 servers can host either the
central or configuration directories. Domino 4.6 and Domino 5
servers can host the central directory, but not the configuration
directories.
• To implement cross-domain configuration documents in a
mixed-release environment, you must specify a Domino 5 or later
server as the administration server. Cross-domain requests are
processed only by Domino 5 or later servers.
Domain search
• When you include a Domino 4.6 server in a Domain search, the
Catalog task spiders the Domino 4.6 server rather than using
pull-replication as the task does with the database catalogs on
Domino 5 or Domino 6 servers. As a result, creating or updating the
Domain Catalog is time-consuming.
Mail and messaging

• In a mixed-release cluster, users cannot have a Notes/Domino 6 mail
file on Domino 4.6 or Domino 5 servers — the Notes/Domino 6 mail
template does not work properly on these releases. If you have a
mixed-release cluster with mail files, use the Notes/Domino 4.6 or
Notes/Domino 5 design for mail files or place users’ mail files only
on Domino 4.6 servers (with Domino 4.6 design), on Domino 5
servers only (with Domino 5 design), or on Domino 6 servers only
with the Domino 6 design. Do not mix mail file templates. Because
cluster replication ignores selective replication formulas, you cannot
prevent the mail file design from replicating to other clustered
servers.
• Message tracking for administrators (using the Tracking Center in
the Domino Administrator) can only track messages across Domino 6
servers that have message tracking enabled. If a message was
transferred to an earlier Domino or third-party server, you can no
longer track that message using the Tracking Center.
Users with a Notes/Domino 6 mail file can track messages that are
routed through earlier Domino and third-party servers as long as
these servers maintain the fidelity of the Notes fields in the message
1-42 Upgrade Guide

tracking request. Lotus Domino 6 only returns message tracking
information from Domino 6 servers that have message tracking
enabled. If the third-party servers do not maintain these fields,
messages cannot be tracked beyond these servers.
For more information about message tracking, see the book
Administering the Domino System.
• Lotus Notes 4.6 clients and servers cannot read native MIME
messages. To route a MIME message to a Lotus Domino 4.6 server,
Lotus Domino 6 has to convert a native MIME message to a Notes
document with a MIME attachment. Domino cannot convert an
encrypted MIME (S/MIME) message. When an S/MIME message is
transferred to a Domino 4.6 server, Lotus Domino converts the
message to an attachment containing the S/MIME and a Notes
format message stating that the Notes 4.6 client cannot display the
message because the Domino 4.6 server cannot decrypt it. This
conversion allows IMAP, POP, and Domino 6 users to receive
encrypted MIME mail and for encrypted MIME mail to be
transferred from a Domino 6 server to a Domino 4.6 server to
another Domino 6 server without loss of fidelity or breaking the
encrypted signature.
• Lotus Domino 6 introduces server mail rules, a feature that earlier
releases of Lotus Domino do not support. When you implement mail
rules, Lotus Domino 6 adds new entries to the Configuration Settings
document in the Domino Directory. This increases the size of the
UniqueNameKey (UNK) table. If your environment includes Domino
4.6 servers, those servers must accommodate the increased UNK
table size even though the servers do not support the new feature.
Domino 4.6 servers, prior to Domino 4.6.7a, have a maximum UNK
table size of 64KB.
Security
• With the relaxation of US government regulations on the export of
cryptography, the Domino server and the Domino Administrator,
Domino Designer, and Lotus Notes client have consolidated all
previous encryption strengths — North American, International, and
France — into one strong encryption level resulting in a single
“Global” release of the products. The Global release adopts the
encryption characteristics previously known as North American.
Strong encryption in Global products can be used worldwide, except
in countries whose import laws prohibit it, or except in those
countries to which the export of goods and services is prohibited by
the U.S. government. Customers are no longer required to order
Notes software according to cryptographic strength.

For more information about encryption strength and interoperability
issues, see the book Administering the Domino System.
• User and Server IDs contain a flag bit that indicates that the ID is
North American. Global editions of Lotus Notes/Domino 5.0.3 and
later ignore this flag. However, earlier international editions of Lotus
Notes/Domino (Notes/Domino 5.0.2 and earlier) recognize this flag
and refuse an ID marked North American. If you require an ID that
works with earlier international editions of Lotus Notes/Domino,
create an ID with an earlier international edition of Lotus Notes. For
earlier North American editions of Lotus Notes, use a North
American ID. You can use an international ID; however, those IDs
have a weaker cryptography than the North American IDs.
Transaction logging
• For Domino 4.6 administrators who want to implement transaction
logging, convert Domino 4.6 databases to the Domino 6 database
format. Transaction logging does not support database formats
earlier than Domino 5.
• The Domino 6 Events Log includes a Search Results view in
LOG.NSF. In Lotus Domino 5, you had the option to create a
database, RESULTS.NSF, to display search results, an option which
no longer exists in Lotus Domino 6. If you have a Lotus Domino 6
Administrator and a Lotus Domino 5 server, the log analysis is based
on the Lotus Domino 5 Log Analysis functionality, and the results
are saved in the Results database (RESULTS.NSF).
If you are using a Lotus Domino 6 server, you can still create a
Results database and save your results to this database. To save a
Domino 6 log file to the Results database, open the document from
the Search Results view in LOG.NSF, then use the File - Save As
menu to save it to the desired location.
For more information about transaction logging, see the book
Clients
• Upgrade Lotus Notes clients to Notes 6 before upgrading mail file
databases to the Notes 6 mail file template.
For more information about the Notes client and mail template
interoperability, see the chapter “Upgrading Notes Mail Files.”
• When you access the Archive Settings dialog box of a database on a
Domino 5 server with your Notes 6 client, you see the Domino 5
Archive Settings dialog box rather than the enhanced Domino 6
dialog box.
1-44 Upgrade Guide

Databases
• When you compact a database on a Domino 6 server, the server
upgrades the database to the Domino 6 format. To retain a database
in Domino 4.6 or Domino 5 format, create a replica of the database
and name the replica with an NS4 or NS5 extension (instead of NSF).
After a database is upgraded to Domino 6 format, you can roll back
to Domino 5 format (ODS41) by using the -R option or by creating a
new replica or copy of the database in Domino 5 format. Note that
the -R option will not roll back a database to Domino 4.6 format
(ODS21). You can continue to replicate between a Domino 6 replica
and a Domino 4.6 or Domino 5 replica — the database format does
not replicate.
For more information, see the book Administering the Domino System.
• In Lotus Domino 6, LZ1 compression for file attachments replaces
Huffman compression in Lotus Notes/Domino 5. If the LZ1
compression option is set on a Domino 6 database, a Notes 5 client
will be unable to read the compression. The Lotus Domino 6 server
converts LZ1 to Huffman compression for the Notes 5 client. This
affects server performance. Implement LZ1 compression in an
exclusively Lotus Notes/Domino 6 environment.
• Document locking can be used with a database on Lotus
Notes/Domino 6. A Lotus Notes 6 client cannot lock a document on
a Lotus Domino 5 or earlier server.
• View structures, including collection, btree, and container page, have
changed in Notes/Domino 6. When switching between a previously
released client and a Notes 6 client, Lotus Notes rebuilds the views,
despite the database format. For instance, if you have a local copy of
a mail database in Domino 5 database format and have installed both
Lotus Notes 5 and Lotus Notes 6 on the same computer, Lotus Notes
6 rebuilds the view when the database is opened in that client
release. When you open the database in Lotus Notes 5, that client
also rebuilds the view even though the database format has not
changed. View rebuilds occur every time you open the database in a
client with a different version from the previous client that opened
the same database. View rebuilds do not occur when opening a
database on a server.

• The “Replicate or copy documents” option in Access Control List
dialog box enables replication or copying of documents for a
database. Lotus Notes 5 and 4.6 clients ignore the “Replicate or copy
documents” option. By default, this option is selected. If you deselect
this option with a Lotus Notes 6 client to prevent replication or
copying of documents, Lotus Notes 5 and 4.6 clients can continue to
replicate and copy documents from the database.
For more information about the Access Control List, see the book
1-46 Upgrade Guide

Chapter 2
Upgrading Domino Servers
This chapter describes how to upgrade a Domino server, including the

tasks for installing Lotus Domino 6 and the post-upgrade tasks that you
need to perform on the Public Address Book and Administration
Requests databases. This chapter also covers upgrading the Domino
Administrator.
Upgrading a Domino server to Domino 6

You do not need to uninstall Lotus Domino 4.6 or Domino 5 before
installing Lotus Domino 6. Follow these steps for upgrading servers:
1. Back up important Domino files.
2. Shut down the Domino server.
3. If the Domino server is a Domino NT Service, remove the NT
Service.
4. Install the Lotus Domino 6 software.
Some servers require additional steps to prepare for the upgrade. This
section tells you how to prepare the following Domino servers for
upgrading:
• Domino Administration servers
• Domino 4.6 MTA servers
• Domino 5 mail servers
Consider conducting a pilot project to test your plans for upgrading your
servers before you begin moving your organization to Lotus
Notes/Domino 6. A pilot project lets you refine your plans and deal with
any issues that arise on a smaller scale.
For more information, see the chapter “Planning the Upgrade to
Release 6.”
2-1
Before you upgrade a Domino server
Before you upgrade a Domino server, be aware of the following issues:
• If you have a Domino server with language packs installed, do not
upgrade that server until the updated language packs for the latest
Lotus Domino release are available. When you upgrade a Domino
server with language packs installed, the upgrade process replaces
all translated templates with English language templates.
• Lotus does not support upgrading a single Domino server to a
partitioned Domino server.
• Before you upgrade a Domino server on which you run Lotus
Sametime®, Lotus QuickPlace™, or another Lotus product, make
sure that the other Lotus product supports Lotus Domino 6. If the
other Lotus product does not support Lotus Domino 6, you can
continue to run your current Lotus Domino release.
• In Domino 5.0 and later, underscores and spaces are removed from
all server common names when a Lotus Notes client or Lotus
Domino server first connects to other Domino servers. For example,
the Domino server names Server Name/Boston/Acme or
Server_Name/Boston/Acme are contracted to the common name
“ServerName,” then passed to the IP name resolver services of the
requesting client. The new DNS standards do not recognize
underscores as acceptable characters for host names. Later in the
name lookup process, the underscored name is attempted as one of
the last options to ensure a connection. However, the delay of the
connection impacts performance. If you have underscores in your
server names, make sure your DNS records support both
underscored as well as contracted names. Enter the contracted name
in the Net Address field for the TCPIP port of the given server to
reduce the lookup time until you migrate to a newer server that does
not use an underscored name. Make the contracted name the A
record and the underscored name the CNAME record.
Note In Domino 4.6, spaces in all server common names are
replaced with underscores.
Preparing to upgrade a clustered Domino server

To prepare your clustered Domino 4.6 or Domino 5 servers for the
upgrade to Domino 6, restrict the server that you are upgrading to
prevent new users from accessing the server and to balance the
workload.
2-2 Upgrade Guide

Note When you upgrade a server that is in a cluster, the Cluster
Database Directory is upgraded automatically. However, the title of this
database is not changed from the existing title. The documentation refers
to this title as “Cluster Directory (6),” but the title on your server might
be “Cluster Directory (R5)” or whatever title you are using. You can
change the title to match the documentation or leave it as it is.
For more information about how to restrict a server, see the book
Administering Domino Clusters.
After you have completed these tasks, you can begin backing up your
files.
Backing up files on a Domino server

Back up important Domino server files in case you encounter errors
during upgrading. If necessary, you can use the backed-up copies to
restore your files. Back up files on all servers before you upgrade.
1. Back up the Notes data directory on your server (for example,
C:\NOTES\DATA). This directory includes DESKTOP.DSK, all ID
files (including the server ID and certifier IDs), LOG.NSF,
NAMES.NSF, MAIL.BOX, and any other Public Address Books or
Domino Directories located on the server.
2. Back up the contents of any directories or databases pointed to by
links (DIR files) from your data directory.
3. Back up the NOTES.INI file for the server. On a Domino 4.6 server,
the default location for the file is the system directory (for example,
C:\WINNT40). On a Domino 5 server, the default location for this
file is the data directory.
4. Back up any other Notes databases (NSF files) or Notes templates
(NTF files).
5. (Optional) When you upgrade a Domino 5 server running the LDAP
service, the Lotus Domino 6 installation program deletes the Domino
5 SCHEMA50.NTF template and schema database, SCHEMA50.NSF.
Lotus Domino 6 replaces the database with a new one created with a
new template, SCHEMA.NTF. If you want to keep the Domino 5
schema database, rename it before you upgrade, then move the file
to a directory outside of the Notes data directory path.
6. Continue to one of the following tasks:
If you are upgrading an administration server, see the topic
“Preparing to upgrade a Domino Administration server” later in this
chapter.
Upgrading Domino Servers 2-3

If you are upgrading a Domino 4.6 MTA server, see the topic
“Preparing to upgrade a Domino 4.6 MTA server” later in this
chapter.
If you are upgrading a Domino 5 mail server, see the topic
“Preparing to upgrade a Domino 5 mail server” later in this chapter.
For all other servers, see the topic “Shutting down the Domino
server” later in this chapter.
Preparing to upgrade a Domino Administration server

Upgrade your administration server and Domino Directory before
upgrading other servers in your domain. To upgrade a Domino Admin-
istration server, purge the Administration Requests database of all
pending requests, then shut down the Domino Administration Process.
Note You do not need to process all the requests in the Administration
Requests database to upgrade the database, but process as many as
possible for a faster upgrade.
To clear the Administration Requests database

1. Open the Domino server console.
2. Enter:
tell adminp process all
and press ENTER.
Note You might need to issue this command more than once, as
some Administration Requests create others.
3. After the Administration Process finishes processing requests,
replicate the Administration Requests database to other
administration servers in your domain.
4. After replicating the database, repeat Step 2 to completely purge the
database of pending requests received from other servers.
5. After you purge the Administration Requests database, you can shut
down the Domino Administration Process.
To shut down the Domino Administration Process

Shut down the Administration Process to prevent requests from being
processed by the server.
1. At the Domino server console, enter:
tell adminp quit
and press ENTER.
2-4 Upgrade Guide

2. After you shut down the Domino Administration Process, you can
shut down the Domino server.
For more information, see the topic “Shutting down the Domino
Preparing to upgrade a Domino 4.6 MTA server

To upgrade a Domino 4.6 MTA server, you must disable the
SMTP/MIME MTA housekeeping, shut down the router and inbound
transport, then clear SMTP.BOX and the Inbound and Outbound Work
Queues.
Note Given the time it may take to clear messages from the Inbound
and Outbound Work Queues, upgrade an MTA server at nonpeak times,
such as early mornings or on weekends. The MTA is unavailable while
you clear the queues and upgrade it, affecting Internet mail delivery,
routing, and performance.
To disable SMTP/MIME MTA housekeeping

Before upgrading a Domino 4.6 MTA server, disable MTA housekeeping.
If you do not disable housekeeping and you clear the message queues
during a time when it is set to run (1 AM by default), the MTA turns
itself off, performs housekeeping tasks, and then turns itself on. This
enables inbound and outbound transport, undoing the work of clearing
the queues.
Make sure you backed up the MTA server files. See the topic “Backing
up files on a Domino server” earlier in this chapter
1. Start the Notes client from which you administer the MTA server.
2. Choose File - Database - Open.
3. In the Server field, type the name of the SMTP/MIME MTA server
and click Open.
4. Select the Public Address Book for the MTA server’s domain and
click Open.
5. In the Public Address Book, open the Server/Servers view by
expanding the views under Server in the left pane and clicking
Servers or by choosing View - Servers - Other, selecting
Server/Servers, and clicking OK.
6. Select the Server document for the MTA server.
7. Click the Edit Server button on the Action bar.
8. Expand the Internet Message Transfer Agent (SMTP MTA) section.
9. Under Control, click the down arrow next to the field “Enable daily
housekeeping.”

10. Select Disable and click OK.
11. Click the Save and Close button on the Action bar.
12. Close the Public Address Book.
13. After you disable SMTP/MIME MTA housekeeping, you can shut
down the router.
To shut down the router

Shut down the router to keep other servers from routing outbound
messages to that server.
1. From the Domino server console, enter the following command:
tell router quit
and press ENTER.
Shutting down the router prevents it from transferring more
messages to SMTP.BOX and lets the MTA empty the Outbound
Work Queue by processing existing messages. Incoming messages
are held in MAIL.BOX and processed by the server after you
upgrade it to Lotus Domino 6.
2. After you shut down the router, shut down the inbound transport.
To shut down the inbound transport

Shutting down the inbound transport prevents the MTA from receiving
SMTP messages addressed to recipients in your organization, so that you
can clear the Inbound and Outbound Work Queues.
tell smtpmta stop inbound transport
and press ENTER.
The inbound transport moves messages into the Inbound Work
Queue (SMTPIBWQ.NSF).
2. After you shut down the inbound transport, clear SMTP.BOX.
To clear SMTP.BOX
After shutting down the router and the inbound transport, wait for the
MTA to process all messages in SMTP.BOX before proceeding.
1. Open the SMTP.BOX database in your Notes client. If this is the first
time you have opened the database, you see the “About This
Database” document. Press ESC to close this document.
2. If there are any messages marked Pending Conversion or Pending
Transmission, wait for them to be processed by the Delivery Report
Task (DRT).
2-6 Upgrade Guide

3. Verify message processing by pressing F9 or choosing View -
Refresh; processed messages are removed from the view.
4. When the view is empty, or contains only documents marked Dead,
SMTP.BOX is clear.
5. Press ESC to close SMTP.BOX.
There may be some delay between message processing and the DRT
removing the message from the view due to the cycle time of the
DRT.
6. After SMTP.BOX is cleared, clear the Outbound Work Queue.
To clear the Outbound Work Queue

Clearing the Outbound Work Queue routes all remaining outbound
SMTP messages to their destinations.
1. Double-click the SMTP Outbound Work Queue (SMTPOBWQ.NSF)
icon on your Notes workspace. If this is the first time you have
opened the database, you see the “About This Database” document.
Press ESC.
2. Wait until all messages in the Outbound Work Queue are
successfully processed by the MTA. There should be either no
messages in the view or only messages marked Dead.
3. Verify that all messages except those marked Dead are processed by
pressing F9 or choosing View - Refresh. Processed messages are
removed from the view by the DRT.
4. Press ESC to close the Outbound Work Queue.
There may be some delay between message processing and the DRT
removing the message from the view due to the cycle time of the
DRT.
5. After clearing the Outbound Work Queue, clear the Inbound Work
Queue.
To clear the Inbound Work Queue

Clearing the Inbound Work Queue moves all SMTP messages addressed
to recipients in your organization out of the Inbound Work Queue so
they can be delivered. Messages in MAIL.BOX are delivered after the
server is upgraded and restarted.
1. Double-click the SMTP Inbound Work Queue (SMTPIBWQ.NSF)
icon on your Notes workspace. If this is the first time you have
opened the database, you see the “About This Database” document.
Press ESC.

2. Wait until all messages marked Pending Conversion are processed.
Verify that all messages except those marked Dead are processed by
pressing F9 or choosing View - Refresh. Processed messages are
removed from the view by the DRT.
3. Press ESC to close the Inbound Work Queue.
There may be some delay between message conversion and
transmission, and the removal of the message from the view due to
the cycle time of the DRT.
4. After you clear the Inbound Work Queue, shut down the Domino
server.
Preparing to upgrade a Domino 5 mail server

To upgrade a Domino 5 mail server, shut down the router, then stop the
SMTP service. If your mail server hosts Web mail or iNotes Web Access
clients, you must also stop the HTTP task.
Note Domino automatically upgrades MAIL.BOX to the Domino 6
database format and design. Any messages in MAIL.BOX are preserved.
To shut down the router

Shutting down the router prevents messages from being transferred;
however, messages are still deposited in MAIL.BOX as long as the server
is running.
tell router quit
and press ENTER.
Mail messages can accumulate in MAIL.BOX if other servers and
clients continue to deposit messages, but the router does not deliver
or transfer the messages.
2. After you shut down the router, stop the SMTP service.
To stop the SMTP service

Stop the SMTP service to prevent the server from receiving any incom-
ing SMTP messages.
tell SMTP quit
and press ENTER.
2-8 Upgrade Guide

2. After you stop the SMTP service, do one of the following:
• If the mail server runs the HTTP task for Web mail or for iNotes
Web Access clients, stop the HTTP task.
• Otherwise, shut down the Domino server.
To stop the HTTP task

Stop the HTTP task on mail servers that host Web clients to prevent the
task from depositing messages in MAIL.BOX.
tell http quit
and press ENTER.
2. After you stop the HTTP task, shut down the Domino server.
Shutting down the Domino server

Before you install Lotus Domino 6, shut down the server.
1. At the Domino server console, enter the following command:
quit
then press ENTER.
2. Exit all clients. If you are running Lotus Notes, choose File - Exit
Notes. If you are running the Domino Administrator, choose File -
Exit Administrator.
3. After you shut down the server, do one of the following:
• If your Domino 4.6 server runs as a Windows NT service, remove
Domino as an NT Service.
• Otherwise, upgrade to Lotus Domino 6.
For more information, see the topics “Removing Domino as an NT
Service” and “Upgrading to Lotus Domino 6” later in this chapter.
Removing Domino as an NT Service

If you run Lotus Domino as a Windows NT Service, you must uninstall
the Domino NT Service before upgrading to Lotus Domino 6. If you have
a Domino 4.6 server, perform the following steps to remove Domino as
an NT Service.

1. At the Windows NT server, click Start, then choose Run.
2. Enter the following command in the Run dialog box:
NTSVINST -D
and click OK.
3. After removing Domino as an NT Service, upgrade to Lotus
Domino 6.
Upgrading to Lotus Domino 6

To upgrade to Lotus Domino 6, you can install the new software without
uninstalling the previous release. Uninstalling the Domino server
removes all application and data files. Whether or not you uninstall the
previous release before installing Domino 6, make sure to back up all
important files and to store the files in a directory outside of the Lotus
Domino directory before you uninstall the Domino server.
Upgrading a UNIX system

When you upgrade a UNIX system, you have several installation options
available to that platform only:
• Lotus Domino 6 supports multiple Domino installations on a single
UNIX machine. You can run one earlier version of the Domino server
on a computer with multiple Domino 6 servers as long as each
Domino 6 server has a unique location.
In earlier releases, Lotus Domino was installed in the opt/lotus
location. You can specify any location for Domino 6 installation. If
you choose another location and set the environment variable
NUI_YESOPTLOTUS=1 before you install Lotus Domino 6, the
variable creates a soft link to the location opt/lotus and backs up the
previous Domino installation. Note that if you have an earlier
version of Domino on the machine, the soft link to opt/lotus replaces
the soft link of any earlier release.
• When upgrading an UNIX system to Lotus Domino 6, you can
choose to install to the data directories only. This option upgrades
existing server partitions on a UNIX system.
• With a UNIX system, you can use a script file to install Lotus Domino
6 on more than one server in the domain.
For more information about installing Lotus Domino 6 on UNIX
systems, see the book Installing Domino Servers.
2-10 Upgrade Guide

Upgrading a Lotus Domino server
Follow these steps to install the Lotus Domino 6 software on your
servers.
1. Make sure you backed up all important Domino files.
For more information, see the topic “Backing up files on a Domino
server” earlier in this chapter.
2. For all Domino Administration, Domino 4.6 MTA, and Domino 5
mail servers, make sure to prepare the server for upgrading.
For more information, see the topics “Preparing to upgrade a
Domino Administration server,” “Preparing to upgrade a Domino
4.6 MTA server,” and “Preparing to upgrade a Domino 5 mail
server” earlier in this chapter.
3. Install the Lotus Domino 6 software. If you install Lotus Domino in
the same directory as the previous version, you do not need to make
any changes to the server configuration. If you install Lotus Domino
in a new directory, the program prompts you to configure the server.
4. During installation, select the server type.
5. After you install Lotus Domino 6, do one of the following:
• If you backed up your NOTES.INI file, replace the NOTES.INI file
created during installation with the back up copy before you start
the server. Then, start the server. The server will be set up
automatically.
• If you did not back up the NOTES.INI file, start the Domino server
to begin setup.
For more details, see the book Installing Domino Servers.
Note The Domino server installation does not include the Domino 6
Administrator client. You must perform a second installation using
the client setup program to install the Domino Administrator. Install
the Domino Administrator on a separate computer.
6. After you start the server, if prompted to upgrade the Domino 4.6
Public Address Book or Domino 5 Domino Directory to the Domino
6 Domino Directory template, do so. If you are prompted at the
Domino server console, type Y at the command prompt to upgrade
the directory.
After you upgrade to the Domino 6 Domino Directory template, shut
down the server to compact the database and rebuild the views.
For more information about compacting and rebuilding views in the
Domino Directory, see the chapter “Upgrading the Domino
Directory.”

7. Complete the post-upgrade tasks:
If you upgraded a Domino Administration server, see the topic
“Post-upgrade tasks for Domino Administration servers” later in this
chapter.
If you upgraded a Domino 4.6 MTA server, see the topic
“Post-upgrade tasks for Domino 4.6 MTA servers” later in this
chapter.
If you upgraded a Domino 5 mail server, see the topic “Post-upgrade
tasks for Domino 5 mail servers” later in this chapter.
For all other servers, see the topic “Post-upgrade tasks for Domino
servers” later in this chapter.
Post-upgrade tasks for Domino Administration servers

After you upgrade a Domino Administration server, make sure you do
the following:
1. Upgrading the Domino Administrator client to administer your
Domino 6 servers and Domino 6 Domino Directory.
For more information, see the topic “Upgrading the Domino
Administrator client” later in this chapter.
2. If you have not done so already, shut down the server, then do the
following:
• Compact the directory to the Domino 6 database format
• Rebuild the views in the Domino Directory
• Replicate the new directory to other servers in the domain
Note Replication does not replicate the new database format, only
the template.
For more information about compacting the directory, rebuilding
views, and upgrading directory services, see the chapter “Upgrading
the Domino Directory.”
3. Upgrade the Administration Request database to the Domino 6
template.
For more information, see the topic “Upgrading the Administration
Requests template” later in this chapter.
4. Update the NOTES.INI file. Remove or comment out any obsolete
NOTES.INI settings or variables.
For a table of obsolete NOTES.INI setting, see the topic “Obsolete
NOTES.INI settings” later in this chapter.
2-12 Upgrade Guide

5. If you restricted the Administration server from a cluster, remove the
server_restricted setting from the NOTES.INI file.
6. Upgrade the remaining Domino servers in your domain.
Upgrading the Administration Requests template

After upgrading the administration server and Domino Directory,
upgrade the design of the Administration Requests database on that
server to the Domino 6 template. The Domino 6 Administration Requests
template is designed for backward compatibility with the Domino 4.6
and Domino 5 Administration Process and for use in mixed-release
environments. You should replicate the new design to the Administra-
tion Requests databases on your organization’s other servers.
To upgrade the design of the Administration Requests database

1. From the Domino Administrator, choose File - Database - Open.
2. In the Server field, type the name of the upgraded administration
server.
3. Select the Administration Requests database (ADMIN4.NSF) and
click Open.
4. If this is the first time you have opened the Administration Requests
database, you see the “About This Database” document. Press ESC to
close the document.
5. Choose File - Database - Replace Design.
6. Click Template Server.
7. In the Server field, enter the name of a Domino 6 server and click
OK.
8. Select the Administration Requests (Release 6) template
(ADMIN4.NTF) and click Replace.
9. When the Domino Administrator displays a warning about replacing
the design, click Yes.
10. Close the Administration Requests database.
11. Replicate the new design to the other servers in your organization.
Upgrading the Domino Administrator client

After you upgrade your Public Address Book or Domino Directory to the
Domino 6 Domino Directory template, upgrade to the Domino 6 Admin-
istrator client to administer the Domino 6 directory.
In Lotus Notes/Domino 6, you install the Domino Administrator
separately from the server. New features and enhancements in Lotus
Notes/Domino 6, like delegated server administration, make running a

Domino Administrator client and Domino server on the same computer
unnecessary. However, Lotus continues to support installing the Domino
Administrator on the same computer as a Domino server if you follow
these guidelines:
• Install the Domino Administrator client and Domino server in
separate program directories and specify separate data directories
for the client and server.
• Use a separate user ID file for the Domino Administrator client for
added security. You cannot use the server ID file to access both the
client and the server.
• Access the server databases using only the server. Do not access
those databases locally using the client.
Note If you access local databases that run transaction logging
locally with the Domino Administrator client, you disrupt the
transaction logging process. If that process is disrupted, the next time
you restart the server, restart recovery is impossible for those
databases. You must reset transaction logging for those databases.
Any backups taken using transaction logging are invalid.
Before you install the Domino Administrator client and Domino server
on the same computer, be aware of the following performance and
security issues:
• The Domino Administrator uses resource-intensive processes to
monitor and to administer servers. Installing the Domino
Administrator on the same computer as a server uses server
resources and reduces server performance.
• Installing the client and server on the same computer stores the user
and certifier ID files on one computer. If you do not have copies of
these ID files stored elsewhere and the computer fails, then you
cannot access either ID file. If you install the client and server on
separate computers, copy the files locally to the client computer.
Upgrading the Web Administrator client

When you upgrade a Domino server to Lotus Domino 6, the upgrade
program deletes your Domino 4.6 or Domino 5 Web Administration
database (WEBADMIN.NSF) and creates a new Web Administrator
database based on the Domino 6 template (WEBADMIN.NTF). If you
customized the ACL of your Domino 4.6 or Domino 5 Web Administra-
tion database, you must re-enter this information in the new Web
Administrator database ACL.
2-14 Upgrade Guide

Post-upgrade tasks for Domino 4.6 MTA servers
After you upgrade a Domino 4.6 mail server, do the following:
1. Upgrade to the Domino 6 Administrator.
Administrator client” earlier in this chapter.
2. Shut down the server, then do the following:
the template.
NOTES.INI settings and variables from the file. Perform this task for
all Domino 4.6 servers.
For a table of obsolete NOTES.INI settings, see the topic “Obsolete
4. Enable SMTP routing in the Configurations Settings document to
route Internet mail.
For more information, see the topic “Enabling SMTP routing in the
Configurations Settings document for an Internet mail server” later
in this chapter.
5. Enable the SMTP listener task in the Server document.
For more information, see the topic “Enabling the SMTP listener task
for an Internet mail server” later in this chapter.
6. Create Internet e-mail addresses for your users.
For more information, see the topic “Internet mail addresses in Lotus
Domino 6” later in this chapter.
7. Set Internet mail message format for your users.
For more information, see the topic “Setting message format
preferences for users” later in this chapter.
8. If you have shared mail databases on the server, upgrade the
databases.
For more information, see the topic “Upgrading shared mail
databases” later in this chapter.

9. If the server you upgraded was NNTP-enabled, remove the NNTP
documents from the Domino Directory.
For more information, see the topic “Removing NNTP documents
from the Domino Directory” later in this chapter.
10. If you removed the server from a cluster, add the server back to the
cluster.
11. Upgrade your remaining Domino servers.
Enabling SMTP routing in the Configuration Settings document for

an Internet mail server
You must enable native SMTP routing in the Configuration Settings
document to allow the upgraded Domino 4.6 mail server to route mail
externally using SMTP. Using SMTP to route mail internally is optional.
Configuration Settings documents can apply to a single server, all servers
in a domain, or a group of servers. Edit the Configuration Settings
document that applies to the upgraded server, but be aware that this
modification affects any other servers that use this Configuration Settings
document.
If you do not have Configuration Settings documents for your Domino
servers, create them to reflect your Domino 6 configuration. For example,
if you have a mail server, an application server, and a firewall server,
and only the mail server uses SMTP routing, create two Configuration
Settings documents: one for the mail server with SMTP routing enabled,
and one for the application and firewall servers without SMTP routing
enabled.
Follow these steps to enable SMTP routing in the Configurations Settings
document.
1. Make sure you upgraded the design of your Public Address Book to
the Domino 6 Directory template.
Note The Domino Directory for the domain must use the Domino 6
template because the settings for native SMTP appear only in the
Domino 6 Directory Configuration Settings document.
2. In the Domino Administrator, click the Administration window tab.
3. Click the Configuration tab.
4. Expand the Server Configuration section.
5. Click Configurations.
6. If you have a Configuration Settings document that you want to use
for this server, select it and click Edit Configuration. If not, click Add
Configuration.
2-16 Upgrade Guide

7. If you are creating a new configuration, do the following:
• Enter a server name in the Basics section.
• Select the Group or Server this configuration applies to. Do not
select “Use these settings as the default settings for all servers”
unless you want every server that this document controls to use
SMTP to send messages to the Internet instead of through an
Internet mail server.
8. Click the Router/SMTP tab.
9. Complete this field on the Basics tab, and then save the document:
Field Enter
SMTP used when Choose one:
sending messages • Enabled to use SMTP to route mail to the
outside the local Internet
Internet domain
• Disabled (default) to prevent the server from
routing mail outside the local Internet domain
10. If your organization uses a relay host, enter its host name or IP
address in the field “Relay host for messages leaving the local
Internet domain.”
Note Relay host servers require additional configuration.
For more information about relay host servers, see the book
11. Click the Save and Close button on the Action bar. If you created a
document, it appears in the view.
12. Enable the SMTP listener task.
Enabling the SMTP listener task for an Internet mail server

Edit the Server document for the Domino 4.6 upgraded server to enable
the SMTP listener task, which listens for inbound SMTP requests. This
change tells the server to load the SMTP listener task at startup.
Note The Domino Directory for the domain must use the Domino 6
template because the settings for native SMTP appear only in the
Domino 6 Domino Directory
1. In the Domino Administrator, click the Configuration tab.
2. Expand the Server Configuration section.
3. Click “All Server Documents.”
4. Double-click the server document for the upgraded Internet mail
server.
5. Click Edit Server.

6. On the Basics tab, complete these fields:
Field Enter
Fully qualified The server’s complete combined host name and domain
Internet host name, including the top-level domain. For example,
name smtp.acme.com; smtp is the host name; acme is the
second-level domain; and.com is the top level domain.
In the absence of a Global Domain document, the Router
uses the entry in this field to determine the local Internet
domain. Typically, the fully qualified host name is added
to the Server document during server setup or by the
Administration process (AdminP). A routing loop can
result if this field does not contain a valid entry.
SMTP listener Choose one:
task • Enabled to turn on the Listener so that the server can
receive messages routed via SMTP routing
• Disabled (default) to prevent the server from receiving
messages routed via SMTP routing
7. Click the Ports - Internet Ports - Mail tab.

8. In the Mail (SMTP Inbound) column, ensure that the TCP/IP port
status is set to Enabled, and then click Save and Close.
Note Do not remove SMTP routing information from the Server
document. Existing routing information allows you to route Internet mail
in a mixed-release environment, or in a Lotus Notes/Domino 6
environment that uses Lotus Notes/Domino 4.6-style routing. Removing
this information may affect Internet mail routing and delivery in these
environments.
Internet mail addresses in Lotus Domino 6

When looking up an address for Internet mail in the Domino Directory in
Lotus Domino 6, Lotus Domino checks the $Users view for an exclusive
match of the address. If it finds the complete Internet address of the
recipient (for example, jdoe@acme.com) in either the Short name or Inter-
net Address field, Lotus Domino delivers the message to the mail file of
that person. Lotus Domino also delivers messages based on a match of
the local part of the address (for example, jane_doe) with any of the
fields in the Person document. For example, if the message is addressed
to jane_doe@acme.com, and Lotus Domino finds a Person document
with the entry “Jane Doe” in the User Name field, Lotus Domino delivers
the message to Jane Doe’s mail file.
2-18 Upgrade Guide

Note Lotus Domino converts double underscores (__) into underscores,
underscores into spaces, and periods into spaces. In this example,
jane_doe would become jane doe. The lookup is not case-sensitive — jane
doe matches with the entry Jane Doe in a Person document.
Lotus Domino’s exhaustive lookup in $Users ensures that any address
generated by the Domino 4.6 MTA for a user in your directory is located
properly. While you can use the Internet Address field in the Domino 6
Person document and the tool that populates this field to standardize
Internet addresses in your organization to provide a single place for
locating and changing Internet addresses, this step is optional — Lotus
Domino does not distinguish between Domino 4.6 and Domino 6
addressing and utilizes both equally well.
Populating the Internet Address field in Person documents

When upgrading to Lotus Domino 6 from Lotus Domino 4.6, you can use
the Internet Address tool to fill in the Internet Address field for all
Person documents in which the field is blank in a Domino Directory.
1. From the Domino Administrator, click the People and Groups tab.
2. Select the server and Domino Directory for which you wish to fill in
the Internet Address fields.
3. Click the People tab.
4. Click Set Internet Address.
5. In the Internet Address Construction dialog box, choose a format for
the Internet addresses.
6. Choose a separator for the Internet addresses. This character
separates the items in the Format field.
7. Enter the Internet domain for the company.
Note If you select the option “Use existing address from Short name
field, if available” the tool searches the Short name field in each
Person document for a valid Internet address (for example,
jdoe@acme.com). If the tool finds a valid Internet address, it uses this
address to complete the Internet Address field, instead of creating an
entry based on the information in the dialog box.
8. (Optional) Click More Options and do any of the following:
• Select “Use existing Internet domain from Short name field, if
available” to search the Short name field in each Person document
for a valid Internet domain (for example, @acme.com). If the tool
finds a valid Internet domain, it uses this domain to complete the
Internet address, instead of using the entry in the Internet domain
in the dialog box.

• Select “Separate multi-word names with selected separator
character” to insert the separator character you specify between
words in a name with multiple words.
• Select “Create addresses only for people in a specific Notes
Domain” to set Internet addresses only for users in a given Notes
domain. Enter the domain name of the Notes domain in which
you want to set Internet addresses.
• Select “Use alternative format pattern in case of name conflict” to
specify a second Internet address pattern if Notes generates the
same Internet address for two users. Specify the alternative format
pattern in the box.
For more information, see the topic “Using Custom Format Pattern”
later in this chapter.
This allows you to use the alternative format pattern if the primary
pattern results in an address containing non-ASCII characters, an
address that is not unique, or one that contains an invalid character.
The Internet Address Construction dialog box specifies the server and
Domino Directory on which it runs. It also gives an example for each
address and separator format.
Note The dialog box does not give examples for all Custom Format
combinations.
The Internet Address tool checks all Person documents in the Domino
Directory. When it finds a document without an entry in the Internet
Address field, it creates an entry, verifies that the entry is a valid RFC 821
address, and verifies that the entry is unique by performing an exhaus-
tive name lookup of the entry on all Domino Directories on the server. If
the entry matches an Internet Address field, the tool leaves the field
blank and enters an error in the log file (LOG.NSF).
Caution The Internet Address tool performs an exhaustive name
lookup of every new Internet address and should not be run on a
directory or server that is under heavy load.
2-20 Upgrade Guide

Address formats for the Internet Address tool
The following table lists the address formats that you can choose.
Address format Description

FirstName LastName Uses the contents of the First name field and the Last
name field to form the address.
FirstName MiddleName Uses the contents of the First name field, Middle
LastName name field, and Last name field to form the address.
FirstInitial LastName Uses the first letter in the user’s First name field and
the contents of the Last name field to form the
address.
FirstInitial MiddleName Uses the first letter in the user’s First name field,
LastName Middle name field, and the contents of the Last name
field to form the address.
LastName FirstName Uses the contents of the Last name field and the First
name field to form the address.
LastName FirstName Uses the contents of the Last name field, First name
MiddleName field, and Middle name field to form the address.
LastName FirstInitial Uses the contents of the Last name field and first
letter in the user’s First name field to form the
address.
LastName FirstInitial Uses the Last name field, first letter in the user’s First
MiddleName name field, and Middle name field to form the
address.
FirstName LastInitial Uses the First Name field and the first character of
the Last name field to form the address.
Use Custom Format Use to specify an Internet address.
Pattern
If you choose a Custom Format Pattern, the following address separators

are available:
None
Underscore _
Equal sign =
Percent sign %
Note You must specify an Internet domain in the Internet Domain field
of the dialog box.

Creating an Internet address
For the user Jane R. Jones, whose information appears as follows in her
Person document:
User First name Last name Middle name Internet

field field field domain
Jane R. Jones Jane Jones R acme.com
Running the Internet Address tool produces the following possible Inter-
net addresses:
Format Separator Internet Address after running tool

FirstName LastName _ Jane_Jones@acme.com
FirstName MiddleInitial _ Jane_R_Jones@acme.com
LastName
FirstInitial LastName % J%Jones@acme.com
FirstInitial MiddleInitial % J%R%Jones@acme.com
LastName
LastName FirstName = Jones=Jane@acme.com
LastName FirstName = Jones=Jane=R@acme.com
MiddleInitial
LastName FirstInitial _ Jones_J@acme.com
LastName FirstInitial _ Jones_J_R@acme.com
MiddleInitial
FirstName LastInitial % Jane%J@acme.com
Note You must specify an Internet domain in the Internet Domain field
of the dialog box.
Using Custom Format Pattern

If you select “Use Custom Format Pattern” in the Internet Address
Construction dialog box, you can set how Lotus Domino creates Internet
addresses in Person records without an entry in the Internet Address
field. Use the following characters in the dialog box to specify how the
address should appear:
Abbreviation Meaning
Fn First name, truncate at n characters
Ln Last name, truncate at n characters
M Middle initial
T Title
continued
2-22 Upgrade Guide

Abbreviation Meaning
G Generational qualifier
I Employee ID
C Location
D Department
V Server
O Organizational Unit
S Use the existing Short name field
= Separator
_ Separator
% Separator
By combining the characters and separators above, you can set how
Internet addresses should appear in your organization.
Creating an Internet address using Custom Format Pattern

For the user Jane R. Jones, whose information appears as follows in her
Person document:
Title First Middle Last Name Location Organization Server

Name Initial
Ms Jane R Jones Tampa Acme MailT1
You could set Custom Format to produce the following addresses:
Custom Format Address

FL JaneJones@acme.com
F2L JaJones@acme.com
F_L=C Jane_Jones=Tampa@acme.com
T_F_M_L%V Ms_Jane_R_Jones%MailT1@acme.com
Validating Internet addresses

You can use the Internet Address tool to verify that entries in the
Internet Address field of all Person documents in one or more Domino
Directories are unique. This ensures that Internet addresses do not
conflict. To validate that the entries in the Internet Address fields are
unique, do the following:
1. Start the Domino Administrator.
2. Click the People and Groups tab.

3. Select the server and Domino Directory for which you wish to
validate entries in the Internet Address fields.
4. Click the People tab.
5. Click Validate Internet Address.
6. Choose to validate Internet addresses only in the current Domino
Directory you selected in Step 3 or to validate Internet addresses in
all available Domino Directories on the server and click OK.
The validation tool exhaustively checks every Internet address in the
Domino Directory or directories you selected against all Domino Directo-
ries or against all directories specified in the Directory Assistance
database. If an address is not unique, Lotus Domino records the dupli-
cate address in the server log (LOG.NSF).
Note Validating Internet addresses consumes significant server
resources — do not use this tool when the server is under heavy load or
when response time for users is critical. Run this tool when few users
access the server, such as on weekends or late at night.
Setting message format preference for users

In the Domino 6 Directory Person document, you can set a user’s
message preference in the field “Format preference for incoming mail”
on the Mail tab. There are three choices:
• Prefers MIME. Messages in Notes rich text format are converted to
MIME when delivered to the user’s mail file. This is the preferred
setting for users who access mail using POP3 or IMAP.
Note Lotus Domino 6 stores all inbound Internet mail in MIME
format.
• Prefers Notes rich text. Messages in MIME format are converted to
Notes rich text when delivered to the user’s mail file. This is the
preferred setting for users who access mail using a Notes 4.6 client.
• Keep in Sender’s format. Mail is delivered to the user’s mail file in
the format specified by the sender. Lotus Domino does not convert
the format. This is the preferred setting for users who access mail
using a Notes 5 or 6 client.
Note If you want to register new Notes 4.6 users, use a Notes 4.6 client
to register them.
2-24 Upgrade Guide

Post-upgrade tasks for Domino 5 mail servers
After you upgrade a Domino 5 mail server, do the following:
1. If you have not done so already, upgrade to the Domino 6
Administrator.
following:
the template.
NOTES.INI settings and variables from the file.
For a table of obsolete NOTES.INI settings, see the topic “Obsolete
4. If you have a shared mail database, verify that the database was
upgraded properly. When you upgrade a Domino mail server, the
upgrade process automatically upgrades the shared mail database.
However, if the database was not upgraded properly, you must
manually upgrade the database.
5. (Optional) The Lotus Domino 6 SMTP Inbound relay controls resolve
conflicts differently than the Lotus Domino 5 inbound relay controls.
If you do not want to use the Domino 6 inbound relay controls, you
can set the SMTPRelayAllowHostsandDomains NOTES.INI setting
to preserve the Domino 5 inbound relay controls on your upgrade
SMTP servers.
For more information about this change and how to preserve the
Domino 5 inbound relay controls, see the topic “Configuring Domino
5 SMTP inbound relay controls” later in this chapter.

cluster.
Upgrading shared mail databases

When you upgrade Domino 4.6 or 5 mail servers hosting shared mail
databases, Lotus Domino 6 maintains existing shared mail databases, but
does not use them for new mail. You must configure shared mail to
receive mail.
Note The existing shared mail databases remain on the server, but are
inactive and no longer receive mail. You can continue to read mail from
these share mail databases.
To configure the new shared mail databases to receive mail, edit the
Shared Mail tab of the Server document, then restart the server to apply
the changes.
For more information about configuring shared mail databases, see the
book Administering the Domino System.
To configure and close existing shared mail databases

Existing shared mail databases are not automatically listed in the shared
mail configuration. You can configure these databases as closed. Config-
uring and closing the databases is optional. If you do not close the
databases, they will be listed as not configured when you enter the
command “show SCOS” at the Domino server console.
To configure and close an existing shared mail database, follow these
steps.
1. Open the Shared Mail tab of the Server document.
2. Enter the directory path of the shared mail database that you want to
close in an empty directory row.
3. Enter 1 in the Number of Files column.
4. Enter 0 in the Maximum Directory Size column.
5. Select Closed in the Delivery Status column.
6. Select Online in the Availability column.
7. Click Save and Close.
2-26 Upgrade Guide

Configuring Domino 5 SMTP inbound relay controls
If a Domino SMTP server is accessible from the Internet, people outside
your organization can relay mail through it to destinations in external
Internet domains. This may result not only in one of your servers
burdened with extra traffic, but also mail appearing to originate in your
domain, possibly even spam. To prevent the Domino server from provid-
ing an open relay, Lotus Domino 5 introduced relay controls. Using
Allow and Deny destination lists, these controls determine the relay
destinations to which a server can or cannot send mail and the sources
from which the server can and cannot accept relays.
Because you configure the valid relay destinations separately from the
valid relay sources, conflicts between the two sets of restrictions can
occur. When such conflicts occur, Lotus Domino requires instructions for
resolving the conflict. In Lotus Domino 5, Deny entries took precedence
over Allow entries; in Lotus Domino 6, Allow entries take precedence
over Deny entries.
For example, you allow relays from the following host and deny them to
the following domain:
Allow from hosts: 9.95.91.51
Deny to domains: yahoo.com
On a Domino 5 server, because the Deny entry takes precedence, the
named host, 9.95.91.51, cannot relay to denied destinations. In the
example, the Domino 5 server cannot relay to any address in the
yahoo.com domain.
On a Domino 6 server, in the event of a conflict between entries, Allow
entries take precedence. By giving a specific host “Allow” access, you
allow that host to relay to any destination. In the example, the host
9.95.91.51 can relay to the yahoo.com domain even though the domain is
explicitly denied as a relay destination.
Similarly, the following configuration denies relays from a specified host
and allows them to a specified domain:
Deny from hosts: myhost.iris.com
Allow to domains: hotmail.com
On a Domino 5 server, the Deny entry takes precedence, so that the
named host, myhost.iris.com, is not a valid relay source. The named host
cannot relay to any domain, even to allowed domains.
On a Domino 6 server, the Allow entry takes precedence. In the preced-
ing example, myhost.iris.com is allowed to relay to any destination,
including to the explicitly denied domain hotmail.com.

The differences between how Domino 5 and Domino 6 resolve conflicts
apply to conflicts occurring between entries in the source and destination
lists only. The rules for resolving conflicts between the list of allowed and
denied sources or the allowed and denied destinations are the same for
both Lotus Domino 5 and Lotus Domino 6: Deny entries take precedence.
If you have the following configuration:
Deny to domains: yahoo.com
Allow to domains: hotmail.com, eurosport.com, yahoo.com,
netscape.com
the server rejects relays to addresses in the yahoo.com domain.
To preserve the Domino 5 behavior for resolving conflicts in the

relay controls
When you upgrade the Domino 5 SMTP mail server, you have the option
to not accept this change if you do not want to reconfigure your
upgraded mail servers. Lotus Domino 6 provides the NOTES.INI setting
SMTPRelayAllowHostsandDomains to allow the server to follow the
Domino 5 behavior. Set this setting to 1 to allow the Deny entries to take
precedence. The default value for this setting is 0.
For more information about the SMTPRelayAllowHostsandDomains
setting, see the book Administering the Domino System.
Post-upgrade tasks for Domino servers

After you upgrade a Domino 4.6 or 5 server, do the following:
1. If you have not done so already, upgrade to the Domino 6
Administrator.
following:
the template.
2-28 Upgrade Guide

NOTES.INI settings or variables.
For a table of obsolete NOTES.INI setting, see the topic “Obsolete
5. If you upgrade a Domino 5 registration server that did not have a
Certification Log, create a log.
For more information about creating the Certification Log, see the
topic “Domino 5 registration servers and the Certification Log” later
in this chapter.
6. If you ran the Domino SNMP agent in a previous release of Lotus
Domino, upgrade the agent.
For more information about upgrading the Domino SNMP Agent,
see the topic “Upgrading the Domino SNMP Agent” later in this
chapter.
cluster.
Removing NNTP documents from the Domino Directory

Lotus Domino 6 does not support Network News Transfer Protocol
(NNTP); however, the Lotus Notes 6 client continues to support NNTP.
When you upgrade a Domino NNTP-enabled server, the upgrade
process removes the NNTP executables, the NNTP value from the Server
Tasks setting of the NOTES.INI file, and the News tabs from the Server
document. However, the upgrade process does not remove the NNTP
documents from the Domino Directory. You can delete any NNTP
connection documents, including connection documents that accept
newsfeeds, that push out newsfeeds, and that create a dial-up or LAN
connection for NNTP purposes.
Note If you maintain a mixed-release environment with servers that are
NNTP-enabled, do not delete any newsgroup databases because those
databases are required to read newsletters.

Domino 5 registration servers and the Certification Log
The Certification Log records registration and user name information for
a domain. In Domino 5, the Certification Log was optional. In Domino 6,
the log is required. If you upgrade a Domino 5 registration server
without a Certification Log, then you need to create a log manually. If
you upgrade a Domino 5 server with a Certification Log, Domino 6
upgrades the log automatically.
After you create the log, replicate it to other registration servers in your
domain and to every server with a Domino Directory that is used for
user management.
To create a Certification Log

1. From the Domino Administrator, choose File - Database - New.
2. In the Server field, select the name of the server on which to create
the log.
3. Enter Certification Log as the database title.
4. Enter CERTLOG.NSF as the database file name.
5. Choose a server that has the Certification Log template.
6. Click Show Advanced Templates, select Certification Log as the
template, and then click OK.
7. Choose File - Database - Access Control, and assign Editor access to
all administrators who register users and servers and recertify IDs.
For more information about the Certification Log, see the book Installing
Domino Servers.
Upgrading the Domino SNMP Agent

If you used the Domino SNMP Agent with a previous release of Lotus
Domino, read the instructions in this section before using SNMP with
Lotus Domino 6.
To upgrade the Domino SNMP Agent on the AIX, Linux, and Solaris
platforms, first configure the Domino 6 SNMP Agent, then uninstall the
previous SNMP agent. To upgrade the Domino SNMP Agent on a
Windows platform, first uninstall the previous SNMP agent, then config-
ure the Domino 6 SNMP Agent.
2-30 Upgrade Guide

If you enabled the Server Start, Server Stop, or Reboot System options
that were previously configured in the LSNMPCFG.NSFdatabase,
re-enable the options in the SNMP tab of the server’s Configuration
Settings document in the Domino Directory. After this is done, you can
delete the LSNMPCFG.NSF database because the Domino SNMP Agent
no longer uses it.
Follow these steps to uninstall a previous release of the Domino SNMP
Agent. Check the appropriate sections below for your server platform.
Windows
The configuration steps automatically remove the old LNSNMP service.
After this is done, you can delete the NVMIBDLL.DLL file in your
SYSTEM directory.
AIX
First, stop the LNSNMP process, as the root user, enter the following
command at the server console:
/etc/lnsnmp.rc stop
You may then delete the /etc/notesview directory along with all its
subdirectories and contents. The /etc/lnsnmp.rc script will be replaced
when you follow the configuration steps.
Linux
No action is necessary because the Domino SNMP Agent was not previ-
ously available for Linux.
Solaris
First, stop the LNSNMP process, as the root user, enter the following
command at the server console:
/etc/init.d/nvinit stop
Next, if you’re using the PEER Agent(s), stop them, as the root user, enter
the following command at the server console:
/etc/init.d/peerinit stop
Then delete the following files:
/etc/rc2.d/S77lnsnmp
/etc/rc1.d/K77lnsnmp
/etc/rc2.d/S76peer.snmpd
/etc/rc1.d/K76peer.snmpd

Then delete the following files:
/etc/init.d/nvinit
/etc/init.d/peerinit
You may then delete the /etc/notesview directory along with all its
subdirectories and contents.
zOS (OS/390)
No action is necessary.
For more information about configuring the Domino SNMP Agent, see
the book Administering the Domino System.
Obsolete NOTES.INI settings

With updates to the Domino Directory and new functionality added to
Lotus Notes/Domino 6, some NOTES.INI settings have become obsolete.
Lotus Notes/Domino 6 ignores most obsolete settings. However, remov-
ing or commenting out obsolete settings is recommended. You can use a
text editor to edit the NOTES.INI file.
The following table lists Lotus Notes/Domino 5 and Lotus/Notes
Domino 4.6 NOTES.INI settings that are either no longer supported
or no longer require you to manually set their values in Lotus
Notes/Domino 6.
For more information about supported NOTES.INI settings, see the book
NOTES.INI setting Comment

AdminPInterval
AdminPModifyPersonDocumentsAt
Config_DB Replace Config_DB with Report_DB.
LDAP_CountryCheck See the topic LDAP Schema changes in
Lotus Domino 6 for more information.
LDAP_Enforce_Schema
LDAP_Strict_RFC_Adherence
LDAP_UTF8results
KillProcess Fault Recovery now performs the
function previously performed by this
setting.
continued
2-32 Upgrade Guide

NOTES.INI setting Comment
Mailclusterfailover* Configured by Lotus Domino 6.
Remove or comment out this setting.
New_DNParse
NNTPAddress Not supported.
NNTP_Delete_Days Not supported.
NNTP_Delete_Days_Expired Not supported.
NNTP_Initial_Feed_All Not supported.
NNTP_Previous_X_servername Not supported.
NNTP_Prohibit_NEWSNEWS_ Not supported.
Command
NNTP_PullAsServer Not supported.
Server_Name_Lookup_Noupdate* Configured by Lotus Domino 6.
Remove or comment out this setting.
WebAuth_AD_Group
WebAdmin_Disable_Force_GUI
WebAdmin_Expire_Cache
*Because these settings are configured by Lotus Domino, they no longer appear
in the NOTES.INI file. However, if you do not manually remove or comment out
these settings from an existing NOTES.INI file, Lotus Domino 6 continues to
support them.
Obsolete NOTES.INI variables
This table lists obsolete variables for supported NOTES.INI settings. If
the following variables are not removed from their NOTES.INI settings
after the upgrade process, you can manually remove these variables from
the file.
NOTES.INI setting NOTES.INI setting variables

ServerTasks Apple Talk, CLREPL, CLDBDIR, Design, NNTP,
Object Collect mailobj.nsf, Report, SMTP MTA
Domino mail messaging changes since Lotus Domino 4.6

The following topics describe changes to messaging since Domino 4.6.
• Internet mail routing in mixed-release environment
• Internet mail storage format for Lotus Domino 6
• Relay host changes
• Sending mail in Notes format to Internet users

Internet mail routing in mixed-release environments
Lotus Domino 6 routes Internet mail (MIME) over both Notes RPC
(Remote Procedure Calls) and SMTP. Domino 4.6 servers do not support
native MIME delivery or SMTP routing; those servers use the MTA to
accomplish these tasks.
You can control how a Domino 6 server transfers a MIME message to a
Domino 4.6 server if it cannot access a user’s Person document. The
following table describes the formatting options for incoming mail in the
Person document.
Format preferences for Description

incoming mail
Prefers Notes Rich Text The Domino server converts the MIME message to
Notes format and transfers it, reducing storage
space and bandwidth use but with some loss of
message fidelity.
Prefers MIME The Domino server converts the MIME message to
Notes format and also creates an attachment
containing the original MIME, preserving
message fidelity but increasing storage space and
bandwidth use.
Keep in Sender’s format The Domino server converts MIME messages to
Notes format without an attachment. This is the
default setting.
If you select to convert the message to Notes format and also create an
attachment containing the original MIME, Lotus Domino 6 preserves full
message format. If an Internet mail client accesses the message, Domino
sends it the MIME from the attachment. The Domino 4.6 server deposits
both the Notes format message and the MIME attachment in a user’s
mail file for this reason. For these messages in a mixed-release environ-
ment with this conversion setting, mail storage requirements and
network utilization roughly double for each of these messages only.
Internet mail conversion in mixed-release environments

In a mixed-release environment, routing native MIME messages and
sending Notes format messages to the Internet requires some conversion.
Conversion takes place in the following scenarios.
Using the inbound and outbound services of the Domino 4.6

SMTP/MIME MTA
The MTA converts outbound Notes messages to MIME format and
routes them via SMTP. It converts inbound MIME messages to Notes
format (with or without a MIME attachment) and routes them over Notes
2-34 Upgrade Guide

RPC using the Notes router. The Domino 4.6 MTA converts and delivers
messages based on the settings in the recipient’s Person document, if the
MTA can access it. If the setting of the Internet Message Storage field in
the Notes 4.6 Person document is:
• Prefers Notes Rich Text (Notes only in Lotus Notes/Domino 4.6), the
MTA converts the message to Notes format and routes it.
• Prefers MIME (Internet only in Lotus Notes/Domino 4.6), the MTA
packages the messages as a MIME attachment and routes it.
• No Preference (Notes and Internet in Lotus Notes/Domino 4.6), the
MTA converts the message to Notes format, adds an attachment
containing the original MIME, and routes it.
When a Domino 6 router delivers a message to a recipient’s mail file

on a Domino 5 or Domino 6 server
The router checks the recipient’s Person document in the Domino Direc-
tory. The field “Format preference for incoming mail” determines the
recipient’s preference for Internet messages. If the message is in Notes
format and
• The field is set to Prefers Notes Rich Text, the router delivers the
message and stores it in Notes format (CD format).
• The field is set to Prefers MIME, the router converts the message to
Native MIME format and delivers the MIME message.
• The field is set to Keep the Sender’s format, the router delivers the
message and stores it in Notes format (CD format).
Note If the field is set to No Preference, the router delivers the Notes
format message because the Notes 4.6 and Notes 5 or 6 clients can read
the message and the IMAP and POP server tasks can convert the
message to MIME for Internet clients.
If the message is in MIME format and
• The field is set to Prefer Notes Rich Text, the router converts the
message to Notes format and delivers the Notes format message.
Note If the NOTES.INI parameter MailDeliverCDorMime is set to 1
on the server, the router does not convert the message and instead
delivers it in MIME.
• The field is set to Prefer MIME, the router delivers the message and
stores it in Native MIME format.
• The field is set to Keep in Sender’s format, the router delivers the
message.

If the message is encrypted (S/MIME format), the router creates an
attachment containing the S/MIME and creates a Notes format message
explaining that the message is encrypted and cannot be converted to
Notes format.
Note Inbound Internet mail is stored in Native MIME format for
recipients whose format preference for incoming mail is set to “Prefers
MIME” or “Keep in Sender’s format.” If transferring to a Domino 4.6
server, the MIME message is converted to Notes format because the
Notes 4.6 client cannot understand Native MIME.
When a Domino 6 server transfers a message to a Domino 4.6

server
If the message is in Notes format, the router simply transfers the message
to the Domino 4.6 server.
If the message is MIME, the router tries to access the recipient’s Person
document. If it has access to the recipient’s Person document, it checks
the Internet Message Storage field (Domino 4.6) or Format preference for
incoming mail field (Domino 6).
When a Native MIME message passes from Lotus Domino 5 or later to a
Domino 4.6 server, Lotus Domino 5 or later converts the Native MIME
message to Notes format (CD ) or CD plus the MIME stream as an attach-
ment. If the message is delivered to a Domino 4.6 server, the CD format
is required because Notes 4.6 clients cannot understand MIME. The
attachment is required to maintain fidelity for IMAP and POP3 clients,
for final delivery to Lotus Domino 5 or later, and for retention of content
if the message is encrypted with S/MIME.
• If the field is set to Notes only (Domino 4.6) or Prefers Notes Rich
Text (Domino 6), the router converts the message to Notes format
and transfers the Notes format message.
• If the field is set to Internet only (Domino 4.6) or Prefers MIME
(Domino 5 or later), the router converts the MIME message to a
MIME attachment and transfers the MIME attachment as the
message.
• If the field is set to Notes and Internet (Domino 4.6) or No Preference
(Domino 5 or later), the router converts the message to Notes format,
adds an attachment containing the original MIME, and transfers the
Notes format message with the MIME attachment.
Note If the NOTES.INI parameter MailDeliverCDandMime is set to 1
on the server, the router converts Native MIME messages to Notes
format and adds an attachment containing the original MIME, if the
MIME message is transferred to a Domino 4.6 server.
2-36 Upgrade Guide

If the message is encrypted (S/MIME format), the router creates an
attachment containing the S/MIME and creates a Notes format message
explaining that the message is encrypted and cannot be converted to
Notes format.
If the router cannot access the recipient’s Person document — for
example, if the recipient is in another domain and the router cannot
access that domain’s Domino Directory — the router converts MIME
messages to Notes format and transfers them. You can control this
conversion by setting the router to either follow the default behavior or
to also add an attachment containing the original MIME to the Notes
format message. The default behavior conserves disk space and
bandwidth but reduces message fidelity; the optional behavior preserves
message fidelity, but consumes additional disk space and bandwidth.
When a Domino 6 router sends mail over SMTP

If a Domino 6 router must send a message in Notes format over SMTP, it
converts the message to MIME.
Note The Domino 4.6 SMTP/MIME MTA supported encapsulation,
which placed Notes-specific information in an attachment that could be
converted back into Notes data by another MTA. The Domino 6 router
does not support Domino 4.6 encapsulation, but maintains Notes data by
another method so that another Domino 6 router can convert the
information back into Notes data.
When a Domino 6 server replicates with a Domino 4.6 server

When a Domino 6 server replicates a database with MIME content to a
Domino 4.6 server — for example, if a mail file is on both a Domino 6
and a Domino 4.6 server, with MIME messages in the database on the
Domino 6 server — Domino converts any MIME to Notes format.
Using IMAP and POP3 clients to retrieve messages

If a message is stored in Notes format and retrieved by an Internet client,
the IMAP and POP protocols convert the Notes format message to
Native MIME for the IMAP and POP3 clients.
Internet mail storage format in Lotus Domino 6

You do not need to change how users’ Internet messages are stored when
upgrading to Lotus Domino 6. If you have users who only access mail
with a POP3 or IMAP client and whose Person documents set their Inter-
net message storage to both Notes and Internet in Lotus Domino 4.6,
changing the field “Format preference for incoming mail” on the Mail tab
to “Prefers MIME” will improve performance, but increases bandwidth
use and storage space.

In a mixed Domino 4.6/Domino 6 environment where some clients use
native MIME messages on Domino 6 servers, Domino cannot deliver a
native MIME message to a Notes 4.6 client, mail file, or server, because
native MIME is unreadable in Lotus Notes/Domino 4.6.
For more information, see the topic “Internet mail conversion in
mixed-release environments,” earlier in this chapter.
Relay host changes

In Lotus Domino 6, relay host configuration is easier than in Lotus
Domino 4.6. You can select to route all mail with destinations outside the
local Internet domain to a relay host, or not to use a relay host at all. If
you do not want to use SMTP for internal mail routing in your Internet
domain, you can use a relay host instead. You may also use the relay host
for spam filtering and virus checking.
To enable a relay host after upgrading to Lotus Domino 6, enter the host
name or IP address of the relay host in the Server Configuration
document for the upgraded server. In addition, you must enable “SMTP
used when sending messages outside of the local Internet domain.”
Note A smart host, like a relay host, routes messages. Configuration of
the smart host is similar to the relay host setup. To configure a smart
host, you specify either the hostname or IP address of the host in the
Configuration Settings document. Relay hosts forward messages
addressed to recipients outside of the current Internet domain to a
responsible, SMTP-enabled server. The smart host forwards messages
addressed to local Internet domain recipients, who are not found in the
Domino Directory, to a SMTP-enabled server with an authoritative
directory of these users. This configuration is most common in a
mixed-product environment. For example, you can use a smart host in an
environment in which SMTP inbound traffic for an Internet domain
routes through a Domino server, but the domain uses two mail systems:
Lotus Notes and Microsoft Exchange.
For more information about smart host, see the book Administering the
Domino System.
Using third-party relay hosts with Lotus Domino 6

If messages initially reach your system via a third-party product, you can
still use Domino 6 functionality to improve performance. If your current
path uses Domino 4.6 MTAs, you can replace them with Domino 6 mail
servers through SMTP. Unless the gateway can query the Domino Direc-
tory to determine the correct mail server for a recipient, you use multiple
Mail Exchanger (MX) records in the DNS with the same preference to
spread the incoming load across the Domino 6 mail servers. While the
2-38 Upgrade Guide

percentage of messages that initially reach the correct destination server is
small, it increases as the number of Domino 6 mail servers able to receive
mail throug SMTP increases. In addition, because the Domino 6 servers
can access the Domino Directory to determine the correct mail server for
each recipient, the destination server is generally only one hop away.
This method spreads the load of inbound Internet mail messages across
all your Domino 6 servers. If one server is down, mail automatically
redirects to the other available servers.
If there are only a few Domino 6 servers and many Domino 4.6 servers,
these Domino 6 servers handle the load of receiving and converting
Internet messages for all of the Domino 4.6 servers. However, as the
number of Domino 6 servers increases, this load decreases.
If you replace the third-party gateway with a Domino 6 mail server that
is able to access the Domino Directory through either Notes RPC or
LDAP, the “gateway” server determines the correct destination server for
each message and routes it appropriately.
Sending mail in Notes format to Internet users

When you send a message in Notes format to an Internet user, Lotus
Domino 6 converts the message to MIME for that user. However, some
Notes items do not have MIME equivalents and cannot be converted. The
Notes client warns you if you send a message containing these items to
Internet users, so you can choose whether to edit the message or to send
the message without those features.
Notes items that do not have MIME equivalents include:
• Embedded elements
• Highlighting
• Notes hotspots, such as document links
Note If the server’s outbound MIME conversion option is set to
“Convert from Notes to HTML” or “Convert from Notes to Plain
Text and HTML,” Lotus Notes converts document links to Notes
URLs, such as Notes:///replica-id/view-id/notes-id.
• Objects (OLE)
Note Notes attempts to create an image based on the inactive OLE
object, but not all OLE objects have inactive images.
• Page breaks
• Sections
For more information about MIME conversion options, see the book

Calendar and scheduling features over SMTP
Domino routes calendar and scheduling items, such as meeting invita-
tions, over Notes RPC where possible. If you send a calendar or schedul-
ing item over SMTP — for example, if you send a meeting invitation over
the Internet — Lotus Domino 6 converts the item to text as did Lotus
Domino 4.6.
For more information, see the chapter “Upgrading Notes Clients.”
2-40 Upgrade Guide

Chapter 3
Upgrading the Domino Directory
This chapter describes how to upgrade the Domino 4.6 Public Address
Book or Domino 5 Domino Directory to the Domino 6 Domino Directory
and how to administer Domino servers, Notes clients, and Domino appli-
cations with the Domino 6 Directory.
Upgrading the Domino Directory

After you upgrade to Lotus Domino 6, the server prompts you to
upgrade the design of the Domino 4.6 Public Address Book or
Domino 5 Domino Directory with the Domino 6 Directory template
(PUBNAMES.NTF) if you haven’t already. Upgrade the directory design
to the Domino 6 Directory template to properly administer the Domino 6
server.
The new Domino Directory template works with the Domino 6 Adminis-
trator client to streamline directory and server administration. The
Domino Directory is backward-compatible and can be used in mixed-
release environments. After you upgrade the Domino Administration
server, which is the first server you should upgrade, and the design of
your address book to the Domino 6 Directory template, you can replicate
the directory to other servers in the domain. Make sure to upgrade your
administrator client to Domino 6. With the Domino 6 Administrator
client, upgrade the database format of the Domino Directory by compact-
ing the database, then rebuild the views.
Note Be aware that upgrading the Domino Directory design replaces
the template design. The Domino 6 design overwrites any customizations
made to the Public Address Book or Domino Directory. Before you
upgrade to the Domino 6 design, you may want to create a backup of the
Public Address Book or Domino Directory to preserve your custom
changes. After you upgrade, test the Domino Directory to see if your
custom changes are still necessary. If so, you can modify the Domino 6
directory template.
For more information about upgrading customized directories or address
books, see the topic “Customized Address Books or Directories” later in
this chapter.
3-1
To upgrade to the Domino Directory template
1. After you complete the upgrade, start the Domino server.
2. From the Domino server console, when Domino asks if you want to
upgrade the Domino Directory design to the Domino 6 template,
enter
Y
This replaces the Domino 4.6 Public Address Book or Domino 5
Domino Directory template with the Domino 6 Directory template.
3. Verify that there are no errors or problems. Then, quit the server.
Enter
quit
and press ENTER.
To compact the Domino Directory after upgrading

Compacting the Domino Directory upgrades the database format to the
Domino 6 format. Each of the following commands uses the file name
NAMES.NSF. If your Domino Directory has a file name other than
NAMES.NSF, substitute the correct file name.
From the Domino server console, compact the Domino Directory to the
new database format.
• On Microsoft Windows NT (Intel platforms), enter the following
command:
load compact names.nsf
and press ENTER.
You can also compact the Domino Directory from the operating
system command line. Change to the Domino program directory,
then enter the following command:
ncompact names.nsf
and press ENTER.
• On UNIX platforms, enter the following command:
compact names.nsf
and press ENTER.
To rebuild views in the Domino Directory

Rebuild the ($ServerAccess) and ($Users) views in the Domino Directory
to give clients access to the server.
Note In the Domino 6 Directory, the ($ServerAccess) and ($Users) views
are designated for transaction logging. If you enable transaction logging
for the Domino Directory, future restarts after a server failure will be
faster.
3-2 Upgrade Guide

1. From the command line of your operating system, enter the
following commands based on your operating system.
• On Microsoft Windows NT (Intel platforms), enter the following
command:
nupdall names.nsf -t "($ServerAccess)" -r
and press ENTER. Then enter:
nupdall names.nsf -t "($Users)" -r
and press ENTER.
• On UNIX platforms, enter the following command:
updall names.nsf -t /($ServerAccess) -r
and press ENTER. Then enter:
updall names.nsf -t /($Users) -r
and press ENTER.
2. After you rebuild views in the Domino Directory, start the Domino
server.
Updating views in databases on the upgraded Domino server

Updating database views gives users access faster to the Domino Direc-
tory and other databases on the server. The amount of time Updall takes
to run depends on the number of databases on the server, the size of the
databases, and the complexity of the views in those databases.
At the Domino server console, enter the following command:
load updall
and press ENTER.
Replicating the Domino Directory design to other servers

After you upgrade a server to Lotus Domino 6, you can replicate the
Domino Directory design to your organization’s other servers, including
Domino 5 and Domino 4.6 servers. Domino 4.6 servers must run Domino
4.6.7a to support the Domino 6 Directory.
If you disabled replication for the Domino Directory, remember to enable
it again.
Note After replicating the new template to other servers, you must
rebuild the views in the Domino Directories or Public Address Books on
those servers. The view rebuild for the Domino 6 template on a Domino
4.6 or Domino 5 server is time-consuming. Replicate the template and
rebuild the views for pre-Domino 6 servers on a weekend or during
other times when server load is low.
Upgrading the Domino Directory 3-3

Using the Domino Directory template in a mixed-release environment
The Domino 6 Directory template can be used in a mixed-release
environment that contains Domino 6 and Domino 4.6 or Domino 5
servers. After upgrading your first server to Lotus Domino 6, you can
replicate the new template to the other servers in your organization.
Upgrading Domino 4.6 servers that use the Domino 6 Directory

template
In a mixed environment of Domino 4.6 and Domino 6 servers, upgrade
the Domino 4.6 servers release to Domino 4.6.7a to support the Domino 6
Domino Directory template. When you upgrade, Domino asks if you
want to replace the design of the Public Address Book. If your Domino
4.6 servers use the Domino 6 Directory template (as recommended), and
you click Yes to replace the design, Domino overwrites the Domino 6
Directory template with the Domino 4.6 Public Address Book template.
Do not replace the design of the Public Address Book when upgrading
among pre-Domino 6 Domino servers that have the Domino 6 Directory
template on them.
Note If you upgrade Domino 5 servers to the latest maintenance release,
you are prompted to replace the design of the Domino Directory. If you
have already upgrade the Domino Directory to the Domino 6 Directory
template, click No. Otherwise, the Domino 5 server replaces the Domino
6 Directory with the Domino 5 Directory template.
Accessing the Domino 6 Directory with a Notes 4.6 client

The Domino 6 Directory uses tabbed tables in many of the Directory
forms to consolidate and present information more effectively. However,
Notes 4.6 clients cannot display tabbed tables, so forms that use the
tables do not render perfectly to Notes 4.6 clients. Person and Group
documents in the Domino 6 Directory have an alternate format that
renders well to Notes 4.6 clients and is very similar to the design of the
forms in the Domino 4.6 Public Address Book. Other documents display
all information, but are less easy to read and work with. Because users
primarily open Person and Group documents, the effect of the upgrade
on the Domino Directory should be minimal. To administer the Domino
6 Directory, use the Domino 6 Administrator client because the tabbed
tables render appropriately and make administration easier.
3-4 Upgrade Guide

Customized Address Books or Directories
If you customized the Domino 4.6 Public Address Book or Domino 5
Directory, perform the following steps to upgrade the Address Book or
Directory to the Domino 6 Directory.
1. Back up the design of your Public Address Book or Domino
Directory.
2. Upgrade the address book to the Domino 6 Directory template.
3. Inspect the upgraded Domino Directory to determine which of your
customized changes you still need.
4. To retain the customizations that you added, create a subform for
your customizations and include that subform in another subform
especially designed to work with your customizations.
For more information about customizing the Domino Directory, see the
Note You must add individual Domino 4.6 or Domino 5 customizations
to the Domino 6 Directory design elements. Do not attempt to add the
Domino 6 changes to your Domino 4.6 or Domino 5 design because the
Public Address Book or Domino Directory will not function properly in a
Lotus Notes/Domino 6 environment.
Condensed Directory Catalogs and upgraded Domino servers

If you receive the server console error message:
REBUILD required - version for "...\domino\data\dc.ntf out
of date"
after upgrading a Lotus Domino 5 server running a server-based
condensed Directory Catalog, you need to rebuild the Directory Catalog
full-text index. To do so, enter the following command on the server
console:
load updall dc.nsf-x
in which dc.nsf is the name of the condensed Directory Catalog. You
perform this procedure only once.
For more information about condensed directory catalogs, see the book

LDAP service and Domino Administration servers
In Lotus Domino 6, the LDAP service runs automatically on the Domino
Administration server for the Domino Directory domain. The Domino
administration server maintains the LDAP schema and runs the directory
tree verification process for all LDAP services in the domain.
If you prefer to not have the LDAP service running on the administration
server, you can do the following:
• Prevent the LDAP service from processing LDAP client requests
• Disable the LDAP service for the domain
For more information about preventing the LDAP server from processing
requests or disabling the LDAP service, see the book Administering the
Domino System.
LDAP Schema changes in Lotus Domino 6

The following is a list of changes to the Domino LDAP Schema in Lotus
Domino 6.
• There is a new Domino LDAP Schema database created from the
template SCHEMA.NTF. This database replaces the Domino 5 LDAP
Schema database created from the template SCHEMA50.NTF. A new
process called the schema daemon, spawned by the LDAP service,
creates the new Schema database on the administration server for the
Domino Directory. The schema daemon replicates the databases to
all Lotus Domino 6 servers in a domain that run the LDAP service,
ensuring a consistent schema throughout a domain. In this release,
the Schema database is also a tool you can use to extend the schema.
If you upgrade a Domino 5 server that runs the LDAP service to
Lotus Domino 6, the installation program deletes the Domino 5
SCHEMA50.NTF template, and the LDAP service deletes the
Domino 5 SCHEMA50.NSF database. To retain these files, rename
them before you upgrade.
Note If you previously extended the schema in Domino 5 using the
Domino Designer, you will not lose your changes. The schema
changes appear in the new SCHEMA.NSF database.
3-6 Upgrade Guide

• The first time Domino loads the LDAP service on the administration
server of the Domino domain, Domino creates a new Domino LDAP
Schema database. While Domino creates the schema documents and
builds the views in this database, certain schema elements such as
object classes, attribute types, or syntaxes may be unavailable. To
avoid potential problems, allow at least 15 minutes after the LDAP
service starts for Domino to finish creating all default schema
documents before you extend the schema.
Note The delay that occurs while Domino creates the schema
documents and builds the database views occurs only once when
Domino loads the LDAP service for the first time.
• In Lotus Domino 5, the LDAP service converted a search base of
country (“c=xx”) to root (““) by default. This conversion
accommodates releases of Microsoft Outlook Express earlier than 5.5,
which supply a default country search base when users do not
specify a search base. In Lotus Domino 5, you can use the
NOTES.INI setting LDAP_CountryCheck=1 to prevent the LDAP
service from making this conversion.
By default, the Domino 6 LDAP service does not convert a search
base of country to root. Use the NOTES.INI setting
LDAPPre55Outlook=1 to revert to the Domino 5 LDAP service
behavior of converting a search base of country to root to
accommodate releases of Microsoft Outlook Express earlier than 5.5.
The LDAP_CountryCheck setting is obsolete in Lotus Domino 6.
For more information about the Domino LDAP Schema, see the book
Domino Directory changes since Lotus Domino 4.6

The following topics describe changes made to the Domino Directory in
Lotus Domino 5, but applicable to the Domino 6 Domino Directory.
These topics are intended for Domino 4.6 administrators.
• Increased UniqueNameKey (UNK) table size
• Upgrading Cascading Domino Directories to directory assistance
• Upgrading directory assistance
• Using the Directory Profile
• Web authentication and secondary address books

Increased UniqueNameKey (UNK) table size
The Domino 6 Directory template includes a number of new field names that
increased the size of the UniqueNameKey (UNK) table. By default, data-
bases are limited to 64K of item names. Domino 5 and Domino 6 databases
can exceed this limit if you select the “Allow more fields in database” option
in the NAMES.NSF database. Domino 4.6 databases do not support this
option. To replicate the Domino 6 Domino Directory to Domino 4.6 servers,
upgrade those servers to Domino 4.6.7a. If you replicate the directory to a
release prior to 4.6.7a, you receive the error “Cannot store document;
database has too many unique field names,” then replication ends.
Upgrading Cascading Domino Directories to directory assistance

Prior to Domino 4.5, Domino servers used the NAMES NOTES.INI
setting — also referred to as cascading Domino Directories — to look up
information in a secondary Domino Directory. Although cascading
Domino directories are still supported for backward compatibility, you
should convert to directory assistance.
If you use cascading directories in your Domino 4.6 environment, they
continue to work in the Domino 6 environment. However, you will see
benefits from upgrading to directory assistance.
The following table compares directory assistance to cascading Domino
Directories.
Feature Directory assistance Cascading

Do lookups in secondary Domino Yes Yes
Directories on behalf of Notes users for
mail addressing
Do lookups in LDAP directories on behalf Yes No
of Notes users for mail addressing
Do lookups in secondary Domino Yes Yes
directories on behalf of LDAP clients
Refer LDAP clients to LDAP directories Yes No
Authenticate Internet clients registered in Yes No
secondary Domino Directories
Authenticate Internet clients registered in Yes No
LDAP directories
Fail over to an alternate replica of a Yes No
directory
Use naming rules to efficiently search Yes No
secondary Domino Directories
continued
3-8 Upgrade Guide

Feature Directory assistance Cascading
Support for an unlimited number of Yes No (NAMES=
secondary Domino Directories setting has a
256-character
limit)
Support for “Recipient name type ahead” Yes Yes
addressing
One server cannot use both directory assistance and cascading Domino
Directories.
To upgrade from cascading directories to directory assistance

To upgrade from cascading directories to directory assistance, edit the
NAMES setting in the NOTES.INI file. Remove all secondary directory
names. Do not the remove the primary directory name. Then set up
directory assistance.
Note If the primary directory file name is NAMES.NSF, do not use the
NAMES setting in the NOTES.INI file (that is, do not set a value for this
setting). When no value is specified for the NAMES setting, Domino
defaults to NAMES.NSF.
For more information about directory assistance, see the book
Upgrading directory assistance

Domino 4.6 administrators must upgrade their directory assistance
databases to the Domino 6 directory assistance template design. After
upgrading your Domino 4.6 server and Domino Directory to Domino 6,
upgrade your directory assistance database to the Domino 6 design.
Note Domino 5 administrators do not need to perform this task.
1. Start the Notes client.
3. In the Server box, select the server that contains your directory
assistance database.
4. Navigate to and select the directory assistance database.
5. Click Open.
6. Choose File - Database - Replace Design.
7. Click the Template Server button.
8. Select the Domino 6 server that has the new directory assistance
template (DA50.NTF).
9. Click OK.

10. Select the directory assistance template (DA50.NTF).
11. Click OK.
12. When prompted to replace the template, click Yes.
13. Close the directory assistance database.
The directory assistance template is backward-compatible; replicate the
new design to your Domino 4.6 servers running directory assistance.
Using the Directory Profile

The first time you open the upgraded Domino Directory with a Notes or
Web client, you see the Domino Directory Profile. The profile contains
settings like domain name associated with the Domino Directory,
condensed server directory catalog or Directory Catalogs for the domain,
and other related Domino Directory settings. The Domino Directory
Profile is created automatically when you set up the Domino server. You
can modify this document.
For information on modifying the Directory Profile, see the book
Web authentication and secondary address books

Beginning with Lotus Domino 4.6.2, Web clients cannot authenticate
from cascaded Public Address Books or Domino Directories (the
NAMES= line in the NOTES.INI file). To authenticate Web clients using
secondary address books or directories, choose one of these options:
• Set up directory assistance
• Set up a condensed server directory catalog to aggregate multiple
directories
• Set up an extended server directory catalog, which also aggregates
multiple directories, but contains the same views found in the
Domino Directory
For more information about condensed and extended server directory
catalogs and directory assistance, see the book Administering the Domino
System.
3-10 Upgrade Guide

Chapter 4
Upgrading Notes Clients
This chapter describes the options for upgrading Notes clients to Lotus
Notes 6.
Upgrading Notes clients

Lotus Notes 6 provides the following options for upgrading Notes
clients:
• Upgrade-by-mail
• IBM Lotus Notes Smart Upgrade
• Administrative installation
You also have the option of using third-party tools for upgrading the
Notes client.
Upgrade-by-mail is an e-mail notification system that notifies users to
upgrade their Notes clients and mail file templates to the Notes/Domino
6 design. Upgrade-by-mail requires that you copy all installation files to
a network file server or a shared directory that users can access. In the
upgrade notification, you specify the path to SETUP.EXE. The notifica-
tion message includes buttons that users click to launch the Lotus Notes 6
installation program and to replace the design of their Notes mail file.
Use Upgrade-by-mail to upgrade Notes 4.6 and Notes 5 users to Lotus
Notes 6.
For more information about Upgrade-by-mail, see the topic “Using
Upgrade-by-mail” later in this chapter.
Lotus Notes Smart Upgrade works with the Lotus Notes 6 update kits or
incremental installers that you download from the Lotus Developer
Domain (http://www.lotus.com/ldd/smartupgrade). Like Upgrade-by-
mail, Lotus Notes Smart Upgrade sends a notification to users to
upgrade their Notes clients. Lotus Notes Smart Upgrade lets you set a
grace period in which users must upgrade their clients. When you
upgrade from Lotus Notes 6 to later releases, use Lotus Notes Smart
Upgrade.
4-1
For more information about Lotus Notes Smart Upgrade, see the topic
“Using IBM Lotus Notes Smart Upgrade” later in this chapter.
Administrative installation 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 6 locally on their client
machines. You can use administrative installation to copy the installation
files to a network file server, then use Upgrade-by-mail or Lotus Notes
Smart Upgrade to notify users.
The following table compares the Upgrade-by-mail, Lotus Notes Smart
Upgrade, and administrative installation.
Option Advantages Disadvantages

Upgrade-by-mail • Upgrades Notes 4.6 and • Administrator cannot
Notes 5 clients and mail file determine when
templates upgrades occur
Lotus Notes Smart • Establishes a grace period • Can be used only with
Upgrade in which users must Lotus Notes 6 and later
upgrade their clients releases
Administrative • Uses the command line • Requires the Windows
installation option /A to create an Installer service, which
administrative image of the is part of the Windows
Lotus Notes 6 installation XP and 2000 operating
on a network file server systems and is available
• Can be customized with for, but not part of,
transforms to create a Windows 95, 98, and
silent, automated installa- NT 4.0
tion, a shared installation,
and so on
For more information about transforms and silent installation, see the
All the upgrade options require users to have a network connection. For
mobile users, users with low bandwidth connection or no connection,
these options may not apply. To upgrade these users, you could send
Lotus Notes 6 CDs to them.
4-2 Upgrade Guide

Before you upgrade the Notes client
Before you begin upgrading Lotus Notes clients, make sure that you or
your users do the following:
• If the computer on which you are upgrading runs anti-virus
software, close the application.
• If you are upgrading Lotus Notes on an Apple computer running OS
X, turn off all options in the Application Sharing tab of the Shared
System Preferences panel to avoid any errors.
• To successfully install, upgrade, and use Lotus Notes 6, users must
be allowed both Write and Modify permissions to the Program
directory, Data directory, and all associated subdirectories.
• If you are upgrading Lotus Notes on a Windows NT, 2000, or XP
computer, you must have administrator rights to the system. On a
Windows NT 4.0 computer, log in as an administrator or set
administrator-level privileges for All Users. This can be done from
the command line.
• Windows NT, 2000, and XP users should log onto their computers
with administrative rights to install Lotus Notes 6. For cases in which
administrative rights are not available, enable the setting “Always
install with elevated privileges.” Refer to the Release Notes for the
most current information on permissions required when installing as
a non-administrator.
• Options for installing the Lotus Notes client on Restricted or
Standard/Power User computers are described in the Microsoft
Windows 2000, Windows XP, and Windows Installer documentation.
• Review options for customizing the Notes client installing and set
up.
For more information about customizing installation and setup, see the
Using Upgrade-by-mail
Upgrade-by-mail is a feature that sends an e-mail notification to speci-
fied users to upgrade their Notes clients and optionally, their mail file
templates. You can also use Upgrade-by-mail to notify cc:Mail, Microsoft
Mail, Microsoft Exchanges, and Microsoft Outlook Express users that
their mail files have been migrated to Notes mail.
For more information about sending an upgrade notification to migrated
mail users, see the chapter “Migrating Personal Mail Data.”
Upgrading Notes Clients 4-3

The upgrade notification contains two buttons that users click to upgrade
their clients and mail files. The Install Notes button launches a Notes
client installation program from a directory on a network drive to which
users have access. The Upgrade Mail File button replaces the user’s
current mail template with a locally stored Notes/Domino 6 mail
template or another specified template, like a customized mail template.
Users must upgrade their Notes clients to install the Notes/Domino 6
mail file template locally, before they upgrade their mail files.
Using the Upgrade Mail File button is optional. You must complete the
Mail Template Information section in the upgrade-by-mail notification to
enable the Upgrade Mail File button. If you do not complete this section,
Upgrade-by-mail does not display the button on the e-mail notification.
Before you use Upgrade-by-mail

Before you begin, complete the following tasks:
• Back up Notes client files.
• Create an installation directory on a Domino or file server to which
all users have network access, then copy all Notes installation
directories and files to this folder.
Note To use Upgrade-by-mail to upgrade mail file templates, users
must have at least Designer access to their mail databases. If users do not
have this level of access, use the mail conversion utility to update mail
file templates.
Backing up Notes client files

Back up important Notes client files in case an error occurs during the
upgrade process. If you experience problems, you can restore these files
with the backed-up versions. Back up the following files for each Notes
client:
File Default Location

NOTES.INI (Notes Preferences on the For Lotus Notes 4.6 clients, System
Macintosh) directory (for example, C:\WIN95)
For Lotus Notes 5 clients, Notes data
directory (for example,
C:\NOTES\DATA)
DESKTOP.DSK (Notes 4.6) Notes data directory (for example,
DESKTOP5.DSK (Notes 5) C:\NOTES\DATA)
Personal Address Book (NAMES.NSF Notes data directory (for example,
by default) C:\NOTES\DATA)
continued
4-4 Upgrade Guide

File Default Location
User ID files (for example, Notes data directory (for example,
JSMITH.ID) C:\NOTES\DATA)
Local databases (NSF) Notes data directory (for example,
C:\NOTES\DATA)
Local database directory links (DIR) Notes data directory (for example,
C:\NOTES\DATA)
Any customized Notes database Notes data directory (for example,
templates (NTF) C:\NOTES\DATA)
USER.DIC (Personal dictionary Notes data directory (for example,
entries for spelling checker) C:\NOTES\DATA)
Creating the upgrade notification

The following procedure describes how to upgrade from Lotus Notes 4.6
or Notes 5.0 to Lotus Notes 6.
1. In the Domino Administrator, select the server bookmarks, then
select the server on which your users’ mail files reside.
2. Click the Messaging tab.
3. Open the “Mail users” view, then click “Send Upgrade
Notifications.”
4. In the Upgrade Message document, complete the To field.
5. Select either the “Send out Upgrade Notes/Update Notes Mail
Template notices to users upgrading to R5 or later” or the “Send out
Upgrade Notes/Update Notes Mail Template notices to pre-R5
users” option.
6. Enter a build number to prevent upgrades of Notes clients running
the specified build or a later build. By default, the build number is
determined by the @Version function.
7. In the Notes Install Kit Paths section, enter the directory path in the
“Root path for Install kits” field using the following format:
\\server_name\shared_drive_name\installation_folder_name
8. In the “Path for Windows NT and Windows 95” and “Path for
Macintosh PPC” fields, enter the file path to the installation file
following the format above, but include SETUP.EXE in the path.
9. If you want users to upgrade their mail file templates, complete the
Mail Template Information section. Enter the template name of the
existing mail files. The default field value is a wild card character (*).
Note Complete the Mail Template Information section to include an
Upgrade Mail button in the upgrade notification sent to users.

10. By default the new mail template name appears in the New Mail
template file name field. If you renamed the template or used a
custom mail template, enter the new name. Note that the new
template must exist in your users’ Notes data directory.
11. By default the “Ignore 200 category limit” check box is selected. This
option overrides a default that limits the creation of folders in a
database to 200. If you want no more than 200 folders created,
deselect the check box.
12. If you are upgrading IMAP clients, select the “Mail file to be used by
IMAP mail clients” check box.
13. (Optional) If you want to automatically upgrade custom folders to
the Inbox design, select the “Upgrade custom folders” check box.
14. (Optional) To prompt the user before upgrading custom folders,
select the “Prompt before upgrading custom folders” check box.
15. (Optional) If you want to provide additional information to your
users, complete the Additional Information field.
16. (Optional) Select whether or not to be notified after users have
upgraded their mail file templates.
17. Click Send when done.
Installing the Lotus Notes 6 software with Upgrade-by-mail

The upgrade notification includes two buttons. The Install Notes button
runs the Notes client installation program. The following procedure is
intended for Notes client users.
1. Click the Install Notes button.
2. Follow the prompts on the Setup screens to properly install the
software.
3. Launch Notes.
Notes sets up and upgrades the software automatically if you install
Lotus Notes 6 in the same directory as the previous release of Lotus
Notes. If you install the Lotus Notes 6 software in a different directory,
Lotus Notes prompts you to complete the configuration process. If you
install Lotus Notes in a different directory, be aware that the Setup
program places the NOTES.INI file in the Notes program directory. In
Lotus Notes 4.6, the install program placed the NOTES.INI file in the
system directory by default.
Note Lotus Notes automatically upgrades the Personal Address Book to
the Notes/Domino 6 design. If you have Internet mail set up to work
with POP3, Lotus Notes creates an Account record for that Internet mail
configuration.
4-6 Upgrade Guide

For more information, see the topic “Creating Account records for
Internet mail” later in this chapter.
Upgrading the mail file template with Upgrade-by-mail

After users install Lotus Notes 6, they must return to the upgrade notifi-
cation to upgrade the mail file template.
1. Click Upgrade Mail File.
2. When prompted for a password, enter your Notes password.
Lotus Notes upgrades the template automatically.
Using IBM Lotus Notes Smart Upgrade

IBM Lotus Notes Smart Upgrade notifies users to update their Notes 6
clients to later releases. Lotus Notes Smart Upgrade uses policy and
settings documents to help manage updates. Policy documents are a new
feature of Lotus Notes/Domino 6. You create these documents in the
Domino Directory to distribute standard settings and configurations
across groups, departments, or entire organizations.
Domino System.
To use Lotus Notes Smart Upgrade, follow this procedure:
1. Create a database using the Smart Upgrade Kits template to host
Notes client update kits.
2. Update the Configurations Settings document in the Domino
Directory with a link to the Lotus Notes Smart Upgrade database.
3. Download an update kit, also known as an incremental installer,
from the Lotus Developer Domain Web site
(http://www.lotus.com/ldd/smartupgrade).
4. Create a Kit document in the Lotus Notes Smart Upgrade database
and attach the kit to it.
5. Create or modify a desktop policy settings document where you
specify the updated release to deploy and the date on which the
grace period for updating a Notes client ends.
6. Create or modify a master policy to assign users or groups to the
desktop policy settings document.
7. Depending on the master policy created, edit Person documents to
assign users to the master policy and/or set the Lotus Notes Smart
Upgrade desktop policy settings document for one or more groups.

When users log into their Domino 6 home server, Lotus Notes Smart
Upgrade does the following:
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 Lotus Notes Smart Upgrade database.
2. Compares the update kit release number specified in the Deploy
version field of the desktop policy settings document to the release
number specified in the Destination version field of the Kit
document.
3. Specifying the upgrade kit release number in the Deploy version
field of the desktop policy settings document is optional. If the
Deploy version field is blank, but an update kit is available in the
Lotus Notes Smart Upgrade database, Lotus Notes Smart Upgrade
skips Step 2 and uses the release number of the update kit to
continue the upgrade process.
4. If the Notes client release number matches the release number in the
Source version field and the update kit release number matches the
release number in the “Destination version” field, Lotus Notes Smart
Upgrade checks whether or not the user is specified or is a member
of a group which is allowed to upgrade.
5. If users are specified or are members of a specified group, then Lotus
Notes Smart Upgrade prompts the users to upgrade their Notes
client. Users can choose to update their clients when prompted or to
delay the upgrade for the specified grace period.
6. If at the end of the grace period, the Notes clients have not been
updated, Lotus Notes Smart Upgrade presents users with an
“Update Now” button that forces them to update their Notes client.
Creating a Lotus Notes Smart Upgrade database

Use the Smart Upgrade Kits template (SMUPGRADE.NTF) to create the
Lotus Notes Smart Upgrade database that will store the upgrade kits.
The database must reside on at least one server in the domain. After the
Lotus Notes Smart Upgrade database is added to the database catalog,
other servers can locate the database. If you replicate the Lotus Notes
Smart Upgrade database to other servers in the domain, users will have
more choices in the database catalog and possibly fewer network
problems accessing the update kits.
1. In the Domino Administrator client, choose File - Database - New.
2. In the New Database dialog box, enter the server name and database
title.
3. Enter a file name in the File Name field.
4-8 Upgrade Guide

4. Click Template Server, then choose the server on which the database
will reside.
5. Select the “Show advanced templates” check box.
6. Select “Smart Upgrade Kits” from the box of template names, then
click OK.
7. After you create the Lotus Notes Smart Upgrade database, create a
database link in your Configuration Settings document in the
Domino Directory.
Creating a database link to the Lotus Notes Smart Upgrade database

In the Domino Directory, the Configuration Settings document contains a
Lotus Notes Smart Upgrade database link field in which you paste the
database link.
1. In the Domino Administrator, open the Lotus Notes Smart Upgrade
database that you created.
2. Choose Edit - Copy as link - Database link.
3. Open the Domino Directory, then open the Server - Configurations
view.
4. Select the server, then click “Edit Configuration” to edit an existing
Configuration Settings document.
Note Lotus Notes Smart Upgrade first checks for the Lotus Notes
Smart Upgrade database link in the Configuration Settings document
of the home server specified in the Notes client location document. If
that Configuration Settings document does not contain a Lotus Notes
Smart Upgrade database link, Lotus Notes Smart Upgrade next
checks the * - [All Servers] Configuration Settings document for the
database link.
5. On the Basics tab of the document, paste the database link in the
“Lotus Notes Smart Upgrade DB link” field.
6. Save and close the Configuration Settings document.
7. With the Lotus Notes Smart Upgrade database set up, you can begin
adding update kits to the database.
Adding update kits to the Lotus Notes Smart Upgrade database

You can download update kits as they become available from the Lotus
Developer Domain http://www.lotus.com/ldd/smartupgrade. After
you download a kit, follow these steps to create a Kit document in the
Lotus Notes Smart Upgrade database. You can attach the kit to the Kit
document or store the kit in a directory on a shared network drive that
users can access.

1. In the Domino Administrator client, open the Lotus Notes Smart
Upgrade database that you created.
2. Click New Kit to create a Kit document.
3. On the Basics tab, complete the following fields:
In this field Do this
Source version Enter your current Notes client release.
Note To find the current Notes client release
number, check the About Notes document. To
open the document, choose Help - About Notes.
Operating system Enter or select the operating system for which the
kit is intended.
Localization Enter or select the language of the kit.
Kit type Select one of the following:
• “Full client” to install all clients
• “Lite client” to install the Notes client only
Destination version Enter the release number of the update kit.
The value of this field must match the value in the
Deploy Versions field of the desktop policy
settings document.
4. Select the Enabled check box to make the kit available to authorized
users.
5. Click the Data tab, then choose the option for the location of the
update kit.
6. Depending on the option that you choose, do one of the following:
• If you choose “Attached to this note,” click the Attachment icon,
then attach the update kit or full installation kit.
Note Attach the EXE file that you downloaded to the document
without decompressing the file.
• If you choose “On a shared network drive,” enter the file path to
the SETUP.EXE. Follow this convention:
\\networkfileservername\shareddirectoryname\setup.exe
When you use the shared network drive option, make sure to
decompress the file, then copy all files in the installation kit to the
directory specified.
7. Click the Admin Notes tab, then enter the message that will appear
when Lotus Notes Smart Upgrade prompts users to upgrade their
Notes clients.
4-10 Upgrade Guide

8. Click the Administration tab, then complete the following fields:
Allowed Users Enter or select the users or groups allowed to upgrade
their Notes clients. To include all users in your
organization, enter a value using the following format:
*/OrgUnit/Organization/CountryCode
Owners Enter or select the persons who own this document.
Administrators Enter or select the persons who administer the
document.

10. Create a desktop policy to deploy the update kit.
Creating a Lotus Notes Smart Upgrade desktop policy settings

document
A desktop policy settings document enables Lotus Notes Smart Upgrade
to function automatically, to deploy different releases of the Notes client
to different groups of users, to upgrade Notes clients through several
updates at one time, and to control when updates occur, which preserves
server performance. The desktop policy settings document is applied
continually during authentication and is enforced by dynamic configura-
tion. The policy settings document is applied to users’ client configura-
tion whenever a change to the document occurs.
For more information about the desktop policy settings document, see
1. In the Domino Administrator, open the Settings view on the People
and Groups tab.
2. If you are creating a desktop policy settings document, click Add
Settings, then choose Desktop. If you are modifying a desktop policy
settings document, select the policy, then click Edit Settings.
3. If you are creating a desktop policy settings document, complete the
Policy name and Description fields in the Basic tab of document.
4. In the Deploy version field, enter the release number of the Notes
client to which you want users to upgrade.
5. In the Grace Period field, enter the date on which the grace period
ends. Use the mm/dd/yyyy date format.
7. Create a master policy to administer the Lotus Notes Smart Upgrade
desktop policy settings document to users and groups.

Creating a master policy document for Lotus Notes Smart Upgrade
You create or modify a master policy document to determine which users
and groups will be assigned the Lotus Notes Smart Upgrade desktop
policy settings document. There are two types of master policies: organ-
izational and explicit. Organizational policies are based on your organ-
izational hierarchy and are assigned automatically to the users within an
organization. If you want all users in your organization to upgrade their
Notes clients, create an organizational policy. Explicit policies are
assigned to specific users and groups. If you want only specific users and
groups to upgrade their Notes clients, create an explicit policy.
Domino System.
1. On the People and Groups tab of the Domino Directory, open the
Policies view.
2. If you are creating a master policy, click Add Policy. If you are
modifying an existing master policy, select the policy to modify, then
click Edit Policy.
3. If you are creating a master policy, do the following:
• On the Basics tab, enter the policy name, then choose either
Explicit or Organizational as the policy type.
• Provide a description for the policy.
4. In the Desktop field, select the Lotus Notes Smart Upgrade policy to
associate the master policy with the Lotus Notes Smart Upgrade
desktop policy settings document.
6. If you created an explicit policy, then you can assign the master
policy to users and groups. If you created an organizational policy,
then the process is complete.
Note A user who is not assigned to the Lotus Notes Smart Upgrade
desktop policy settings document may still update the Notes clients. If
the user has ACL access to the Lotus Notes Smart Upgrade database,
when the user’s Notes 6 client authenticates with the home server, the
server compares the Notes client release information with the available
update kit release information. The server then checks the master policy
to see if the user is assigned to the Lotus Notes Smart Upgrade desktop
policy settings document. If the user is not assigned to the desktop policy
settings document, but has access to the Lotus Notes Smart Upgrade
database, then the user is prompted to upgrade the Notes client.
4-12 Upgrade Guide

Assigning the Lotus Notes Smart Upgrade master policy to users
and groups
If you created an explicit master policy, then you must assign the policy
to users and/or groups. To assign a master policy to a user, edit the
Person document. To assign a master policy to a group, use the Set Policy
Options dialog box.
To assign a master policy to a user

1. In the Domino Administrator, go to the Persons view on the People
and Groups tab.
2. Select the person to whom you want to assign the Lotus Notes Smart
Upgrade master policy.
3. Click Edit Person.
4. In the Person document, click the Administration tab.
5. In the Policy field, select the name of the Lotus Notes Smart Upgrade
master policy.
To assign a master policy to a group

1. In the Domino Administrator, go to the Groups view on the People
and Groups tab.
2. Select the group to which you want to assign the Lotus Notes Smart
Upgrade master policy.
3. On the Tools pane, select Groups - Set Policy.
4. In the Set Policy Options dialog box, select the Lotus Notes Smart
Upgrade master policy, then click OK.
Note You can assign only one master policy per group; however, you
can assign several policy settings documents to a master policy.
Notes users and Lotus Notes Smart Upgrade

The following is general information about Notes users and Lotus Notes
Smart Upgrade.
• Users’ location documents must specify the correct home server on
the Servers tab of the document. If the wrong home server is
specified, then Lotus Notes Smart Upgrade will not begin the
upgrade process.
• The Windows Installer allows you to specify administrator-level
privileges for Lotus Notes 6. This allows users with Windows NT,
Windows 2000 Professional, and Windows XP Professional operating
systems to install Lotus Notes 6 without administrator access.

• At any time during the grace period, users can choose File - Tools -
Notes Smart Upgrade to begin the upgrade process.
Maintaining Lotus Notes Smart Upgrade

After you have completed the procedure for setting up the Lotus Notes
Smart Upgrade database and Lotus Notes Smart Upgrade policies,
perform the following tasks to maintain Lotus Notes Smart Upgrade:
• Download new update kits as they become available on Lotus
Developer Domain http://www.lotus.com/ldd/smartupgrade and
add the new kits to the Lotus Notes Smart Upgrade database.
• Disable the previous update kits and enable the latest update kit. To
disable a kit, clear the Enable check box on the Basics tab of the Lotus
Notes Smart Upgrade document.
• Edit the Lotus Notes Smart Upgrade desktop policy settings
document with the new release number and grace period.
Upgrading shared installation

Shared installation saves disk space by installing a single copy of the
Lotus Notes program files on a network file server to be shared by
multiple users. It copies only data files, like DESKTOP.DSK,
BOOKMARK.NTF, and local databases, locally to the client computer.
In previous releases of Lotus Notes, shared installation was an option
available from the Lotus Notes installation wizard. In Lotus Notes 6, you
create shared installation using a transform applied to an administrative
image.
To upgrade a shared installation, delete the old administrative image,
then perform an administrative installation to create a new administra-
tive image in the same location as the previous image. Administrative
installation installs all program files on the server; however, by default,
the components of the administrative installation are not shared. To
modify the administrative image, create a transform that indicates
which components are shared. You can create the transform using
InstallShield Tuner for Windows Installer, which is available with Lotus
Notes/Domino 6. Copy the transform to the server directory in which
the administrative image resides.
For more information about administrative installation, see the book
Shared installation is a Windows only feature. To upgrade shared instal-
lation to Lotus Notes 6, client computers require the Windows Installer
service, which is part of the Windows 2000 and XP operating systems. It
4-14 Upgrade Guide

is available for the Windows 95, 98, and NT 4.0 operating systems. Using
the Windows Installer and a SETUP.EXE file to perform an installation
on a Windows 95, 98, or NT 4.0 system installs the Windows Installer
service. If the Windows Installer service is not installed, users will receive
an error message when they launch the installation program.
Note Administrative installation does not copy the SETUP.EXE file to
the network file server. When you upgrade shared installation, you must
make sure that each Windows client has the Windows Installer service
installed because shared installation will not install the Windows
Installer service.
If you have more than one existing administrative images for different
sets of users, you can replace the old images with one administrative
image and multiple transforms. Transforms are applied to the Windows
Installer package (MSI file) included in the administrative image to create
different shared installations. For instance, if you had different shared
installations for your Notes users and Notes developers, you can replace
both existing images with one administrative image and two transforms.
The first transform installs only the Notes client, while the second trans-
form installs both the Notes and Domino Designer clients.
Deploying Notes client settings with policies

After users upgrade to Lotus Notes 6, you can use policies to configure
Notes client settings for users. These settings include customized
Welcome pages, standard bookmarks, and workstation Execution Control
Lists (ECLs). Policies are new to Lotus Notes/Domino 6 and replace Setup
Profiles used in earlier releases. Before implementing policies, disable any
Setup Profiles in your organization’s Person documents.
Domino System.
Setting default workstation security

Before upgrading Notes, the domain administrator may want to set the
Administration Execution Control List (ECL) in the Domino Directory.
The Administration ECL sets the default security on the Notes client
when users start Notes for the first time after they upgrade. Workstation
security defines which group’s applications can execute on a Notes client.
If a group is not specified in the ECL for a client, Notes warns the user
when an application created by the group attempts to run on that client.
For information on setting the Administration ECL, see the book

Lotus Notes client changes since Notes 4.6
The following topics describe changes in the Lotus Notes client, includ-
ing changes to the mail file template and calendar and scheduling, that
first appeared in Lotus Notes 5. These changes are applicable to Lotus
Notes 4.6 administrators and users upgrading to Lotus Notes 6.
• Converting the workspace to bookmarks
• Creating Account records for Internet mail
• Repeating meetings and Lotus Notes 6
• Setting your Personal Address Book preferences
• Using calendar and scheduling features with Internet mail
Converting the workspace to bookmarks

Lotus Notes 6 automatically converts the Lotus Notes 4.6 workspace into
bookmarks. You can still access the workspace if you want, but it is not
necessary because the workspace pages convert to bookmark icons,
which are located on the left side of the client screen.
Notes provides you the following bookmark icons or folders initially:
Bookmark icon or folder Description

Welcome Displays your home page, where you can perform tasks
and browse and search the Web.
Mail Displays your mail file.
Calendar Displays your calendar.
Address Book Displays your Personal Address Book.
To Do Displays your To Do list of tasks.
Replication Displays your Replicator page. This entry appears only
if you have local replicas with replication enabled.
Sametime Connect Opens the Sametime Connect client.
Note This bookmark appears only if you installed
Sametime Connect.
Domino Opens the Domino Administrator for administering
Administrator Domino servers.
Note This bookmark appears only if you installed the
Domino Administrator.
Domino Designer Opens the Domino Designer for designing Domino
applications.
Note This bookmark appears only if you installed the
Domino Designer.
continued
4-16 Upgrade Guide

Bookmark icon or folder Description
Favorite Bookmarks Displays a bookmark list of the databases you used
folder most recently.
Databases folder Displays bookmarks organized as they are on your
workspace.
More Bookmarks Displays bookmarks for searching Notes databases and
folder the Web.
History folder Displays databases that you opened in the last four
days.
Internet Explorer Contains bookmarks from your Microsoft Internet
Links folder Explorer Favorites links
Navigator Links Contains bookmarks from your Netscape Navigator
folder Bookmarks links
You can add a bookmark to any Bookmark folder by dragging it to that

folder.
For more information on using bookmarks, see Lotus Notes 6 Help.
Creating Account records for Internet mail

Lotus Notes 5 introduced Account records, which contain information
for accessing mail using POP, IMAP, and sending mail with SMTP. If
your Lotus Notes 4 Location record is set up to use POP3, Notes converts
this information into an Account record for that setting. If you send mail
to the Internet, Notes creates an SMTP Account record. The accounts are
set for the location that you set up for Internet mail.
Repeating meetings and Lotus Notes 6

Organizations that want to use the repeating meetings feature in the
Notes/Domino 6 mail template should upgrade their Notes 4.6 clients
and mail templates to Notes 4.6.3 for repeating meetings to work
properly in a mixed-release environment. You do not need to upgrade
servers, but you must upgrade the mail templates for those clients that
want to use repeating meetings.
Setting your Personal Address Book preferences

When you upgrade to Lotus Notes 6, Notes automatically upgrades the
design of your Personal Address Book. The first time you open your
Personal Address Book after upgrading, Notes asks you to enter your
preferences into the Personal Address Book profile. To enter your prefer-
ences, do the following:

1. Select an Address Book owner. Generally this is the person whose
Notes client has been upgraded and who is the primary user of the
address book.
2. Select whether to sort alphabetically new groups that you create.
3. Select whether to allow LDAP queries of the address book to elicit
detailed information. This option lets you search your address book
by categories such as country or phone number when looking up
users during mail addressing.
4. Choose a background for the Business Cards in your address book.
You can scroll through the backgrounds by clicking the right and left
arrow buttons.
5. Choose a style for the Business Cards in your address book. You can
scroll through the styles by clicking the right and left arrow buttons.
Using calendar and scheduling features with Internet mail

In an environment that routes mail over Notes RPC and SMTP, the
Domino router automatically routes meeting invitations, appointments,
and other calendar and scheduling information over Notes RPC when
possible. When mail is routed over SMTP — for example, if you send a
meeting invitation to someone over the Internet — calendar and schedul-
ing items are converted to text messages. Notes RPC is required to use
the workflow features in Notes calendar and scheduling items.
Note Conversion of calendar and scheduling items to text when routing
over SMTP works the same way in Lotus Notes 6 as it did in Lotus Notes
4.6 and Lotus Notes 5.
4-18 Upgrade Guide

Chapter 5
Upgrading Notes Mail Files
This chapter tells you how to upgrade Notes mail file templates using the
mail conversion utility and seamless mail upgrade. It also describes how
to upgrade iNotes Web Access clients.
Upgrading Notes mail files

After upgrading to Lotus Notes 6, you can upgrade user mail file
templates to the Notes 6 design or to another mail template. You have
three options for upgrading mail file templates:
• Upgrade-by-mail upgrades both the Notes client and the Notes mail
file template.
For more information about Upgrade-by-mail, see the chapter
• The mail conversion utility upgrades mail file templates using the
mail convert task.
For more information about the mail conversion utility, see the topic
“Using the mail conversion utility” later in this chapter.
• Seamless mail upgrade automatically upgrades the mail file template
after users upgrade their Lotus Notes clients to Notes 6.
For more information about seamless mail upgrade, see the topic
“Using seamless mail upgrade” later in this chapter.
When you upgrade users’ mail files, you can specify any mail template,
including:
• Notes 6 mail file template (MAIL6.NTF)
• iNotes Web Access (R6.0) (iNotes60.ntf)
• A customized mail template
Note The iNotes Web Access (R6.0) template is supported by the Notes
6 client and the iNotes Web Access client.
The following table compares the mail conversion utility, Upgrade-by-
mail, and seamless mail upgrade.
5-1
Option Advantages Considerations
Mail • Administrators determine • You must ensure that
conversion when to upgrade mail file Notes clients are
utility templates upgraded before upgrad-
• Upgrade options available for ing mail file templates
upgrading one or more mail
files, mail files located in a
subdirectory, and so on
• Upgrades Notes 4.6 and Notes
5 mail file templates to the
Notes 6 design
Upgrade-by- • Upgrades Notes 4.6 and Notes • Requires users to have at
mail 5 mail file templates to the least Designer access to
Notes 6 design mail files for template
• Can be used to notify users upgrades
when mail files have been
migrated from cc:Mail, Micro-
soft Mail, Microsoft Exchange,
and Microsoft Outlook Express
Seamless mail • Can specify different mail file • Requires that users be
upgrade templates for different Lotus assigned to either a
Notes client versions policy or Setup Profile.
• Can also upgrade custom mail Users not assigned to one
folders or the other are not
upgraded.
• Does not require users to have
Designer access to mail • If seamless mail upgrade
databases fails, it prompts users to
upgrade their mail files
manually. Users can
ignore this prompt and
select the “Do not display
this message again”
option.
Tip You can use both Upgrade-by-mail and the mail conversion utility
to upgrade users. Use Upgrade-by-mail to notify users to upgrade their
Notes clients, but do not complete the mail file portion of the notification.
After users upgrade their Lotus Notes clients, use the mail conversion
utility to upgrade their mail file templates. This ensures that all clients
are upgraded to Notes 6 before you upgrade the Notes mail file template.
5-2 Upgrade Guide

Upgrading mail files with the mail conversion utility
When you upgrade users’ mail files to the Notes 6 mail template or to the
iNotes Web Access (R6.0) template, you can upgrade one file at a time or
use the mail conversion utility to automate upgrading the design. Be sure
that you have already upgraded the Domino server that hosts the mail
files and the Notes clients that access them to Domino 6, or users will not
be able to use the features in the new design. Upgrade mail files at a time
when users won’t be accessing them — for example, early mornings or
over a weekend. Notify users that their mail files will be unavailable
during the upgrade.
Note Before using the mail conversion utility, make sure that all clients
are upgraded to Lotus Notes 6.
To use the mail conversion utility

1. If users have customized their mail files, instruct them to back up
these customizations. For example, users can make a copy of their
mail file that includes only the database design. This allows users to
apply changes they made to their Notes 4.6 or Notes 5 mail file to the
new Notes 6 mail template, if necessary.
2. Start the Domino server on which you want to customize mail files.
3. Shut down the router. Enter:
tell router quit
and press ENTER to prevent Domino from routing mail to the mail
files while they are being upgraded. Mail is stored in MAIL.BOX
while you upgrade the mail files. After you upgrade the mail files
and load the router task again, the router processes and delivers the
mail in MAIL.BOX.
4. Load the mail conversion utility. Type:
load convert [arguments]
and press ENTER.
The mail conversion utility command uses arguments to specify
options. It has the form:
load convert [-r | -l | -f | -m | -e | -u | -s]
mailfilepath existingtemplatename newtemplatefilename
where -r converts mail files in subdirectories of the specified
directory, -l creates a text list of mail files, -f uses a text list of mail
databases to determine which mail files to upgrade, -m converts the
file or files for IMAP use in Notes 5, -e converts the file or files for
IMAP use in Notes 6, -u converts all custom folders to the Inbox
Upgrading Notes Mail Files 5-3

design, and -s upgrades folders created without the Preserve bit set.
Mailfilepath specifies which mail file or files to upgrade,
existingtemplatename specifies a certain mail file design (for example,
only mail files using Notes 5 design) to upgrade, and
newtemplatefilename specifies the template with which to upgrade the
mail files.
5. Once you have finished upgrading mail files to the Notes 6 template
on this server, load the router. Enter:
load router
and press ENTER.
6. Notify users that you upgraded their mail files to the Notes 6 design.
Mail conversion utility tasks

You can use the mail conversion utility to upgrade one or more mail
databases. The following table describes the tasks that the mail conver-
sion utility can perform.
Task Description
Upgrading a single This example finds the mail database USER.NSF in the
mail database \MAIL subdirectory of the Notes data directory. The mail
conversion utility replaces the current mail template —
regardless of which template the mail file uses — with
MAIL6.NTF, the Notes 6 mail template.
load convert mail\user.nsf * mail6.ntf
Upgrading all mail This example finds all databases located in the \MAIL
databases in a subdirectory of the Notes data directory that use
directory StdR46Mail, the Notes 4.6 mail template, and replaces
their design template with StdR60Mail (MAIL6.NTF), the
Notes 6 mail template.
load convert mail\*.nsf stdr46mail
mail6.ntf
Upgrading all mail This example finds all databases located in the \MAIL
databases in a subdirectory of the Notes data directory and all
directory and in its subdirectories of the \MAIL directory (for example,
subdirectories C:\NOTES\DATA\MAIL\GROUP1,
C:\NOTES\DATA\MAIL\GROUP2, and
C:\NOTES\DATA\MAIL\GROUP3) and upgrades them
to the Notes 6 mail template, MAIL6.NTF.
load convert -r mail\*.nsf * mail6.ntf
continued
5-4 Upgrade Guide

Task Description
Upgrading all mail You can create a text file listing databases you want to
databases listed in a upgrade and use it with the mail conversion utility to
text file upgrade only those databases. For example, you can
create the text file MAILLIST.TXT to list all the mail
databases you want to upgrade and save it in the
directory C:\TEMP. This example finds all databases
listed in MAILLIST.TXT, determines whether the
databases use a design template name that matches STD*
(StdR46Mail, for example), and replaces the designs of
the matching databases with StdR60Mail (MAIL6.NTF),
the Notes 6 mail template.
load convert -f c:\temp\maillist.txt std*
mail6.ntf
Creating a text file You can use the mail conversion utility to create a text file
that lists all mail that lists all primary mail databases on the server (it does
databases in a not list replica mail databases). This example creates a
directory text file, MAILLIST.TXT, in the C:\TEMP directory.
MAILLIST.TXT contains a list of primary mail databases
on the server but excludes replica mail databases. After
you create the text file using this option, you can use the
file to upgrade the mail databases listed in it. See
“Upgrading all mail databases listed in a text file” in this
table.
load convert -l c:\temp\maillist.txt
Converting mail If you use a Notes 5 mail file with IMAP, run the mail
files for use with conversion utility to enable IMAP-specific features in the
IMAP in Notes 5 mail file. This example readies the mail database
USER.NSF in the \MAIL subdirectory of the Notes data
directory for use with IMAP.
load convert -m mail\user.nsf
Converting mail If you use a Notes 6 mail file with IMAP, run the mail
files for use with conversion utility to enable IMAP-specific features in the
IMAP in Notes 6 mail file. This example readies the mail database
USER.NSF in the \MAIL subdirectory of the Notes data
directory for use with IMAP.
load convert -e mail\user.nsf
Upgrading custom You can use the mail conversion utility to upgrade
folder design custom folder design to the Inbox design. This example
upgrades the custom folder design of all mail databases
in the \Mail subdirectory of the Notes data directory to
the Inbox design.
load convert -u mail\*
continued

Task Description
Upgrading folder Do not use the -s argument with the mail conversion
design of folders utility when upgrading mail files from the Notes 4.6
without the design to the Notes 6 design. The -s argument ignores
Preserve bit any folder or view with the Preserve bit deselected. This
bit corresponds to the “Do not allow refresh/replace to
modify” option in the design properties. System folders
and other design elements from the original template
used to create the mail file do not have this bit set, even if
the database is set to inherit from design. System folders,
such as the Inbox, are not updated if you run the mail
conversion utility with the -s argument. This affects mail
files being upgraded to Lotus Notes 6 because required
script libraries have been removed and action buttons
have been upgraded.
load convert -s mail\*
Note When you use a wildcard character, such as an asterisk (*), to

specify which files to upgrade to the Notes 6 mail template, be sure that
all databases in the directory (and, if specified, subdirectories) are mail
files. When you use a wildcard character, Lotus Domino replaces the
design of all databases specified by the wildcard character with the
specified template, such as the Notes 6 mail template. If you replace the
design of a non-mail database with the Notes 6 mail template by mistake,
you can use the mail conversion utility by to restore the original design
and then specify the correct template.
Using seamless mail upgrade

Seamless mail upgrade automatically upgrades mail file templates after
users upgrade their Lotus Notes clients to Notes 6. When users first start
the Lotus Notes client after upgrading, Lotus Notes begins upgrading the
design of local databases like the Personal Address Book. At this time,
the client also sends a call to the users’ home server to upgrade the mail
file template.
The server looks for an assigned Desktop policy settings document or
Setup Profile document for the users. If one is found and the Mail
Template Information section is complete, then seamless mail upgrade
starts the mail conversion utility to upgrade the template.
Setting up seamless mail upgrade

When the Domino server receives the call to upgrade a mail file template,
the server checks for a Desktop policy settings document or Setup Profile
assigned to the user. The Desktop policy settings document and the
5-6 Upgrade Guide

Setup Profile contain a “Mail Template Information” section. This section
is new to Setup Profiles in Notes 6. In this section, you can specify which
mail file template to apply according to the Lotus Notes client version.
To set up seamless mail upgrade in the Desktop policy settings

document
1. In the Domino Administrator, open the Settings view on the People
and Groups tab.
2. If you are creating a Desktop policy settings document, click Add
Settings, then choose Setup. If you are modifying a desktop settings
document, select the document, then click Edit Settings.
For more information about creating a Desktop policy settings
document, see the book Administering the Domino System.
3. Under the Mail template information heading, complete the fields
described in the following table.
Prompt user before Select the check box to inform users before
upgrading mail file upgrading their mail files. If prompted, users can
choose to defer the template upgrade.
Old design template Enter the name of the mail template that you want
name for your mail to upgrade. For instance, if you want to upgrade the
files Lotus Notes 5 mail template, enter MAIL50.NTF. If
you are upgrading users with different templates,
specify an asterisk (*).
New mail template Enter or select the name of the mail file template to
file name apply. The standard Notes 6 mail file template
name is MAIL6.NTF. If you do not want to
implement seamless mail upgrade, do not complete
this field.
Ignore 200 category Select this option to override the default that limits
limit the creation of folders in a database to 200.
Mail file to be used Select this option if you are upgrading IMAP mail
by IMAP mail clients clients.
Upgrade the design Select this check box to upgrade the design of
of custom folders custom folders to the Inbox design.
Prompt before Select this check box to inform users before
upgrading folder upgrading their mail folder design. If prompted,
design users can choose to defer the folder upgrade.
Notify these Enter the names of administrators who must be
administrators of notified of the upgrade.
mail upgrade status

5. If you have not already done so, create a master policy and associate
the Desktop policy settings document to the policy. Then, assign
users and groups to the master policy.
For more information about creating and assigning policies, see the
To set mail template information in the Setup Profiles

1. In the Domino Administrator, choose View - Server - Other.
2. In the Other dialog box, select Server\Setup Profiles, then click OK.
3. Select the Setup Profile you want to modify, then click Edit Setup
Profile.
4. Under the Mail template information heading, complete the fields in
the previous table.
Lotus Notes 6 mail files and mixed-release environments

If you have a mail file on a Domino 6 server with a Notes 6 template and
a replica of that file on a Domino 4.6 or Domino 5 server that uses a
template from an earlier release, you must ensure that the designs of the
mail files do not replicate. A mail file with a Notes 6 design on a Domino
4.6 or Domino 5 server does not work properly, and you want to ensure
that the older Notes 4.6 design does not overwrite the Notes 6 design on
the Domino 6 server. To prevent the mail templates of the two replicas
from replicating, do the following for each mail file:
1. Open the mail file replica.
2. Choose File - Replication - Settings.
3. Click the Advanced tab.
4. Under “Replicate incoming,” clear the “Forms, views, etc.” and
“Agents” check boxes.
5. Click OK.
6. Repeat Steps 1 to 5 for each replica.
Note This procedure does not work for clustered servers and databases
because cluster replication ignores selective replication.
Lotus Notes 6 mail file template interoperability

The following table describes Lotus Notes client version and mail file
template interoperability.
5-8 Upgrade Guide

Notes client Notes 4.6 mail Notes 5 mail template Notes 6 mail template
release template
Notes 4.6 Fully Functional with the Functional with the
functional following exceptions: following exceptions:
• Can only display • Can only display 30-day
30-day calendar calendar view
view • Releases prior to 4.6.4*
• Releases prior to may experience errors
4.6.4* may experi- upon opening and
ence errors upon closing the mail database
opening and
closing the mail
database
Notes 5 Fully Fully functional Functional with the
functional following exceptions:
• Support for mail and To
Do functionality avail-
able in Lotus Notes 5;
does not support new
Notes 6 mail and To Do
functionality
• Users can view calendar
entries, but cannot delete,
edit, or act upon them
• Display calendar views
supported in Lotus Notes
5; cannot display new
Notes 6 calendar views
• No support for soft
deletions
• No access to preferences
Notes 6 Fully Fully functional Fully functional
functional
*Lotus Notes 4.6.4 is the minimum Notes client release for compatibility.
Upgrading iNotes Web Access clients

The same options available for upgrading the Notes mail file template
are also available for upgrading the iNotes Web Access client. To
upgrade iNotes Web Access clients, use either Upgrade-by-mail or the
mail conversion utility to apply the iNotes template to users’ mail files.
For more information about Upgrade-by-mail, see the chapter

“Upgrading mail files with the mail conversion utility” earlier in this
chapter.
Lotus Notes/Domino 6 provides an iNotes Web Access (R6.0) template
(iNotes60.ntf) that supports both Notes 5 and Notes 6 mail files. The
template supports the Notes client, iNotes Web Access client, and
WebMail.
Upgrading from a custom template to an iNotes Web Access

template
If your organization uses a customized mail template, do the following to
upgrade to iNotes Web Access:
1. Back up the custom mail template.
2. Create replicas of the mail file databases on a Domino 6 server that
does not use the custom template.
3. Disable design replication on those files to prevent overwriting of the
customized design template.
4. Replace the design of the new mail replicas using the mail
conversion utility.
Note The iNotes Web Access client cannot be customized. Also, do not
apply the iNotes60.ntf template to a Notes 5.0.7 or earlier mail file. The
mail file may not work properly.
Upgrading to the Notes 6 folder design

You have two options for upgrading to the Notes 6 folder design:
• Specify the -u argument for the mail conversion utility
• Use the Upgrade Folder Design agent
If you do not use the -u argument with the mail conversion utility when
you upgrade mail files with the Notes 6 mail template (MAIL6.NTF), the
new folder design is not applied to existing folders because folders are
not part of the template design.
“Upgrading mail files with the mail conversion utility” earlier in this
chapter.
The Upgrade Folder Design agent is available in the Notes 6 mail
template (MAIL6.NTF). With the agent, you can choose to upgrade one
or more shared or private folders to the following standard folder
5-10 Upgrade Guide

designs: Inbox, Alarms, Trash, Rules, or Calendar. Users can upgrade
their folder design following this procedure:
1. From the Lotus Notes 6 client, open the mail file database.
2. Choose Actions - Upgrade Folder Design.
3. Do one of the following:
• To upgrade all your folders at once to a single default folder
design, click Automatic Upgrade.
• To upgrade folders individually, click Manual Upgrade. Select a
folder design, like Inbox, then select the folders to upgrade to that
design. Click OK. Repeat as necessary.
Note If you created folders using another style, such as Calendar, and
upgrade the folder to another design, like Inbox, you will lose
functionality provided by that original folder style.

Chapter 6
Upgrading Databases and Applications
After upgrading your Domino servers and Notes clients, upgrade your
databases and applications.
Upgrading databases and applications

Lotus Notes/Domino 4.6 and Lotus Notes/Domino 5 applications
created with system templates that ship with Lotus Notes/Domino run
without modification on a Domino 6 server and with the new database
format or On-Disk Structure (ODS). Any known incompatibility issues
are documented in this guide and in the Release Notes. Test your applica-
tions on a Domino 6 server before deploying them. If you encounter a
problem or incompatibility that is not documented, you can check the
IBM Lotus knowledge base at
http://www.ibm.com/software/lotus/support.
Upgrading databases and applications includes compacting the
databases to upgrade the database format and upgrading database
templates. When you upgrade to Lotus Notes/Domino 6 templates and
features, be aware that Notes 4.6 and Notes 5 clients cannot use these
features. Using Lotus Notes/Domino 6 templates and features in a
mixed-release environment can cause complications by preventing some
clients (those running earlier releases of Notes) from using the full
functionality of the application.
Lotus internal testing, and testing done in conjunction with ISV partners,
demonstrates that upgrade concerns and issues for applications are
generally minor or nonexistent. However, each application is different.
Test all mission-critical, revenue-generating, or complex applications on
Lotus Notes/Domino 6 before deploying them.
There are three choices for upgrading databases and applications in the
Lotus Notes/Domino 6 environment:
1. Upgrade an application server to Lotus Domino 6, but leave
databases in Domino 4.6 or Domino 5 format.
All clients can access the databases.
6-1
2. Upgrade the server and database format to Domino 6, but leave the
database design and features at Domino 4.6 or Domino 5.
All clients can access the databases. Compact the database to the new
database format.
3. Upgrade the server, database format, database design, and database
features to Domino 6.
Notes 4.6 and Notes 5 clients cannot use the Notes 6 features. You
may need to make changes to the application to use new features.
Compact the database to the new database format, upgrade to the
Notes 6 design, and add new Notes 6 features as wanted.
Upgrading databases to Lotus Notes/Domino 6

After upgrading a server to Lotus Domino 6, you can upgrade the
databases on that server to the Domino 6 database format and design
(template). These two steps — upgrading database format and upgrad-
ing database design — are independent of each other. Because database
format does not replicate, you can leave the design of a database based
on an Domino 4.6 or Domino 5 template and upgrade the database
format on that server to the Domino 6 format. If you decide to upgrade
the database design to use Domino 6 templates and features, be aware
that Notes 4.6 and Notes 5 clients cannot use Notes/Domino 6 features.
Some Domino 6 features and templates require that a database use the
Domino 6 database format.
Before upgrading database format to Domino 6

• Upgrade the application server to Lotus Domino 6 (necessary to
allow the server to host Domino 6 databases and use Domino 6-style
compaction)
• Run Fixup on databases — to prevent most errors that interfere with
compaction to the new database format
After upgrading database format to Domino 6

• Consider running Updall -r on the database — to rebuild views in
the database and to prevent delay when users first try to access it.
This task is especially important for databases that are used
frequently, are mission-critical, or have large views.
6-2 Upgrade Guide

Upgrading database format
After you install Lotus Domino 6 on a server, you can upgrade the
format of databases on that server. The database format determines
which features are available in a database. Some Domino 6 features, such
as LZ1 compression and view logging, require the Domino 6 database
format.
When you compact a database, the database format is upgraded. Domino
6 databases are theoretically unlimited in size. Lotus has tested and certi-
fied databases up to 64GB.
If you do not want to upgrade database format, you have three options:
• Use the -R option with the Compact command to keep a database in
Domino 4.6 or Domino 5 format or to roll its format back to Domino
5 database format.
• Make a database copy or replica and rename the file extension to
NS4 for Domino 4.6 applications or NS5 for Domino 5 applications.
• Do not run the compact task.
To check a database’s ODS version, open the Info tab of the Database
Properties box. The following table lists the ODS version and Lotus
Notes/Domino releases.
ODS version Lotus Notes/Domino release

ODS43 Release 6
ODS41 Release 5
ODS21 Release 4.6
Compacting a database to Domino 6 format from the Domino

Administrator
1. Make sure the server hosting the database has been upgraded to
Lotus Domino 6.
3. Click the Files tab.
4. Select the database(s) to compact to Domino 6 ODS.
5. In the Tools pane at the right, select Database - Compact.
6. Click OK.
Compacting a database to Domino 6 format from the server console

1. Upgrade the application server to Lotus Domino 6.
2. Start the upgraded server.
Upgrading Databases and Applications 6-3

3. Enter the following command:
load compact databaseName.nsf
and press ENTER, where databaseName.nsf is the file name of the
database you want to compact to Domino 6 format.
You can also use an indirect file to list databases that you want to
compact from the Domino server console.
For more information about the indirect file, see the topic “Compacting
databases, rebuilding views, and fixing corrupt databases with an
indirect file” later in this chapter.
Compacting databases from a Notes client

If a user compacts a database from a Notes client (for example, from the
Info tab of the Database Properties box), the server compacts the
database for the client. A Domino 6 server compacts the database using
Domino 6 compaction and a Domino 4.6 or Domino 5 server compacts
the database using Domino 4.6 or Domino 5 compaction respectively. It
is possible for Notes users to compact a Domino 4.6 or Domino 5
database on a Domino 6 server to the new database format. To prevent
this, rename Domino 4.6 or Domino 5 databases using the NS4 or NS5
extension.
Keeping a new database in Domino 4.6 or Domino 5 format

Any Notes client can access a database hosted on a Domino server,
regardless of the client or server release or the database format.
However, Notes clients cannot access or use database features from later
releases; for example, a Notes 5 client can access a Domino 6 database on
a Domino server, but it cannot access or use the Domino 6 features in that
database.
If a database is stored on the local drive of a client, only clients of the
same release and later can access it. For example, a database in Domino 5
format can be accessed locally by a Notes 5 or Notes 6 client, but not by a
Notes 4.6 client.
Domino servers can only host applications in their release format and
earlier formats. For example, a Domino 5 server can host a Domino 5 or
Domino 4.6 database, but not a Domino 6 database.
To create an application that can be accessed locally by Notes 4.6 or
Notes 5 clients and stored on Domino 4.6 or Domino 5 servers, give it the
extension NS4 or NS5 in the File name field when you create the data-
base. To keep a database in Domino 4.6 or Domino 5 format so it can be
accessed locally by Notes 4.6 or Notes 5 clients or stored on a Domino 4.6
or Domino 5 server, change the database’s extension to NS4 or NS5 at the
6-4 Upgrade Guide

operating system level before compacting to the Domino 6 format, or
create a new replica of the database and use the extension NS4 or NS5.
Note If a Notes 6 client compacts a local replica of a Domino 4.6 or
Domino 5 database, the database format changes to the Domino 6
database format and cannot be accessed locally by Notes 4.6 or Notes 5
clients.
Creating a replica of a database in Domino 4.6 or Domino 5 format

2. Select the database for which you want a Domino 4.6 or Domino 5
replica.
3. Click Open.
4. Choose File - Replication - New Replica.
5. In the File name field, give the new replica the extension NS4 or NS5.
6. Click OK.
Rolling back databases to Domino 5 database format

After you upgrade an application or database, you can change its format
to an earlier format by using Compact -R, compacting from the Domino
Administrator, or by creating a replica or copy of the database in Domino
4.6 or Domino 5 format. Notes 4.6 and Notes 5 clients can access
databases on Domino 6 servers, but you cannot use a Domino 6 database
on a Domino server running an earlier release of the software.
The Domino 6 database format does not replicate, and Domino 4.6 and
Domino 5 servers ignore Domino 6 features, so you can safely replicate a
database replica that has been upgraded to Domino 6 database format
with a replica that has not been upgraded.
Rolling back a Domino 6 database to Domino 5 format from the

Domino Administrator
2. Click the Files tab.
3. Select the database(s) to roll back to the Domino 5 format.
4. In the Tools pane at the right, choose Database - Compact.
5. Select “Keep or revert database back to R5 format.”
6. Click OK.
Rolling back a Domino 6 database to Domino 5 format from the

server console
1. Change to the Domino server console.

2. Enter the following command:
load compact databaseName.nsf -R
and press ENTER, where databaseName.nsf is the file name of the
database you want to roll back to Domino 5 format.
Domino compacts the database back to Domino 5 format.
Rolling back a Domino 6 database to Domino 4.6 or Domino 5

format by creating a replica
1. Start the Notes 6 client.
3. In the Server field, type the name of the server that hosts the
database you want to roll back and click Open.
4. Navigate to and select the database you want to roll back and click
Open.
5. Choose File - Replication - New Replica.
6. In the File name field, change the database extension from NSF to
NS4 or NS5.
7. Click OK.
The new replica will be in Domino 4.6 or Domino 5 format and can be
placed on any server running Domino 4.6 or later and accessed locally by
any Notes 4.6 or later client.
Rebuilding views
In Lotus Notes and Lotus Domino 6, users may experience a delay when
accessing upgraded databases for the first time. This delay occurs
because all database views rebuild on initial access due to the updated
View version in this release. To prevent this delay, run Updall -r on the
database to rebuild the views.
Note You can use an indirect file to specify databases for the Updall
task.
Compacting databases, rebuilding views, and fixing corrupt

databases with an indirect file
You can use an indirect file to specify one or more databases to compact,
to rebuild views, or to fix corrupted views and documents. An indirect
file is a text file that lists database file names or directory names and that
you can specify for the compact, updall, or fixup task on the Domino
console command line. The indirect file allows you to specify more than
one database on the command line.
6-6 Upgrade Guide

To create the indirect file
1. Use a text editor, such as Notepad, to create the text file.
2. List the files names of the databases in the Data directory that you
want to fixup, compact, or rebuild. If the databases reside in a
subdirectory of the Data directory, specify the directory and the
database file name. If you want to fixup, compact, or rebuild all
databases in a subdirectory, specify only the directory name.
3. Save the file with the file extension IND.
To specify the indirect file for the fixup, compact, or updall task
1. At the Domino server console, enter one of the following commands
and the indirect file name:
• To run fixup, enter:
load fixup filename.ind
Note On a Windows NT system, enter nfixup.exe filename.ind.
• To run updall, enter:
load updall filename.ind
• To run compact, enter:
load compact filename.ind
Upgrading system templates

Lotus Domino automatically upgrades many system templates to
Domino 6 design.
Databases and templates upgraded automatically

This table lists the Release 4.6 and Release 5 database templates that
Lotus Domino 6 upgrades automatically after set up.
Database title File name

Administration Requests ADMIN4.NTF
Agent Log ALOG4.NTF
Archive Log ARCHLG50.NTF
Billing BILLING.NTF
Bookmarks BOOKMARK.NTF
Catalog CATALOG.NTF
Certification Log CERTLOG.NTF
Cluster Directory CLDBDIR4.NTF
Database Analysis DBA4.NTF
continued

DOLS Resource Template DOLRES.NTF
DOLS Offline Services DOLADMIN.NTF
Domino Configuration DOMCFG.NTF
Domino Web Server Log DOMLOG.NTF
Local free time info BUSYTIME.NTF
<Server> Mailbox MAIL.BOX
Mail Router Mailbox MAILBOX.NTF
Master Address Book (to Directory MAB.NTF (DA50.NTF)
Assistance)
Monitoring Configuration (formerly EVENTS4.NTF
Statistics & Events)
Notes Log Analysis LOGA4.NTF
Notes Log LOG.NTF
NT/Migrating Users’ Passwords NTSYNC45.NTF
Personal Address Book PERNAMES.NTF
Personal Journal JOURNAL6.NTF
Public Address Book (to Domino Directory) PUBNAMES.NTF
Server Web Navigator PUBWEB45.NTF
(PUBWEB50.NTF)
Subscriptions HEADLINE.NTF
Databases not upgraded automatically

This table lists database templates which you must manually upgrade.

Certificate Authority CCA*.NTF (* = Release Number; for
example, 50)
Domino Web Administration WEBADMIN.NTF
Extended Mail (R5) MAIL5EX.NTF
Mail (R5) MAIL5.NTF
Monitoring Results (formerly STATREP.NTF
Statistics Reporting)
Server Certificate Admin CSRV*.NTF (* = Release Number; for
example, 50)
TeamRoom (R5) TEAMRM5.NTF
6-8 Upgrade Guide

Templates in a mixed-release environment
Notes 4.6 and Notes 5 clients can render some system databases that use
Domino 6 templates. Some Domino 6 templates, though, do not render
well to Notes 4.6 or Notes 5 clients. Templates fall into three categories:
those that are supported with the Notes 4.6 or Notes 5 client, those that
are supported but have altered appearance (that is, the templates are
functional, but do not appear as they would in a Notes 6 client), and
those that should not be used in a mixed environment.
Templates supported by the Notes 4.6 and Notes 5 client

This table lists Domino 6 templates supported by the Notes 4.6 and Notes
5 client.

Agent Log ALOG4.NTF
Billing BILLING.NTF
Certification Log CERTLOG.NTF
Cluster Analysis (6) CLUSTA4.NTF
Database Library DBLIB4.NTF
Doc Library - Notes & Web (R6) DOCLBW6.NTF
Domino Certificate Authority (6) CCA50.NTF
Domino Configuration DOMCFG.NTF
Domino Web Server Log (6) DOMLOG.NTF
Local free time info BUSYTIME.NTF
Mail Router Mailbox (6) MAILBOX.NTF
Mailing List MAILLIST.NTF
Microsoft Office Library (6) DOCLBM6.NTF
Monitoring Results (6) (formerly STATREP5.NTF
Statistics Reporting)
Notes Log LOG.NTF
NT/Migrating Users’ Passwords NTSYNC45.NTF
Personal Web Navigator (6) PERWEB50.NTF
Reports REPORTS.NTF
Resource Reservations (6) RESRC60.NTF
Server Web Navigator PUBWEB50.NTF
Site Registration SIREGW50.NTF

Templates supported by the Notes 5.0 client
This table lists Domino 6 templates that are supported by a Notes 5.0
client.

Extended Mail (R6) MAIL6EX.NTF
iNotes Web Access (R6.0) (formerly INOTES60.NTF
iNotes Mail and C&S)
Mail (R6) MAIL6.NTF
Templates supported with altered appearance by the Notes 4.6

client
This table lists Domino 6 templates that appear altered in the Notes 4.6
client; however, the template continues to function.

Catalog (6) CATALOG6.NTF
Cluster Directory (6) CLDBDIR4.6.NTF
Database Analysis DBA4.NTF
Decommission Server Reports DECOMSRV.NTF
DECS Administrator Template (partial DECSADM.NTF
support)
Directory Assistance (6) DA50.NTF
Domino Directory PUBNAMES.NTF
Monitoring Configuration (6) (formerly EVENTS4.NTF
Statistics & Events)
Notes Log Analysis (6) LOGA4.NTF
Templates that are not supported by the Notes 4.6 client

This table lists Domino 6 templates that are not supported by the Notes
4.6 client.

Archive Log (6) ARCHLG50.NTF
Bookmarks (6) BOOKMARK.NTF
Design Synopsis DSGNSYN.NTF
Directory Catalog DIRCAT5.NTF
Domino 5 Certificate Administration CSRV50.NTF
Domino Administrator (6) DOMADMIN.NTF
continued
6-10 Upgrade Guide

Domino MailTracker Store (6) MTSTORE.NTF
iNotes Mail and C&S INOTES5.NTF
Mail (IMAP) IMAPCL5.NTF
News Articles (6) NNTPCL5.NTF
Subscriptions (6) HEADLINE.NTF
TeamRoom (6) TEAMRM6.NTF
User Registration Queue (6) USERREG.NTF
Web Administration WEBADMIN.NTF
Templates that are not supported by the Notes 5.0 client

This table lists Domino 6 templates that are not supported by the Notes
5.0 client.

Bookmarks (6) BOOKMARK.NTF
Subscriptions (6) HEADLINE.NTF
TeamRoom (6) TEAMRM6.NTF
Upgrading Domino Off-Line Services (DOLS) subscriptions

To upgrade a DOLS environment, the administrator must upgrade all
DOLS-enabled online subscriptions (on the server), then users must
update their iNotes Sync Manager software and the existing off-line
subscriptions (on their computer).
To upgrade online subscriptions

Administrators must do the following to upgrade online subscriptions.
1. Upgrade the host server to Domino 6. DOLRES.NTF is automatically
upgraded.
2. Open each DOLS subscription, choose File - Database - Properties,
and click the Design tab.
3. Check “Inherit design from template.” In the “Template name” field,
enter DOLRES.NTF.
4. Run the Design Task. The DOLS design elements in the subscription
NSFs are upgraded.

To upgrade the iNotes Sync Manager and off-line subscriptions
Users must do the following to upgrade the iNotes Sync Manager and
off-line subscriptions.
1. Netscape users must delete the file
netscape\communicator\program\plugins\npdolctl.dll.
2. Install a new subscription from the upgraded server. This
automatically upgrades the iNotes Sync Manager.
3. Synchronize each off-line subscription to upgrade its design.
For more information about DOLS, see the book Administering the Domino
System.
Application design changes since Lotus Notes/Domino 4.6

The following topics describe application design changes introduced in
Lotus Notes/Domino 5. These changes are applicable to Notes/Domino
4.6 applications that you upgrade to Notes/Domino 6.
• Allowing more database fields in a mixed-release environment
• Changes in case-sensitive and accent-sensitive sorting of characters
• Managing databases with the Domain Catalog
• Upgrading Domino 4.6 applications and Lotus Domino 6
requirements
• Upgrading Domino 4.6 document libraries
• Upgrading Domino 4.6 TeamRoom templates
• Upgrading Domino 4.6 Web applications
• Upgrading the statistics mail-in database name
• Using default Web templates with older browsers
Allowing more database fields in a mixed-release environment

You can increase the number of database fields by selecting the “Allow
more fields in database” option on the Advanced tab of the Database
Properties box. This option allows up to 23,000 fields. Databases in
Domino 4.6 format and databases that do not have this option enabled
can have up to 3000 fields (where the total length of the concatenated
field names is less than 64KB).
Enabling “Allow more fields in database” increases the number of fields
allowed in a database, but keeps some features, such as full-text
indexing, searching by form, and populating the field list in the Design
6-12 Upgrade Guide

pane of Lotus Domino Designer, from working. Also, you cannot create a
replica of a database that has this option enabled on a Domino 4.6 server.
Changes in case-sensitive and accent-sensitive sorting of

characters
In Lotus Notes/Domino 4.6, when creating a column in a view, you can
select to have the column use case-sensitive sorting, accent-sensitive
sorting, or both. Those options remain in Lotus Notes/Domino 6, but
they control different functionality.
If you view the same application from a Notes 4.6 client and from a
Notes 6 client, the two property selections produce different results. For
example, if you have selected both sensitivity settings in Lotus Notes 4.6,
upgrade the database to Domino 6, and inspect the settings from a Notes
6 client, the settings are off or deselected. If you check the properties
from a Notes 4.6 client, the Notes 4.6 settings are still selected and are
displayed.
Because views do not replicate between Lotus Notes/Domino 4.6 and
Lotus Notes/Domino 6, there are no issues when replicating between a
Domino 4.6 replica and a Domino 6 replica that have the properties set
differently. However, view notes do replicate, so view notes for this view
may contain four settings: case-sensitive for Domino 4.6, case-sensitive
for Domino 6, accent-sensitive for Domino 4.6, and accent-sensitive for
Domino 6.
In Lotus Notes/Domino 4.6, case-sensitive and accent-sensitive settings
were not used unless two entries in a column were composed of the same
string (except for case or accent). Then, the view compared the case and
accents of the two entries to determine sort order. For example, in Lotus
Notes/Domino 4.6 with accent-sensitive sorting, “äa” sorts before “ab.”
In Lotus Notes 6, “ab” sorts before “äa.” In Lotus Notes/Domino 4.6
with case-sensitive sorting, “Aa” sorts before “ab.” In Lotus Notes/
Domino 6, “ab” sorts before “Aa.” In Lotus Notes/Domino 6 case-
sensitive sorting, Lotus Domino checks the first letter and sorts
lowercase before uppercase letters.
If you have a view that uses case-sensitive or accent-sensitive sorting in
Lotus Notes/Domino 4.6, upgrade it to Lotus Notes/Domino 6, and turn
on the same settings in Lotus Notes/Domino 6, the view may sort
differently.
In Lotus Notes/Domino 4.6, case-sensitive and accent-sensitive sorting
are on by default. In Lotus Notes/Domino 6, case-sensitive and accent-
sensitive sorting are off by default. Having Lotus Notes/Domino 6
sorting off by default provides the least disruption to applications and
databases when upgrading.

Managing databases with the Domain Catalog
The Domain Catalog replaced the database catalog in Lotus Domino 5.
Database managers accustomed to using the Domino 4.6 database
catalog to find replicas of their databases must use the Domain Catalog
in Lotus Domino 6.
For more information about Domain Catalogs and how to create one, see
Upgrading Domino 4.6 applications and Lotus Domino 6

requirements
After you upgrade an application server and its applications to Lotus
Domino 6, be sure to do the following:
• Specify a drive with sufficient disk space for view rebuilds by setting
the View_Rebuild_Dir setting in the NOTES.INI file to that drive. By
default, this variable is set to the temp directory on the system. This
drive holds the temporary files used to rebuild views; a larger disk
allows faster rebuilds and greater optimization. View rebuilds can be
as much as five times faster in Lotus Domino 6 than in Lotus Domino
4.6. The size of the drive needed for view rebuilds depends on the
size of the views you are rebuilding.
• Use a separate, single-purpose disk to hold the log files for
transaction logging. The default location for these files is the
LOGDIR directory in the server’s data directory. A separate disk
allows faster writes to the log. The log requires at least 200MB of disk
space and can be set as large as 4GB; use a separate disk of at least
1GB. A dedicated mirrored drive is even better than a single disk for
data recovery if the log disk fails.
• Use a third-party backup utility that supports Lotus Notes/Domino
6 and transaction logging to provide maximum data recovery in case
of errors or data corruption. With the backup utility, you can per-
form daily incremental backups and archives of the transaction log.
Upgrading Domino 4.6 document libraries

When you replace a Domino 4.6 document library design with a Domino
6 template (Doc Library - Notes & Web), run the “Upgrade Doclib R4.6
Documents to New Design” agent in the database before opening any of
the converted documents.
1. Open the upgraded database.
2. Choose Actions - Upgrade Doclib R4.6 Documents to New Design.
6-14 Upgrade Guide

If you do not run this agent, you receive an error message when you
attempt to open a document, and views do not correctly display
document status.
Upgrading Domino 4.6 TeamRoom templates

Domino 6 does not support the Domino 4.6 TeamRoom templates.
Upgrade the TeamRoom templates to Domino 5 or later. Follow these
steps to replace the design of the Domino 4.6 TeamRoom templates.
1. Open the Domino 4.6 TeamRoom database.
2. Choose File - Database - Replace design.
3. In the Replace Database Design dialog box, select TeamRoom (5.0) or
TeamRoom (6), then click Replace.
4. Close and reopen the database.
Upgrading Domino 4.6 Web applications

Lotus Domino 4.6.5 automatically hid Web applications with unsup-
ported formulas. In Lotus Domino 6, if you select the “Use JavaScript”
property in the Database Properties box, Domino doesn’t check hotspot
or button formulas before using JavaScript to generate the page. Web
users see all buttons, actions, and hotspots — even those that contain
@commands and @functions that aren’t supported for Web applications.
To avoid this problem, do the following:
• Rewrite any formulas that relied on hotspot formulas being
evaluated at display time. Test your Web applications to make sure
these formulas evaluate correctly after the user clicks the hotspot, not
before.
• Replace Lotus Domino 4.6.5 attachment fields with Web Element -
File Upload Controls if you set the “Use JavaScript” property. The
“Use JavaScript” property disables
@Command([EditInsertFileAttachment]) hotspots used to create
attachment fields in Lotus Notes/Domino 4.6.5, because the hotspot
is not evaluated when the page is displayed.
• Rewrite any formulas that rely on accessing a Query_String or
Path_Info URL fragment. The “Use JavaScript” property can cause
unexpected results because the URL generation in Lotus
Notes/Domino 6 is different from Lotus Notes/Domino 4.6.5 URL
generation. POST URLs that included ?CreateDocument and
?SaveDocument are no longer generated in Lotus Notes/Domino 6.
The new POST URL is a variation of ?OpenForm or ?EditDocument.

Upgrading the statistics mail-in database name
In Lotus Domino 5, the statistics mail-in database name format changed
from “ServerName/Org/OU Stats” to “servername Stat/Org.” When
you upgrade from Lotus Domino 4.6 to Lotus Domino 6, the upgrade
process does not update the statistics mail-in database name. You must
rename the database using the new name format. The statistics mail-in
database name must meet the following requirements:
• The mail-in database name must follow the “servername Stat/Org”
format in which you provide the server name and organization name.
• The mail-in database file name must be STATMAIL.NSF.
• In the Mail-in database document, you must specify the updated
database name in the Fullname field, STATMAIL.NSF in the Mailfile
field, and the server name in the Mailserver field.
For more information about the statistics mail-in database, see the book
Using default Web templates with older browsers

The default Web templates that ship with Lotus Notes/Domino 6 are
not supported on browsers that do not conform to the JavaScript 1.1
standard. If a browser that does not conform to JavaScript 1.1 attempts to
access one of the default Domino 6 Web templates, the template displays
an error message. Lotus Notes/Domino 6 includes special Web templates
designed to work with non-compliant browsers.
Web applications function as expected when accessed with browsers that
do not comply with the JavaScript 1.1 standard as long as the application
does not use JavaScript features not supported by these browsers. This is
a limitation with the browsers and not with the templates or applications.
Lotus Domino applications support all browsers, but some of the tools
that you can use with Lotus Domino (for example, JavaScript) are not
supported by all browsers.
The following table lists the operating systems that support JavaScript
1.1-compliant browsers.
Operating system Web browser

Windows XP Professional Microsoft Internet Explorer 5.5 and 6.0; Netscape
Navigator 4.7x
Windows 2000 Microsoft Internet Explorer 5.5 and 6.0; Netscape
Navigator 4.7x
continued
6-16 Upgrade Guide

Operating system Web browser
Windows NT 4.0 Microsoft Internet Explorer 5.0, 5.5 and 6.0;
Netscape Navigator 4.7x
Windows 98 Microsoft Internet Explorer 5.0, 5.5 and 6.0;
Netscape Navigator 4.7x
Linux Netscape Navigator 4.7x
Solaris Netscape Navigator 4.7x
OS/2 Warp Netscape Navigator 4.7x
Mac OS9 and OSX Netscape Navigator 4.7x
If you are designing applications to be accessed by browsers that are not

compliant with the JavaScript 1.1 standard and want to use the Domino 6
Web templates, be sure to use the special Web templates designed for
non-compliant browsers.
Note The Java applets Lotus Domino uses for templates depend on
specific browser versions to run properly. See the Release Notes for a list
of supported browsers.
Note Lotus Domino 6 does not support Netscape Communicator 4.6
due to LiveConnect issues. Netscape Communicator 4.61 addresses these
LiveConnect issues.

Chapter 7
Upgrading Search
This chapter describes changes to Domino search. It also tells how to

update search indexes.
Upgrading search
Lotus Notes/Domino 6 includes Domain Search, a feature introduced in
Lotus Notes/Domino 5, which you can use to index and search an entire
domain of Domino databases, including attachments to documents, and
files in a file system. Domain Search filters search results according to a
user’s access to a document that matches the search query. If the user
does not have read access to a document, Domain Search does not
include that document in the search results.
All Notes/Domino 4.6 and Notes/Domino 5 search functions and
methods are preserved in Lotus Notes/Domino 6. Existing Notes appli-
cations that use search through the Notes Search API (Application
Programming Interface) work without modification in Lotus
Notes/Domino 6.
For more information about Domain Search, see the book Administering
the Domino System.
Upgrade information on search

For more information on upgrading search, see the following topics:
• Changes in search
• Updating server indexes
• Search interoperability issues
• Search Site and Lotus Notes/Domino 6
• Domain search and Domino 4.6 servers
7-1
Changes in search
Since Lotus Notes/Domino 4.6, search has undergone the following
changes:
• Thesaurus and stop words are no longer available.
• Indexes are larger — depending on the database, the index may be as
much as 50 percent larger than the Domino 4.6 index.
• Search is fully double-byte character enabled; you can use it with
multiple languages and in multinational organizations.
Updating server indexes

Many databases have indexes allowing users to search their views. After
upgrading to Lotus Domino 6, the Domino server indexer automatically
detects Domino 4.6 or Domino 5 single-database indexes and replaces
them with Domino 6 indexes. When the indexer periodically runs in the
background to update single-database indexes, it also updates the
Domain Index.
If users attempt to search a database on a server that is being updated
from Domino 5 to Domino 6 search, they get an error. They can search
the database after the Domino server rebuilds the database index. Single-
database indexes on a client are upgraded by a background agent in
Lotus Notes 6; if users try to search before the background agent runs,
they receive an error. In this case, users can rebuild the index manually.
Note By default, background agents, like the one that updates the
search indexes, are disabled. You must enable background agents.
Administrators can override individual database settings to include or
exclude databases from the Domain Index by setting the “Include in
multi database indexing” option in the Database Properties box.
Search interoperability issues

In the process of upgrading, you may have an environment that uses the
Domino 4.6 or Domino 5 and Domino 6 search engines. Lotus Notes 6
clients can access Notes/Domino 4.6 indexes through a Domino 4.6
server. Notes 4.6 clients cannot access a Notes/Domino 6 Domain Index,
but can use a Web browser or the Microsoft Internet Explorer component
embedded in the Notes Web Navigator to run Notes/Domino Domain
Searches. Notes 4.6 clients can search database views that have
Notes/Domino 6 indexes. Web clients run Domain Searches through a
7-2 Upgrade Guide

link to the correct search form in the Domain Catalog. Application
designers can set multiple search forms in the catalog and provide multi-
ple links.
If a Notes 6 client tries to access a Notes/Domino 4.6 index locally or on a
Domino 6 server, Lotus Notes displays an error message indicating that
the index must be rebuilt. You can manually update the index or wait for
the background indexing agent to refresh and update the index. When a
Notes 6 client runs this agent, it detects Notes/Domino 4.6 indexes and
upgrades them.
Domino servers have a background task that updates indexes. When it
encounters a Notes/Domino 4.6 index on a Domino 6 server, the task
upgrades the index. You can also update an index manually.
To manually update a database index

2. Select the database for which you wish to update the index and click
Open.
3. Click the Discovery button at the top right of the screen.
4. In the Search bar, click More.

5. Click Update Index.
Note You can index all file attachments in a database using file filters,
or index only the text in files for faster indexing.
For more information about file filters, see the book Administering the
Domino System.
Search Site and Lotus Notes/Domino 6

Although Search Site is supported by Lotus Notes/Domino 6, most of its
features are now included in Domain Search.
If you use Search Site, consider the following:
• A query returns a newsletter of links, with no security filtering of the
results. While users can’t open a link to which they don’t have access,
they do know that their search generated a result on the query entry.
• The results from a search cannot be viewed until all results are
completely formatted in the newsletter, which lengthens response
time, especially if there are many results from a search.
Upgrading Search 7-3

Search Site is useful when you want to index a subset of databases that
are not highly confidential. You can also categorize these databases and
use Domain Search to index them, though there is some overhead to this
approach.
Domain Search incorporates Search Site features and adds the filtering
security based on the Domain Catalog.
To set up Domain Search, see the book Administering the Domino System.
Domain Search and Domino 4.6 servers

If you implement Domain Search in a mixed-release environment includ-
ing Domino 4.6 servers, the Catalog task must spider the Domino 4.6
servers rather than performing a pull-replication of the server’s database
catalogs. Spidering the servers slows the creation and upgrading of the
Domain Catalog.
In addition, for the Domain Indexer to properly spider a Domino 4.6 Web
server, you must configure the Domino 4.6 Web servers to resolve links
to the server.
To configure Domino 4.6 Web servers to be spidered by the Domain

Indexer
While default configurations often result in Server documents that
contain sufficient information for the indexing server to resolve links to
the servers holding the data, performing this procedure for each Domino
4.6 Web server that you want to index helps to ensure good links.
1. From the Domino Administrator, select the server.
2. Click the Configuration tab.
3. Expand the Server section in the view pane.
4. Click Current Server Document.
5. Click Edit Server, and then click the Internet Protocols - Domino Web
Engine tab.
6. Under Generating References to this Server, enter the information for
the indexing server. Make sure you use the server’s fully qualified
domain name in the Host name field.
7-4 Upgrade Guide

Chapter 8
Upgrading Security
This chapter describes known authentication and interoperability consid-

erations between Lotus Notes/Domino 6 and earlier releases.
Upgrading security
Security in Lotus Notes/Domino 6 operates in the same way as in Lotus
Notes/Domino 5, but offers additional features for Internet users,
servers, and clients.
See information on:
• Notes 6 ID files and earlier Lotus Notes client releases
• X.509 certificates and interoperability
• Web server authentication in a mixed-release environment
• Making root certificates available to clients using SSL and S/MIME
• How ECLs respond when you install or upgrade a Notes client
Notes 6 ID files and earlier Lotus Notes client releases

In a mixed-release environment, unsupported ID file version errors can
occur with Notes 6 ID files and earlier releases of the Lotus Notes clients
under certain conditions. The following table lists known Notes ID
features that can cause an unsupported ID file version error and in which
versions these errors can appear.
8-1
Lotus Notes 6 supported feature Lotus Notes 5 Lotus Notes
4.6
Alternative names* Supported Unsupported
Objects greater than 64K in length*, such as Supported Unsupported
Internet certificates
Smartcard-enabled login Unsupported Unsupported
128-bit password encryption Unsupported Unsupported
*These features were introduced in Lotus Notes/Domino 5. All other features
were introduced in Lotus Notes 6. In addition, if an alternative name is specified
in the Notes 6 ID file, you cannot use the file with a Notes 4.6 client. However,
Notes 6 clients using an ID file with alternate names can authenticate and inter-
act with Notes 4.6 clients and Domino 4.6 servers.
For more information about ID files, see the book Administering the
Domino System.
X.509 certificates and interoperability

Lotus Notes/Domino 5 and Lotus Notes/Domino 6 support X.509 certifi-
cates. If you add an X.509 certificate to a Notes ID file, you can continue
to use the file with Lotus Notes 4.6 clients. However, Lotus Notes 4.6
clients do not support those certificates.
Internet/intranet authentication in a mixed-release environment

Lotus Domino 6 provides greater control over how Domino authenticates
users accessing the server from Internet clients. In Domino 5, this setting
applied only to Web browsers; in Domino 6, it now applies to all Internet
protocols, including LDAP, POP3, IMAP, and so on.
On the Security tab of the Server document, the setting “Internet authen-
tication” provides two choices: “More name variations with lower
security” or “Fewer name variations with higher security.” Selecting
“More name variations” authenticates users the way Domino 4.6 did —
users can enter any of the following as a user name when prompted by
the browser or other Internet client:
• Last name only
• First name only
• Short name
• Common name
8-2 Upgrade Guide

• Full hierarchical name
• Any alias in the User name field
• Internet address
• UID, if using an LDAP directory for authentication
If you select “Fewer name variations,” users can enter any of the follow-
ing as a user name when prompted by the browser:
• Full hierarchical name
• Common name
• Any alias in the User name field
• UID, if using an LDAP directory for authentication
Note “Fewer name variations” is the default, and recommended, setting
for Domino 6 servers.
For more information about Internet authentication, see the book
Making root certificates available to clients using SSL or S/MIME

Notes clients that use SSL or S/MIME must have the trusted root certifi-
cates from third-party certifying authorities (CA) in their Personal
Address Book to authenticate servers using certificates from these CAs.
The Domino 6 Domino Directory contains root certificates needed to
authenticate the signatures created with these third-party CAs. Copy
these certificates from the Domino 6 Domino Directory to any Domino
4.6 Public Address Book that needs to authenticate clients over SSL.
To make root certificates available to Notes clients

1. Open the Domino Directory.
2. Go to the Server-Certifiers view.
3. Copy any trusted root certificates from third-party CAs.
4. Open the Public Address Book to which you want to add the root
certificates.
5. Paste the certificates into any view in the Public Address Book.
Users can copy these certificates to their Personal Address Books.
For more information about SSL and S/MIME for clients, see the book
Upgrading Security 8-3

How ECLs respond when you install or upgrade a Notes client
The default settings for the workstation ECL help strengthen the security
that ECLs offer. If you’re upgrading clients to a new release of Notes or
installing a new client, the following table describes how ECLs respond
to these changes.
Note In the table below, the “Results when there is no administration
ECL” applies under either of the following two circumstances:
• The user is disconnected (that is, there is no server connectivity).
• The server to which the user is connecting has the default ECL
and not an administration ECL.
Action Results when there is no Results when there is a
administration ECL home server with an
administration ECL
Install a new client ECL defaults are The workstation ECL is
assigned based on release updated with the server’s
of the client that you administration ECL
install. The user’s name is
automatically added to
the ECL.
• The workstation ECL Not applicable The workstation ECL is
is being updated by a updated with the server’s
refresh or replacement administration ECL
of the administration
ECL
• “Allow user to
modify” button is not
selected in the admini-
stration ECL
Upgrade any client The workstation ECL The workstation ECL
release 4.6 or later to a maintains its original maintains its original
newer release in which a settings from before it settings from before it
workstation ECL already was upgraded. was upgraded.
exists in the desktop
continued
8-4 Upgrade Guide

Action Results when there is no Results when there is a
administration ECL home server with an
administration ECL
• Upgrade a client that • The workstation ECL • The server’s admini-
runs a release earlier takes on the default stration ECL
than 4.6 and has no workstation ECL overwrites the
desktop (or ECL), to settings. workstation ECL. The
release 4.6 or later. • The user’s name is resulting ECL includes
-or- automatically added entries from the old
to the ECL. workstation ECL, in
• Start a client that runs
release 4.6 or higher addition to new
and has no desktop entries from the server
Admin ECL.
• The privileges in the
Admin ECL overwrite
the privileges of the
same entry in the
client default ECL.
• The user’s name is
automatically entered
in the ECL because
there is no existing
workstation ECL.
Note This table concentrates on the workstation security access options,

but the principles are the same for the Java and JavaScript access options.
Examples:
An existing enterprise has clients and servers currently running Release
4.6 to Release 5.0.1 of Lotus Notes and Domino. Upgrading all existing
servers, all existing clients, or all existing clients or servers to Release 6
will not automatically enforce the new ECL settings on any of the exist-
ing clients.
In the same enterprise, installing a new Release 6 client will enforce the
new ECL settings regardless of the release of the Domino server, as long
as the server doesn’t have a customized administration ECL.
Upgrading Security 8-5

Chapter 9
Certifying Users and Servers in Flat Organizations
This chapter describes how to convert flat user and server names to
hierarchical names. Converting flat names to hierarchical names has
many advantages, including increased security in the system.
Converting flat names to hierarchical names

You use the Domino Administration Process to convert flat user and
server names to hierarchical names. Convert to hierarchical names to:
• Ensure name uniqueness
• Distribute responsibility for creating IDs and recertifying users and
servers
• Use cross-certification, which simplifies access between your
organization and others
For more information about the Domino Administration Process, see the
How the Domino Administration Process converts flat names

You initiate the conversion of flat user or server names to hierarchical
names by choosing specific actions in the Domino Directory. The Domino
Administration Process then completes the following steps to carry out
your request.
Note You can also use the Domino Administration Process to rename
hierarchical users (not servers). You can change users’ common names or
move their names to a different hierarchical name scheme. The steps the
Domino Administration Process follows to change common names of
users are the same ones it follows to convert flat names to hierarchical.
The steps the Domino Administration Process follows to move names to
a different hierarchical name scheme are also the same except that an
administrator must first approve the request.
1. Lotus Domino creates an Initiate Rename in Address Book request in
the Administration Requests database. This request starts the process
of adding the converted or changed name to the Person or Server
document in the Domino Directory.
9-1
2. The Domino Administration Process completes this request by
making one of the following changes in the Domino Directory:
• If you are converting or changing a user name, the Domino
Administration Process adds the new name to the User name field
while keeping the old name so mail can still be sent using the
original name; adds the hierarchical certificate to the Certified
Public Key field; and adds a change request to the Change
Request field of the Person document.
• If you are converting a server name, the Domino Administration
Process adds the hierarchical certificate to the Certified Public Key
field and adds a change request to the Change Request field of the
Server document.
3. Next, one of the following occurs:
• If you are converting or changing a user name, the next time the
user accesses a server, the server looks at the Change request field
in the Person document in the Domino Directory and compares
the name in the field to the name stored in the user ID. If the
names do not match — because the user name was converted or
changed — the user sees a message asking if the new name is
correct.
If the user selects Yes, Lotus Domino updates the user ID with the
hierarchical name and certificate and creates a Rename Person in
Address Book document in the server’s Administration Requests
database; this document is a request to update all remaining
occurrences of the user’s original name in the Domino Directory.
The Domino Administration Process converts or changes the name
in the ACLs of the user’s local databases if the user is designated
as the administration server for those databases. It also updates
the name in Readers and Authors fields of local databases if the
ACL option Modify all Reader and Author fields is selected. The
Domino Administration Process also converts or changes the flat
name where it occurs in the user’s Personal Address Book if the
user has Manager access to the Personal Address Book or is
designated as the administration server for it.
If the user selects No, the user ID is not converted or changed.
• If you are converting a server name, the server periodically checks
its own Server document in the Domino Directory to see if its
name has changed. The server compares the name listed in the
Change request field of the Server document to the name stored in
its own server ID.
9-2 Upgrade Guide

If the names do not match — because the server name was
converted — Lotus Domino automatically updates the server ID
with the hierarchical name and certificate and creates a Rename
Server in Address Book document in the server’s Administration
Requests database. This document is a request to update all
remaining occurrences of the server’s flat name in the Domino
Directory.
Note The information in the Change request field in the Person and
Server documents expires after 21 days by default. The expiration
period begins once you initiate the request from the Domino
Directory. You can change the default expiration by changing the
Name_Change_Expiration_Days setting in the NOTES.INI file. If a
user has multiple IDs and switches to an ID not yet converted, Lotus
Domino converts that ID if the information in the Change request
field has not yet expired.
4. After the Domino Administration Process has executed the Rename
Person in Address Book or Rename Server in Address Book request,
it creates a Rename in Access Control List request in the
Administration Requests database to update the name in the ACLs
for databases. After the Rename in Access Control List request
replicates to every Administration Requests database in the domain,
each server’s Domino Administration Process completes the request
by converting or changing names in the access control list for all
databases that list that server as the administration server.
Users and servers can continue to access databases that have access
control lists containing their original names; they do not have to wait
until the Domino Administration Process converts or changes them.
The Domino Administration Process also creates a Rename in Person
documents request to change the name where it occurs in Person
documents in the Domino Directory.
5. Next the Domino Administration Process creates a Rename in
Reader/Author fields request in the Administration Requests
database. After this request replicates to other servers, the
Administration Process on each server changes the name from all
Readers and Authors fields of each of its databases for which it is an
administration server and that have the ACL setting “Modify Reader
or Author fields” selected. Because this can be time consuming, the
Domino Administration Process carries out this request according to
the Delayed Request settings in the Administration Process section of
the Server document. The Administration Process does not delete
names from Readers or Authors fields of signed or encrypted
documents.
Certifying Users and Servers in Flat Organizations 9-3

Converting when you have multiple Public Address books
If you create replicas of two or more Public Address books on a server,
the Domino Administration Process modifies documents only in the
primary Domino Directory, the first one listed in the NAMES=
NOTES.INI setting file.
The primary Domino Directory must contain the Person or Server
document of the user or server you want to convert and the Certifier
documents of the hierarchical certifier ID and hierarchical ancestors of
the certifier ID. For example, to convert Alan Wilson to Alan
Wilson/Finance/Boston/Acme, the primary Domino Directory must
have the Person document for Alan Wilson and the Certifier documents
for /Finance/Boston/Acme, /Boston/Acme, and /Acme.
For more information on using multiple Domino Directories, see the
Converting in a Domino 4.6 environment

If you have Domino 4.6 servers, keep in mind that Lotus Domino does
not convert user and server names in ACLs of databases that reside on
Domino 4.6 servers.
Backing up converted IDs

Because Lotus Domino does not automatically convert backup IDs or IDs
attached to documents in the Domino Directory, tell users and adminis-
trators to make backups of their converted IDs.
Examples of converting flat names to hierarchical names

The company, Acme Corporation, has offices in Cambridge and Los
Angeles. Each office has two departments: Sales and Marketing in
Cambridge, and Development and Human Resources in Los Angeles.
Acme employees rarely change departments, so you can base a naming
scheme on both geographical location and departments.
The chart for the hierarchical naming scheme at Acme includes the
following organization and organizational units:
Acme (organization) — The top-level hierarchical name. All servers and
users in the company use this organization name. Use this hierarchical
name in conjunction with an organizational unit as described below.
East and West (organizational units) — First-level organizational units of
Acme.
Sales and Marketing (organizational units) — Second-level organiza-
tional units of East.
Dev and HR (organizational units) — These are second-level organiza-
tional units of West.
9-4 Upgrade Guide

After you create the hierarchical naming scheme, you create the follow-
ing certifiers:
/Acme — The top-level certifier ID.
/East/Acme and /West/Acme — Create these certifiers using the /Acme
certifier ID and use the /East/Acme certifier to name servers in the
Cambridge office and the /West/Acme certifier to name servers in the
Los Angeles office.
/Sales/East/Acme and /Marketing/East/Acme — Create these certifiers
using the /East/Acme certifier ID and use them to name users in the
Cambridge office.
/Dev/West/Acme and /HR/West/Acme — Create these certifiers using
the /West/Acme certifier ID and use them to name users in the Los
Angeles office.
The following tables contain examples of server and user names at Acme
Corporation before converting to hierarchical and after converting to
hierarchical names. The certifier ID that you use for the server or user
name depends on the location of the server or user and the department in
which the user works.
Location Server name before converting Server name after converting

Cambridge Hub-E Hub-E/East/Acme
Cambridge Mail-E Mail-E/East/Acme
Cambridge Passthru Passthru/East/Acme
Los Angeles Hub-W Hub-W/West/Acme
Los Angeles Mail-W Mail-W/West/Acme
Location and department User name before converting User name after converting
Cambridge - Alan Jones Alan Jones/Sales/East/
Sales department Acme
Cambridge - Randi Bowker Randi Bowker/
Marketing department Marketing/East/Acme
Los Angeles - Judy Kaplan Judy Kaplan/Dev/
Development West/Acme
department
Los Angeles - Mark Richards Mark Richards/HR/
Human Resources West/Acme
department

Converting flat server names to hierarchical server names
Before converting user names, you must convert server names to hierar-
chical names. Because the Domino Administration Process must run on a
server that has a hierarchical name, you must complete a specific proce-
dure to convert the name of the first server in a domain and then specify
this server as the administration server for the Domino Directory. Then
you can let the Domino Administration Process complete the work of
converting subsequent servers.
When you convert a server name to hierarchical, the server’s flat name
combines with the certifier name to create the hierarchical name. For
example, if a server’s flat name is Serverwest and the certifier name is
Marketing/Acme, the server’s hierarchical name is Serverwest/
Marketing/Acme. You must use the server’s flat name as the common
name component of the hierarchical name. In other words, you cannot
change the server name when you convert it to a hierarchical name.
You can convert at the same time all server names that use the same
hierarchical certifier. For example, if you have three servers —
Serverwest, Servereast, Servernorth — that you want to convert
to the hierarchical names Serverwest/Marketing/Acme, Servereast/
Marketing/Acme, and Servernorth/Marketing/Acme, use the
Marketing/Acme hierarchical certifier to convert all the names at the
same time.
If hierarchical users and servers access the flat server and they use a
different organization name from the one planned for the flat server, you
must manually change the names of the hierarchical users and servers to
their hierarchical format in the Domino Directory and database ACLs on
both the hierarchical server and the flat server you plan to convert. Issue
cross-certificates between the two organizations so users and servers can
access the server in the other organization.
After you convert flat server names to hierarchical, users with flat names
can continue to access the hierarchical servers without any restrictions.
How the Domino Administration Process converts a flat server name to

hierarchical
The following flowchart shows the sequence of Administration Process
requests that occur when you use the Domino Administration Process to
convert a flat server name to a hierarchical name. More detailed informa-
tion about each request follows the flowchart.
9-6 Upgrade Guide

Choose "Actions: Upgrade Server to
Hierarchical" in the Public Address Book
Initiate Rename in
Address Book
1 Hour
Change Request
Server updates Expires
No its ID before
change request
expires? Delete Obsolete
Change
Yes Requests
End
Daily
Rename Server
in Address
Boo
1 Hour
Rename in Rename in
Access Control Person
List Documents
1 Hour Daily
Rename in
Reader/Author
Fields
Weekly
Initiate Rename in Address Book

Triggered by: Selecting a Server document in the Domino Directory
and choosing “Actions - Upgrade Server to Hierarchical.”
Posted on: The server where you choose the upgrade action.
Carried out on: The administration server for the Domino Directory.
Carried out: According to the Interval setting for the Administration
Process in the Server document.
Result: The Domino Administration Process adds the hierarchical
certificate to the “Certified public key” field in the Server document
and a change request to the “Change request” field.
Rename Server in Address Book

Triggered by: The server updating its ID with the new hierarchical
name and certificate when the server detects the name change in the
“Change request” field of its Server document.
Posted on: The server whose name has changed.

Result: Updates all remaining occurrences of the server name in the
Domino Directory except in Person documents.
Rename in Person Documents

Triggered by: Completion of the “Rename Server in Address Book”
request.
Posted on: The administration server for the Domino Directory.
Carried out: According to the “Execute once a day requests at”
setting for the Administration Process in the Server document.
Result: The Domino Administration Process updates occurrences of
the name in Domino Directory Person documents.
Rename in Access Control List

Triggered by: Completion of the “Rename Server in Address Book”
request.
Carried out on: Each server in the domain.
Result: Each server in the domain updates the server name in ACLs
of databases for which it is an administration server.
Rename in Reader/Author Fields

Triggered by: Completion of the “Rename in Person Documents “
request on the administration server for the Domino Directory.
Carried out on: Each server in the domain.
Carried out: According to the “Delayed Request” settings for the
Administration Process in the Server document.
Result: Each server in the domain updates the name in Reader and
Author fields of databases for which it is an administration server
and that have the advanced ACL option “Modify all Reader and
Author fields” selected.
Delete Obsolete Change Requests

Triggered by: Expiration of the period in which a server can accept a
new name, by default 21 days. You can use the NOTES.INI setting
Name_Change_Expiration_Days to change the expiration period.
9-8 Upgrade Guide

Carried out: According to the “Execute once a day requests at”
setting for the Administration Process in the Server document.
Result: The Domino Administration Process deletes the contents of
the Change Request field from the Server document.
Preparing to convert flat names to hierarchical names

Before you convert a server or user name from flat to hierarchical, you
must do the following:
1. Upgrade all servers to Lotus Domino 6.
2. Create a Certification Log database (CERTLOG.NSF), which you use
to troubleshoot any problems that occur when you convert names.
3. Develop a hierarchical name scheme for your organization.
For more information about hierarchical naming, see the book
Administering the Domino Server.
4. Create hierarchical certifier IDs.
5. Prepare the system for the Domino Administration Process. This
includes creating the Administration Requests database and
replication schedule, giving proper access to administrators and
specifying an administration server for the Domino Directory and
databases.
For more information about the Domino Administration Process, see
6. Follow a specific set of steps to convert the first flat server to a
hierarchical name.
For more information about converting a flat server, see the topic
“Converting the first flat server name to a hierarchical name” later in
this chapter.
7. Before converting a flat server name, manually change the name in
the ACL of MAIL.BOX if the server name is listed explicitly in the
ACL.
Converting the first flat server name to a hierarchical name

Make sure you complete the steps in the topic “Preparing to convert flat
names to hierarchical names” earlier in this chapter.
1. Start the server and Domino Administrator.
2. Choose File - Tools - Server Administration.
3. Click Servers and choose Servers view.

4. Open the Server document of the server to be converted. If the
Certified public key field is empty, copy the certified public key to
this field:
a. Choose File - Tools - Server Administration, Administration - ID
File
b. Select the server ID file, click More Options, and then click Copy
Public Key.
c. Paste the key into the Certified public key field in the
Administration section of the Server document and then save the
Server document.
5. With the Server document selected, choose Actions - Upgrade Server
to Hierarchical.
6. Choose the hierarchical certifier to use and enter the password. Refer
to the hierarchical naming chart you created for the hierarchical
naming scheme.
7. Enter the date when this certificate will expire for the server.
8. Click OK.
9. After Domino processes your request, click OK.
10. Shut down the server and open the Domino Directory locally on the
server machine.
11. Open the Server document of the first server to convert.
12. Delete the contents of the Certified public key field.
13. Open the Administration Requests database.
14. Open the “Initiate Rename in Address Book” request document for
the server being converted.
15. Copy the contents of the Certified public key field to the Certified
public key field of the Server document.
16. Copy the contents of the Change Request field to the Change Request
field of the Server document.
17. Save the Server document.
18. Shut down the Domino Administrator.
19. Restart the server.
Converting the remaining flat server names to hierarchical

Before you can convert a user name, you must convert server names. You
must have Author access with the ServerModifier role or Editor access as
well as the Create Documents permission to the Domino Directory. You
must also have at least Author access with the Create documents permis-
sion to the Certification Log.
9-10 Upgrade Guide

Make sure you completed all the steps in the topic “Converting the first
flat server name to a hierarchical name” earlier in this chapter before you
perform this task.
1. In the Domino Administrator, open the Domino Directory on a
server rather than choosing “Local.”
2. In the Server view, select the servers you want to convert.
3. Choose Actions - Upgrade Server to Hierarchical.
4. Choose the hierarchical certifier to use, and enter the password.
Refer to the hierarchical name scheme that you developed.
5. Enter the date when this certificate will expire for the server.
6. Click OK.
7. After Domino processes the requests, click OK.
8. Repeat Steps 3 through 7 for additional servers whose names you
want to convert using a different hierarchical certifier.
Converting flat Notes user names to hierarchical

After you convert flat server names to hierarchical server names, you can
convert flat user names.
The user’s flat name combines with the certifier name to create the
hierarchical name. For example, if a user’s flat name is Randi Bowker
and the certifier name is Marketing/East/Acme, the user’s hierarchical
name is Randi Bowker/Marketing/East/Acme.
You can convert multiple user names at a time, provided that you use the
same hierarchical certifier to certify all user names. For example, to
convert three users — Randi Bowker, Kara Nguyen, and Bob Murphy —
in the Marketing department of the Acme Corporation, you use the
Marketing/East/Acme hierarchical certifier. The resulting hierarchical
user names are: Randi Bowker/Marketing/East/Acme, Kara Nguyen/
Marketing/East/Acme, and Bob Murphy/Marketing/East/Acme.
If users have administration servers set in their local databases and
Personal Address books, they must accept their names on their own
workstations in order to upgrade the names in these databases.
After user name upgrades occur in a database access control list (ACL)
and the name change expiration period (Name_Change_Expiration_Days
setting) elapses, users cannot access the database using their flat user
names. Similarly, if you manually upgrade user names to hierarchical in
database ACLs on servers in another domain, users cannot access the
database using their flat user names.

However, if you upgrade a user name to hierarchical and the database
ACL lists the user’s flat name, the user can continue to access the
database, but keep in mind that the security that hierarchical naming
provides is not enforced for that database.
How the Domino Administration Process converts flat Notes user

names to hierarchical
You can use the Domino Administration Process to convert a flat Notes
user name to hierarchical by initiating a person rename action in the
Domino Directory. The sequence of Administration Process requests that
occurs when you convert a Notes user name to hierarchical is the same
that occurs when you change the name of a hierarchical Notes user.
Converting flat user names to hierarchical names

Follow these steps to use the Domino Administration Process to convert
flat user names to hierarchical. You must have Author access with the
UserModifier role or Editor access and the Create Documents permission
access to the Domino Directory. You must also have Author access with
the Create Documents permission to the Certification Log.
Make sure you completed the steps in the topics “Converting the first flat
server name to a hierarchical name” and “Converting flat server names
to hierarchical names” earlier in this chapter before you perform this
task.
1. Make sure all the requests for converting server IDs have completed
successfully. Do not continue with this procedure until the server IDs
are converted.
2. In the Domino Administrator, open the Domino Directory on a
server rather than choosing “Local.”
3. In the People & Groups view, select the users whose names you want
to convert.
4. From the Tools pane, choose People - Rename.
5. Click Upgrade to Hierarchical.
9-12 Upgrade Guide

6. Complete the fields of the Choose a Certifier dialog box according to
the following table:
Field Action
Server • If you are using the CA process, choose the
server that has the Domino Directory contain-
ing the CA’s record, and the copy of the
Administration Requests (ADMIN4.NSF)
database to be updated with the request for the
new certificate.
• If you are supplying a certifier ID, select the
registration server for the current certifier ID.
The registration server is the server that the
Domino Administrator contacts to perform the
registration tasks.
Supply certifier ID • Choose the certifier ID that certified the user’s
and password ID.
• Click “Certifier ID” if you want to use an ID
other than the one displayed.
• Enter the password for the certifier ID.
Use the CA process • Choose this option to use the CA process.
• Select a CA configured certifier from the list
and click OK.
Note You choose either the certifier ID or the CA process, but you
do not use both.
7. Enter the date when this certificate will expire for the users.
8. Click OK.
9. After Domino processes the requests, click OK.
After you initiate a request in the Domino Directory to convert a flat
name to hierarchical, check the Updates Status view of the Certification
Log database (CERTLOG.NSF) for any errors that the Domino Admin-
istration Process encountered while processing the request.
After the Domino Administration Process responds to the request, check
response documents in the Administration Requests database for any
errors it encounters.

Flat names
Flat names are supported for compatibility with earlier releases. Continu-
ing to use flat names prevents you from using many of the new features
in Lotus Notes and Lotus Domino 6, including the Domino Administra-
tion Process, which simplifies many administrative tasks.
Using flat names makes it difficult to exchange information securely with
users and servers in a different organization. With flat names, each user
or server in one organization must be individually certified by the certi-
fier ID in the other organization. Organizations that use flat names often
use several certifier IDs and each user ID and server ID can include a
separate certificate generated by each flat certifier ID.
When you create a flat certifier ID, Domino creates a Certifier document
describing it in the Server - Certificates view of the Domino Directory on
the registration server. You must have access to the registration server
and have at least Author access to the Domino Directory to create a certi-
fier ID.
Make sure to store one copy of all certifier IDs in a physically secure
location and store a backup copy off-site as insurance against fire, flood,
or theft.
Communication with organizations that use flat names

To establish authentication between servers at two different organiza-
tions when either organization is flat, the client must have a certificate
from a certifier that the server trusts and the server must have a certifi-
cate from a certifier that the client trusts. One way to do this is to have
each organization send a safe copy of its server IDs to the other for flat
certification and upon receiving the newly-certified ID turn off the option
“Trust other certificates signed by this certifier.”
For example, if two organizations, Alpha and Beta, need to communicate,
Alpha’s server Hub-A obtains a certificate from Beta and turns off the
“Trust” option. Hub-A now has a trusted Alpha certificate and an
untrusted Beta certificate. Beta’s server Mail-B obtains a certificate from
Alpha and turns off the “Trust” option. Mail-B now has a trusted Beta
certificate and an untrusted Alpha certificate.
Hub-A presents Beta’s certificate to Mail-B because Mail-B trusts that
certificate. Mail-B present Alpha’s certificate to Hub-A because Hub-A
trusts that certificate. Authentication proceeds because the servers have
certificates from the same certifiers even though they don’t share a
trusted certificate.
9-14 Upgrade Guide

Optionally, “trust” could be turned on for Beta’s certificate on Hub-A,
and Hub-A would accept any ID containing a Beta certificate. By doing
this, other servers at Alpha do not need to get any new certificates.
However, servers at Alpha would be vulnerable to access by fraudulent
IDs created by Beta.
Unlike cross-certification used between hierarchical organizations, certi-
fying between flat organizations requires that server IDs be certified
individually.
To exchange flat certificates between organizations, each organization
should follow the steps described in the topics “Recertifying flat IDs
using Notes mail” or “Recertifying flat IDs without Notes mail” later in
this chapter.
Each organization should make sure to turn off the “Trust other certifi-
cates” option for the certificate received from the other organization.
Note Hierarchical organizations that want to certify server IDs of flat
organizations must create a flat certifier ID with which to do this.
For more information about creating a flat certifier ID, see the topic
“Creating a flat certifier ID” later in this chapter.
Creating a flat certifier ID

When you create a flat certifier ID, follow these guidelines:
• Use any of these characters in the name: A - Z, 0 - 9, & -. _ ‘
(ampersand, dash, period, space, underscore, apostrophe). Do not
use any other characters, as this can cause unexpected results. The
name can be up to 64 characters long.
• Use a short name without spaces for easier administration.
• Don’t use a name already assigned to a group in the Domino
Directory.
• Use a phrase for a password to make the password easier to
remember and more difficult for an unauthorized person to guess.
• Assign multiple passwords to the certifier ID to avoid giving one
person complete authority.
Follow this procedure to create a flat certifier ID.
1. In the Domino Administrator, choose File - Tools - Server
Administration.
2. Click Certifiers and then choose Register Non-Hierarchical.
3. Enter a name in the Certifier name field.

4. Enter a case-sensitive password between 12 and 32 characters. Use
passwords at least 13 characters in length and of mixed case.
5. Specify a minimum password length of at least 12 characters.
6. Select a license type.
7. Click OK.
8. Specify a file name and location for the certifier ID.
9. Click OK.
Deleting a flat certificate from an ID

To delete a flat certificate from an ID, follow these steps:
1. In the Notes client, choose Tools - User ID.
2. Enter the password for the current ID.
3. Click Certificate and select the certificate to delete.
4. Click Delete.
5. Click Done.
Creating flat ID files

You cannot create new flat ID files with Lotus Notes/Domino 6. If your
organization continues to use flat ID files with Lotus Notes/Domino 6,
you must retain at least one Notes 4.6 client to create new flat ID files.
However, Lotus Notes/Domino 6 fully supports flat ID file maintenance.
You can renew certificates for existing flat ID files and issue new flat
certificates to new hierarchical users who need access to servers with flat
IDs. If your organization uses flat ID files, consider upgrading to hierar-
chical ID files for increased security and flexibility of access control, ID
generation and certification, and maintenance.
Ways to recertify IDs with a flat certifier ID

You use a flat certifier ID to recertify an ID to:
• Add a flat certificate to a flat ID
• Recertify a certificate on a flat ID that is about to expire
• Add a flat certificate to a hierarchical ID to allow authentication with
a flat organization
• Recertify a flat certificate on a hierarchical ID
9-16 Upgrade Guide

You can recertify an ID in either of the following ways:
• Using Notes mail
• Without Notes mail
Recertifying flat IDs using Notes mail

Follow these steps to manually recertify a flat ID that has a certificate that
is about to expire. The owner of the ID and the certification administrator
must be able to communicate through Notes mail; each takes turns
processing the request.
To mail the ID, the owner of the ID does the following:

1. In the Notes client, choose File - Tools - User ID.
2. Click Certificates.
3. Click Request Certificate.
4. Enter the name of the certification administrator in the To field.
5. Click Send to mail the request to the certification administrator.
To recertify the ID, the certification administrator does the

following:
1. In the Domino Administrator, open the certification request in your
mail file.
2. If the certifier is on a disk, insert the disk in the disk drive.
3. Choose Actions - Certify Attached ID File.
4. Select the certifier to use and click OK.
5. Enter the password for the certifier and click OK.
6. If the certifier is on a disk, remove the disk from the disk drive and
click OK.
7. (Optional) Accept or change the certificate expiration date.
8. Leave “Trust other certificates signed by this certifier” selected
unless the certificate is from another organization’s certifier.
9. (Optional) Click Server, select a server, then click OK to change the
server in whose Domino Directory Lotus Domino updates the Person
document. If the server isn’t local, you must have at least Author
access to its Domino Directory.
10. Click Certify.
11. Click Sign to prove your identity to the recipient.
12. Choose Send to send the recertified safe copy of the ID to the user.

To merge the new certificate, the owner of the ID does the following:
1. In the Notes client, open the mail document containing the recertified
ID.
2. Choose Actions - Accept Certificate.
3. Enter the password for the ID. You see the new certificate.
4. If this is a certificate received from another organization, turn off
For more information, see the topic “Communication with
organizations that use flat names” earlier in this chapter.
5. Click Accept.
Recertifying flat IDs without Notes mail

Follow these steps to manually recertify a flat ID if its certificate is due to
expire or to manually convert an ID to hierarchical naming if its owner
and the certification administrator cannot communicate through Notes
mail. This process requires that the owner of the ID and the certification
administrator take turns processing the request.
To deliver a safe copy of the ID, the owner of the ID must do the
following:
2. Click More Options.
3. Click Create Safe Copy.
4. Specify a name and location for the safe copy and click OK. The
default name is SAFE.ID.
5. Enter a path and name for the safe copy, then click OK. The default
name is SAFE.ID.
6. (UNIX users) Do one of the following:
• Transfer the file to a disk, for example:
tar -cvf filename /dev/fd0
• Use a network facility such as FTP to transfer the file.

7. Deliver the disk in person or by postal service to the certification
administrator.
To recertify the ID, the certification administrator must do the

following:
Administration.
2. Click the Certifiers icon and choose Certify ID File.
9-18 Upgrade Guide

4. Enter a password for the certifier and click OK.
5. If the certifier is on a disk, remove the disk and click OK.
6. Select the safe copy of the ID file to be recertified and click OK.
7. (Optional) Accept or change the certificate expiration date.
8. Leave “Trust other certificates signed by this certifier” selected
unless this is a certificate from another organization’s certifier.
or Server document. If the server isn’t local, you must have at least
Author access to its Domino Directory.
10. Click Certify.
11. Remove the disk with the recertified safe copy of the ID and deliver
the disk to its owner in person or through the postal service.
To merge the new certificate, the owner of the ID must do the

following:
1. Insert the disk with the recertified safe copy of the ID in the disk
drive. Or, if it’s a diskless workstation, copy the safe copy of the
recertified ID file to the program directory on the file server; give the
copy a name different from the original ID file so the original is not
overwritten.
2. Make sure the current ID is the one you want recertified, then in the
Notes client, choose File Tools - User ID.
4. Click Merge A Copy.
5. Select the recertified safe copy of the ID and click OK.
6. Click Merge.
7. If this is a certificate received from another organization, turn off
For more information, see the topic “Communication with organizations
that use flat names” earlier in this chapter.
Results of recertification
The results of recertification vary depending on whether the IDs
involved are hierarchical or flat. The following table shows the outcome
for all possible scenarios.

Flat user/server ID Hierarchical user/server ID
(Contains one or more flat (Contains one hierarchical certificate;
certificates only) may also include flat certificates)
Flat certifier ID Resulting certificate is Resulting certificate is flat;
flat. Other certificates hierarchical name and certificate
remain. are maintained along with any
other flat certificates.
Hierarchical Name on the ID becomes Resulting certificate is either a
certifier ID hierarchical and resulting cross-certificate or a recertified
certificate is hierarchical. hierarchical certificate.
Flat certificates remain.
Ways to rename flat user IDs

You can rename flat user IDs in the following ways:
• Using Notes mail
• Without Notes mail
Renaming flat user IDs using Notes mail

Before you rename flat user IDs with Notes mail, note the following:
• Lotus Notes deletes all other flat certificates from the ID when the
name on it is changed. Therefore, the owner must have the ID
recertified by these flat certificates.
• You must manually add the new name to the Domino Directory
documents in which it appears and to the appropriate database
access control lists, including the access control list for the user’s mail
file. The user can still read any signed or encrypted mail created
under the original name.
Complete these steps to manually rename a flat user ID when its owner
can communicate through Notes mail. This process requires that the
owner of the ID and the certification administrator take turns processing
the request.
To request a new user name, the owner of the ID must do the

following:
1. In the Notes client, choose File - Tools - User ID, enter the password,
and click OK.
3. Click Request New Name.
9-20 Upgrade Guide

4. Enter the complete new name — for example, Randi Bowker — then
click OK.
5. Enter the name of the certification administrator in the To field, and
then click Send.
To certify the newly named ID, the certification administrator must

do the following:
1. In the Domino Administrator, open the request received in the mail.
2. Choose Actions - Certify Attached ID file.
3. Select the certifier and click OK.
5. If the certifier is on a disk, remove the disk and store it in a secure
place.
6. (Optional) Change the certificate expiration date.
7. Enter a minimum password length to require password use and a
minimum password length on this ID. To maintain the current ID’s
setting, leave the field blank.
8. (Optional) Click Server to change the server in whose Domino
Directory Lotus Domino updates the Person or Server document,
select a server, then click OK. If the server isn’t local, you must have
at least Editor access to its Domino Directory.
9. Click Certify.
The To field of the Mail Certified ID dialog box displays the old
name.
10. Select Send to send the recertified safe copy of the ID to the user.
To merge the new certificate with the current ID, the owner of the ID
must do the following:
1. In the Notes client, open the mail message.
2. Make sure the current ID is the one you want changed.
3. Choose Actions - Accept certificate.
4. Verify that the new name is correct in the Name field, then click OK.
Merging the new certificate with the current ID adds the certificate to the
ID.
Renaming flat user IDs without Notes mail

Before you rename flat user IDs without Notes mail, note the following:
• All other flat certificates are deleted from the ID when the name on it
is changed. Therefore, the owner must have the ID recertified by
these flat certifiers.

• You must manually add the new name to Domino Directory
documents in which it appears and to the appropriate database
access control lists, including the access control list for the user’s mail
file.
• Add the new name before the old one in the Person document in the
Domino Directory; retaining the old name ensures that mail
addressed to the old name is sent successfully. The user can still read
any signed or encrypted mail created under the original name.
Complete these steps to manually rename a flat user ID when its owner
cannot communicate through Notes mail. Note that this process requires
that the owner of the ID and the certification administrator take turns
processing the request.
To request a new user name, the owner of the ID must do the

following:
1. Make a backup copy of the ID file.
2. In the Notes client, choose File - Tools - Switch ID, and select the new
copy.
3. Choose File - Tools - User ID and enter the ID password.
5. Click Change Name, enter the new name, and click OK.
6. Click Yes. This removes all certificates from the ID.
7. Click Create Safe Copy.
8. Enter a path and name for the safe copy and then click OK. The
default name is SAFE.ID.
9. (UNIX users) Do one of the following:
• Transfer the file to a disk, for example:
tar -cvf filename /dev/fd0
• Use a network facility such as FTP to transfer the file.

10. Remove the disk with the recertified safe copy of the ID and deliver
the disk to its owner in person or through the postal service.
11. Choose File - Tools - Switch ID, and select the original ID to use until
the certifier recertifies the newly-named ID.
To recertify the newly named ID, the certification administrator must

do the following:
Administration.
2. Click the Certifiers icon and choose Certify ID File.
9-22 Upgrade Guide

5. Select the safe copy of the newly named ID to be recertified.
6. (Optional) Change the certificate expiration date.
or Server document. If the server isn’t local, you must have at least
Editor access to its Domino Directory.
8. Click Certify.
9. Remove the disk containing the recertified ID and deliver the disk to
the ID’s owner in person or through the postal service.
To merge the safe copy with the current ID, the owner of the ID must
do the following:
3. Click Merge A Copy.
4. Select the recertified safe copy of the ID and click OK.
5. Click Merge.
Merging the safe copy of the ID with the current ID updates the current
ID with the new user name.

Chapter 10
Overview of Domino Upgrade Services
This chapter provides an overview of Domino Upgrade Services that

provide migration tools that import people and groups from foreign
directories into the Domino Directory and upgrade wizards that import
personal mail and address book information into Notes mail. This
chapter discusses terms and concepts you should be familiar with before
migrating users.
Using this guide

This guide is for information services (IS) managers, Notes administra-
tors, database managers, application designers, and anyone else respon-
sible for migrating users from external directory sources or messaging
systems to Lotus Domino 6. The administrator performing a migration
should be familiar with Lotus Domino and Notes, as well as with the
directory or messaging system that users are moving from.
The migration process differs between organizations, depending on the
network configuration, available resources, and desired level of migra-
tion. This guide provides basic guidelines and procedures that you can
adapt to your organization as you plan and perform the migration to
Lotus Domino 6.
Before performing a migration, read this section, as well as the sections
containing information specific to the system you are importing from.
The users you migrate may have messaging data stored in locations
outside their mailboxes. Read the chapter “Migrating personal mail data”
to help prepare users to run the upgrade wizard that migrates such data.
Overview of Domino Upgrade Services

The address books, message stores, and archives of a messaging system
contain a great deal of information. When migrating users from another
system to Domino and Notes or iNotes, it is important not only to maintain
reliable messaging services with minimal disruption, but also to maintain
access to the information on the old system, by converting that information
so that users can access it from a Notes client or iNotes Web Access client.
10-1
Migration is the process of moving user directory information, mailboxes,
mail, and addresses from one system to another. Migration includes
importing data from a legacy messaging system and converting it to
Notes mail and Domino Directory format. Importing refers to the task of
moving data from an external directory, post office, or mailbox and
making it available for processing into Domino or Notes format. Convert-
ing refers to the task of processing imported information and changing it
to Domino or Notes format.
Domino Upgrade Services include the migration tools for administrators
and the upgrade wizards for users. Depending on your environment,
and the type of migration you are performing, you may use one or both
of these tools.
Domino Upgrade Services, which can be installed as part of the Domino
Administrator, can be used by an administrator to:
• Import users from a server-based foreign directory
• Register imported users
• Automatically create Notes mail files for registered users
• Convert messages from mail boxes in the legacy mail system into
Notes format
Domino Upgrade Services migrates data from the following messaging
and directory systems:
• LDIF (LDAP Data Interchange Format) files
• LDAP-compliant foreign directories
• Lotus cc:Mail® and Organizer® 2.x for cc:Mail
• Microsoft Exchange
• Microsoft Mail
• Microsoft Windows NT Server
• Microsoft Active Directory
Domino Upgrade Services place most of the data from the old system
directly into Notes databases on the Domino server. However, in the
Notes environment some types of data, such as personal address book
information, are typically stored on the Notes client. Domino Upgrade
Services use Notes mail messages to send client data to migrated users.
Users can then run the upgrade wizard at their workstations to transfer
the data stored in the mail message to the appropriate database on the
Notes client. The upgrade wizards migrate users’ private addresses,
private distribution lists, and message archives to local Notes databases.
10-2 Upgrade Guide

For more information about the upgrade wizards, see the chapter
“Migrating Personal Mail Data.”
Installing the Domino Administrator and Domino Upgrade Services

The migration tasks require use of the Domino Administrator and
Domino Upgrade Services. Installing Domino Upgrade Services with the
Domino Administrator client is optional; select the Admin Migration
Tools component during installation to install both the migration tools
and the upgrade wizards. If you did not install either the Domino
Administrator or Domino Upgrade Services when you first installed the
Notes client, run the installation again.
For more information about installing the Domino Administrator client
and Domino Upgrade Services, see the book Administering the Domino
System.
Tip For best performance, run the Domino Administrator on a
computer within the same Notes domain as the destination mail server.
Also, if you are using the cc:Mail MTA to provide coexistence between
cc:Mail and Notes, do not run the Domino Administrator on the MTA
server.
Importing users from a foreign directory

Use Domino Upgrade Services to extract information from a foreign
directory source and import that information into the Domino Directory.
When importing users to the Domino Directory, you must direct the
Domino Upgrade Services to an external, or foreign, directory that will
serve as the source for names to import. The foreign directory can be an
application-specific post office directory, such as a cc:Mail post office
directory or a Microsoft Exchange Address Book, or a standard LDAP
directory that is not application-specific. Domino Upgrade Services
import names and other basic user information from the source
directory: secondary names, mail addresses, passwords, and so forth.
The information from the source directory is copied to Person documents
in the Domino Directory.
The administrator performing the migration should be familiar with the
Domino Directory as well as the source directory.
Overview of Domino Upgrade Services 10-3

The process of importing users consists of the following tasks:
• Specifying the foreign directory source
• Selecting users to migrate
• Setting migration options
Specifying the foreign directory source

A source directory or address book contains important information about
users of the old mail system. Using the Domino Administrator, you select
the type of directory and then enter the information needed to connect to
it and extract information from it. You can then retrieve some or all users
and groups from the foreign directory and select those to be imported to
Notes.
Selecting people and groups to migrate

After selecting a directory to import, you can select the users and groups
you want to migrate. If you are migrating from multiple systems, you
can select users and groups from different foreign directories during a
single session.
For example, from the People and Groups Migration dialog box, you can
select 10 users to migrate from a cc:Mail directory, and then select
additional users from a Microsoft Exchange directory. If you select the
cc:Mail directory again, the 10 users are still selected.
Depending on the Domino Upgrade Service, you may have a customer or
user-supplied filter available. For directories with many users, filters
save time and memory when retrieving the whole directory. There are
three filter options:
• All users and groups — Imports all users and groups
• All users — Imports only users
• All groups — Imports only groups
Filter format and syntax are specific to the Domino Upgrade Service
selected.
Migrating groups
With Domino Upgrade Services, you can migrate groups and their
members from a foreign directory. Domino Upgrade Services support
migration of two types of group members:
• Local users
• Nested groups within parent groups
10-4 Upgrade Guide

Local users have entries in the local directory — that is, the same direc-
tory where the group entry exists. When you select a group to migrate,
the local users in the group are always selected for migration, too.
Nested groups are groups that are members of another group. A
top-level group may contain a single nested group or even a hierarchy of
nested groups. By default, when you migrate a group you also migrate
the groups nested within it, and the local users in those groups. A nested
group is migrated only if you migrate its parent group.
For more information about migrating nested groups, see the topic
“Migrating nested groups” later in this chapter.
If you decide that you do not want to add nested groups and their
members, you can change the default to prevent them from being added.
However, you cannot prevent Domino Upgrade Services from adding
local users of the main group.
Migrating groups with duplicate names

When you select one or more groups to migrate, the migration tool
searches the Domino Directory to determine whether the name of any
selected group duplicates the name of an existing Notes group. If the
name of a selected group is the same as that of an existing Notes group,
the Existing Group Migration Options dialog box appears, so that you
can specify how to process the duplicate group. You can choose one of
the following options for migrating a duplicate group:
• Use the existing Notes group
• Create a new group — Don’t use the Notes group
• Skip this group — Do not migrate it for now
Using an existing Notes group to migrate groups with duplicate
names
You can migrate a duplicate group to the existing Notes group. Select
this option if an existing Notes group is functionally equivalent to a
migrating group with the same name. For example, if both the migrating
group Sales Managers and the existing Notes group Sales Managers are
used to send e-mail to the organization’s regional sales managers, add
the migrating group to the existing Notes group.
After you click OK, the migration tool displays the Group Migration
Options dialog box, which displays options related to adding members to
an existing Notes group, such as whether to add the available members
of the migrating group to the Notes group. Because the Notes group
already exists, you cannot change its name, type, or description.

Creating a new group to migrate groups with duplicate names
You can create a new Notes group and migrate a duplicate group to it.
Select this option if an existing Notes group is used differently from a
migrating group with the same name. For example, if a migrating group
Directors is used to send e-mail to the directors of various projects within
an organization, and an existing group with the same name in Notes is
used to send mail to the directors of each division in the organization,
create a new group with a different name for the migrating group.
After you click OK, the migration tool displays the Group Migration
Options dialog box, which displays options related to creating a Notes
group and adding members to it, such as the group name, type, and
description.
If you choose to create a new Notes group, Notes adds the available
members of the migrating group to the new group during registration.
Avoiding the creation of duplicate Group documents

As a precaution against creating duplicate groups, do not select the
option “Use above settings for all currently selected or nested groups.”
The use of this option prevents you from altering the name of a migrat-
ing group. As a result, if a migrating group has the same name as an
existing Notes group, the Domino Directory would contain two Group
documents with this name after registration.
Skipping migration for groups with duplicate names

You can decide not to migrate a duplicate group at all. Select this option
to cancel the migration of a group and return to the People and Groups
Migration dialog box. The group is not added to the “People/Groups to
migrate list.”
Setting Group Migration Options

From the People and Groups Migration dialog box, you can select groups
to migrate from a foreign directory. After you select a group, the Group
Migration Options dialog box lets you specify how to migrate the group
and its members. The settings that are available depend on whether you
are migrating users to a new group or to an existing Notes group. The
following fields are available from the Group Migration Options dialog
box.
10-6 Upgrade Guide

Option/field name For migrating to an For migrating to
existing group a new group
Add members of this group to the Yes —
existing Notes group
Create a new Notes group with the — Yes
following settings
Notes group name Read-only Yes
Group type Read-only Yes
Description Read-only Yes
Add nested groups contained in this Yes* Yes *
group and their members
Add people contained in nested Yes** Yes **
groups as Notes users
Use above settings for all currently Yes Yes
selected or nested groups (don’t
prompt again)
Cancel Yes Yes
Cancel All Yes Yes
Note Read-only fields have values that you cannot edit in the Group Migration
Options dialog box. You can edit these fields in the Group document.
*Available if you select the “Add members of this group to the existing Notes
group” check box or “Create a new Notes group with the following settings”
check box.
**Available if you clear the “Add members of this group to the existing Notes
group” check box or the “Create a new Notes group with the following settings”
check box.
In addition to the settings in the Group Migration Options dialog box,
you can also set an option to migrate empty groups. See the topic
“Allowing the addition of empty groups to Notes” later in this chapter
for more information about migrating empty groups.
Note After a migration completes, always review any resulting Group
documents to ensure that they contain the expected members.
Add members of this group to the existing Notes group

If you use an existing group to migrate groups with duplicate names, the
Group Migration Options dialog box displays the “Add members of this
group to the existing Notes group” check box, which is selected by
default. When the check box is selected, Domino Upgrade Services add
members of the migrating group to the existing Notes group. After you
click OK to close the dialog box, the “People/Groups to migrate list”

displays the name of the migrating group, as well as the names of local
users in the group. During registration, migrated users will be added to
the existing Notes group.
Clear the check box if you do not want to add users in the migrating
group to the existing Notes group. The names of local users in the
migrating group will appear in the “People/Groups to migrate list.”
During registration, migrated users are not added to the existing Notes
group.
Create a new Notes group with the following settings

When the name of a migrating group is unique among the groups in the
Domino Directory, the Group Migration Options dialog box displays the
option “Create a new Notes group with the following settings.”
By default, this option is selected and the migration tool will create a new
Notes group that has the name of the migrating group, and includes the
local users of the original group, as well as any nested groups and their
available members. You can edit the default information in the following
fields:
• Notes Group Name
• Group Type
• Description
When you create a new Notes group for a migrating group, you can also
migrate nested groups that are members of the group. By default, the
option Add nested groups contained in this group and their members is
selected.
If you clear the check box, you migrate local users of the group, but you
do not create a new Notes group based on the group. Local users become
Notes users, but are no longer members of the group.
When you clear the check box, you cannot migrate nested groups that are
members of this group. However, you can migrate users who belong to
such nested groups by selecting the option Add people contained in
nested groups as Notes users.
Specifying a name, group type, and description for migrated groups

When creating a new Notes group from a migrated group, you can
specify the name and type of the group, as well as provide an optional
description of the group. You cannot modify this information if you are
adding the migrating group to an existing Notes group.
10-8 Upgrade Guide

Notes Group Name
This field displays the name that the migration tool will assign to an
imported group. When creating a new Notes group from an imported
group, you can retain the original name or specify a new name. By
default, imported groups retain their original names, which appear in the
Notes Group Name field. To rename the imported group, enter a new
name in this field.
You can edit the group name only if you are creating a new Notes group
for a migrating group. By default, imported groups retain their original
names. For example, if you import a cc:Mail group called #admins, a
Notes group created from this group would also have the name #admins.
You cannot edit this field if the group is an existing Notes group, or if
you clear the check box “Create a new Notes group with the following
settings.”
Group type
If you create a new Notes group for a migrating group, you can edit the
Group Type. You can create any of the following types of Notes groups:
•
Mail only
• Access Control list
• Multi-purpose
• Deny list only
For more information about creating and modifying groups, see the book
You cannot edit the Group type field if the group is an existing Notes
group, or if you clear the check box “Create a new Notes group with the
following settings.”
Description
This field displays an optional description of the imported group, which
the migration tool adds to the Description field of the Notes Group
document. By default, if the imported group has description information
available, it appears in this field.
You can edit the description only if you are creating a new Notes group
for a migrating group. You cannot edit this field if the group is an exist-
ing Notes group, or if you clear the check box Create a new Notes group
with the following settings.

Migrating nested groups
A group that is a member of another group, is said to be nested within
that group, and is considered to be a nested group. Groups may be nested
hierarchically, with each nested group containing one or more additional
nested groups. For example, the groups #IS Managers may have as a
member the group #admins, which includes the group #po admins, which
includes the member #po backups, and so forth.
You can only migrate a nested group if you are migrating its parent
group. Regardless of whether you add the main group, you can still add
users in the nested groups.
There are two options related to migrating nested groups:
• Add nested groups contained in this group and their members
• Add people contained in nested groups as Notes users
“Add nested groups contained in this group and their members”
check box
By default, when you migrate a group, the check box “Add nested
groups contained in this group and their members” is selected and
Domino Upgrade Services add all members of a migrating group, includ-
ing other nested groups and their local users, to the “People/Groups to
migrate list.”
For example, if you are migrating a group #IS Managers, which includes
the group #admins, which includes the group #po admins, and you select
the option “Add nested groups contained in this group and their
members,” all three groups (#IS Managers, #admins, and #po admins) and
all their members are added to the “People/Groups to migrate list.”
Clear the check box if you do not want to add nested groups or their
users to the “People/Groups to migrate list.”
This field is not available if you clear the “Add members of this group to
the existing Notes group” check box or the “Create a new Notes group
with the following settings” check box.
“Add people contained in nested groups as Notes users” check box

Select this check box if you want to migrate local users in a group’s
nested groups, without migrating the parent group. By default, the check
box is cleared.
After you click OK, Domino Upgrade Services add users in all of a
group’s nested groups to the “People/Groups to migrate list.”
10-10 Upgrade Guide

This field is not available if you select the “Add members of this group to
the existing Notes group” check box or the Create a new Notes group
with the following settings check box.
Migrating groups with common members

In some situations, a user or group in a migrating group hierarchy may
be a member of more than one group in the hierarchy. When migrating
nested groups, Domino Upgrade Services ignore duplicate occurrences
of users or groups. Items are added to Notes only once.
Use above settings for all currently selected or nested groups (don’t
prompt again)
If you have selected multiple groups to import, you may want to use the
same set of options for importing each group. Select this check box if you
want the settings in the Group Migration Options dialog box — create a
Notes group, import nested groups, and so forth — to apply to all
remaining groups currently selected for import, including any nested
groups. The settings do not apply to groups that have already been
processed or to groups that you select later.
Caution Do not use the same settings when migrating groups to a
combination of existing groups and new Notes groups. After you set the
“Use above settings for all currently selected or nested groups (don’t
prompt again)” option, Domino Upgrade Services do not display the
Group Migration Options dialog box again as it continues processing any
remaining selected groups, so you cannot specify how to create or add
members to those groups. As a result, Domino Upgrade Services will
create any new groups using their original names, which may lead to the
creation of duplicate Notes groups.
Canceling migration of a group

From the Group Migration Options dialog box, you can cancel the opera-
tion by clicking either of the following buttons:
• Cancel
• Cancel All
Cancel
Click Cancel if you decide not to migrate the group specified in the Notes
Group Name field. The migration tool skips the current group and its
nested groups and proceeds to the next selected group. Neither the
current group nor any of its members are added to the “People/Groups
to migrate list.”

Cancel All
Click Cancel All if you decide not to migrate the group specified in the
Notes Group Name field, any of its nested groups, or any of the other
currently selected groups. Domino Upgrade Services close the Group
Migration Options dialog box and stops processing groups that remain to
be processed among those currently selected. No items in the current
group or its child groups are added to the “People/Groups to migrate
list.”
Adding users to a ‘migration’ group

Before migrating users, consider creating a Notes group, called Migrate-
dUsers, and adding everyone you migrate to this group during registra-
tion. Creating such a group provides you with an easy way of identifying
migrated users later on, when sending out upgrade notification messages
or other information related to the migration.
For more information about sending an upgrade notification message,
see the chapter “Migrating Personal Mail Data.”
Setting migration options

You can set options on the People and Groups Migration dialog box to
specify how information in the source directory is imported into the
Domino Directory and Notes mail file. The options you set apply to all
users imported from the current directory source during this session.
You can select a different set of options for each directory source you
import from during the session.
The items available in the Migration Options list depend on the foreign
directory source selected. The following import options are available:
• Generate random passwords for users with no passwords
• Generate random passwords for all users (overwrite existing
passwords)
• Add full name provided to the Notes person document
• Allow addition of empty groups to Notes
• Convert mail
• Add administrator to mail file access control list
• Convert mail ONLY (Notes users and mail files must already exist)
10-12 Upgrade Guide

Generating random passwords during migration
For user registration to complete successfully, the password specified for
the user must meet the minimum password quality requirements set in
the registration preferences. If a user’s password does not conform to the
requirements, you must modify it before you can register the user.
For additional information about the password quality scale, see the
By default, Domino Upgrade Services that import passwords automati-
cally set the Notes password to a user’s existing password. Domino
Upgrade Services for Windows NT and for Active Directory do not
import a user’s existing password.
Domino Upgrade Services provide the following options to automatically
create passwords for migrating users who either do not have passwords
or for whom you prefer not to import existing passwords:
• Generate random passwords for users with no passwords
• Generate random passwords for all users (overwrite existing
passwords)
Users for whom you create new Notes passwords can change their
password using the Notes client. The password they create must conform
to the quality scale set at registration.
Giving passwords to new users

To make it easy for you to give migrated users their new passwords the
first time they log in to Notes, the Domino Administrator maintains a
record of generated passwords. Password information for migrated users
is stored in the database NTSynch45.nsf in the Notes Data directory.
You can also maintain a record of generated user passwords by setting a
registration option to keep successfully registered users in the queue.
Keeping users in the registration queue after registration lets you
automatically store password and other registration information for
migrated users. After registration, you can select users in the queue and
view their password information.
For information about how to keep users in the registration queue, see
the topic “Saving pending registrations in the registration queue” later in
this chapter.
Generate random passwords for users with no passwords

For users who have no existing password to import, or whose passwords
Domino Upgrade Services cannot import (Windows NT users, for
example), Domino Upgrade Services provide an option to generate a

random password that conforms to the specified password quality scale.
The default setting for this option differs for each Domino Upgrade
Service. When using this option, passwords are only generated for users
if the password field is empty; generated passwords do not overwrite
passwords imported from the legacy system.
This option and the option “Generate random passwords for all users
(overwrite existing passwords)” are mutually exclusive. If you select one
of the options and then attempt to select the other, an error message
appears.
Note In the current release, the cc:Mail Domino Upgrade Service does
not support the option “Generate random passwords.” To successfully
migrate a user’s cc:Mail mail box, you must provide a cc:Mail password
for the user. Use the cc:Mail administration tool to create passwords for
users before migration.
Generate random passwords for all users (overwrite existing

passwords)
Select this option to generate new random passwords for all migrating
users, regardless of whether they already have a password available for
import from the legacy directory. The migration tool generates pass-
words that conform to the password quality scale specified in the current
registration preferences. If a migrating user already has a password
imported from the legacy system, the new password overwrites it.
This option and the option “Generate random passwords for users with
no passwords” are mutually exclusive. If you select one of the options
and then attempt to select the other, an error message appears.
Add full names provided to the Notes person document

The User name field of a Person document lists one or more full names
— as opposed to name components like first and last name — by which a
user is known in Notes. For a registered user, the first name listed in this
field, the primary Notes name, is a hierarchical name based on the certi-
fier ID used to register the user, and is the name checked when authenti-
cating a user’s right to access Domino resources. In addition to this
primary name, the User name field can contain secondary entries, which
serve as aliases for the user and can be used in addressing mail.
Domino Upgrade Services import full names for use as secondary Notes
names from the following fields in each source directory:
• cc:Mail — User name
• Microsoft Mail — Friendly, or display name
• Microsoft Exchange — Display name
10-14 Upgrade Guide

• Windows NT — Full name
• LDIF — Distinguished name
• LDAP — Distinguished name
• Microsoft Active Directory — Display name
Note If you migrate information for a user, but do not register the user,
the imported full name may become the primary entry in the User name
field.
Add administrator to a mail file access control list

By default, when you create a mail file for a user during migration, your
administrator ID is temporarily placed in the ACL of the new mail file and is
assigned Manager access. After the migration completes and the migrated
user is successfully registered in Notes, the administrator ID is removed
automatically from the ACL and replaced with the name of the mail file
owner. At this point, only the mail file owner can open the mail file.
Note If you are migrating user mail boxes and choose to retain the
default mail file ACL during migration, the administrator ID remains in
the ACL as Manager if the mail box conversion fail.
You may need manager access to the mail file to perform additional tasks.
For instance, you may need to convert additional messages for users after
you migrate them to Notes and create their Notes mail files. However,
under the default mail file ACLs, you do not have the level of access
needed because your ID has been removed from the mail file ACLs.
If you anticipate needing to perform such a secondary migration, when
you first select users to migrate, select the migration option “Add adminis-
trator to mail file access control list” from the list on the People and Groups
Migration dialog box. This option changes the default mail file ACL so that
the administrator retains Manager access to the mail file. The owner of the
mail file also remains in the ACL with the default Manager access.
Note This option adds the administrator ID to the ACL of every mail
file you create during the migration process, regardless of whether any
messages are migrated.
Allow the addition of empty groups to Notes

Groups selected for import are considered empty if they do not contain
any members who can be registered in Notes. By default, Domino
Upgrade Services do not import empty groups. A group may be empty
because it contains no members — for example, an obsolete group that
was never removed from the address book; or the group may not contain
any local users — for example, an e-mail distribution list that lists only
the Internet addresses of users on other mail systems.

Migrating a group whose members are not available — and that would
therefore, be empty — results in an entry in the Domino Directory that
serves no useful purpose. Set this option only if you intend to add users
to any empty groups either during registration or after registration
completes.
Convert mail
By default, Domino Upgrade Services for cc:Mail, Microsoft Mail, and
Microsoft Exchange convert existing mail files into Notes mail files.
During the registration process, if you choose to convert mail, Domino
Upgrade Services automatically convert mail files on the old system to
Notes mail files.
Mail files are created on the server that is specified in your registration
preferences. If the Domino Upgrade Service cannot create a user’s mail
file for any reason - for example, if the specified mail server lacks suffi-
cient disk space - the user remains unregistered and an error is logged.
Because mail conversion requires mail files to be created immediately,
you cannot choose the option on the Mail pane of the Register Person
dialog box to create mail files using a background process (adminp). An
error message is displayed if you attempt to select this option.
Note The options “Convert mail” and “Convert mail ONLY” are
mutually exclusive. An error message appears if you select one of these
options and the other is already selected.
Convert mail ONLY

Domino Upgrade Services for cc:Mail and Microsoft Mail provide the
option to convert mail only. This option is not available in the Microsoft
Exchange Domino Upgrade Service. Select this option if you want to
migrate additional mail messages for users who are already registered in
Notes. By default, this option is not selected.
For the selected users, Domino Upgrade Services migrate only those
messages that were not previously migrated. Notes IDs are not created
and the Domino Upgrade Services do not modify the users’ Person
documents.
For example, you have created a Notes account and mail file for Mark
Richards, a cc:Mail user. Mark receives additional mail in his cc:Mail
mail box, and you need to migrate these messages and folders to his
existing Notes file, while preserving his Notes messages and folders. You
can migrate Mark’s new cc:Mail messages using the “Convert Mail
ONLY (Notes users and mail file must already exist)” option.
10-16 Upgrade Guide

You can use the “Convert Mail ONLY” option only if the users selected for
import in the Available people/groups dialog box are already registered
Notes users. Furthermore, if you use this option to convert additional mail
for migrated cc:Mail users, the users’ cc:Mail names must exist as secon-
dary entries in the User name field of their Person documents.
When this option is enabled, the migration tool processes only mail infor-
mation, regardless of the other migration options you have set.
Note The options “Convert mail” and “Convert mail ONLY” are
mutually exclusive. An error message appears if you select one of these
options and the other is already selected.
Access rights required to migrate mail to an existing mail file

To migrate mail to an existing mail file, you must have Manager access in
the ACL for the file. However, by default, only the owner of the mail file
has Manager access. When you first migrate users, consider whether you
may need to migrate additional messages for these users later. If so,
modify the default access rights that apply to the user’s mail file.
For information about how to modify the default access rights when
creating a mail file during migration, see the topic “Add administrator to
a mail file access control list” later in this chapter.
Registering users and migrating messaging data

After you import users from the old system into the registration queue,
they are available for registration. After users are registered in Domino,
they can log in and access resources on the Domino server, including
mail files. You can register users on a single Domino server or distribute
them among multiple servers.
For each user selected for registration, Domino automatically creates a
Notes ID using the certifier ID specified and if applicable, migrates the
mail data from the legacy messaging server to Notes mail files. Messag-
ing data stored in locations other than the old messaging server is not
migrated.
Domino Upgrade Services import some registration information, such as
user names and passwords, from the old system. You can specify
additional registration information as necessary.
For more information about setting up users in Notes, see the book

Specifying where to register imported users
When registering imported users, you are not required to place them on
a single server or within a single organizational unit. You can specify the
registration server, mail server, and certifier ID to use in registering each
user in the queue.
For more information about specifying registration information, see the
Determining the reason for failed registrations

If you attempt to register a user and the registration fails for any reason,
the entry remains in the queue, and the status indicates the reason for the
failure. You can modify the registration information as necessary and
attempt to register the user again later.
Importing passwords
When importing a user for registration, Domino Upgrade Services
compare the length and complexity of the user’s existing password
against the specified password quality scale. If the existing password
does not meet or exceed the standards for the given password quality
scale, the registration status will indicate that the user’s password needs
to be modified before successful registration can occur.
Domino Upgrade Services for Windows NT and for Active Directory do
not import passwords from a domain list.
For additional information about the password quality scale, see the
You can modify the passwords of users in the registration queue as
necessary. Select the user in the Registration status box, edit the
password in the Basics pane, and click Apply to update the status.
Specifying advanced person registration options

After importing users and groups, you can specify options that deter-
mine how Notes processes information when registering users.
You can select the following registration options:
• Do not continue on registration errors
• Keep successfully registered people in the queue
• Try to register queued people with error status
• Allow registration of previously registered people
In addition, you can configure the registration process to proceed as
follows if the user being registered has the same user name or mail file
name as an existing person:
10-18 Upgrade Guide

• Skip registration when the name of a new Notes user or mail file
matches those of an existing user
• Update an existing person with the information for the migrated user
• Replace an existing mail file with the migrated mail file
• Generate a unique mail file name
Note If you choose to create a user’s mail file in the background
using adminp, the option to replace an existing mail file is ignored
for migrations that do not involve converting mail.
By default, none of these options is enabled. The options you select apply
to all users selected for registration in the current session.
For more information about setting registration options, see the book
Setting registration defaults

When registering migrating users, you must specify several registration
settings. Although some of these settings, such as mail file name or Inter-
net address, are specific to an individual user, there are also a number of
public settings, such as mail server or password quality scale, that can be
applied to multiple users.
Rather than having to specify the same registration information for each
new user, you can specify default settings for public registration informa-
tion. After you set registration defaults, Domino Upgrade Services
automatically apply these defaults to each user they add to the registra-
tion queue.
Pay particular attention to the default settings for registration server and
mail server. If the computer on which you are running the Domino
Administrator is not the Domino server, you must change the default
setting of Local for these servers. Depending on your security needs, you
may also want to apply a new default setting for the password quality
scale required for the users you migrate.
You can create default registration settings using either of the following
methods:
• Setting Administrative preferences
• Defining settings through user registration
Setting Administrative preferences
Registration settings that you define through the administrative prefer-
ences are used as the defaults at the start of each registration session. You
can override them by setting new defaults for a session, but they go into
effect again the next time you start a new session.

For additional information about setting Administration preferences, see
Defining default settings through user registration

If you have already registered users, the public settings used in register-
ing the last user become the defaults for the next user. You can also set
registration defaults before you register any users from within the Regis-
ter Person dialog box, using the following procedure:
1. From the Domino Administrator, click People — Register, and enter
the password for the certifier ID to open the Register Person dialog
box.
When you first open the Register Person dialog box, it is set to accept
new entries, as indicated by the words “Register Person - New
Entry” on the title bar.
2. Click the Advanced check box at the top of the dialog box to display
all of the available selection panes.
3. Select each pane in turn, changing the registration settings on each
pane to the desired default values. Leave the name information (First
name, Middle name, and Last name fields) on the Basics pane blank.
4. Click “Migrate people” to open the “People and Groups Migration”
dialog box and begin migrating users.
The public registration settings defined during the preceding steps
apply to all users you migrate to the registration queue during this
session. After you exit the “People and Groups Migration” dialog
box, the registration settings revert to those defined in the current
administrative preferences.
Saving pending registrations in the registration queue

Domino Upgrade Services automatically place users imported for regis-
tration in a special database known as the registration queue. The regis-
tration queue stores the registration information set for each user and
reports the status of each pending registration.
The names of users currently in the registration queue appear in the
Registration status box on the Register Person dialog box. Groups
selected for migration do not appear in the registration queue.
Users remain in the queue until registered or specifically removed. If you
have users in the registration queue and you are unable to complete the
registration, you are prompted to save the users for later registration
when you exit the Register Person dialog box. After the interruption, the
user data remains intact so you can continue the process where it left off.
10-20 Upgrade Guide

Note If the users in the queue at the time you exit registration are pending
registration with different organization certifiers, you must supply each
certifier ID and password when you re-open the Register Person dialog box.
You can set a registration option to keep users in the queue after
registration.
For additional information about setting registration options, see the
Applying registration settings to multiple users

You can apply some registration settings to multiple users at one time.
The following table shows the settings for each pane of the Register
Person dialog box that you can modify when multiple users are selected
in the registration queue.
Basics pane Registration Server

Password options
First, Middle, and Last Names
Short Name
Password
Mail System
Explicit policy
Let this person roam
Create a Notes ID for this person
Mail pane Mail system
Mail file name
Mail server*
Mail file owner access
Create file now/Create file in background
Mail file template*
Mail file replicas
Set mail database quota
Set warning threshold
Create full text index
Address pane Internet address
Internet domain
Address name format and separator
continued

ID Info pane Certifier ID
Security type
Certificate expiration date
ID file location
Groups pane Assign person to groups
Roaming pane Put roaming user files on mail server
Roaming server
Personal roaming folder
Sub-folder format
Creating roaming files now/Create roaming files in
background (using the Administration Process)
Create replicas
Roaming user client clean-up options
Other pane Setup profile
Unique org unit
Location
Local administrator
Comment
Alternate name language
Windows user options
*The mail server and mail template settings are interdependent. If multiple users
are selected and you change one of these settings, the current value of the other
setting is applied to all of the selected users.
For more information about advanced registration, see the book
Creating Notes mail files

In the mail pane of the Register Person dialog box, you specify the type of
mail file to create for a user — with the standard Notes mail template,
iNotes Web Access template, or a customized mail template — and
whether to create the file now or to let the Administration Process create it
later. To create Notes mail files for migrated users, you must create the
file now. Notes mail files must be created during the registration process;
you cannot choose to create them in the background with the Administra-
tion Process.
10-22 Upgrade Guide

Setting mail database quotas
When migrating a user’s mail file, Domino Upgrade Services ignore the
size restrictions specified in the mail database quota field. Imported mail
files continue to receive mail after registration, regardless of the specified
size restrictions. To enforce size restrictions on a mail file, you must set a
limit after the initial user registration and enable enforcement of database
limits in the Configuration Settings document for the server. If size
checking is enabled, the user cannot receive mail if it would result in the
quota being exceeded.
Migrating duplicate messages

Mailboxes in the old mail system may contain duplicate copies of a
message, one in each of several folders. After migration, duplicate messages
may display in multiple Notes views, corresponding to the folders on the
legacy system, but only a single copy of the message is migrated.
Users migrating from other systems should understand how message
storage works in Notes. On mail systems that use true folders to store
messages, copying a message from the Sent folder to another folder
creates a duplicate copy of the message.
A Notes mail file, by contrast, stores messages in a single database that
has multiple folder views. Each view of the database displays messages
based on a set of selection criteria, such as sent messages. However,
although a message may display in several views, Notes maintains only a
single copy of it in the mail file database.
In particular, users should be careful about deleting messages from the
Notes Sent view. Although a message in the Sent view can be displayed
in other secondary views, it cannot be moved out of the Sent view. Delet-
ing it from the Sent view removes it from all other views.
Migrating folders and subfolders

Folders in a Notes mail file behave differently from folders in the
mailboxes on other systems. In some cases, folder names may be
truncated during migration and nested folders are not migrated to the
same location in the folder hierarchy as in the source mail file.
Subfolders in the Inbox and Sent folders

The Notes Inbox and Sent mail views cannot contain subfolders. As a
result, subfolders in the Inbox or Sent folders of a legacy mailbox are
converted to top-level folders in the Notes mail file during migration.
Maximum length for folder names

A Notes folder name cannot exceed 64 characters. During migration,
folder names longer than 64 characters are truncated.

Maximum length for subfolder names
Notes mail files support the use of hierarchical, or nested, folders. In the
folder hierarchy, the subfolder name includes the name of its parent
folders. For example, in the following folder hierarchy:
Projects/1998/Q3/July/Letters
Notes considers the full name of the Letters subfolder to be 25 characters
long, because it includes the names of the Projects, 1998, Q3, and July
folders.
If the complete path for a subfolder (that is, the name of the subfolder
and all of its parent folders) contains 64 characters or fewer, the folder
hierarchy is migrated intact. However, subfolder paths that contain more
than 64 characters are shortened during migration. Domino Upgrade
Services replicate the path up to 64 characters, truncating the name of the
last subfolder created, if necessary. The remaining subfolders are not
migrated, but the messages in them are migrated to the last subfolder
that was migrated.
So, for example, if a subfolder in the source mail file is nested seven
levels deep and the path name for a subfolder nested four levels deep
exceeds 64 characters, then the migration tool creates folders 1 through 3,
preserving the existing folder hierarchy. Folder 4 is also created in its
original place in the hierarchy (nested within folder 3), but its name is
truncated. All of the messages contained in the folders nested within
folder 4 (folders 5 through 7) are migrated to folder 4.
Verifying that a migration was successful

After a migration completes, perform the following tasks to verify that
the migration was successful:
• Check the Pending Registrations box to see if users in the queue were
registered successfully
• Search the Miscellaneous Events view of the Notes Log for
indications that users could not be registered
• Check the contents of users’ Notes mail files
• Test access to mail and mail transfer for migrated users
• Review membership of migrated groups to ensure they contain valid
entries
After you determine that the migration was successful, you can prepare
users to migrate locally-stored messaging data with the upgrade wizard.
For information about migrating users’ personal mail data to Notes, see
the chapter “Migrating Personal Mail Data.”
10-24 Upgrade Guide

Chapter 11
Migrating Users from cc:Mail
This chapter discusses issues involved in migrating users from cc:Mail to

Lotus Notes 6 and provides instructions on using the Domino Adminis-
trator and the cc:Mail Domino Upgrade Service to complete the
migration.
Migrating cc:Mail users

Using the cc:Mail Domino Upgrade Service in the Domino
Administrator, you can import cc:Mail users and groups from a selected
post office and register them as Notes users. The migration process:
•
Imports local users and groups from the post office (users in the
directory whose locations are designated as “L” for local or “R” for
mobile) and creates entries for them in the Domino Directory
• Lets you create a Notes ID and mail file for imported users
• Migrates the contents of mail boxes from the cc:Mail post office
server
• Converts Organizer 2.x for cc:Mail Group Scheduling files (OR2 files)
into Notes group scheduling format (NSF)
The cc:Mail Domino Upgrade Service supports migrating users of the
cc:Mail 6.3x client. After the migration completes, the cc:Mail 6.3x client
accesses a mail file on the Domino server, rather than a mailbox in the
cc:Mail post office.
If you want to migrate mail boxes for a cc:Mail mobile post office, you
must first archive the messages and then migrate them using a separate
user upgrade wizard.
For more information about using the upgrade wizard, see the chapter
Refer to the following topics for information on moving users from
cc:Mail to Lotus Notes:
• Supported cc:Mail versions
• Preparing to migrate cc:Mail users
11-1
• Migrating cc:Mail data to Notes
• Migrating cc:Mail Organizer information
• Migrating users in a mixed environment
Supported cc:Mail versions

There are two versions of the cc:Mail LAN post office database in use.
They are commonly referred to as DB6 and DB8. The cc:Mail Domino
Upgrade Service lets you migrate data from either database version.
Upgrading from either version of the cc:Mail post office extracts informa-
tion from the following:
cc:Mail post office directory — The directory contains public post office
information, including the post office name and directory entries, public
mailing lists, and bulletin boards. This file contains a list of all user file
numbers and pointers to all messages in the message file.
Message file — The message file stores one copy of each message for all
users in the post office. To save disk space, messages addressed to multi-
ple users are stored just once in this file.
Post office user files — The user files contain all private mailbox infor-
mation, such as lists and folders. These files contain no messages, just
pointers to the mail directory and message files.
Organizer 2.x group scheduling files (OR2 files) — For cc:Mail users
who use Lotus Organizer 2.x, the OR2 files contain calendar and schedul-
ing information.
Notes equivalents for migrated cc:Mail information

The cc:Mail Domino Upgrade Service converts information in a cc:Mail
post office to a Notes mail file, including mail boxes, messages, bulletin
boards, and private and public directories, as shown in the following
table. In addition, you can optionally migrate users’ Organizer 2.x group
scheduling files (OR2 files).
For information about migrating Organizer group scheduling files, see
the topic “Migrating Organizer information” later in this chapter.
11-2 Upgrade Guide

These items in the cc:Mail Are migrated to these items in the
mailbox . . . Notes mail file . . .
Archives Not migrated*
Bulletin boards Discussion databases
Bulletin board messages on mobile post Not migrated
offices
Clipboard folder Not migrated
Folders and subfolders Folders and subfolders **
Message date Message date
Message priority Message priority***
Messages and attachments in migrated Messages and attachments****
folders
Mobile sessions log Not migrated
Organizer data (OR2 files) Entries in mail file, Personal Journal,
and Personal Address Book
Password Password
Post office directory Domino Directory
Private mailing lists Group documents in Personal
Address Book+
Public mailing list Group document in Domino
Directory
Read and unread marks Not migrated++
Return receipts Return receipts
Rules Not migrated
Sender and recipient information Sender and recipient information
Trash folder Not migrated
Undeliverable mail reports Not migrated
*Archives are not migrated by the cc:Mail Domino Upgrade Service, but after
you migrate users, they can run an upgrade wizard at their workstations to
migrate their message archives.
**For cc:Mail 8 clients, the migration converts nested folders and the messages
they contain.
***The cc:Mail Domino Upgrade Service preserves message status in cc:Mail
messages marked Urgent (an exclamation mark appears beside the message in
the Notes Inbox or folder). However, Lotus Notes does not assign a special status
to migrated cc:Mail messages that were marked Low priority.
****During migration rich text attributes such as color, font style, font size,
underlining, boldface, bullets, embedded objects, and doclinks are not preserved.
Migrating Users from cc:Mail 11-3

+Private mailing lists are automatically sent to users in a Notes message
attachment. Users then run an upgrade wizard at their workstations to migrate
these lists to their Notes Personal Address Books. The upgrade wizard also
migrates private addresses that cc:Mail 2.x and 6.x clients maintain locally in the
file PRIVDIR.INI. The upgrade wizard does not support migrating private
addresses for cc:Mail 8.x clients.
++All migrated messages are marked unread.
For information about the user upgrade wizards, see the chapter
Notes equivalents for migrated Organizer information

The following table shows the Notes equivalents for migrated Organizer
information.
Organizer record type Equivalent Notes entry Comments

Address Business card in Mailed to user
Personal Address Book
Alarm Alarm*
Anniversary Calendar anniversary
Calendar appointment Calendar appointment
Call To Do task
Categories Category Migrates first category
listed only
Cost code — Not migrated
Group Scheduling meeting Calendar appointment
Included section — Not migrated
Link — Not migrated
Notepad page Personal Journal Mailed to user
Preference options — Not migrated
Planner event Calendar event
Repeating entry Repeating entry**
Rooms and resources — Not migrated
Pending meeting notices*** — Not migrated
To Do tasks To Do tasks
User preferences and — Not migrated
passwords
11-4 Upgrade Guide

*An alarm is migrated only if the resulting Notes record type also supports
alarms.
**Repeating items migrated to the Notes Calendar use the Lotus Notes 4.5 repeat
structure, not the 5.0 repeat structure. Repeating entries migrated to the Notes To
Do view appear as individual entries and no longer are designated as Repeating
nor do they include the repeating entry symbol.
***Meeting invitations are migrated only if a user has responded to them. Users
need to process any pending meeting notices they want migrated.
For more information about Organizer calls, see the topic “Migrating
Organizer Calls sections” later in this chapter.
Preparing to migrate cc:Mail users

To prepare for a successful cc:Mail migration, you must complete the
following types of tasks:
• General administrative tasks
• Lotus Notes and Domino preparation tasks
• cc:Mail preparation tasks
To complete some of these tasks, refer to the Lotus cc:Mail Administrator’s
Guide and to Administering the Domino System.
General administrative tasks

• Determine the order in which to migrate post offices. Use this order
to determine your migration schedule.
• Decide which types of cc:Mail and Organizer data to migrate.
Migrating certain types of data, such as bulletin boards and
Organizer information may require additional planning and
preparation.
For more information about the types of messaging data you can
migrate, see the topic “Specifying cc:Mail conversion settings” later
in this chapter.
• Estimate the amount of disk space required to migrate cc:Mail mail
boxes.
For more information, see the topic “Estimating the size of a
converted mailbox” later in this chapter.
• Decide how your cc:Mail gateways will map to Notes domains for
routing mail to external mail systems.

For more information about mapping cc:Mail gateways to Notes
domains, see the topic “Mapping cc:Mail gateways to Notes domains”
Lotus Notes and Domino preparation tasks

• If you did not perform a custom installation of the Domino
Administrator client that installed the cc:Mail Domino Upgrade
Service, run the Domino 6 Administrator client again and choose the
cc:Mail Domino Upgrade Service.
• From the Domino Administrator machine, map a drive to the
location of the cc:Mail post office you are migrating users from.
• Back up Domino information.
For more information, see the topic “Backing up Domino
information” later in this chapter.
• Log in to Lotus Notes with a Notes ID that has “Create database
access” on the Mail server.
• Verify that you have access to the certifier IDs and passwords for the
Domino organizations and organizational units where you are
registering users.
• Verify that you have Editor, Designer, or Manager access rights to
the Domino Directory on the Registration Server.
• If you anticipate migrating additional mail for users after
registration, configure the mail file ACLs to ensure that you retain
the appropriate access rights. Use the migration option Add
administrator to mail file access control list.
For instructions on how to change the default access level of a mail
file before migration, see the chapter “Overview of Domino Upgrade
Services.”
• (Optional) Set default registration preferences.
For more information about default registration preferences, see the
• (Optional) Create a Notes group that you can add migrated users to.
For more information about adding migrated users to a group, see
the chapter “Overview of Domino Upgrade Services.”
• From the Domino Administrator or from the Domino Administrator
machine, close all applications, except for Lotus Notes, and close any
Notes databases.
11-6 Upgrade Guide

cc:Mail preparation tasks
• Clean up the cc:Mail message store. Instruct users to archive or
delete mail that they no longer need. Consider limiting the amount of
mail that users can migrate.
• Clean up the post office directory.
For more information about cleaning up the post office directory, see
the topic “Preparing the directory for migration” later in this chapter.
• Familiarize yourself with how the cc:Mail Domino Upgrade Service
parses cc:Mail names formats. Certain name formats and characters
may not be converted correctly during migration. To ensure that all
migrated users are created with appropriate Notes names, it may be
necessary to edit certain names either before or after migration.
• Make sure all users being migrated have assigned passwords. If the
cc:Mail password is blank, null, or zero-length, the migration of the
user will fail. If you have a cc:Mail user with this type of password,
change it to a non-blank password in cc:Mail.
Note The cc:Mail Domino Upgrade Service does not support the
selection in the Migration Options box “Generate random passwords
for users with no passwords.”
• Take the post office off-line to make it inaccessible to users.
For more information about taking the post office off-line, see the
topic “Taking the post office off-line” later in this chapter.
• Send any in-transit cc:Mail messages. Post office mail queues are not
migrated. Clear all Post Office Message Queues and Router Express
calls with Send Only. Run Link products and run the Organizer
scheduling agent.
• Back up the cc:Mail post office being migrated. This backup
preserves the state the post office was in before you run the
maintenance utilities.
For more information about backing up the post office, see the topic
“Backing up the cc:Mail post office” later in this chapter.
• Verify the integrity of your post office by running regular
maintenance. See the Lotus cc:Mail Administrator’s Guide for more
information about using the cc:Mail maintenance tools.
• (Optional) Delete unnecessary messages in the cc:Mail Message Log,
Trash, and so forth, using the CHKSTAT command for DB6 or
MSGMGR for DB8. After deleting messages, run RECLAIM to
recover disk space from these deleted messages.
• Create a second backup of the post office that preserves the state the
post office was in after you ran the maintenance utilities.

• If you are also migrating Organizer information for users, prepare
users to upgrade Organizer information.
• After you complete the preparation tasks, migrate your Organizer
users first. When migrating Organizer data, add the Organizer users
to the registration queue before any other users.
Estimating the size of a converted mailbox

As you plan your migration from cc:Mail to Lotus Notes, you need to
know the amount of disk space needed to convert cc:Mail post offices to
Notes mail databases. There is no formula for calculating exactly how
much disk space a mailbox will require after it is converted to a Notes
mail file. However, you can estimate the size of a converted mailbox by
running a test migration and comparing the size of a cc:Mail mailbox
with the size of the resulting Notes mail file. cc:Mail provides the follow-
ing commands for measuring the size of mail boxes in a post office:
For a DB6 office
At the command prompt, enter the following command:
chkstat /N po_name /P po_password /D po_path /msgs/all
>output.txt
where po_name is the name of the post office; po_password is the post
office password; po_path is the network path to the directory where the
post office is located; and output.txt is the name of the file where you
want the report saved.
The report indicates the total number of bytes for each mailbox in the
post office.
For a DB8 post office
msgmgr /N po_name /P po_password /D po_path /U "username"
where po_name is the name of the post office; po_password is the post
office password; po_path is the network path to the directory where the
post office is located; and username is the name of the user whose mailbox
you are measuring.
The command displays the total size in kilobytes for the specified
mailbox. It does not generate a report.
11-8 Upgrade Guide

Preparing the directory for migration
The cc:Mail Domino Upgrade Service converts user names in the cc:Mail
directory to Person documents in the Domino Directory. Before migra-
tion, prepare for directory conversion as follows to help minimize
processing time and errors:
• Remove inactive accounts from the post office directory
• Understand how the cc:Mail Domino Upgrade Service processes
cc:Mail names
Removing inactive accounts from the post office directory

For each cc:Mail post office being migrated to Lotus Notes, review the
contents of the cc:Mail directory and verify each account. Identify and
make a list of inactive accounts, for example, local accounts that were
created, but never used, or accounts for employees who have left the
company. To avoid processing invalid accounts, refer to this list when
you select users to import to Lotus Notes.
Generate a report of cc:Mail account usage as follows:
CHKSTAT po_name po_pass po_path STATUSERS/N >output.txt
DIRSTAT /N po_name /P po_pass /D po_path /DL /LU /LOG
output.txt
where po_name is the name of the post office; po_pass is the post office
password; po_path is the network path to the directory where the post
office is located; and output.txt is the name of the file to which you want
the report saved.
Understanding how the cc:Mail Domino Upgrade Service processes

cc:Mail names
When preparing to import names from the post office directory, keep in
mind how the cc:Mail Domino Upgrade Service processes cc:Mail direc-
tory entries to create Notes names and Person documents. You should be
familiar with the following naming issues:
• Differences between the characters allowed in cc:Mail and Notes
names
• How the cc:Mail Domino Upgrade Service parses cc:Mail names to
create Notes names
• Updating existing Person documents

Understanding how the cc:Mail Domino Upgrade Service parses
cc:Mail name formats
Unlike Notes names, which are made up of First name, Last name, and
Middle initial components, the cc:Mail directory stores names as a single
character string, including commas and spaces. The name format used
depends on the conventions established within the organization. For
example, the same user could be listed in the cc:Mail directory as either
Susan Salani or Salani, Susan.
In generating a Notes names from an imported cc:Mail name, the cc:Mail
Domino Upgrade Service first determines the format of the name, and
then parses the name into Notes name components.
If you do not want to accept a name generated by the cc:Mail Domino
Upgrade Service, you can edit the name after you add the user to the
Registration queue.
The following table shows how the cc:Mail Domino Upgrade Service
generates Notes names from common cc:Mail name formats:
Format of cc:Mail name Resulting Notes name components

Description Example Components Example
Single name ssalani Last name ssalani
First name <blank>
Middle name <blank>
First Last Susan Salani Last name Salani
First name Susan
Middle name <blank>
First Last1 Last2 Craig Van Horn Last name Van Horn
First name Craig
Middle name <blank>
First1 First2 Last Jo Anne Lordan Last name Anne Lordan
First name Jo
Middle name <blank>
First Middle Last Cheryl Lynn Last name Lordan
Lordan First name Cheryl
Middle name Lynn
First Middle initial Last Judy J. Kaplan Last name Kaplan
First name Judy
Middle name J.
continued
11-10 Upgrade Guide

Format of cc:Mail name Resulting Notes name components
First1 First2 Middle Jo Anne B. Last name Lordan
initial Last Lordan First name Jo Anne
Middle name B.
First Middle initial Last1 Craig R. Van Last name Van Horn
Last2 Horn First name Craig
Middle name R.
Last, First Salani, Susan Last name Salani
First name Susan
Middle name <blank>
Last1 Last2, First Van Horn, Craig Last name Van Horn
First name Craig
Middle name <blank>
Last, First Middle Malone, Derek Last name Malone
Kevin First name Derek
Middle name Kevin
Last, First Middle initial Rutherford, Last name Rutherford
Robin R. First name Robin
Middle name R.
Last1 Last2, First1 First2 Van Horn, Jo Last name Van Horn
Middle initial Ann B. First name Jo Ann
Middle name B.
Checking names for invalid characters

The only characters supported by Lotus Notes for registered user names
are: letters (including those with accents and other diacritical marks from
the ISO Latin1 character set), numbers, ampersand, apostrophe, hyphen,
period, space, and underscore. A cc:Mail name may contain characters
that are not valid for use in a Notes name. If you try to register a cc:Mail
user whose name contains other characters, the registration process
generates an error.
Note These character restrictions apply only to the primary names for
registered Lotus Notes users. Lotus Notes permits the use of invalid
characters in the names in Person documents for unregistered users, such
as those that the cc:Mail MTA adds to the Domino Directory, as well as in
secondary user names.
Although you can remove invalid characters by editing names in the
registration queue after you import the cc:Mail directory, you may want
to edit names before migration, using the administrative tool for your
cc:Mail post office.

Updating existing Person documents
In some cases, for instance, in environments where the cc:Mail MTA
passes mail between cc:Mail and Lotus Notes, users being migrated from
cc:Mail may already have Person documents in the Domino Directory.
The directory synchronization component of the MTA adds an unregis-
tered Person document to the Domino Directory for each user in the
cc:Mail directory.
When migrating users, it is recommended that you update existing
Person documents, rather than create new ones. Creating multiple Person
documents for a user can result in confusion and security problems. If
you inadvertently create a second Person document for a user, delete one
of the documents.
When you register a user, the registration process searches the Domino
Directory to find a Person document that matches the one the cc:Mail
Domino Upgrade Service created for the migrating user. Matches are
based on entries in the User name field of the Person document. The
registration process does not look for matching names in the short name
field or the name component fields.
For a registered Lotus Notes user, the primary entry in the User name
field is the Notes hierarchical name, which specifies the organization and
organizational unit (OU) that a user belongs to. For an unregistered
person, such as the directory listings created by the cc:Mail MTA, the
Person document does not contain a hierarchical name.
When you migrate cc:Mail users, the cc:Mail Domino Upgrade Service
automatically adds a hierarchical name to the Person document. The
registration process generates this hierarchical name by parsing the
cc:Mail name into Notes name components and appending OU informa-
tion from the certifier ID used during registration. If you edit the Notes
name components in the Register Person dialog box, Lotus Notes uses
the modified name components to create the hierarchical name.
Adding the cc:Mail name to the Notes Person document

When migrating users from a cc:Mail MTA environment, the “Add
cc:Mail name to Notes person document (required for cc:MTA)” option
in the Migration Options list of the People and Groups Migration dialog
box is selected by default. This option adds a user’s cc:Mail name as a
secondary entry in the user name field of the Notes Person document. As
a result, Domino Upgrade Services can find an existing Person document
created by the MTA that uses this name. If the cc:Mail name of the
migrating user matches the user name in a single document in the
Domino Directory, the cc:Mail Domino Upgrade Service prompts you to
update that document.
11-12 Upgrade Guide

If more than one matching document is found, the registration fails, and
the user remains in the registration queue. Review the matching
documents in the Domino Directory and modify names for the existing
users or the new user to eliminate duplication. For example, you may
need to add middle names to distinguish between users.
Suppressing prompts to update matching Person documents

By default, if the registration process finds a Person document in the
Domino Directory that matches one generated for a migrating user, it
prompts you to update or skip the registration. If you want to automati-
cally update or skip the matching documents, follow this procedure to
suppress these prompts.
1. When you are ready to register users, click Options on the Register
Person dialog box.
2. In the Advanced Person Registration Options dialog box, select
“Don’t prompt for a duplicate person.”
3. From the drop-down box, select “Update the existing address book
entry.”
Taking the post office off-line
To ensure that the post office remains inactive while you perform the
cc:Mail migration, take the post office off-line by changing the directory
name and revoking users’ rights to the directory.
Do not shut down the post office. The cc:Mail Domino Upgrade Service
uses the Mail Engine API (MEAPI) to communicate with the post office.
If the post office is shut down, MEAPI cannot access it, and the migration
will fail.
If a post office is shut down, the file CCPODOWN is created within the
directory containing the post office data. Delete the CCPODOWN file, if
it exists.
Backing up the cc:Mail post office

After you take the post office off-line, back up the post office directory.
During migration, the cc:Mail Domino Upgrade Service may modify post
office data when:
• Migrating Organizer information
• Using the cc:Mail MTA to provide coexistence between cc:Mail and
Lotus Notes
Having a backup lets you safely restore the post office to its original state
if you encounter errors during the migration. Back up the entire post
office directory before you begin the migration.

Backing up Domino information
Before you migrate cc:Mail users, it is recommended that you back up
the following Domino information:
• NAMES.NSF
• DESKTOP.DSK
• NOTES.INI
• *.ID files
You can restores these files from the backups in case an error occurs
during migration.
Migrating Organizer information

When migrating mail boxes for cc:Mail users, you have the option to also
convert their Lotus Organizer 2.x Group Scheduling information (OR2
files) into Notes data. By default, this option is enabled, and Organizer
information will be migrated, if it exists and your workstation is
connected to the appropriate Organizer data directories.
If you migrate Organizer information, the cc:Mail Domino Upgrade
Service converts information from the available OR2 files of all selected
cc:Mail users. If you want to migrate Organizer information for only a
subset of users in the post office, you must migrate users in multiple
sessions, migrating users whose Organizer data you want to migrate in
one session, and users whose Organizer data you do not want to migrate
during a later session.
Organizer information is migrated to locations in the Notes mail file,
Personal Journal database, and Personal Name and Address Book. Some
Organizer data is not migrated; the cc:Mail Domino Upgrade Service
only reproduces the Organizer views and documents that have appropri-
ate equivalents in Lotus Notes.
Note The cc:Mail Domino Upgrade Service migrates data from
Organizer 2.x for cc:Mail for Windows only; it does not migrate data for
standalone OR2 files, Notes Calendar and Scheduling versions of OR2
files, or the Organizer PIM version (all other ORx files). Also, the cc:Mail
Domino Upgrade Service does not support the migration of Organizer
information from a Japanese-language post office.
During the migration, Organizer creates temporary Views and internal
notes in the Notes mail file, and Organizer group scheduling information
from cc:Mail is temporarily propagated to the Comments field of the
Lotus Notes user’s Person document. After the migration completes,
these items are deleted.
11-14 Upgrade Guide

Errors encountered during the migration are recorded in the log file
(LOG.NSF) of the computer running the Domino Administrator.
After you migrate a user’s OR2 file, the user can no longer open the file
in Organizer 2.x. Also, other users can no longer view the Organizer free-
time schedules for migrated users or send scheduling messages to the
user’s Organizer Agent. However, migrated users can use e-mail to
schedule and respond to invitations if you configure automatic forward-
ing from their old cc:Mail accounts to their new Notes mail accounts.
Determining the character set (code page) for migrating Organizer

data
When migrating Organizer data, the cc:Mail Domino Upgrade Service
uses the character set (code page) that you specify for migrating data
from the cc:Mail post office. You select the code page when specifying
conversion settings in the cc:Mail Upgrade Advanced Settings dialog
box.
For more information about setting the code page when migrating
cc:Mail data, see the topic “Specifying the code page to use for
converting cc:Mail data” later in this chapter.
Migrating multiple sections of one type

The cc:Mail Domino Upgrade Service merges multiple Organizer
sections of a given type into a single Lotus Notes equivalent. For
example, if the user has more than one To Do section in Organizer, the
cc:Mail Domino Upgrade Service combines them into a single Notes To
Do list. Similarly, multiple instances of Address, Anniversary, Calendar,
Calls, Notepad, and Planner sections are merged into a single Lotus
Notes equivalent.
Supplying a password when migrating Organizer data

Lotus Notes requires you to authenticate a process before it runs.
Because the Organizer migration is a separate process, before you can
complete an Organizer migration and register users, you must supply a
Notes password. The cc:Mail Domino Upgrade Service prompts you for
a Notes password when it is ready to register the first cc:Mail user for
whom you selected the option “Convert Organizer .OR2 scheduling files
to Notes.” You are prompted for the password only once during the
session.
Users are registered in the order in which you added them to the regis-
tration queue. If there is Organizer data to migrate for those users who
are at the beginning of the registration queue, the cc:Mail Domino
Upgrade Service prompts you for the password immediately after you

click the Registration button. However, if the first block of users being
registered does not include an Organizer migration, the password
prompt appears later. The migration process stops until you enter the
password.
Migrating Organizer category information

In Organizer, a user can assign multiple categories to entries in the
Address, Calendar, Calls, Notepad, or To Do sections. However, Lotus
Notes supports only single categories. As a result, the cc:Mail Domino
Upgrade Service assigns only the first category listed for an Organizer
entry to the resulting Notes entry.
Notes Journal entries do not have a field for displaying category informa-
tion. Users can view migrated category information by opening the
document properties for the journal entry.
Migrating Organizer meeting information

Scheduled meetings in a user’s Calendar section are converted to
personal appointments in the user’s Notes Calendar. Status information,
and information about the meeting Chair and Attendees are migrated to
the Detailed description field of the Appointment document. The infor-
mation migrated to this field depends on whether the user is the meeting
Chair or a meeting Attendee. For a meeting Chair, the complete list of
attendees is migrated. For an Attendee, the description contains the name
of the Chair only; the list of other attendees is not migrated. Other
meeting information is not migrated.
Migrating Organizer Calls sections

Entries in the Organizer Calls sections are migrated to tasks in the Notes
Personal To Do view. The cc:Mail Domino Upgrade Service preserves the
major data items of a call, placing them in equivalent fields of the task
entry, or in the Details field. Call fields that do not have appropriate
equivalents in Lotus Notes are not migrated.
The following table shows the mapping between fields in an Organizer
Calls section and a Notes To Do entry.
Information in these fields in Is migrated to these fields in

the Organizer Calls section a Notes To Do entry
First name, last name Title, Details
Company Details
Phone number (Country code, area code, Details
and number)
continued
11-16 Upgrade Guide

Information in these fields in Is migrated to these fields in
the Organizer Calls section a Notes To Do entry
Extension Details
Status Details
Notes Details
Date Start/Due*
Categories Categories**
Completed Status: Completed***
*For calls that are marked as completed, the date of the call is also migrated to
the Due value in the Notes To Do task.
**In Organizer, a user may assign multiple categories to a call. For example, the
Categories field of a call can contain the values “Follow up” and the category
“Clients.” When you migrate the call, the Categories field of the Notes To Do
task displays only the first of these values.
***Completed Calls are migrated to Notes To Do tasks with the status
Completed. Although the Notes Personal To Do task document does not display
the completion time of the call, this information is available in the field
COMPLETEDDATETIME in the Document Properties for the task.
Other information about a call is not migrated.
Migrating Organizer Address and Notepad sections

Organizer Address and Notepad sections are migrated to the Personal
Address Book (PAB) and Personal Journal databases, respectively, on a
user’s Lotus Notes workstation. Multiple Address sections are migrated
to a single PAB. Similarly, multiple Notepad sections are migrated to a
single Personal Journal.
Pages in an Organizer Notepad section can contain graphics as well as
text. Graphics are migrated as file attachments embedded within the
Personal Journal database mailed to the user. The ASCII text in the
Notepad section is written to the body of the Personal Journal as rich
text.
As with other information in a Notepad page, graphics are migrated only
if the user created them from the OR2 file. Information linked from exter-
nal files, such as included sections and shared DDE (Dynamic Data
Exchange) information, is not migrated. Graphics created using copy and
paste are not migrated because their content is not stored within the file.
The administrative workstation running the cc:Mail Domino Upgrade
Service cannot write directly to a user’s Lotus Notes client. To provide
users with the information migrated from Organizer, the cc:Mail Domino
Upgrade Service places a message in the Notes Inbox, to which the

Personal Address Book and Personal Journal containing the migrated
Organizer information are attached. The message provides instructions
for detaching the files and adding the information to the existing
Personal Address Book and Personal Journal databases.
Users who have information to migrate from one of the sections, but not
the other, receive two messages: one for the section that was migrated,
and another for the other section, explaining that there was no informa-
tion to migrate. Users who do not have Address or Notepad sections to
migrate do not receive either message.
You can open the files containing the text of these messages in any text
editor and modify them to provide users with information that is specific
to your environment. The files for each message reside in the Notes data
directory, and are as follows:
• Address section migrated message — OR2ADDR.TXT
• Notepad section migrated message — ORGNPN.TXT
• No Address section migrated — OR2NOADD.TXT
• No Notepad section migrated — ORGNOPN.TXT
Preparing to migrate Organizer information

If you are migrating Organizer data for the cc:Mail users being moved to
Lotus Notes, perform the following additional tasks:
• Map network drives to directories where users’ Organizer (OR2 files)
are stored.
• Disconnect Organizer users from the directory where the Organizer
data files (*.OR2) reside.
• Verify that you have full access rights to the file server directories
containing the OR2 files and at least Read access to Organizer OR2
files to be migrated.
• Verify that you have Editor or higher access to the Notes mail files
that will contain the migrated Organizer information.
• Turn off all Organizer scheduling agents.
• Verify that you have sufficient disk space to migrate the Organizer
information. There must be 2MB of free disk space on the target
Domino server for each 1MB of OR2 file you migrate.
11-18 Upgrade Guide

• Instruct Organizer users to perform preparation tasks that will assist
in a faster migration.
For more information about preparing Organizer users, see the topic
“Preparing Organizer users for migration” later in this chapter.
• Compact Organizer data files to be migrated, using version 2.11 or
greater of the Organizer administration program.
Refer to the Organizer 2.11 Administrator’s Guide for information
about how to compact files.
• Configure autoforwarding from the cc:Mail accounts to the Notes
mail accounts.
Connecting to the Organizer data directories

Organizer OR2 files are typically stored separately from a user’s cc:Mail
mailbox. To enable the cc:Mail Domino Upgrade Service to correctly
locate the OR2 files and migrate Organizer information, you must map
drives on the administrative workstation to the Organizer data
directories.
Note Although the cc:Mail Domino Upgrade Service can only migrate
OR2 files for Windows versions of Organizer for cc:Mail, OR2 files can be
migrated from any location that the administrative workstation is
connected to, regardless of the operating system.
Changes made to a user’s cc:Mail directory entry when migrating

Organizer information
After you migrate a cc:Mail user’s Organizer information, the cc:Mail
Domino Upgrade Service modifies Organizer information in the
Comments field of the user’s cc:Mail directory entry as follows:
• Changes the 02 keyword, which identifies the Organizer Calendar
Path, to 92
• Changes the 04 keyword, which identifies the Organizer Agent
Name, to 94
These changes prevent other Organizer users from viewing migrated
users’ free-time schedules or sending scheduling messages to these users’
Organizer Agents when you perform subsequent migrations to convert
users’ remaining Organizer information. The cc:Mail Domino Upgrade
Service interprets the modified Comments information and correctly
migrates additional Organizer data.

Preparing Organizer users for migration
In addition to the administrative tasks you perform before migrating
from Organizer, users must complete the following tasks:
• Record the names of any included sections
• Process pending meeting notices
• Delete data that does not need to be migrated
• Archive data to be migrated
Recording information about included sections
The cc:Mail Domino Upgrade Service does not migrate included sections.
By recording the names of any included sections, users can create links
between the migrated documents in Lotus Notes.
Processing meeting notices

The cc:Mail Domino Upgrade Service does not migrate meeting invita-
tions that have not been acted upon. Users need to process any pending
meeting notices they want migrated.
Removing data that does not need to be migrated

Encourage users to minimize the amount of data to be migrated by
having them clear entries or remove sections they do not need migrated.
Archiving data to be migrated

Migrating Organizer data requires a considerable amount of time. You
can improve migration performance by having users prepare for migra-
tion by archiving and compacting their Organizer sections to reduce the
size of their OR2 files. Smaller Organizer files migrate faster and result in
smaller Notes mail, Personal Journal, and Personal Address Book
databases.
Importing the cc:Mail post office directory

The cc:Mail post office directory contains information for all cc:Mail
users who have mailboxes in that post office. Lotus Notes uses the infor-
mation extracted from the post office directory to configure migrated
users for registration.
To import the cc:Mail post office directory, you must:
• Connect to the cc:Mail post office
• Import users and groups
After completing these tasks, you will be ready to register the imported
users in Notes.
11-20 Upgrade Guide

Connecting to the cc:Mail post office
To import users into the Notes registration queue for migration, locate
the post office where users have their mail boxes and log in to the post
office.
2. From the Tools pane, click People - Register.
3. When prompted, enter your certifier ID password and click OK.
4. From the Basics pane of the Register Person — New Entry dialog
box, specify a registration server if necessary by clicking Registration
Server and selecting the server that registers new users. Click OK.
5. Click Migrate People.
6. From the People and Groups Migration dialog box, select cc:Mail
Users from the Foreign directory source list.
7. Complete the following information in the cc:Mail Post Office
Information dialog box:
• Post office name — name of the cc:Mail post office being migrated
• Post office path — the drive letter and directory path that point to
the post office
• Post office password
Note You must have a drive mapped to the post office location.
8. Click OK. The post office name, path, and password are verified. If
any of the values are incorrect, an error message is displayed.
9. In the People and Groups Migration dialog box, select a filter, then
click Go! to populate the Available people/groups box with entries.
The Available people/groups box displays the contents of the post
office directory. You are now ready to import users from the post
office into the Notes registration queue..
For more information about importing cc:Mail users and groups, see
the topic “Importing cc:Mail users and groups into the Notes
registration queue” later in this chapter.
Importing cc:Mail users and groups into the Notes registration

queue
After the Available people/groups box displays the contents of the
cc:Mail post office directory, select users to import and migration options
that determine the cc:Mail data to migrate.

1. From the People and Groups Migration dialog box, enable options by
selecting items in the Migration Options box. The options you select
apply to all cc:Mail users imported during this session.
2. Click Advanced to open a dialog box that lets you specify advanced
upgrade settings for migrating people from cc:Mail.
3. Click Done when you finish specifying these settings.
4. From the Available people/groups box, select users and groups to
migrate and click Add. To migrate all people and groups, click Add
All.
5. Click Migrate to place the selected users in the registration queue,
and click OK to close the message indicating the status and number
of users queued for registration.
If you are migrating Organizer information, you are prompted to
confirm that you have established the necessary network connections
to directories where users’ Organizer (OR2) files are stored.
6. Click Done. The people queued for registration now appear in the
Registration status box. You are now ready to register users.
For more information about registering cc:Mail users, see the topic
“Registering users and completing the cc:Mail migration” later in this
chapter.
Importing cc:Mail Mobile users

The cc:Mail post office directory includes the names of cc:Mail Mobile
users (users designated by an uppercase “R”) for whom the post office
serves as the home post office. Mobile users can also be imported to the
Notes registration queue, but the cc:Mail Domino Upgrade Service does
not support direct migration of cc:Mail Mobile post offices and user
mailboxes. After registration, mobile users can migrate the contents of
their own mailboxes by archiving their messages and then running the
cc:Mail to Lotus Notes upgrade wizard to migrate archives.
For information about using the cc:Mail to Lotus Notes upgrade wizard
to migrate personal mail data, see the chapter “Migrating Personal Mail
Data.”
Customizing cc:Mail migration settings

When you are ready to import users, you can set options to specify how
the cc:Mail Domino Upgrade Service uses information from the cc:Mail
post office to create Lotus Notes users. You can specify two types of
migration settings:
11-22 Upgrade Guide

• Migration options — Determine how the cc:Mail Domino Upgrade
Service creates a user in Lotus Notes from information imported
from cc:Mail. The migration options available are similar for each of
the migration tools.
• Advanced upgrade settings — Let you specify additional settings
affecting conversion and coexistence between cc:Mail and Lotus
Notes.
Setting migration options for cc:Mail

You can set options to determine what information the cc:Mail Domino
Upgrade Service imports from the cc:Mail post office. The options you
specify apply to all users and groups imported from cc:Mail during this
session.
The cc:Mail Domino Upgrade Service does not support the option
“Generate random passwords.” To successfully migrate a user’s cc:Mail
mailbox, use the cc:Mail administration tool to create passwords for users
before migration.
For more information about the available migration options, see the
chapter “Overview of Domino Upgrade Services.”
1. From the People and Groups Migration dialog box, click Options.
2. In the Migration Options box, accept the defaults or select new
options. To clear a selection, click the selected option a second time.
The following table lists the available import options and their
default status:
Migration option Default status
Generate random passwords for users Off - Not supported for cc:Mail
with no passwords
Generate random passwords for all users Off
(overwrite existing passwords)
Add cc:Mail name to Notes person On
document (required for cc:MTA)
Allow addition of empty groups to Notes Off
Convert mail On
Convert mail ONLY (Person document Off
must already exist)
3. Continue with the import procedure by specifying Advanced

upgrade settings.

You set migration options independently for each Domino Upgrade
Service, so that if you are migrating users from multiple mail systems,
you can apply a different set of options for each system. The options you
select apply to all users imported from a given directory during the
session.
Specifying advanced settings for migrating cc:Mail users

In addition to the migration options set on the People and Groups Migra-
tion dialog box, the cc:Mail Domino Upgrade Service provides other
options you can set to control the process of migrating cc:Mail users. The
settings you select apply to all users you import from the cc:Mail post
office during this session. You can specify the following types of cc:Mail
upgrade settings:
• Conversion settings
• Gateway settings
• Other settings
Specifying cc:Mail conversion settings

The Conversion Settings pane of the cc:Mail Upgrade Advanced Settings
dialog box lets you specify which information to migrate from the cc:Mail
post office. By default, all of the options, except “Convert Bulletin Boards
to Notes discussion database” are enabled.
1. From the People and Groups Migration dialog box, click Advanced.
2. From the cc:Mail Upgrade Advanced Settings dialog box, click
Conversion Settings.
3. Specify the options to use and, if necessary, for a DB6 post office, set
the code page to use when migrating the post office.
For more information about setting the code page, see the topic
“Specifying the code page to use for converting cc:Mail data” later in
this chapter.
The code page defaults to the current language version of the post
office.
The following options are available. By default, the first three options
are enabled (check boxes selected):
• Mail private mailing lists/R8 address books as Notes attachments
• Convert Organizer OR2 scheduling files to Notes
• Convert alias entries
11-24 Upgrade Guide

• Convert bulletin boards to Notes discussion database
• Retain cc:Mail MTA routing information for deferred mailbox
migration
Caution Do not select the option “Mail private mailing lists/R8
address books as Notes attachments” if you are migrating cc:Mail 6.3x
users. The cc:Mail 6.3x client for Domino cannot correctly process
migrated private mailing lists and users will be unable to access the mail
file on the Domino server.
Mailing cc:Mail R8 private mailing lists and address books as Notes

attachments
Select this check box on the Conversion Settings pane of the cc:Mail
Upgrade Advanced Settings dialog box to migrate private mailing lists
contained in users’ cc:Mail R8 mail boxes. During the migration, each
user’s private mailing list is converted to a Notes Personal Group and
placed within a temporary Personal Address Book (PAB). The cc:Mail
Domino Upgrade Services automatically mails this PAB to the user.
Users can run the cc:Mail to Lotus Notes upgrade wizard at their
workstation to copy information from the temporary PAB to the PAB on
their workstation.
If you select this option when migrating users, the cc:Mail Domino
Upgrade Service places a warning message in the log file for each migrat-
ing user for whom it cannot locate any private mailing lists.
Do not select this option if you are migrating cc:Mail 6.3x users. The
cc:Mail 6.3x client for Domino cannot correctly process migrated private
mailing lists and users will be unable to access the mail file on the
Domino server.
Converting Organizer OR2 scheduling files to Notes

Upgrade Advanced Settings dialog box to convert Organizer data (OR2
files) for the selected cc:Mail users to Notes Calendar and Scheduling
information.
For more information about converting Organizer information to Lotus
Notes, see the topic “Migrating Organizer Information” earlier in this
chapter.
Note Converting Organizer data requires you to connect network
drives to the directories where the selected cc:Mail users store their
Organizer data.

Converting cc:Mail alias entries
Upgrade Advanced Settings dialog box to retain cc:Mail aliases for
migrated users. Aliases for entries in the cc:Mail directory are added as
entries in the User name field of the migrated user’s Notes Person
document.
Do not migrate the alias entries for cc:Mail users if you are using the Nth
FullName Propagation field in the cc:Mail Post Office Server document
for a post office. If you migrate alias names and use the Nth FullName
Propagation field, subsequent MTA synchronization procedures can
delete existing alias names and create new aliases in the cc:Mail post
office directory.
To avoid inadvertently deleting and creating alias names in a post office
directory, clear the Convert Alias Entries check box in the Conversion
Settings pane of the cc:Mail Upgrade Options Advanced Settings dialog
box when you use the cc:Mail Domino Upgrade Service with the MTA.
Converting bulletin boards to a Notes discussion database

Upgrade Advanced Settings dialog box to convert bulletin boards in the
specified cc:Mail post office to a Notes discussion database. All of the
bulletin boards in a given post office are migrated to a single Notes
discussion database on the Mail server, called cc:Mail Migrated Bulletin
Boards (CCNOTBB.NSF). Each migrated bulletin board becomes a
category within the database. After migration, users can open this
database and sort by category to see the names of the migrated cc:Mail
Bulletin Boards.
Only bulletin boards that contain at least one message are migrated.
Empty cc:Mail bulletin boards do not migrate. Duplicate messages are
migrated only once, so that messages sent to multiple Bulletin Boards
appear in only one Notes Category.
Converting bulletin boards requires a considerable amount of time and
slows the progress of the migration. However, you only need to convert
bulletin boards once for each post office. To enhance performance when
migrating bulletin boards, enable the option when migrating a single
user, and then register that user. If you enable bulletin board conversion
for multiple users, the conversion process is repeated for each of the
selected users.
You cannot migrate bulletin boards for mobile cc:Mail users. Mobile
users can either archive the bulletin board messages they want to keep or
create a local replica of the Notes discussion database after migration.
11-26 Upgrade Guide

For networks that employ the cc:Mail MTA to provide coexistence
between cc:Mail and Domino, use the Bulletin Board Conversion compo-
nent of the cc:Mail MTA to automatically synchronize bulletin boards.
The cc:Mail MTA creates a Notes discussion database named
CCMTABBX.NSF (using the template CCMTABBX.NTF). By contrast, the
cc:Mail Domino Upgrade Service migrates bulletin boards to a database
named CCNOTBB.NSF (using the template CCNOTBB.NTF). These two
databases are separate and do not share information. If you intend to use
the cc:Mail MTA for bulletin board synchronization during lengthy
migrations in which cc:Mail and Lotus Notes need to coexist and be
synchronized with each other, do not use the migration option “Convert
bulletin boards.” If you do not intend to maintain a cc:Mail and Lotus
Notes mixed environment, you can use the bulletin board conversion
option to do a one-time conversion of bulletin boards.
For more information about administering cc:Mail bulletin boards and
Notes discussion databases when using the cc:Mail MTA, see the topic
“Synchronizing cc:Mail bulletin boards and Notes discussion databases,”
Migrating subscription bulletin boards
cc:Mail Release 8 supports subscription bulletin boards. Subscription
bulletin boards differ from regular community bulletin boards in that
only users on a restricted member list have access to the bulletin board.
By default, the cc:Mail Domino Upgrade Service does not convert
subscription bulletin boards to Notes databases. Before you can migrate a
subscription bulletin board, you must first add the cc:Mail post office to
the member list for the bulletin board as follows:
1. Using WinAdmin, select the Bulletin Boards tab.
2. Select the name of the subscription bulletin board to migrate.
3. Add the cc:Mail post office to the member list for the bulletin board.
You can now migrate the bulletin board.
Note Completing this procedure gives all users on the specified post
office access to the bulletin board.
Retaining cc:Mail MTA routing information for deferred mailbox

migration
The Conversion Settings pane of the cc:Mail Upgrade Advanced Settings
dialog box includes the check box “Retain cc:Mail MTA routing informa-
tion for deferred mailbox migration.” If you can’t migrate all cc:Mail
users at once, select this check box to migrate users in two phases, as
follows:

Phase 1
• Register cc:Mail MTA users from their existing Notes Person
documents
• Create Notes mail files
• Defer mailbox migration for these users
• Retain cc:Mail connectivity for these users
Phase 2
• Migrate messages from users’ cc:Mail mail boxes
Completing the first phase of the migration
During the first phase of the migration, complete the following:
1. From the People and Groups Migration dialog box, select cc:Mail
MTA users to migrate from the Available people/groups list.
2. In the Migration options list:
• Select “Add administrator to mail file access control list”
• Deselect “Convert mail”
3. Click Advanced to open the Conversions Settings pane of the cc:Mail
Upgrade Advanced Settings dialog box and select “Retain cc:Mail
MTA routing information for deferred mailbox migration.”
4. Click Migrate and then click Done to add the users to the
Registration Queue.
5. From the Register Person dialog box, select the users to register in the
Registration queue.
6. Select the Mail pane and then select Lotus Notes in the Mail system
field.
7. Click Register.
After you complete Phase 1, each user’s Person document is updated to
indicate they are registered Lotus Notes users with Notes IDs and mail
files. However, because users retain the cc:Mail MTA routing informa-
tion in their Notes Person documents, they continue to receive messages
in their cc:Mail mailboxes and access their mail using the cc:Mail client.
The cc:Mail Domino Upgrade Service saves the mail system setting
(Lotus Notes) you specify in Step 6, but the setting is saved in the
background and is not put into effect. Instead, the Mail system field in
the Person document remains set to cc:Mail and other cc:Mail routing
11-28 Upgrade Guide

information is retained. As a result, routing support for the cc:Mail MTA
is maintained, and the Lotus Notes user is prevented from using the
Notes mail system. Users only receive mail through the cc:Mail MTA
router. The cc:Mail Automatic Directory Exchange (ADE) facility contin-
ues to propagate the users’ cc:Mail directory information to other cc:Mail
post offices.
This option only affects users whom you register from cc:Mail MTA
Person documents.
Completing the second phase of the migration

During the second phase of the migration, you:
1. Select the same users you migrated in Step 1 of the first migration
phase.
2. In the Migration options list of the People and Groups Migration
dialog box, select “Convert mail only.”
The cc:Mail Domino Upgrade Service converts messages in the users’
mail boxes to Notes format and places them in their Notes mail files. It
also removes the cc:Mail MTA settings from the Person document and
replaces them with the saved Notes settings.
Specifying the code page to use for converting cc:Mail data

cc:Mail post offices store mail messages using a language code page, just
as Lotus Notes does. When migrating users from DB6 post offices, you
must specify the language code page to use. The cc:Mail Domino
Upgrade Service needs to know the post office code page so it can
correctly convert characters to be displayed in Lotus Notes. By default,
the cc:Mail Domino Upgrade Service uses the current code page of the
post office. If necessary, specify the appropriate code page for the
language version used by the post office being migrated.
If the code page of the cc:Mail post office is different from the Notes code
page, you must change the cc:Mail code page to match the Notes code
page.
The following table shows the code pages available for a cc:Mail post
office.

Post office language version Code page number
Canadian French 863
Greek 851
Hebrew 862
Icelandic 861
Multilingual 850
Nordic 865
Portuguese 860
Slavic 852
Turkish 857
United States 437
Mapping cc:Mail gateways to Notes domains

To connect to external mail systems across the Internet or other WANs,
cc:Mail post offices use special gateway post offices. A cc:Mail gateway
post office routes messages from the local post office to foreign mail
systems. Gateways translate the format of messages, addresses, headers,
attachments, and other messaging data between a native mail format and
the format used by the external system. Each mail gateway has an entry
in the cc:Mail post office Directory.
When a cc:Mail user receives a message from an external mail system,
the name of the cc:Mail gateway that routed the message is included as
part of the sender’s address. If the user replies to the message, the reply
is automatically routed back through the gateway and to the external
mail system.
By default, when you migrate a message from cc:Mail to Lotus Notes, the
gateway information in the sender’s address remains unchanged; it
contains the name of the cc:Mail gateway. Because Lotus Notes cannot
send messages back out to an external mail system through this cc:Mail
gateway, a user is unable to send a direct reply to the migrated message.
To enable Lotus Notes users to reply to messages received from external
mail systems after you move their mailboxes to Lotus Notes, you can
map each cc:Mail gateway to a Notes domain. During migration, the
cc:Mail Domino Upgrade Service then automatically replaces the names
of cc:Mail gateways in the sender’s address with the names of equivalent
Notes domains.
11-30 Upgrade Guide

The user upgrade wizard that migrates a user’s archived messages and
personal addresses to Lotus Notes also uses gateway mapping informa-
tion, but you configure this independently, when you send users an
upgrade notification message.
For more information about sending an upgrade notification, see the
chapter “Migrating Personal Mail Data.”
Example of mapping a cc:Mail gateway to a Notes domain

The Acme corporation uses a cc:Mail gateway post office called INTER-
NET to route cc:Mail messages to Internet addresses and a Notes domain
called INET to route Notes messages to Internet addresses. When config-
uring gateway mapping for migration, the system administrator at Acme
maps the cc:Mail gateway INTERNET to the Notes domain INET.
Cheryl Lordan, in the IS division at Acme, has had her mail migrated
from cc:Mail to Lotus Notes. In her cc:Mail mailbox, Cheryl Lordan had a
message from abc@def.com, which was received through the cc:Mail
INTERNET gateway. If no gateway mapping were used, and Cheryl
replied to the cc:Mail message after migration, she would get an error
stating that INTERNET is not a valid address, because in Lotus Notes the
Internet domain is called INET. However, with gateway mapping
enabled during migration, the cc:Mail gateway name INTERNET would
be rewritten as INET in all addresses, making them valid Notes
addresses. So when Cheryl replies to the message, it is correctly routed to
the sender.
You can enable migrated cc:Mail users to reply to messages that they
received from external gateways, such as the Internet, by mapping the
names of cc:Mail gateway post offices to Notes domains.
During migration the cc:Mail Domino Upgrade Service automatically
overwrites the name of the cc:Mail gateway in the sender’s address of a
message with the name of a corresponding Notes domain. Later, when a
new Lotus Notes user replies to a message migrated from cc:Mail, the
message is routed to the external mail system by way of the named Notes
domain.
Follow these steps to map the cc:Mail gateway to the Notes domain:
1. From the Foreign Directory Import dialog box, click Advanced.
2. From the cc:Mail Upgrade Advanced Settings dialog box, click
Gateway Settings.
3. In the cc:Mail gateway post office field, enter the name of a cc:Mail
post office that routes messages from cc:Mail to an external mail
system.

4. In the Notes mail domain name field, enter the name of the Notes
mail domain to be used for routing messages to the same external
mail system.
5. Click Add pair to establish the mapping between the cc:Mail
gateway and the Notes domain.
Specifying other cc:Mail upgrade settings

The Other Settings pane lets you specify special mailbox upgrade
settings and establish an error threshold to use during the migration.
1. From the Foreign Directory Import dialog box, click Advanced.
2. From the cc:Mail Upgrade Settings dialog box, click Other Settings.
3. The following settings are available:
• Upgrading to cc:Mail Release 6.3 Client for Domino
• Post office for routing mail to Notes
• Error threshold
Caution When migrating cc:Mail Release 6.3x users, do not select the
option “Mail private mailing lists as attachments” on the Conversion
Settings pane. The cc:Mail 6.3x client for Domino cannot correctly process
migrated private mailing lists and will be unable to log in to the mail file.
Upgrading to the cc:Mail Release 6.3 client for Domino

Select this option to automatically configure internal cc:Mail information
that lets users access mail files on a Domino server with the cc:Mail 6.3x
client. Do not select this option when importing users who are currently
running a version of cc:Mail other than Release 6.3x, or who will use the
Notes mail client after migration.
If you need to import users who are running other releases of the cc:Mail
client, or who will use the Notes mail client after migration, import the
Release 6.3x users in one session and the remaining users in a second
session.
To migrate users to the cc:Mail 6.3x client, the mail template
R63MAIL.NTF must be available in the data directory of the users’ mail
servers. The file is installed in the Notes data directory of workstations
running the Domino Administrator and the cc:Mail Domino Upgrade
Service. Copy this file to the Domino data directory of each mail server
that supports migrating cc:Mail 6.3x clients. When preparing to register
cc:Mail 6.3x users, select R63MAIL.NTF as the mail template. If you do
not provide the correct mail template for cc:Mail 6.3x users, they cannot
access their mail files.
11-32 Upgrade Guide

Caution When migrating cc:Mail 6.3x users, do not select the option
“Mail private mailing lists as attachments” on the Conversion Settings
pane. The cc:Mail 6.3x client for Domino cannot correctly process
migrated private mailing lists and will be unable to log in to the mail file.
Specifying the post office for routing mail to Notes

In networks where the cc:Mail MTA connects cc:Mail and Lotus Notes,
you can configure cc:Mail Domino Upgrade Service to enable automatic
forwarding from a cc:Mail post office to Lotus Notes. Having messages
automatically forwarded eliminates the need to migrate additional
messages later.
In a cc:Mail post office directory, each user is assigned a location code
that describes where their mailbox is in relation to the post office. When
the post office receives a message, it checks the location code to deter-
mine whether to look for the recipient’s mailbox at the current post
office, or on another post office. Before migration, a cc:Mail user whose
mail file is located on the local post office is assigned the location code
uppercase “L.”
By default, after migration, this location code is unchanged. As a result,
mail sent to a user’s old cc:Mail mailbox, continues to be accepted. If you
are not using the cc:Mail MTA, you may want to let users continue to
receive mail at their old mail boxes for a limited amount of time. Later,
you can run cc:Mail Domino Upgrade Service again to move these
messages to the user’s Notes mail file.
For more information about performing a secondary migration, see the
topic “Migrating additional cc:Mail messages after registration” later in
this chapter.
To configure mail forwarding, on the Other Settings pane of the cc:Mail
Upgrade Advanced Settings dialog box, select the name of the Notes
domain where the user’s mail file is located from the list of available
remote post offices. The domain must be connected to the cc:Mail post
office and MTA, and must already be included as a remote post office
entry in the cc:Mail directory. Generally, the Notes domain that serves as
the gateway between cc:Mail and Lotus Notes will be the same as the
name of the cc:Mail MTA server.
When you specify the post office for routing mail to Lotus Notes, the
cc:Mail post office directory retains an entry for each migrated user.
However, the cc:Mail Domino Upgrade Service updates information in a
user’s cc:Mail directory listing, as follows:
• Changes the location code to lowercase “r“ to indicate that the user is
now remote to this post office

• Adds the name of the Notes mail domain where mail will be
forwarded to the address field
The setting applies to all users imported during this session.
After the cc:Mail Domino Upgrade Service changes users’ location infor-
mation, they can no longer use a cc:Mail client to retrieve messages from
their cc:Mail mailbox.
cc:Mail user files and messages left after migration

After migration, if the cc:Mail Domino Upgrade Service changes the
address and location type for a user’s entry in the cc:Mail directory, that
user can no longer access his cc:Mail mailbox. However, the cc:Mail user
file and mailbox messages remain in the cc:Mail post office. You can
restore the cc:Mail client’s ability to access the mailbox and other related
mail data (private mailing lists, archives, and so forth) by resetting the
user’s original location information back to an uppercase “L” (local),
using the cc:Mail ADMIN or WinAdmin. Resetting the location type also
lets you migrate the user again, if necessary.
For the recommended method for removing user data from the cc:Mail
post office, see the topic “Removing the user files and messages of
migrated users from the cc:Mail post office” later in this chapter.
Specifying an error threshold

You can specify the number of errors to tolerate when migrating
messages from mailboxes in the cc:Mail post office to Notes mail files. By
default, the migration tolerates an unlimited number of errors, and
completes the migration regardless of the error count. If you specify an
error threshold, the migration process terminates when it reaches the
number of errors specified.
Users who are successfully processed before the error threshold is
reached are registered in Lotus Notes. If the migration terminates, you
should analyze and resolve the error conditions reported for the users
who remain in the queue and attempt to register them again.
Registering users and completing the cc:Mail migration

After you successfully import users into the registration queue, you are
ready to register them and complete the migration. Depending on the
options you select, the registration process:
• Creates a Notes Person document and Notes ID for each migrated
user
• Creates a Notes mail file
11-34 Upgrade Guide

You can specify additional Notes registration information for users,
including mail server name, group membership, organizational unit, and
so forth.
For information about advanced user registration, see the book
Note After the registration process has started, you cannot use the
workstation for any other task until the process completes. If necessary,
you can stop the registration process by pressing CTRL+Break. When
you exit the Register Person dialog box, you are prompted to save the
users for later registration.
1. From the Basics view of the Register Person dialog box, view the
registration information for each name that appears in the
Registration status box to ensure that it is correct.
2. (Optional) Specify registration settings for users. You can apply
registration settings to an individual or to multiple users, or you can
set registration defaults.
If you created a ‘migration’ group, open the Groups pane and assign
users to this group now.
3. (Optional) Click the Options button, select the registration options to
apply during this session, and click OK.
4. From the Registration status box, select users to register and click
Register. The Domino Administrator attempts to register the selected
users in the order in which they were added to the queue and
migrates data from their mailboxes to Lotus Notes. Users whom you
do not select remain in the queue for later registration.
If you chose to migrate Organizer information for users, you are
prompted to enter your Notes password.
For more information about supplying passwords, see the topic
“Migrating Organizer information” earlier in this chapter.
The registration process may require a considerable amount of time,
depending on the number of users and number and size of the
mailboxes being upgraded.
After the registration completes, a message informs you of the
registration status. Failed registrations are listed in the Registration
status box with a status message indicating the reason for the failure.
Correct registration settings as needed and attempt to register the
user again.
5. Verify that the migration was successful.
For information on how to verify that the migration was successful,
see the chapter “Overview of Domino Upgrade Services.”

For information about how to install and run the upgrade wizard for
cc:Mail on the Lotus Notes client, see the chapter “Migrating Personal
Mail Data.”
Creating the Notes mail file

If you retained the default setting for the migration option “Convert
Mail” (that is, the option remains selected), when you register migrated
users, the Domino Administrator automatically converts their cc:Mail
mail boxes to Notes mail files as part of the registration process. On the
Mail pane of the Register Person dialog box, the option “Create mail file
now” is selected. An error message is displayed if you attempt to change
this option to create mail files using the background administrative
process (adminp).
Removing the user files and messages of migrated users from the
cc:Mail post office
After the migration process completes, user files and messages remain in
the cc:Mail post office. Neither the cc:Mail Domino Upgrade Service nor
cc:Mail delete these objects or mark them for deletion.
After you verify that the migration was successful, you can clean up
migrated users’ files and messages that remain in a DB6 or DB8 post
office using one of the following methods:
• Delete user files by using the cc:Mail ADMIN (DB6) or WinAdmin
(and DB8) programs. Deleting user files also deletes the messages in
those files. This is the recommended method for removing message
data for migrated users from the post office.
• Delete messages only, using the cc:Mail CHKSTAT (DB6) or
MSGMGR (DB8) utilities. Deleting users’ mail messages does not
remove the user file, but restores disk space by reducing the size of
the message store and removing message pointers in the user file.
Refer to your Lotus cc:Mail Administrator’s Guide for information on
running these utilities.
Caution Do not manually delete the user files in the cc:Mail post office
directory.
Deleting cc:Mail user files using cc:Mail Admin or WinAdmin

Using the administrative tool for your post office database (ADMIN or
WinAdmin), you can delete user files by editing the location information
in the post office directory entries for migrated users. Refer to the Lotus
cc:Mail Administrator’s Guide for details about running the administrative
utility for your post office.
11-36 Upgrade Guide

For post office entries where lowercase “l” or “r” designates the user’s
location
1. Using ADMIN or WinAdmin, edit the user’s entry in the post office
directory to remove the name of a remote post office in the address
field.
Removing the name of the remote post office assigns the user to the
local post office and changes the user’s location to uppercase “L.”
2. Add the name of a remote post office — generally the cc:Mail MTA
post office that serves as the gateway between cc:Mail and Lotus
Notes — and save the entry.
Adding the name of a remote post office assigns the user to that post
office and changes the user’s location designation in the local post
office to lowercase “l” or “r.”
3. Select Yes when prompted to delete the user file.
For post office entries where uppercase “L” or “R” designates the
user’s location
1. Using ADMIN or WinAdmin, edit the user’s entry in the post office
directory to add the name of a remote post office — generally the
cc:Mail MTA post office that serves as the gateway between cc:Mail
and Lotus Notes — and save the entry.
Adding the name of a remote post office assigns the user to that post
office and changes the user’s location designation in the local post
office to lowercase “l” or “r.”
2. Select Yes when prompted to delete the user file.
Migrating additional cc:Mail messages after registration

If necessary, after you migrate users, you can run the cc:Mail Domino
Upgrade Service again to migrate additional messages from cc:Mail. You
can perform such secondary migrations only for users who already have
Notes mail files. Also, migrating additional messages to a mail file
requires Manager access to the file. If you did not give yourself Manager
access to the mail file during the initial migration, you may need to ask
the Notes mail users to edit the ACL to provide you with the appropriate
access rights.
If you are running the cc:Mail MTA, you can eliminate the need to
migrate cc:Mail messages after migration if you enable automatic
forwarding of messages received at a user’s cc:Mail mailbox to their
Notes mail file.

To perform a secondary migration:
1. Connect to the cc:Mail post office.
2. Import previously migrated cc:Mail users into the Notes registration
queue.
3. Set the migration option Convert Mail ONLY. The cc:Mail Domino
Upgrade Service ignores any other options that are set, preventing
the creation of duplicate Person documents and Notes ID files.
4. In the Registration status box, select the users whose messages you
want to migrate and click Register.
The registration process automatically locates the users’ mail files and
converts messages in the cc:Mail mailbox to messages in the appropriate
folders of the Notes mail file. Messages that already exist in the Notes
mail file are not converted again.
For more information about the Convert Mail Only option, see the
Ensuring compatibility with the cc:Mail MTA

On networks where the cc:Mail MTA provides interim support for
cc:Mail users during the migration period, you need to follow specific
guidelines when configuring the migration to maintain connectivity
between your cc:Mail post office and Domino mail servers.
• During the migration, the cc:Mail MTA must be running if you want
cc:Mail and Lotus Notes to exchange directory entries and messages.
• Do not run the cc:Mail Domino Upgrade Service and the cc:Mail
MTA on the same computer; use dedicated resources for each of
these.
• The computer running the Domino Administrator and the cc:Mail
MTA should be located as close as possible on the network to the
cc:Mail post offices and Domino servers involved in the conversion.
The following topics contain additional information about using the
cc:Mail Domino Upgrade Service with the cc:Mail MTA:
• Synchronizing the cc:Mail directory and Domino Directory when
using the cc:Mail MTA
• Synchronizing directories when migrating from a downstream post
office
• Synchronizing cc:Mail bulletin boards and Notes discussion
databases
11-38 Upgrade Guide

• Retaining cc:Mail MTA routing information for deferred mailbox
migration
• Specifying the post office for routing mail to Lotus Notes
• Converting cc:Mail alias entries
• Updating existing Person documents
• Cleaning up error messages after migration
Synchronizing the cc:Mail directory and Domino Directory when

using the cc:Mail MTA
If you use the cc:Mail MTA and plan to migrate users to Lotus Notes
with the cc:Mail Domino Upgrade Service, make sure that you synchro-
nize the cc:Mail post office directory and the primary Domino Directory
both before and after the migration.
Synchronization commands update the cc:MTA work file with the Notes
addresses of migrated users and ensure that messages sent to their
cc:Mail mail boxes are properly routed to their new Notes mail files.
Perform the following steps to synchronize directories:
1. At the console, enter the command
Tell Ccmta Request post_office_name
where post_office_name is the name of the post office whose entire
contents you want to send to the target Domino Directory.
2. After the cc:Mail MTA Directory Conversion displays a message
indicating it has finished processing the Tell command, call the
cc:Mail post office to send the request for cc:Mail user names by
entering the following command at the console:
Tell Ccmta Call Poname=post_office_name
where post_office_name is the name of the post office you specified in
Step 1.
3. Process the message you received from cc:Mail in Step 2 by entering
the following command:
Tell Ccmta Applyade
4. After Directory Conversion displays a message indicating it has
finished processing the information it received from cc:Mail, enter
the command:
Tell Ccmta Synch post_office_name
Step 1. This command generates a message that includes the names
of all the Lotus Notes users in the source Domino Directory, the

names of all the post offices and domains in the primary Domino
Directory, and the names of all the cc:Mail users from other post
offices (if any) in the source Domino Directory.
5. Call the cc:Mail post office to send the Notes information by entering
the following command at the console:
Tell Ccmta Call Poname=post_office_name
Step 2.
For additional information about installing and configuring the cc:Mail
MTA, refer to the Lotus Notes cc:Mail MTA Administrator’s Guide.
Synchronizing directories when migrating from a downstream post

office
A post office that receives its directory updates from a hub post office is
considered to be downstream from the hub post office. In some cc:Mail
Automatic Directory Exchange (ADE) topologies, migrating users from a
downstream post office can result in discrepancies between the directory
on this post office and the directory on the hub post office.
For example, if the cc:Mail MTA and the cc:Mail hub post office have a
broadcaster-to-broadcaster relationship, and the hub post office is in a
superior relationship with subordinate downstream post offices, the
subordinate downstream post office would not be allowed to propagate
the users’ address changes up to the superior hub post office. As a result,
although the users’ records in both the Domino Directory and the subor-
dinate post office are updated to reflect the fact that users have been
migrated, records in the hub post office still indicate that the users’ mail
boxes are in the cc:Mail post office.
In this type of topology, if you migrate users from the downstream post
office, you also must update the cc:Mail addresses for migrated users at
the hub post office. Although the cc:Mail Domino Upgrade Service
automatically changes the address of a migrated user to a Notes domain
name, this address change is not necessarily propagated to either the hub
post office or to its other downstream post offices.
When migrating users from a downstream post office, you can update
addresses at the hub post office on an individual basis, using the cc:Mail
Administration program.
11-40 Upgrade Guide

Alternatively, when using the cc:Mail MTA to connect the two mail
systems during migration, you can synchronize the Domino and cc:Mail
directories as follows:
1. Before a migration, use the cc:Mail EXPORT program to export a
Local user list from the downstream post office.
2. View this list with a text editor and delete names of users you do not
want to migrate.
3. Using the Find and Replace feature of the text editor, replace the
cc:Mail post office name with the name of the Notes domain.
4. After you migrate all users at the post office, use the cc:Mail IMPORT
program to import these names into the hub post office. The changed
address entries are propagated throughout the cc:Mail post office
network.
The following table shows a user entry in the directory of a cc:Mail
post office before and after migration:
Directory field Entry for cc:Mail user Entry for same user after migration
Name John Doe John Doe
Addr AcmeNotes
Locn L r
Cmts CEO CEO
Synchronizing cc:Mail bulletin boards and Notes discussion

databases
If you are using the cc:Mail MTA version 2.0 or later, and want to keep
information synchronized between cc:Mail Bulletin Boards and a Notes
Discussion database, use the Bulletin Board Conversion component of
the cc:Mail MTA and clear the option in the cc:Mail Domino Upgrade
Service to convert bulletin boards.
For information about how to change the option to convert bulletin
boards, see the topic “Converting bulletin boards to Notes discussion
databases” earlier in this chapter.
When you synchronize bulletin boards between cc:Mail and Lotus Notes
through the cc:Mail MTA, you ensure that all cc:Mail bulletin board
messages propagated to Lotus Notes are present in the cc:Mail MTA
Bulletin Board Exchange database and vice versa.

Perform the following steps to synchronize cc:Mail bulletin boards with
Notes discussion databases:
1. Make sure that the propagation lists for the bulletin boards you are
synchronizing with the cc:Mail MTA Bulletin Board Exchange
discussion database include entries for the domain post office.
2. Make sure that you have configured the propagation type for the
bulletin boards in cc:Mail to allow sending and receiving between
the cc:Mail connected post office and the cc:Mail MTA server.
3. Make sure that all the bulletin board titles exist as categories in the
cc:Mail Bulletin Board Exchange database. On the cc:Mail MTA
Domino server, run a directory synchronization (SYNCH command)
between cc:Mail and Lotus Notes and apply the ADE update
(APPLYADE command) to create the bulletin board categories in the
cc:Mail Bulletin Board Exchange database if they are not already
present.
4. From the cc:Mail Router responsible for the directly connected post
office, run a bulletin board synchronization request EXCH/BS.
After completing these steps, any bulletin board messages that were
posted before you enabled bulletin board exchange through the cc:Mail
MTA will be present in the cc:Mail Bulletin Board Exchange database.
For detailed information about the procedures and commands discussed
in this topic, refer to the Lotus Notes cc:Mail MTA Administrator’s Guide.
11-42 Upgrade Guide

Chapter 12
Migrating Users from Microsoft Mail
This chapter discusses issues involved in migrating users from Microsoft

Mail to Lotus Notes 6 and provides instructions on using the Domino
Administrator and Microsoft Mail Domino Upgrade Service to complete
the migration.
Migrating Microsoft Mail users

Using the Microsoft Mail Domino Upgrade Service in the Domino
Administrator, you can import users and groups from a selected Micro-
soft Mail Postoffice and add them to Notes. The migration process:
•
Imports users and groups from the postoffice and creates entries for
them in the Domino Directory
• Creates Notes IDs and mail files for imported users
• Migrates the contents of mailboxes (MMF files) from a central
location, such as the Microsoft Mail Postoffice server
You must be able to map a drive to the location of the MS Mail mailboxes
from the workstation running the Domino Administrator.
You can migrate mailbox information from Microsoft Mail versions 3.2,
3.5, and 3.6.
You can also migrate messages from an off-line Microsoft Mail mailbox
by means of a separate user upgrade wizard.
For information about the user upgrade wizard, see the chapter
This section includes the following topics:
• Notes equivalents for migrated Microsoft Mail data information
• Preparing to migrate Microsoft Mail users
• Importing the Microsoft Mail Postoffice Address List
• Customizing Microsoft Mail migration settings
• Registering users and completing the migration from Microsoft Mail
12-1
Notes equivalents for migrated Microsoft Mail data
The Microsoft Mail Domino Upgrade Service converts information in a
Microsoft Mail Postoffice to Notes, including messages, and private and
public address books, as shown in the following table:
These items in Microsoft Mail . . . Become these Notes items . . .

Custom message types, including Not migrated
Scheduler messages
Delivery failure messages Not migrated
Public groups Group document in Domino Directory
Interpersonal mail messages (IPM) Not migrated
Message date and priority Message date and priority
Messages and attachments Messages and attachments
Outbox folder Not migrated
Password Password
Personal Address Book Personal Address book*
Postoffice Address List Domino Directory
Read and unread status Read and unread status
Shared and group folder Not migrated
Wastebasket or Deleted mail folder Not migrated
*Personal Address Books are automatically sent to users in a Notes mail message
attachment. Users then run an upgrade wizard at their workstations to migrate
address book information to their Notes Personal Address Books.
For information about the user upgrade wizards, see the chapter
Understanding how the migration tool parses Microsoft Mail name

formats
Unlike Notes names, which are stored as First name, Last name, and
Middle name components, the Microsoft Mail Address Book stores
names as a single character string, including commas and spaces. The
Microsoft Mail name format used depends on the conventions estab-
lished within the organization. For example, the same user could be
listed in the address book as either Susan Salani or Salani, Susan.
12-2 Upgrade Guide

In generating a Notes name from an imported Microsoft Mail name, the
Microsoft Mail Domino Upgrade Service first determines the format of
the name, and then parses the name into Notes name components. In
some cases, one or more of the resulting Notes name components may be
empty.
Notes supports converting Microsoft Mail names that have the following
characters: letters, numbers, ampersands (&), apostrophes (‘), hyphens
(-), periods (.), spaces ( ), and underscores (_). Microsoft Mail names that
have special characters, such as dollar sign ($), tilde (~), percentage (%),
or caret (^), generate name errors when added to the registration queue.
The migration tool validates and creates Notes name components from
the Microsoft Mail full name, not the mailbox name.
Note After adding users to the registration queue, always review the
names that the Microsoft Mail Domino Upgrade Service generates to
ensure that they are appropriate. Edit names as necessary.
Generating Notes name components from Microsoft Mail names

The following table shows how the Microsoft Mail Domino Upgrade
Service generates Notes names from common Microsoft Mail name
formats:
Format of Microsoft Mail full name Resulting Notes name components

Description Example Components Example
Single name ssalani Last name ssalani
First name <blank>
Middle name <blank>
First name Last name Susan Salani Last name Salani
First name Susan
Middle name <blank>
First name Compound Maria de la Last name la Garza
last name Garza First name Maria
Middle name de
First name Middle Initial Judy J. Kaplan Last name Kaplan
Last name First name Judy
Middle name J.
First name Middle name Cheryl Lynn Last name Lordan
Last name Lordan First name Cheryl
Middle name Lynn
continued
Migrating Users from Microsoft Mail 12-3

Format of Microsoft Mail full name Resulting Notes name components
Compound first name Jo Anne B. Last name B. Lordan
Middle initial Last name Lordan First name Jo
Middle name Anne
Last name, First name Salani, Susan Last name Salani
First name Susan
Middle name <blank>
Compound last name, Van Horn, Craig Last name Van Horn
First name First name Craig
Middle name <blank>
Compound last name, Van Horn, Jo Last name Van Horn
Compound first name Anne B. First name Jo
Middle initial Middle name Anne
Last name, First name Rutherford, Last name Rutherford
Middle Initial Robin R. First name Robin
Middle name R.
Last name, First name Malone, Derek Last name Malone
Middle Name Kevin First name Derek
Middle name Kevin
Parsing names that have no blank spaces or commas

The Microsoft Mail Domino Upgrade Service places the entire name in
the Last name field of the Notes Person document. For example, for the
Microsoft Mail name ssalani the Microsoft Mail Domino Upgrade Service
generates a Notes Last name of ssalani, and leaves the First name and
Middle name fields blank.
Parsing names that include a comma

The Microsoft Mail Domino Upgrade Service places all of the characters
preceding the comma in the Notes Last name field and all of the charac-
ters after the comma, but before a space, in the First name field. The
middle name is placed in the Middle name field.
Parsing names with three components that have spaces and no

commas
Example: Cheryl Lynn Lordan
The Microsoft Mail Domino Upgrade Service places all of the characters
after the last blank space in the Last name field. All of the characters
from the beginning of the name string and before the first space are
placed in the First name field. The middle name after the first space, and
before the second space, are placed in the Middle name field.
12-4 Upgrade Guide

Parsing names of four or more components that have spaces, and
no commas
Example: Craig G. Van Horn
The Microsoft Mail Domino Upgrade Service places the first component
in the First name field; the second component in the Middle name field;
and all remaining components in the Last name field.
Parsing errors
In some cases, the Microsoft Mail Domino Upgrade Service does not
correctly parse Microsoft Mail names:
• Names in the form Last name, First name Middle name that include
compound first names.
Example: Horn, Jo Anne B.
The Microsoft Mail Domino Upgrade Service generates the following
Notes name components:
First name: Jo; Middle name: Anne; Last name: Horn
• Names in the form First name Middle initial Last name that include
compound last names and no middle initial.
Example: Maria de la Garza
First name: Maria; Middle name: de ; Last name: la Garza.
• Names in the form First name Middle initial Last name that include
compound first names and a middle initial.
Example: Jo Anne B. Horn
First name: Jo ; Middle name: Anne ; Last name: B. Horn
You can edit incorrectly parsed names in the Register Person dialog box
before you register the users.
Preparing to migrate Microsoft Mail users

Before migrating users from Microsoft Mail to Notes, complete the
following tasks:
• Determine the order in which you want to convert your postoffices.
This should be your migration schedule.

registering users.
• On your administrative workstation, install the Domino 6
Administrator client and optional MS Mail Administrative migration
tools. You must perform a custom installation to install the migration
tools component.
• From the administrative workstation, log in to Notes with a Notes ID
that has “Create database access” on the Mail server.
• From the administrative workstation, map a drive to the location of
the Microsoft Mail Postoffice you are migrating users from.
• If you anticipate migrating additional mail for users after
registration, configure the mail file ACLs to ensure that you retain
the appropriate access rights. Use the migration option Adding an
administrator to mail file access control list.
For instructions on how to change the default access level, see the
For more information about setting default registration preferences,
see the book Administering the Domino System.
For more information about adding migrated users to Notes groups,
• Send any pending Microsoft Mail messages.
• Back up the mailbox files stored at the postoffice. If you do not have
an MS Mail administrator who backs up mailbox files on a regular
basis, refer to the Microsoft Mail Administrator’s Guide for instructions
on backing up data.
• On the administrative workstation, close all applications, except for
Notes, and close any Notes databases.
Backing up Domino Information

Before you migrate users, it is recommended that you back up the
following Domino information:
• NAMES.NSF
• DESKTOP.DSK
12-6 Upgrade Guide

• NOTES.INI
• *.ID files
Importing the Microsoft Mail Postoffice Address List

The Microsoft Mail Postoffice Address List contains information for the
Microsoft Mail users who have mailboxes in that post office. Notes uses
the information extracted from the postoffice address list to configure
migrated users for registration.
To import the Microsoft Mail Postoffice Address List, you must:
• Connect to the Microsoft Mail Postoffice
• Import users
users in Notes.
Connecting to the Microsoft Mail Postoffice
To import users to migrate, locate the postoffice where users have their
mailboxes and log in to it.
3. When prompted, enter the certifier ID password and click OK.
box, click Registration Server and select the server that registers new
users. Click OK.
6. From the People and Group Migration dialog box, select MS Mail
Users from the Foreign directory source list.
7. Complete the following information in the MS Mail Initialization
dialog box:
• Postoffice path
• Administrator’s name
• Administrator’s password
8. Click OK. The Microsoft Mail Domino Upgrade Service verifies the
postoffice name, path, and password. An error message appears if
any of the values are incorrect.

The Available people/groups list displays the users and groups in
the postoffice address list. You are now ready to import users from
the postoffice into the Notes registration queue.
For more information about importing users from the postoffice, see
the topic “Importing Microsoft Mail users into the registration
queue” later in this chapter.
Importing Microsoft Mail users into the registration queue

Microsoft Mail Postoffice Address List, select the users to import and the
migration options that determine the data to migrate.
1. From the People and Groups Migration dialog box, select items in
the Migration Options box. The options you select apply to all
Microsoft Mail users imported during this session. Click OK.
2. Click Advanced to open a dialog box that lets you specify advanced
upgrade settings for migrating people from Microsoft Mail.
For information about advanced migration options, see the topic
“Specifying advanced options for Microsoft Mail users” later in this
chapter.
3. Click OK when you finish specifying these settings.
migrate and click Add. To add all users and groups, click Add All.
For more information about importing groups, refer to the chapter
“Overview of Domino Upgrade Services.”
and click OK to close the message that indicates the status and
number of users queued for registration.
6. Click Done. The people queued for registration now appear in the
Registration status box. You are now ready to register users.
Customizing Microsoft Mail migration settings

When you are ready to import users, you can set options to specify how
the Microsoft Mail Domino Upgrade Service uses information from the
Microsoft Mail Postoffice to create Notes users. You can specify two
types of migration settings:
12-8 Upgrade Guide

• Migration options — determine how the migration tool creates a user
in Notes from information imported from Microsoft Mail. The
migration options available are similar for each of the migration
tools.
• Advanced options — let you specify additional settings affecting
conversion from Microsoft Mail and Notes.
Setting migration options for Microsoft Mail users

You can set options to determine what information the Microsoft Mail
Domino Upgrade Service imports from the Microsoft Mail Postoffice. The
options you specify apply to all users and groups imported from Micro-
soft Mail during this session.
2. In the Migration Options box, accept the defaults or select new
options. To clear a selection, click the selected option a second time.
The following table lists the available import options:
Generate random passwords for users with no Off
passwords
Add full name provided to the Notes person Off
document
Convert mail On
Convert mail ONLY (Notes user and mail file must Off
already exist)

options.
Within a given session, you set migration options for each foreign direc-
tory independently, so that if you are migrating users from several
systems, you can apply a different set of options for each system. The
options you select apply to all users imported from a given directory
during the session.

Specifying advanced options for migrating Microsoft Mail users
In addition to the migration options set on the People and Groups Migra-
tion dialog box, the Microsoft Mail Domino Upgrade Service provides
other options for controlling the process of migrating Microsoft Mail
users. The settings you select apply to all users you import from the
Microsoft Mail post office during this session.
1. From the People and Groups Migration dialog box, click Advanced.
2. From the MS Mail Advanced Options dialog box, choose settings for
the following, then click OK:
• Migrating Personal Address Books
• Setting an error threshold
• Specifying the post office language (code page)
Specifying the code page to use for converting the Microsoft Mail
Postoffice
When migrating users from Microsoft Mail, you need to specify the
language code page to use so that the Microsoft Mail Domino Upgrade
Service can correctly convert characters to be displayed in Notes. By
default, the Microsoft Mail Domino Upgrade Service uses the current
code page of the postoffice. If necessary, specify the appropriate code
page for the language version used by the postoffice being migrated. The
following table shows the code pages available for a Microsoft Mail
Postoffice:
Postoffice language version Code page number

Arabic 1,256
Canadian French 863
Chinese (Traditional) 950
Chinese (Simplified) 936
Czech 1,250
Danish 1,252
Dutch 1,252
English 1,252
Finnish 1,252
French 1,252
German 1,252
Greek 851
continued
12-10 Upgrade Guide

Postoffice language version Code page number
Hebrew 862
Hungarian 1,250
Icelandic 1,252
Indonesian 1,252
Italian 1,252
Japanese 932
Korean 949
Multilingual 1,252
Nordic 865
Norwegian 1,252
Polish 1,250
Portuguese 1,252
Romanian 1,250
Russian 1,251
Serbian 1,250
Slovak 1,250
Spanish 1,252
Swedish 1,252
Thai 874
Turkish 857
Ukrainian 1,251
Specifying an error threshold

You can specify the number of errors to tolerate when migrating
messages from mailboxes in the Microsoft Mail Postoffice to Notes mail
files. By default, the migration tolerates an unlimited number of errors,
and completes the migration regardless of the error count. If you specify
an error threshold, the migration process terminates when it reaches the
number of errors specified.
1. Select the Maximum Errors radio button.
2. In the text box, enter the number of errors to tolerate.
Users who are successfully processed before the error threshold is
reached are registered in Notes. If the migration terminates, you should
analyze and resolve the error conditions reported for the users who
remain in the queue and attempt to register them again.

Migrating Microsoft Mail Personal Address Books to Notes
By default, when you migrate a user from Microsoft Mail, the Personal
Address Book information stored with the mailbox is also migrated.
After the migration completes, the Domino Administrator automatically
places a message in the Inbox of the user’s mail file to which it attaches a
temporary Notes Personal Address Book, which contains the migrated
information. Users run the upgrade wizard for Microsoft Mail at the
Notes client to copy the information from this temporary Notes
document to the Personal Address Book on the Notes desktop.
To prevent migration of Personal Address Book information, clear the
Convert Personal Address Book check box and click OK.
Registering users and completing the migration from Microsoft Mail

After you successfully import users into the Registration Queue, you are
• Creates a Notes Person document and Notes ID
• Migrates messages and other data from the Microsoft Mail mailbox
so forth.
For more information about advanced user registration, see the book
you can stop the registration process by pressing CTRL-Break.
2. (Optional) Click the Options button, and select the registration
options to apply during this session and click OK.
3. (Optional) Specify additional registration information for users as
necessary. If you created a ‘migration’ group, open the Groups pane
and assign users to this group now.
12-12 Upgrade Guide

users in the order in which they were added to the queue and
migrates data from their mailboxes to Notes. Users whom you do not
select remain in the queue for later registration.
registration status. Failed registrations continue to be listed in the
Registration status box with a status message indicating the reason
for the failure. Correct registration settings as needed and attempt to
register the user again.
After the migration is complete, users can run an upgrade wizard to
convert local mail archives and other Microsoft Mail data that the
Domino migration tool did not process.
Microsoft Mail on the Notes client, see the chapter “Migrating Personal
Mail Data.”

Mail” (that is, the option remains selected), the Domino Administrator
automatically converts users’ Microsoft Mail mailboxes to Notes mail
files as part of the registration process. On the Mail pane of the Register
Person dialog box, the option “Create mail file now” is selected. An error
message is displayed if you attempt to change this option to create mail
files using the background Domino Administration Process.
Migrating additional Microsoft Mail messages after registration

After you migrate users, you can run the Microsoft Mail Domino
Upgrade Service again to migrate additional messages from Microsoft
Mail. You must have Manager access to a user’s Notes mail file before
you can migrate additional messages to it. By default, administrators do
not have Manager access to mail files. If you did not give yourself

Manager access to the mail file when preparing for the initial migration,
you may need to ask users to edit the ACL to provide you with the
appropriate access rights.
1. Connect to the Microsoft Mail Postoffice.
2. Import previously migrated Microsoft Mail users into the Notes
registration queue.
3. Set the migration option Convert Mail ONLY. The migration tool
ignores any other options that are set.
4. In the Registration status box, select the users whose messages you
want to migrate and click Register.
The registration process automatically locates the users’ mail files and
converts messages in the Microsoft Mail mailbox to messages in the
appropriate folders of the Notes mail file. Messages that already exist in
the Notes mail file are not converted again.
For more information about the Convert Mail ONLY option, and about
how to retain Manager access to mail files after migration, see the chapter
12-14 Upgrade Guide

Chapter 13
Migrating Users from Microsoft Exchange
This chapter discusses issues involved in migrating users from Microsoft

Exchange to Lotus Domino 6 and provides instructions on using the
Domino Administrator and Microsoft Exchange Domino Upgrade
Service to complete the migration.
Migrating Microsoft Exchange users

Using the Microsoft Exchange Domino Upgrade Service in the Domino
Administrator, you can import Microsoft Exchange users and distribu-
tion lists from a selected server and add them to the Domino Directory as
Notes users and groups. The migration process:
• Imports users and distribution lists from the Exchange server and
creates entries for them in the Domino Directory
• Migrates the contents of mailboxes (PST files) that are located in a
central location, such as on the Microsoft Exchange server. Mail
messages, Calendar entries, and Tasks are all migrated.
This section of the migration guide discusses the following topics related
to moving users from Microsoft Exchange to Notes:
• Notes equivalents for migrated Microsoft Exchange data
• Preparing to migrate users from Microsoft Exchange
• Importing users and groups from the Microsoft Exchange directory
• Registering migrated users
Notes equivalents for migrated Microsoft Exchange data

The Microsoft Exchange Domino Upgrade Service converts information
from the Microsoft Exchange server to Notes, including messages and
contact information as shown in the following table.
13-1
Microsoft Exchange/Outlook data Equivalent Notes data
Calendar and scheduling information Calendar view of the Notes Mail file
Contacts Personal Address Book entries*
Custom message types, including Not migrated
Scheduler messages
Deleted items Trash folder**
Delivery failure messages Not migrated
Digital signatures Not migrated
Distribution lists Group document in Domino Directory
Encrypted messages Not migrated
Document links Not migrated
Journals Not migrated
Message date and priority Message date and priority
Messages and attachments Messages and attachments
Microsoft Office documents Messages with attached Microsoft
Office document
Notes To Do tasks
Outbox folder Drafts folder
Sent folder Sent folder
Exchange directory Person documents in Domino
Directory
Private Address Book Not migrated
Public folders Not migrated
Read and unread status Not migrated***
Roles and Permissions on Mailboxes Not migrated
and Folders
Tasks To Do tasks
*Contacts, which are stored on the Exchange server, are available for Outlook
clients only. During migration Contacts information is placed in a Notes
Personal Address Book database, which is automatically mailed to the user.
Users run the upgrade wizard for Microsoft Exchange to copy information from
this temporary database to the Personal Address Book on the Notes client.
**Depending on the user preferences set at the Notes client, messages migrated
to the Trash folder may be deleted when users close their mail files.
***The Microsoft Exchange Domino Upgrade Service marks all messages
migrated from Microsoft Exchange as unread in the Notes mail file.
13-2 Upgrade Guide

Modifying gateway names in migrated messages
When migrating messages and directory information from Exchange,
Microsoft Exchange Domino Upgrade Service does not automatically
convert the names of Exchange gateways in the sender’s address to
Notes gateway addresses. After they begin using Notes mail, users who
reply to messages that were received from an external messaging system
and migrated from Exchange may need to manually edit the gateway
address of the recipient.
Locating the Microsoft Exchange mail file

The Microsoft Exchange client stores mail messages and Calendar entries
in a PST file, which is roughly equivalent to the MMF that Microsoft Mail
clients use. However, unlike Microsoft Mail, which stores both the user’s
Personal Address Book and mail messages in a single MMF file, Micro-
soft Exchange uses different files to store these two items.
Exchange clients store a user’s Personal Address Book in a PAB file,
which is usually located on the user’s workstation. Users can run the
Microsoft Exchange to Notes upgrade wizard to migrate information
from a locally-stored PAB file to the Notes Personal Address Book
(NAMES.NSF) on the workstation.
Outlook clients can store personal addresses in a PAB file, or in a
Contacts list on the Exchange server. The Microsoft Exchange Domino
Upgrade Service automatically places Contacts information in a tempo-
rary Notes Personal Address Book, which it attaches to a mail message
and places in the Inbox of the migrated user. Microsoft Exchange
Domino Upgrade Service generates a warning message in the Notes log
for each migrating user for whom Contacts information is not found.
Users can run the Microsoft Exchange to Notes upgrade wizard to
migrate address information from a temporary Personal Address Book to
the Personal Address Book on the workstation.
The Microsoft Exchange mail box is stored in a PST file, which can be
stored either locally or on the Exchange server. The Microsoft Exchange
Domino Upgrade Service can migrate information only from PST files
that are located on the Exchange server. Users can run the Microsoft
Exchange to Notes upgrade wizard at their workstation to migrate
messages and other items from locally-stored PST files.
Migrating messages from the Outbox and Sent Items folders

All Exchange mailboxes contain the folders Outbox and Sent Items. When
you migrate mail for Exchange users, these folders are not added to the
Notes mail file. However, in general, the messages in these folders are
migrated. Messages in the Sent Items folder are migrated to the Notes Sent
folder, and messages in the Outbox folder are migrated to the Drafts folder.
Migrating Users from Microsoft Exchange 13-3

If a user manually copied received messages to the Outbox, or saved
unsent, draft messages to the Sent Items folders (for example, by using a
drag-and-drop operation), Microsoft Exchange Domino Upgrade Service
migrates the messages, but does not place them in the equivalent Notes
Drafts and Sent folders. After migration, users must select the All
documents view to see the messages.
Migrating an Exchange folder that has the same name as an existing

Notes folder
If a folder in a migrating Exchange mailbox has the same name as a
folder view that already exists in the Notes mail file (for example, Discus-
sion Threads), Microsoft Exchange Domino Upgrade Service appends the
numeral 1 to the name of the folder name to make it unique (for example,
Discussion Threads1). Additional duplicates are numbered sequentially
to ensure uniqueness (for example, Discussion Threads2, Discussion
Threads3, and so forth).
Preparing to migrate Exchange users

Before migrating users from Microsoft Exchange to Notes, complete the
following tasks:
• Determine the order in which you want to convert your Exchange
servers to Notes. This should be your migration schedule.
Administrator client and the optional Microsoft Exchange Domino
Upgrade Service. You must perform a custom installation to install
the migration tools component.
registering users.
• From the administrative workstation, log in to Notes with a Notes ID
• On the administrative workstation, close all applications except for
13-4 Upgrade Guide

For information about adding migrated users to a group, see the
• Send any pending Microsoft Exchange messages by making sure
Synchronization has been performed on each client.
• Perform an Exchange Directory Synchronization to ensure that the
Exchange directory being migrated is complete. For more
information about Exchange Directory Synchronization, refer to the
Microsoft Exchange documentation.
• Make sure the workstation running the Domino Administrator has
an Outlook or Exchange client installed and an Administrator mail
profile that points to the Exchange server.
For more information about the administrator mail profile, see the
topic “Specifying an administrator mail profile” later in this chapter.
Importing the Microsoft Exchange directory
The Microsoft Exchange directory contains information for the Microsoft
Exchange users who will be migrated to Notes. Notes uses the informa-
tion extracted from the directory to configure migrated users for
registration.
Importing the Microsoft Exchange directory involves the following:
• Connecting to the Exchange server
• Importing Microsoft Exchange users into the registration queue
users in Notes.
Connecting to the Exchange server

To import users to migrate, locate the Exchange server where users have
their mailboxes, and log in to it.
users. Click OK.

6. From the People and Group Migration dialog box, select Microsoft
Exchange Users from the Foreign directory source list.
7. From the Choose Profile dialog box, select the administrator mail
profile that connects to the Exchange server and click OK.
The Microsoft Exchange Domino Upgrade Service fails to load if you
do not specify an appropriate mail profile.
For more information about the administrator mail profile, see the
topic “Specifying an administrator mail profile” later in this chapter.
Note If you are not logged in to the Windows NT domain where the
Exchange server is located, you are prompted to supply a user name
and password for the domain.
The Available people/groups box displays the names of contents of
the postoffice address list. You are now ready to import users from
the postoffice into the Notes registration queue.
Specifying an administrator mail profile

To migrate users from Exchange, you must connect to the Exchange
server that has the mailboxes you want to migrate. You connect to an
Exchange server by selecting the Administrator mail profile for the
Exchange server that you want to migrate. The Administrator account,
which must have the Service Account Administrator role for the
Exchange site and server, gives you full access to all accounts and
mailboxes in the Exchange server directory.
The profile you use should connect with Microsoft Exchange server
service only; do not use a profile that connects to multiple messaging
services. If necessary, create a new profile for use during migration. The
profile must be available locally or on a network drive accessible from
the workstation where you are running the Domino Administrator.
Importing Microsoft Exchange users into the registration queue

Microsoft Exchange server directory, select the users to import and the
migration options that determine the data to migrate.
1. From the People and Groups Migration dialog box, enable options by
selecting items in the Migration Options box. The options you select
apply to all Microsoft Exchange users imported during this session.
For more information about migration options, see the topic “Setting
migration options for Microsoft Exchange users” later in this chapter.
13-6 Upgrade Guide

migrate and click Add. To add all users and groups, click Add All.
For more information about importing groups, see the chapter
4. Click Done.
The people queued for registration now appear in the Registration
status box. You are now ready to register users.
Setting migration options for Microsoft Exchange users

You can set options to determine what information Microsoft Exchange
Domino Upgrade Service imports from the Microsoft Exchange server.
The options you specify apply to all users and groups imported from
Microsoft Exchange during this session.
For more information about the available migration options, see the topic
“Setting migration options.”
2. In the Migration Options box, select the options you want. To clear a
selection, click the selected option a second time. The following table
lists the options available for migrating users from an Exchange
server:
Generate random passwords for users with On
no passwords
Add full name provided to the Notes person Off
document
Convert mail On
You set migration options independently for each migration tool, so that
if you are migrating users from multiple mail systems, you can apply a
different set of options for each system. The options you select apply to
all users imported from a given directory during the session.

Registering users and completing the migration from Exchange
user
For more information about the Notes mail file, see the topic
“Creating the Notes mail file” later in this chapter.
• Migrates messages and Calendar entries from the Microsoft
Exchange PST file
so forth.
For more information about advanced user registration options, see the
you can stop the registration process by pressing CTRL+Break.
2. (Optional) Click the Options button, and select the registration
users in the order in which they were added to the queue, and
migrates data from their mailboxes to Notes. Users whom you do not
select remain in the queue for later registration.
13-8 Upgrade Guide

After the migration is complete, users can run an upgrade wizard to
convert local mail archives and other Microsoft Exchange data that the
Domino migration tool did not process.
Microsoft Exchange on the Notes client, see the chapter “Migrating
Personal Mail Data.”

Mail” (that is, the option remains selected), when you register migrated
users, the Domino Administrator automatically converts their Microsoft
Exchange mail files to Notes mail files as part of the registration process.
On the Mail pane of the Register Person dialog box, the option “Create
mail file now” is selected. An error message is displayed if you attempt
to change this option to create mail files using the background Domino
Administration Process.

Chapter 14
Migrating Users from a Windows NT Domain List
This chapter discusses issues specific to migrating users from a Windows

NT domain list using the Windows NT Domino Upgrade Service.
Migrating Windows NT users

Using the Windows NT Domino Upgrade Service in the Domino Admin-
istrator, you can import users and groups from a selected Windows NT
domain and register them as Notes users. The migration process:
• Imports users and groups from the Windows NT domain list and
creates Person documents for them in the Domino Directory
You can choose to create unregistered users, that is users without Notes
IDs and mail files. However, if you do, those users cannot access all
Domino resources.
Follow this procedure to migrate Windows NT users to the Domino
Directory:
• Prepare to import users from Windows NT
• Specify the Windows NT domain to import from
• Set migration options for Windows NT users
• Specify advanced options for Windows NT users
• Import Windows NT users into the Notes registration queue
• Register users and complete the migration from Windows NT
Note that setting migration and advanced options for Windows NT users
are optional steps in this procedure.
14-1
Preparing to import users from Windows NT
You need to complete a number of tasks to prepare for a successful
migration:
• Determine the order in which you want to move users from
Windows NT domains to Notes. This should be your migration
schedule.
registering users.
• Log into Windows NT as an Administrator or Account Operator of
the domains you want to import users from. To migrate Windows
NT users to Notes, the computer where you run the Domino
Administrator must be running Windows NT.
• If you are creating Notes mail files for imported users, log in to Notes
from the administrative workstation using a Notes ID that has
“Create database access” on the Mail server.
• On an administrative workstation running Windows NT, install the
Domino 6 Administrator client and the Windows NT Domino
Upgrade Service. You must perform a custom installation to install
the migration tools component.
• Verify that you have Read/Write/Update access to the Domino
Directory on the server used for migration.
14-2 Upgrade Guide

Specifying the Windows NT domain to import from
The following procedure explains how to connect to a Windows NT
domain and retrieve the domain list. After you retrieve the domain list,
you can import users and groups from it to the registration queue. You
must be an Administrator or Account Operator in the domain to
complete this procedure.
Note In order to migrate Windows NT users to Notes, the computer
where you run the Domino Administrator must be running Windows NT
or Windows 2000 Professional connected to your NT domain.
box, click Registration Server, then select the server that registers
new users. Click OK.
6. From the People and Group Migration dialog box, select Windows
NT Users/Groups from the Foreign directory source list.
7. From the Choose Windows NT Domain dialog box, specify the
Windows NT domain to import from and click OK.
You can select a domain from the list, or enter the name of a different
domain.
Note If a domain controller for the selected Windows NT domain is
not available, an error message appears and the Available Users box
displays the default list of local user accounts.
8. In the People and Group Migration dialog box, select a filter, then
click Go! to display entries in the Available people/groups box.
9. Continue on to one of the following procedures:
If you want to set migration options, see the topic “Setting migration
options for Windows NT users” later in this chapter.
If you want to set advanced migration options, see the topic “Specifying
advanced options for importing Windows NT users” later in this chapter.
If you want to import users, see the topic “Importing Windows NT uses
into the Notes registration queue” later in this chapter.
Migrating Users from a Windows NT Domain List 14-3

Importing Windows NT users into the Notes registration queue
Windows NT domain list, select users to import and the migration
options that determine the data to migrate.
1. In the People and Groups Migration dialog box, select users and
groups to migrate from the Available people/groups box, then click
Add. To migrate all users and groups, click Add All.
For more information about importing groups, refer to the chapter
3. Click Done.
status box. You are now ready to register users.
Setting migration options for Windows NT users

You can set options to determine what information the Windows NT
Domino Upgrade Service imports from the Windows NT domain list.
The options you specify apply to all users and groups imported from
Windows NT during this session.
1. In the People and Groups Migration dialog box, click Options.
2. In the Migration Options box, select the options you want. To clear a
selection, click the selected option a second time. The following table
lists the options available for migrating users from a Windows NT
domain:
Generate random passwords for users with no passwords On
Generate random passwords for all users (overwrite Off
existing passwords)
Add full name provided to the Notes person document Off
14-4 Upgrade Guide

Note Existing Windows NT passwords are not imported by the
Windows NT Domino Upgrade Service. If you disable the option to
generate passwords, you must supply passwords for each user
imported to the registration queue before you can register them.
settings.
You set migration options independently for each Domino Upgrade
Service, so that if you are migrating users from multiple systems, you can
apply a different set of options for each system. The options you select
apply to all users imported from a given directory during the session.
Specifying advanced options for importing Windows NT users

In addition to the basic import options set on the People and Groups
Migration dialog box, you can set options that determine how the
Windows NT Domino Upgrade Service processes names imported from
Windows NT. The settings you select apply to all users that you import
from the Windows NT domain during this session.
1. In the People and Groups Migration dialog box, click Advanced.
2. From the Windows NT User Upgrade Options dialog box, choose
settings for the following, then click OK:
• Name format for full name parsing
• Retain unique Windows NT user name as Notes short name
Creating Notes short names from Windows NT user names

You have the option to generate Notes short names for imported users
based on their Windows NT user names.
On the Windows NT User Upgrade Options dialog box, select the
“Retain unique NT user name as Notes short name” check box. The
Windows NT user name is added as the primary entry in the short name
field of the Person document.
The short name is the default for the mail file name and the user ID file
name. If you do not select the short name option, Notes generates a short
name from the first character of the user’s first name, followed by the
first seven characters of the last name, for example ssalani, for the user
Susan Salani.

Specifying how to convert Windows NT full names into Notes name
components
You can specify how the full names of Windows NT users are parsed into
Notes name components during migration. You specify a parsing format
as follows:
From the Windows NT User Upgrade Options dialog box, select the
format from the “Name format for full name parsing” box. The Windows
NT Domino Upgrade Service automatically parses imported Windows
NT full names into Notes first name and last name components accord-
ing to the specified parsing format.
In Windows NT, there are two types of names associated with a user
account, a unique user name and a full name. The Windows NT user
name consists of a string of up to 20 characters and has no required
format. The full name is optional and generally represents the user’s
complete name, formatted according to the conventions of the organiza-
tion, such as last name followed by first name. For example, in the
Windows NT domain list, the user Susan Salani might have the user
name ssalani, and the full name Salani Susan.
In Notes, name information is stored as separate first name, middle
name, and last name components. For example, the name Susan Salani is
stored not as a single full name, but as separate first name (Susan) and
last name (Salani) components. When you import names from a
Windows NT domain list, you need to specify how users’ full names will
be converted into Notes name components.
In Notes the following formats are available:
Notes name format Example

Firstname Lastname Susan Salani
Title Firstname Lastname Dr. Susan Salani
Firstname Middlename Lastname Susan Rachel Salani
Title Firstname Middlename Lastname Dr. Susan Rachel Salani
Firstname Lastname1 Lastname2 Susan Mills Salani
Title Firstname Lastname1 Lastname2 Dr. Susan Mills Salani
Title Lastname Dr. Salani
Lastname Firstname Salani Susan
Title Lastname Firstname Dr. Salani Susan
Lastname, Firstname Salani, Susan
Lastname, Title Firstname Salani, Dr. Susan
continued
14-6 Upgrade Guide

Notes name format Example
Lastname, Title Firstname Middle Name Salani, Dr. Susan Rachel
Lastname1 Lastname2, Firstname Mills Salani, Susan
Lastname1 Lastname2, Title Firstname Mills Salani, Dr. Susan
Selecting a parsing format

When you import users from a Windows NT domain list, you have the
option of selecting the parsing format to use in converting Windows NT
full names into the components of a Notes name (First name, Middle
name, and Last name). The default parsing format assumes that the full
names in the Windows NT domain list are entered in First name Last name
format (for example, Susan Salani). If the domain list you import uses a
different format, select the most compatible parsing format.
If the Windows NT Domino Upgrade Service cannot parse a name
correctly — for example, if the number of name components in the
Windows NT full name does not equal the number of name components
in the specified parsing format — the Adjust Windows NT User Name
Components dialog box appears. The dialog box specifies whether the
Windows NT full name has too few or too many components to accom-
modate the parsing format selected. For example, if you specify the
format Title Firstname Lastname and the full name is Susan Salani, the
dialog indicates that too few components have been specified. “Susan” is
placed in the Title field and “Salani” in the First name field.
On the other hand, if you select the parsing format Lastname, Firstname,
and the full name is Susan R. Salani, the dialog box indicates that there
are too many components to accommodate the parsing format selected.
Rather than discarding the extra components, and placing just the middle
initial in the Firstname field, the Windows NT Domino Upgrade Service
places “Susan” in the Last name field, and “R. Salani” in the First name
field.
An incompatible parsing format may require considerable editing to
create suitable Notes names. If you do not adjust names in the dialog
box, the names added to the registration queue may not be suitable for
registering users. Always be sure that each imported name has a last
name component; Notes requires a valid last name component to register
users.
Note The Windows NT Domino Upgrade Service only checks whether a
parsed name is missing components for the format specified; it does not
verify that components appear in the correct field, or check for invalid
characters. For example, the Windows NT Domino Upgrade Service does
not check whether the first name component contains title information.

Importing users who do not have full names
If there is no full name to import from Windows NT, the Windows NT
Domino Upgrade Service does not prompt you to make any adjustments.
Instead, the Windows NT Domino Upgrade Service automatically adds
the Windows NT user name to the Notes Last name field, regardless of
the specified parsing format. For example, if you import the user name
ssalani from the Windows NT domain list, the user added to the registra-
tion queue has a last name of ssalani and no first name. You can edit the
name in the registration queue as needed, adding S or Susan to the First
name field and changing the Last name field to Salani.
Registering users and completing the migration from Windows NT

user
• Creates a Notes mail file for each migrated user
so forth.
For information about advanced user registration options, see the book
2. (Optional) Click the Options button and select the registration
3. Specify additional registration information for users as necessary. If
you created a ‘migration’ group, open the Groups pane and assign
users to this group now.
users in the order in which they were added to the queue. Users
whom you do not select remain in the queue for later registration.
14-8 Upgrade Guide

depending on the number of users imported.
For information on how to verify that the migration was successful, see

Chapter 15
Migrating Users from an LDIF File
This chapter discusses issues specific to migrating users from an LDAP

Data Interchange Format (LDIF) file using the LDIF Domino Upgrade
Service.
Migrating users from an LDIF file

Using an LDIF export tool in combination with the LDIF Domino
Upgrade Service, you can migrate users from any LDAP-compliant exter-
nal directory and add them to the Domino Directory.
The LDIF Domino Upgrade Service creates Person documents in the
Domino Directory from the person entries in an LDIF file. Optionally,
you can create Notes IDs and mail files for migrated users and register
them as Notes users. Unregistered users who have no Notes IDs or mail
files can be added to Domino as directory entries only. That is, the LDIF
Domino Upgrade Service creates Person documents for the users.
However, the unregistered users cannot log in to Notes and access
Domino resources.
Note The LDIF Domino Upgrade Service does not process LDIF group
entries.
The following topics how to migrate users to Notes from LDIF files:
• What is LDIF?
• Understanding how Notes uses information in the LDIF file
• Preparing to import an LDIF file
• Specifying the LDIF file to migrate from
• Registering users migrated from an LDIF file
• Adding imported users as directory entries only
15-1
What is LDIF?
LDIF (LDAP Data Interchange Format - RFC 2849) is a data format
standard for conveying information from a directory that complies with
the Lightweight Directory Access Protocol (LDAP). You can use LDIF
files to import users from any LDAP directory to Notes.
Each entry in the LDIF file contains a sequence of lines describing a
directory object and its attributes as shown in the following example.
dn: cn=Susan Salani, ou=Human Resources, o=Acme Corporation,
c=US
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
cn: Susan Salani
cn: Susan R Salani
cn: Sue Salani
sn: Salani
uid: ssalani
telephonenumber: +1 888 555 1212
facsimiletelephonenumber: +1 888 555 1999
mail: ssalani@acme.com
roomnumber: 1111
userpassword: password
Understanding how Notes uses information in the LDIF file

The LDIF Domino Upgrade Service validates entries before migrating the
user described in the entry. Valid entries must include the following
attributes:
• Distinguished name (DN)
• Surname (SN, S, or SurName)
• Object classes
15-2 Upgrade Guide

The object class definition top is required for all entries, as is an object
class specifying the type of entry (for example, person). Other object
classes are optional. Entries in the file must be separated by a blank line.
When the migration tool encounters an entry that does not contain all of
the mandatory information, it skips it and logs the error in the Notes log.
The LDIF Domino Upgrade Service attempts to migrate entries based on
a standard supported LDAP schema. Some schemas may use LDAP
attributes that do not have equivalent fields in the Notes Person
document. If the LDIF Domino Upgrade Service cannot map an attribute
to a Notes equivalent, it skips it and logs the error in the Notes log.
Adding the distinguished name to the Person document

The LDAP distinguished name (DN) represents not only a user’s name,
but also the user’s location in the organizational hierarchy, as defined by
attributes which specify the organizational unit, organization, and
country. For example, the following distinguished name tells you that the
user named Susan Salani is in the Human Resources division of the
Acme Corporation, located in the United States:
dn: cn=Susan Salani, ou=Human Resources, o=Acme Corporation,
c=US
This hierarchical structure is similar to the one that Notes uses in forming
the primary names of registered users, except that, in Notes, information
about a user’s organization and organizational unit come from the certi-
fier ID used during registration.
Because the hierarchical information in imported distinguished names
may conflict with Notes hierarchical information, by default the LDIF
Domino Upgrade Service does not add the distinguished names to the
User name field of the Person document when you register users
imported from an LDIF file. The LDAP attributes O (Organization), and
OU (Organizational Unit), and C (Country) are not mapped to fields in
the Person document. Each mapping failure is noted in the Notes log.
If the users you migrate from an LDIF file will become directory entries
only, and not registered Notes users, (that is, you will not create Notes
IDs and mail files for them), you may want their Person documents to
include the original distinguished names in their LDIF entries. The LDIF
Domino Upgrade Service can add the original distinguished names from
the migrated LDIF entries to the Person document as secondary values in
the User name field of the Person document.
The primary entry in the User Name field of the Person document is
always derived from the First Name and Last Name components,
together with the organizational information taken from the certifier ID.
Migrating Users from an LDIF File 15-3

To add the original distinguished names from migrated LDIF entries as
secondary values in the User name field, select the migration option
“Add full name provided to the Notes Person document” on the People
and Groups Migration dialog box.
Processing object classes

The LDIF Domino Upgrade Service supports the migration of any
foreign LDAP entry that exists in the Person Object class or any
EXTENDED object class that is considered a “descended” object class of
person (that is, a subclass of the “person” object class).
If the LDIF Domino Upgrade Service does not find one of those object
classes when importing an LDIF file, then the entry is skipped because it
does not meet the criteria for being migrated as a person.
The LDIF Domino Upgrade Service supports the importing of Persons
only. It does not import groups or schemas.
Generating Notes name components from LDAP attributes

The LDIF Domino Upgrade Service generates Notes name components
from values in the following attributes in a user entry:
LDAP attribute Notes name component generated during migration

GN or GivenName First name
MiddleName Middle name
SN, S, or SurName Last name
Migrated users are successfully added to the registration queue regard-

less of whether their entries include GivenName (or GN) or MiddleName
attributes. However, if an entry does not include a SurName, SN, or S
attribute, you must provide last name information for the user before the
user is ready for registration.
Other name information in an entry (for example, CN) may be added to
the Person document as a secondary name in the User name field.
Processing attributes that have multiple values

The LDIF Domino Upgrade Services does not migrate multiple values for
the following attributes:
• First name
• Last name
• Middle initial
• Short name
15-4 Upgrade Guide
If an LDIF entry contains multiple values for any of these attributes, only
the first value is added to the Person document. In addition, the LDIF
Domino Upgrade Service places a message in the Notes log indicating
that the attribute already exists.
Adding common names as secondary user name values in the

Person document
The LDIF Domino Upgrade Service adds values from the common name
(CN) and UID attributes of an LDIF entry as secondary values in the
User name field of the Person document.
Importing Internet addresses from an LDIF entry

If a user’s entry in a migrated LDIF file includes the mail attribute, the
LDIF Domino Upgrade Service imports that address and copies it to the
InternetAddress field of the user’s Person document when the user is
registered. The domain name portion of the user’s mail remains intact,
that is, exactly as it was in the LDIF file. The administrator can change
the user’s Internet address by modifying the entry in the InternetAddress
field.
When registering users not migrated from an LDIF file, the Domino
Administrator changes the Internet address to reflect the default domain
name as displayed in the Internet Domain field on the Basics pane of the
User Registration dialog box.
Importing passwords from an LDIF entry

By default, if a record for a user has an associated password, that
password is imported as the user’s Notes password. The LDIF Domino
Upgrade Service provides two options for automatically generating
random passwords. By default, the LDIF Domino Upgrade Service
generates random passwords only for those entries that do not have
associated passwords. You can also choose to create new random
passwords that will replace the passwords specified in the imported
LDIF file.
Preparing to import an LDIF file

The tasks you perform to prepare an LDIF file for import into Notes
depend on how you plan on integrating the users listed in the file into
Notes. You can use an LDIF file to register users listed in the file as Notes
users.

Before importing people from an LDIF file to Notes, complete the follow-
ing tasks:
• Consider generating one or more LDIF files for these reasons:
• If you divide large files into multiple smaller files, you will have
greater control over the migration process.
• If you are registering users and plan to place them in multiple
Notes organizational units, create separate LDIF files for each
organizational unit.
• Obtain or generate the LDIF file containing the users to be imported.
For information about the ldapsearch utility, see the book
• Decide whether to use the imported entries to create registered Notes
users or directory entries only.
• If you are registering users, verify that you have access to the
certifier IDs and passwords for the Domino organizations and
organizational units where you are registering users.
• If you are creating mail files for users, log in to Notes with a Notes ID
Administrator client and select the LDIF Domino Upgrade Service.
You must perform a custom installation to install the migration tools
component.
• On the administrative workstation, close all applications, except for
• From the administrative workstation, map a drive to the location of
the LDIF file you are migrating users from.
15-6 Upgrade Guide

Preparing LDIF files for import into multiple Notes organizational
units
Notes security requires that you supply a certifier ID and password for
each organizational unit (OU) into which you register users.
Although the distinguished name for an entry in the LDIF file may
contain information about a user’s OU, this OU is not necessarily the
same as the Notes OU, and the LDIF Domino Upgrade Service cannot
import OU information in creating Notes hierarchical names. The OU
portion of a user’s Notes hierarchical name depends on the certifier ID
used to register the user. When you launch the LDIF Domino Upgrade
Service, you are prompted to supply a certifier ID. Users whom you
import during the session are queued for registration into the organiza-
tional unit for the specified certifier ID.
If you need to migrate users from an LDIF file into different OUs in the
Notes hierarchy, you must create a separate file for each OU where you
want to register users. If you exported all of the users from an LDAP
directory into a single file, you must extract the entries in the original file
into different files for each OU. Then, import each file independently,
using the certifier ID for the corresponding organizational unit.
For example, if the Notes hierarchy in the Acme company has a Sales
unit and a Finance unit, and the LDIF file you are importing contains
entries for users in each of these units, create separate LDIF files named
SALES and FINANCE and place the appropriate entries in each. Then
import the SALES file using the Sales/Acme certifier ID, and the
FINANCE file using the Finance/Acme certifier ID.
Specifying the LDIF file to migrate from

To migrate users from an LDIF file, you need to specify the location of
the file. Make sure that the format of the entries in the file follows
approved LDIF conventions.
Note It is recommended that the LDIF files you import be generated by
a standard LDAP export utility, such as the ldapsearch utility supplied
with the Domino 6 server.
For information about using the ldapsearch utility, see the book

users. Click OK.
6. From the People and Group Migration dialog box, select LDIF
Entries from the Foreign directory source list.
7. In the Select LDIF File dialog box, specify the LDIF file to import or
click Browse to open a dialog box that lets you search the file system
for an LDIF file, beginning in the Notes Data directory. Click OK.
8. Set migration options by selecting items in the Migration Options
box. The options you select apply to all users imported from the file
during this session.
For more information about migration options, see the topic “Setting
options for importing users from an LDIF file” later in this chapter.
Note If you are not registering the users migrated from the file (not
creating Notes IDs or mail files for them), the OU portion of the
users’ Notes hierarchical name created will depend on the certifier
ID used to register the users. If you select the option “Add full name
provided to the Notes person,” LDIF Domino Upgrade Services
includes the original LDAP distinguished names, as well as any
secondary CN values specified in the LDIF file, as secondary values
of the User Name field. By default, this option is selected.
9. Click Migrate and click OK to close the message that indicates the
number and status of the users queued for registration.
10. Click Done.
status box. You can now register the available users or add users to
Domino as directory entries only.
For more information about registering users or adding users to the
Domino Directory, see the topics “Registering users migrated from
an LDIF file” or “Adding imported users as directory entries only”
Setting options for importing users from an LDIF file

You can set options to determine what information the LDIF Domino
Upgrade Service imports from the LDIF file. The options you specify
apply to all users imported from the file during this session.
15-8 Upgrade Guide

1. In the People and Groups Migration dialog box, click Options.
2. After the message In the Migration Options box, select the options
you want. To clear a selection, click the selected option a second
time. The following table lists the options for importing users from
an LDIF file:
Generate random passwords for users with no passwords On
existing passwords)
Add full name provided to the Notes person document Off*
*If you are not registering the users migrated from the file (not creating
Notes IDs or mail files for them), the OU portion of the users’ Notes
hierarchical name created will depend on the certifier ID used to register the
users. If you select the option “Add full name provided to the Notes
person,” LDIF Domino Upgrade Services includes the original LDAP
distinguished names, as well as any secondary CN values specified in the
LDIF file, as secondary values of the User Name field. By default, this option
is selected.
For more information, see the topic “Adding the distinguished name to
the Person document” earlier in this chapter.
Registering users migrated from an LDIF file

user
In addition to the information imported from the attributes for each
entry, you can specify other Notes registration information for users,
including mail server name, group membership, and so forth.
For more information about the available registration settings, see the
If you want to add imported names to the Domino Directory, but not
register the imported people as Notes users, see the topic “Adding
imported users as directory entries only” later in this chapter.

Registration status box to ensure that it is correct. Modify
information as needed.
Note The Register Person dialog box displays a subset of the
attributes imported from the LDIF file. The LDIF Domino Upgrade
Service imports other attributes, such as phone number, manager,
and so forth, even though they do not appear here.
2. (Optional) Click the Options button and select the registration
Register.
The Domino Administrator attempts to register the selected users in
the order in which they were added to the queue. Users whom you
do not select remain in the queue for later registration.
depending on the size of the LDIF file being imported.
Adding imported users as directory entries only

You can use the entries in the imported LDIF file to create entries in the
Domino Directory only without creating new Notes users. The LDIF
Domino Upgrade Service then creates new Person documents for each
imported name, but does not generate Notes IDs or mail files. The people
represented by the resulting Person documents appear in the Domino
Directory, but cannot access Domino resources from a Notes client.
15-10 Upgrade Guide

Using entries imported from an LDIF file strictly as directory entries lets
you:
• Add user information from external directories to the Domino
Directory so it can serve as a master directory. Using Domino’s Web
server capabilities, you can then make the contents of this master
directory available to HTTP search engines.
• Create subscription accounts for a Web site.
Use the following procedure to import users as directory entries only:
Note After the import process has started, you cannot use the
you can stop the process by pressing CTRL-Break.
1. Import users from an LDIF file into the registration queue.
For more information about importing users from an LDIF file, see
the topic “Specifying the LDIF file to migrate from” earlier in this
chapter.
Registration status box, to ensure that it is correct. Modify
information as needed.
3. (Optional) Click the Options button, select registration options to
apply during this session, and click OK.
4. From the Registration status box, select all of the users to be added as
directory entries only.
5. Select the Advanced check box, and then select the Mail pane.
6. From the Mail pane, select None in the Mail system box, and click
Apply.
7. Select the ID Info pane, clear the check boxes in the Store user ID
section, and click Apply.
8. In the Registration status box, make sure the users you selected in
Step 4 are still selected, and click Register.
The Domino Administrator attempts to add the selected users to the
Domino Directory in the order in which they were added to the
queue. Users whom you do not select remain in the queue for later
processing.
The import process may require considerable time, depending on the
number of users being imported.
After the process completes, a message appears, informing you of the
registration status. Users who could not be imported continue to be
listed in the Registration status box with a status message indicating

the reason for the failure. Correct the information in the registration
profile and attempt to import the user again.
Using imported users in subscription accounts

You can use the entries from an imported LDIF file to create subscription
accounts that let you manage access to the resources Domino publishes
to a company Web site. Subscription accounts let you protect certain
information on the Web site, making it available only to specified users.
To gain access to protected information, users must provide a password
to authenticate themselves.
When creating subscription accounts, you can either import existing
passwords (from the userpassword attribute in the LDIF file) or instruct
the LDIF Domino Upgrade Service to generate passwords by selecting
the option provided in the LDIF migration dialog box.
15-12 Upgrade Guide

Chapter 16
Migrating Personal Mail Data
This chapter contains information about the user upgrade wizards for
migrating personal messaging data from cc:Mail, Microsoft Mail, Micro-
soft Outlook Express, and Microsoft Exchange clients to Lotus Notes 6.
Migrating personal mail data

During the first phase of a migration, you used Domino Upgrade
Services in the Domino Administrator to migrate the users listed in the
public directory of the old mail system and to move the contents of their
mail boxes from the old messaging server. Users can now complete the
migration by converting their personal mail data, such as private
addresses, mailing lists, and message archives, to Lotus Notes.
Users migrate personal mail data by running an upgrade wizard, which
guides them through the process of converting their personal mail data
to Notes data. Users launch the upgrade wizard from an upgrade
message in the Inbox of their Notes mail file. The administrator sends the
upgrade message from the Domino Administrator, which specifies the
location of the wizard program files. You can install the upgrade wizard
as part of each user’s Lotus Notes client or in a shared network directory.
Lotus Notes/Domino 6 provides user upgrade wizards for migrating
personal mail data from:
• Lotus cc:Mail
• Microsoft Mail
• Microsoft Outlook Express
• Microsoft Exchange
This section includes the following topics:
• Data migrated by the user upgrade wizards
• Before running the upgrade wizard
• Platform requirements for running the user upgrade wizards
• Installing the upgrade wizard
• Sending users an upgrade notification message
Migrating Personal Mail Data 16-1

• Running the upgrade wizard
• Converting message archives
• Migrating mail messages from Microsoft Outlook Express
• Migrating personal address book information
• After the upgrade wizard finishes processing
Messaging data migrated by the user upgrade wizards

The upgrade wizards let users migrate their personal mail data from any
local or mapped drive location. The upgrade wizards convert archived
messages from the old mail system into messages in a Notes mail file
archive. Private addresses and private mailing lists are migrated into a
Notes Personal Address Book (NAMES.NSF) on the user’s workstation.
The following table shows how information in each mail system is
converted to Notes information.
Mail data from Mail data from Mail data from Mail data from Converts to
cc:Mail Microsoft Mail Microsoft Microsoft these Lotus
Outlook Express Exchange/Outlook Notes
equivalents
Archives Archives/ — Personal Folders Folder in
(CCA files) backups (PST files) mail file
(MMF files) archive
database
Attachments Attachments Attachments Attachments Attachments
Message — Message Message Message
priorities priorities priorities priorities
Messages Messages Messages Messages Messages*
— Folder Folder Folder hierarchy Hierarchical
hierarchy hierarchy folder views
Mobile post Mobile post — Mobile post Not migrated
offices** offices offices
Private Personal Groups Personal Group
mailing lists groups distribution document in
lists*** PAB
Private Personal Contacts Contacts Contact in
addresses Address Book (Outlook PAB
entry only)/Personal
Address Books
(PAB file)
continued
16-2 Upgrade Guide

Mail data from Mail data from Mail data from Mail data from Converts to
cc:Mail Microsoft Mail Microsoft Microsoft these Lotus
Outlook Express Exchange/Outlook Notes
equivalents
Read/unread Read/unread Read/unread Read/unread Read/unread
marks**** marks marks marks status
Return Return — Return receipts Return
receipts receipts receipts
Trash folder Wastebasket Delete Items Wastebasket Not migrated
folder Folder folder
— Custom mail — — Not migrated
messages
— Delivery — — Not migrated
failure reports
— Interpersonal — — Not migrated
mail (IPM)
messages
— — — Sensitivity levels Mood stamps
— — — Calendar entries Calendar
entries
— — — Tasks To Do tasks
*Rich text formatting is not preserved in messages migrated from cc:Mail. Inter-
national characters in the message body are converted during migration.
**The upgrade wizard can only migrate the archived messages of a cc:Mail
Mobile user. Users cannot migrate the contents of an entire mailbox from a
mobile post office on their workstation. Mobile users who want to migrate
messages must archive the messages in the old mail program before running the
upgrade wizard.
***The upgrade wizard migrates Exchange personal distribution lists maintained
in the PAB file on the client.
****Because the cc:Mail archives can contain only messages that have been read,
the upgrade wizard assigns the status read to all migrated archived messages.
The upgrade wizard for Microsoft Exchange assigns all messages migrated from
Exchange the status unread.

Before running the upgrade wizard
Before a user runs the upgrade wizard, the system administrator must:
• Migrate users and their mail boxes to Lotus Notes, using Domino
Upgrade Services in the Domino Administrator
Note For Microsoft Outlook Express users, make sure to select the
“Internet authentication: More name variations with lower security”
option in the Internet Access field on the Security tab of the Server
document. This option lets users connect to the Domino server using
short names.
• Decide whether users will run the upgrade wizard locally or over the
network
For more information about running the upgrade wizards locally or
over a network, see the topic “Installing the upgrade wizard” later in
this chapter.
• Install the Lotus Notes 6 client on users’ workstations
• Send an upgrade notification message to users
For more information about sending the upgrade notification, see the
topic “Sending users an upgrade notification message” later in this
chapter.
Platform requirements for running the user upgrade wizards

The following table shows the software required to run each version of
the upgrade wizard:
Requirements Client migrated Client migrated Client migrated Client migrated

from cc:Mail from Microsoft from Microsoft from Microsoft
Mail Outlook Express Exchange/Micros
oft Outlook
Supported Release 6.x, 3.2, 3.5, 3.6 5.0 and 5.5 All
versions Release 8.x*
Lotus Notes Release 5.x, Release 5.x, Release 5.x, Release 5.x,
client** Release 6 Release 6 Release 6 Release 6
Workstation Windows 95, Windows NT Windows 95, Windows 95,
operating Windows NT 4.0 Windows NT Windows NT
system 4.0 4.0, 4.0
Windows 98
*Private addresses for cc:Mail 8.x clients cannot be migrated.
**The upgrade wizard may fail to work properly on computers where the Lotus
Notes 6 client is installed along with an earlier version of Lotus Notes. To
prevent errors when running the upgrade wizard on computers with multiple
releases of Lotus Notes installed, edit the user’s path statement to include the
16-4 Upgrade Guide

Lotus Notes 6 Program and Data directories and exclude the Program and Data
directories for other Lotus Notes releases. Even after you change the path state-
ment, the Lotus Notes 6 client still attempts to locate and use earlier versions of
the NOTES.INI file (in the Windows directory, for example). To prevent errors
when running the upgrade wizard, rename earlier versions of the NOTES.INI
file on the user’s workstation.
Installing the upgrade wizard

Users run the upgrade wizard by clicking a button in the body of the
upgrade message you send from the Domino Administrator. When you
complete the upgrade message form, you specify the location of the
upgrade wizard. Users must run the upgrade wizard from a Lotus Notes
client that is either installed on the same computer as the mail data they
want to migrate, or at least has access to this data.
You can install the wizard program files in either of the following
locations:
• In a shared network location
• Locally, as part of the Lotus Notes client
Installing the upgrade wizard with a user’s Lotus Notes client

When you install the Lotus Notes client software, the files required to run
the upgrade wizard locally are not installed by default. If users will run
the upgrade wizard locally, customize the Lotus Notes client installation
to load the appropriate program files on the workstation. Follow this
procedure to perform a custom Lotus Notes client installation and to
install the upgrade wizard locally.
1. Run the Lotus Notes installation program.
2. When prompted to select the type of client to install, click the
appropriate client type and then click Customize.
3. From the Components list, select Migration tools and then click
Change.
4. From the Select Sub-components dialog box, select the check box for
the client migration tools you want to install and clear all other check
boxes. For example, to install the cc:Mail to Lotus Notes upgrade
wizard, select the cc:Mail Client Migration Tools check box and clear
the other check boxes.

5. Click Continue.
6. Click Next, and then proceed with the rest of the installation as
directed.
Installing the upgrade wizard on a network drive

If users will run the upgrade wizard from a network drive, perform the
following tasks:
Perform a custom installation of the Lotus Notes client to install the
upgrade wizard on a network drive to which all users have access
• Map drives on users’ workstations to the directory containing the
upgrade wizard program files. Use a login script to automatically
map workstation drives to the directory.
• Send users an upgrade notification message that specifies the path to
the directory where the upgrade wizard resides.
For more information about sending the upgrade notification, see the
topic “Sending users an upgrade notification message” later in this
chapter.
If you decide to have users run the upgrade wizard from a network
location, rather than locally, load the necessary software in a directory
that is accessible to all migrated users. To ensure that all of the required
files are placed in the directory, perform a custom installation of the
Lotus Notes client, as shown in the following procedure. Do not attempt
to manually copy the wizard’s program files from one location to
another.
1. Run the Lotus Notes installation program.
2. When prompted to select the type of client to install, click any of the
available selections and then click Customize.
3. From the Components list, select Migration tools and then click
Change.
4. From the Select Sub-components dialog box, select the check box for
the client migration tools you want to install and clear all other check
boxes. For example, to install the cc:Mail to Lotus Notes upgrade
wizard, select the cc:Mail Client Migration Tools check box and clear
the other check boxes.
5. Click Continue.
6. From the Components list, clear the check boxes for the other
installation components.
7. Click Next, and then proceed with the rest of the installation as
directed.
16-6 Upgrade Guide

8. After the installation completes, provide all migrated users with
access to this directory, and send an upgrade notification message
that specifies the path to the directory. Configure users’ workstations
to run a client login script that automatically connects a workstation
drive to the directory.
Sending users an upgrade notification message

Migrated users run an upgrade wizard at the Lotus Notes client to
migrate personal mail information to Notes mail archives and Personal
Address Books. Users run the wizard by clicking a button in the body of
a Notes mail message you send from the Domino Administrator. The
upgrade notification message contains information about:
• The type of mail system users are migrating from
• The location of the wizard program files
• Other information needed to migrate personal mail data
Before sending the upgrade notification, install the upgrade wizard
either locally on each migrated user’s workstation as part of the Lotus
Notes client or on a network directory that all the users have access to.
Then follow this procedure to send the upgrade notification message.
1. From the Server pane of the Domino Administrator, select the server
where you registered the migrated users.
2. In the Task pane, click the People and Groups tab, right-click the
name of the server’s Domino Directory, and select Open Directory.
3. From the Lotus Notes menu, select File - Database - Access Control.
4. From the Basics pane of the Access Control List dialog box, select the
Administrator ID you are using, and from the Roles box, select
UserModifier or NetModifier.
If you are using a local copy of the Domino Directory, also select the
Advanced pane and click the following check box: “Enforce a
consistent Access Control List across all replicas of this database.”
5. Click OK.
6. From the Messaging tab, click the Mail subtab, and then click Mail
Users.
7. From the Action bar, click Send Upgrade Notifications.
8. Click Address on the action bar, and specify the users to send the
upgrade notification message to.
If you added users to a ‘Migration’ group when you registered them,
address the message to the group name.

9. In the Administrator Setup section, select “Send out cc:Mail/MS
Mail/MS Exchange/MS Outlook Express convert local information
notices.”
10. If users will run a network copy of the upgrade wizard, in the Mail
Conversion Utility Path section, enter a DOS path to the network
directory where you installed the appropriate upgrade wizard. End
the path with a backslash (‘ \ ‘) character.
The path you specify must be identical to the path users have
mapped to this directory from their workstations. For example, if
users map drive J to the directory that contains the upgrade wizard,
you would enter the following in this field: J:\
If you installed the upgrade wizard locally on each user’s
workstation, leave this field blank.
11. In the Mail Conversion Options section, select the mail system users
are migrating from.
12. (Optional) For a cc:Mail migration, complete gateway mapping
information as follows:
• Enter the names of cc:Mail gateway post offices in the field
“Convert the following cc:Mail POs.”
• Enter the names of the equivalent Notes domains in the field “To
the following Notes Domains.”
The upgrade wizard replaces occurrences of cc:Mail gateway names
in the addresses of migrated messages and in migrated personal
addresses with the specified Notes domain names.
13. The Additional Information section displays the text included in the
upgrade notification message that users receive. Edit this text as
necessary to provide users with additional information about the
migration.
14. When you have completed the form, click Send on the action bar to
deliver the upgrade notification message to each user you specified.
Running the upgrade wizard

Users start the upgrade wizard by opening the upgrade notification
message received after migration and clicking a button in the message
body or by using desktop shortcut. You must have previously installed
the upgrade wizard either locally, as part of the user’s Lotus Notes client,
or on a shared network directory. You send upgrade notification
messages to users’ Notes mail files after migrating their mail boxes with
the upgrade tools in the Domino Administrator.
16-8 Upgrade Guide

After a user launches the upgrade wizard, it automatically checks for a
Lotus Notes installation on the user’s workstation. If a Notes program
directory is not found, the wizard fails to load.
The upgrade wizard obtains information about the Notes environment
from the active NOTES.INI file in the Notes Data directory and from the
upgrade notification message. For users migrating from cc:Mail 2.x and
cc:Mail 6.x, the upgrade wizard also obtains information from
PRIVDIR.INI on the user’s workstation.
Users must run the upgrade wizard from a Lotus Notes client that is
either installed on the same computer as the mail data they want to
migrate, or at least has access to this data.
Running the upgrade wizard from a desktop shortcut

Alternately, you can create a desktop shortcut from which users can run
the upgrade wizard. The shortcut must point to the location where you
installed the upgrade wizard and must specify a target application as
follows:
• cc:Mail — NUPGRADE.EXE 1
• Microsoft Mail — NUPGRADE.EXE 2
• Microsoft Exchange — NUPGRADE.EXE 3
• Microsoft Outlook Express — NUPGRADE.EXE 4
By default, the “Start in” field on the Shortcut property page specifies the
directory where the upgrade application resides as the starting point for
selecting archive files to migrate.
Information the upgrade wizard obtains from the upgrade

notification message
The Upgrade Notification message provides information that the
upgrade wizard uses to migrate personal mail data. The wizard obtains
the following information from the upgrade message:
• The type of mail system being migrated (cc:Mail, Microsoft Mail,
Microsoft Outlook Express, or Microsoft Exchange)
• The name of the user’s Notes mail server
• Mapping between cc:Mail post office gateways and Domino domains
(cc:Mail users only)
• A message ID (for cc:Mail users only)
The cc:Mail to Lotus Notes upgrade wizard uses the message ID to find
the message in the user’s mail file, so that it can read gateway mapping
information for processing archives and private addresses.

Information the upgrade wizard obtains from the NOTES.INI file
The upgrade wizard obtains additional information from the active
NOTES.INI file in the Notes Data directory on the user’s workstation. If a
NOTES.INI file is not found in the Notes Data directory, the wizard
searches for it in the Program directory, and then along the system path.
The upgrade wizard obtains information from the following values in the
NOTES.INI file:
Information NOTES.INI setting

Personal Address Book (PAB) First entry in “NAMES=”
Location of the Notes Data directory Value of “Directory=”
Notes mail file name Value of “MailFile=”
User credentials (password, etc.) Value of “KeyFileName=”
The default file name for the Personal Address Book file is NAMES.NSF,
which is stored in the local Notes Data directory. The value of the
“MailFile” field indicates the name of the active mail as specified in a
user’s current Location document.
Selecting an upgrade method

Each type of upgrade wizards migrates two or three types of personal
data, as shown in the following table:
Upgrade wizard Mail data migrated

cc:Mail Private mailing lists, private addresses, archives
Microsoft Mail Personal address books, archives
Microsoft Outlook Personal address books, local folders, messages in
Express* local folders
Microsoft Personal address books/contacts, personal folders,
Exchange/Outlook calendar entries and messages in local PST file
*The Microsoft Outlook Express upgrade wizard does not offer Express or
Custom upgrade options. This wizard creates a Notes mail account in Outlook
Express to which users manually copy messages to their Notes mail folders and
export their contacts to the Notes Personal Address Book in Outlook Express.
The Microsoft Outlook Express upgrade wizard does not migrate mail messages
and contact information automatically.
Users can choose between an Express or Custom upgrade method. The
default Express method processes all the available messaging data using
the default settings. When users select Custom upgrade, they can selec-
tively migrate each of the available data types. For example, during a
16-10 Upgrade Guide

Custom upgrade, a user migrating from cc:Mail can select private
addresses, private mailing lists, and archives. The upgrade wizards
report an error if they cannot locate or convert any of the data types.
Converting message archives

Users may have considerable amounts of data stored in message
archives. The upgrade wizard can convert users’ archived messages into
a Notes archive database. For each user, the selected message archives
are consolidated into a single Notes database. Within this database, the
name of the original archive files appear as folder names. By default, the
Notes archive database is created in the Mail subdirectory of the Notes
Data directory.
Note If users create the archive database on a network drive, they need
read/write access to that drive.
The upgrade wizard can be run more than once to migrate additional
sets of message archives. The additional archives can be added to the
Notes archive database already created or become part of a new
database.
Microsoft Mail and Microsoft Exchange do not specifically allow users to
archive mail. Instead, users can back up their mailboxes, creating off-line
copies of their mailboxes, which are stored in the same file format (MMF
and PST, respectively) as their active mailboxes. The upgrade wizard for
these mail systems can migrate data from any MMF or PST file.
Although Microsoft Outlook Express users can create backup folders
locally or on network drives with a DBX file extension, the Microsoft
Outlook Express upgrade wizard does not migrate DBX files.
The cc:Mail to Lotus Notes upgrade wizard cannot migrate messages
from a cc:Mail Mobile post office. Users who want to migrate messages
from a Mobile post office must first archive the messages. Afterward,
they can run the upgrade wizard to migrate the archived messages.
Migrating archives during an Express upgrade

When running the upgrade wizard, users are prompted to select either
an Express or a Custom upgrade. For most users, an Express upgrade is
recommended. Note that the Microsoft Outlook Express upgrade wizard
does not provide these upgrade options.
During an Express upgrade, each upgrade wizard uses a different
method to determine which archive files to migrate, as shown in the
following table:

Mail system How upgrade wizard selects archives to migrate
cc:Mail* Migrates all CCA files in location specified in
[cc:Archives] section of WMAIL.INI
Microsoft Mail Users specifies files to migrate
Exchange/Outlook Migrates all PST files in location specified in
MAPI profile
*The cc:Mail 8.x client does not store information in the WMAIL.INI file. As a
result, when users of the cc:Mail 8.x client perform an Express upgrade, the
upgrade wizard does not migrate any archive files. To migrate archives,
cc:Mail 8.x clients must use the Custom migration option and specify the
location of archive files to migrate.
Migrating archives during a Custom upgrade

After selecting a Custom migration, users migrating from cc:Mail or
Microsoft Mail can specify the following options for migrating archives:
• The archive files to migrate
For more information about migrating archive files, see the topic
“Selecting archive files to migrate” later in this chapter.
• The Notes mail file template to use in creating the Notes archive
database
For more information about using the Notes mail file template for the
archive database, see the topic “Specifying the template for migrated
archives” later in this chapter.
• The directory in which to create the resulting Notes mail archive
For more information about selecting the directory for Notes mail
archives, see the topic “Specifying where to migrate archives” later in
this chapter.
For users migrating from Microsoft Exchange, the upgrade wizard
migrates the personal folders specified in the user’s MAPI profile.
Selecting archive files to migrate

The upgrade wizards for cc:Mail and Microsoft Mail let users specify the
archive files to migrate. When specifying files to migrate, users can
browse the file system and select archive files from any available
network or local drive.
16-12 Upgrade Guide

Users migrating from cc:Mail can specify archive files only if they run the
wizard using the Custom upgrade method. The upgrade wizard for
Microsoft Mail requires users to select archive files regardless of the
upgrade method selected.
By default, when you specify archive files to migrate, the upgrade
wizards look for the files in the current working directory. If users run
the upgrade wizard from a Windows desktop shortcut, you can set the
current working directory by editing the ‘Start in’ field in the shortcut
properties for the application. If users run the upgrade wizard from the
upgrade notification message, or if you do not edit the “Start in” location,
the current working directory is set to the directory from which the
application was started. To specify a different archive source, users can
browse the file system to locate the archives to migrate.
Users must have read/write access to the directory containing the
archive files to migrate, as well as to the directory that stores temporary
files used during the migration process. The upgrade wizard places
temporary files in the directory specified by the Windows environment
variable “TEMP=”. Typically, the TEMP variable specifies a local direc-
tory, such as C:\WINDOWS\TEMP.
When migrating Microsoft Mail or Microsoft Exchange archives that are
protected with a password, a user must supply the appropriate user
name and password. cc:Mail archives are not password-protected, and
can be opened and migrated by any user who has the appropriate file
access.
Specifying the template for migrated archives

The upgrade wizard uses the specified mail template to convert the
archives into a Notes archive database. By default, the upgrade wizard
uses the template defined by the DefaultMailTemplate setting in the
user’s NOTES.INI file, or, if this setting is undefined, the template
MAIL6.NTF. In most instances, users should not change the default
setting.
To modify the template setting, users migrating from cc:Mail must select
Custom upgrade and edit the Template name field on the Archive
Conversion Options dialog box. Users migrating from Microsoft Mail or
Microsoft Exchange can specify a mail template regardless of whether
they perform an Express or Custom upgrade.

Specifying where to migrate archives
When migrating archives, users can specify where the upgrade wizard
will store the resulting Notes archive database. By default, the upgrade
wizard migrates all archives into a single Notes mail file database. That
is, if a user migrates cc:Mail archives and Microsoft Mail archives, all of
the archives are placed in a single Notes archive database. Unless other-
wise specified, the database is created in the MAIL subdirectory of the
user’s Notes Data directory, as specified in the NOTES.INI file. Users are
prompted to provide a Notes password when they create the archive
database.
The resulting Notes archive automatically derives an eight-character
name from the Notes name of the migrated user, to which it adds the
prefix A_ . For example, if the Notes name of the user migrating an
archive is Robin Rutherford, the resulting Notes archive database would
have the name A_RRUTHE.NSF.
For Microsoft Mail and Microsoft Exchange, if an archive file contains
multiple files, these files become folder views in the resulting Notes
archive database. To distinguish among duplicate archive filenames
(from multiple source directories) the wizard appends a numeral to the
archive name. For example, if the upgrade wizard moves the two files
archive\1996\meetings and archive\1997\meetings they appear as
folders with the names meetings1 and meetings2 within a single Notes
database.
The default settings are maintained when users select Express as the
upgrade method. To specify a different destination, cc:Mail users must
select the Custom upgrade method and edit the Folder field on the
Archive Conversion Options dialog box. Users converting from Microsoft
Mail or Microsoft Exchange can change the destination regardless of the
upgrade method selected.
Running the wizard again to migrate additional archives

Users can run the upgrade wizard more than once to migrate archives.
By default, archives migrated after the initial session are added to the
existing Notes archive database. User can place archives that they
migrate later in a different archive database as follows:
• Before migrating additional archives, rename the original database.
Then, run the upgrade wizard and migrate the archives to the
default location.
16-14 Upgrade Guide

• Run the upgrade wizard and select Custom upgrade. Then, on the
Folder field of the Archive Conversion Options dialog box, specify a
directory location for the Notes archive database that is different
from the location of the original database.
Space requirements for migrating archives

The Notes mail file template is approximately 2MB in size. The size of
each migrated archive is approximately equal to the sum of the template
size and 130% of the original archive size.
For example, if the original archive is 3MB, the migrated archive will be
approximately equal to (1.3 * 3MB) + 2MB, or 5.9MB. Instruct users to
estimate the amount of disk space required before migrating their
archives.
Translating cc:Mail gateway names in archived messages

For cc:Mail, gateway names in the sender’s address of archived messages
are translated according to the gateway mapping specified in the
upgrade message sent by the upgrade tool in the Domino Administrator.
Gateway mapping is not supported for migrated Microsoft Mail or
Microsoft Exchange message archives. Messages migrated from Micro-
soft Mail or Microsoft Exchange are not automatically updated with the
names of Notes gateways. Users might need to edit addresses to make
sure they refer to the correct Notes gateway.
Migrating a mailbox folder hierarchy

Microsoft Mail and Microsoft Exchange users can create backup copies of
their mailboxes. These off-line replicas are stored in the same file format
as active mailboxes (MMF and PST files, respectively) and can contain
multiple folders and subfolders. When migrating these files to a Notes
archive mail file, the upgrade wizard maintains the existing folder
hierarchy.
For example, a Microsoft Mail user might have a backup of a mailbox
folder called Projects in which there are four subfolders named Q1, Q2,
Q3, and Q4. When the user migrates this file, Projects.MMF, the upgrade
wizard creates a folder called Projects within the Notes archive, and then
replicates the existing folder hierarchy within this folder, creating
subfolders called Q1, Q2, Q3, and Q4.
When migrating cc:Mail archives, the upgrade wizard also converts each
archive into a folder within the Notes archive database, migrating the
messages within each cc:Mail archive into the appropriate folder. How-
ever, because cc:Mail archives contain individual messages only, and not
subfolders, migrated cc:Mail archives contain top-level folders only.

Migrating mail messages from Microsoft Outlook Express
After users run the Microsoft Outlook Express upgrade wizard to create
Notes mail accounts in Outlook Express, they can migrate mail messages
to their Notes mail account. To migrate messages, users open any folder
in the Local Folders mail account in Outlook Express, then do any of the
following:
• Drag and drop messages into Notes mail account folders
• Copy messages to the Notes mail account folders
• Move messages to the Notes mail account folders
The Notes mail account contains the same folders found in the Local
Folders mail account in Outlook Express. If users want to create
additional folders for their Notes mail accounts, they can do so in
Outlook Express.
After migrating messages to their Notes mail account, users can access
those messages through their Notes mail database in the Lotus Notes 6
client.
Tip If users cannot connect with the Domino server, check the Security
tab of the Server document. Select the “Internet authentication: More
name variations with lower security” option in the Internet Access field.
This allows Outlook Express users to connect with the server using their
short names.
Overview of migrating personal address book information

Users who have migrated to Lotus Notes may retain personal address
book information from their old mail system by migrating the informa-
tion to a Notes Personal Address Book (PAB).
There are two types of personal address book entries users can migrate:
• Personal addresses for users not listed in the public address book; for
example, Internet e-mail addresses
• Personal mailing lists for distributing e-mail to multiple addresses at
one time
When migrating personal address book information, the upgrade
wizards convert private addresses to Contact entries in the PAB. Users
migrating from the cc:Mail 8.x client cannot migrate private addresses.
Personal mailing lists are converted to Multi-purpose groups in the PAB.
Multi-purpose groups can be used as access control lists and deny access
lists in a Server document, as well as for mailing lists.
16-16 Upgrade Guide

How the upgrade wizards obtain personal address book information
The user upgrade wizards read migrated address book information from
either or both of two sources, depending on the mail system the user is
migrating from:
• Attachments to messages sent by Domino Upgrade Services
• Personal address book files located on a workstation local or mapped
drive
The upgrade wizard copies information from message attachments and
data files to the PAB on the user’s Lotus Notes client.
Migrating cc:Mail personal address book information

For users migrating from cc:Mail, the upgrade wizard extracts some
personal address book information from a message attachment and some
from a data file on the user’s workstation. The upgrade wizard obtains a
user’s private mailing lists, which are stored with the user’s cc:Mail mail
box, from a PAB attachment in the user’s Notes mail file. Migrated users
automatically receive this message if you select the option to “Mail
private mailing lists as attachments” from the Conversion Settings pane
of the “cc:Mail Upgrade Advanced Settings” dialog box of the cc:Mail
Domino Upgrade Service.
For cc:Mail 6.x clients, the upgrade wizard obtains private addresses,
directly from the file PRIVDIR.INI on the user’s workstation. The cc:Mail
to Lotus Notes upgrade wizard does not support migrating private
addresses for cc:Mail 8.x users.
Migrating Microsoft Mail personal address book information

For users migrating from Microsoft Mail, the upgrade wizard extracts
information from a temporary Notes PAB attached to a Notes mail
message. This temporary PAB contains personal addresses and personal
mailing lists migrated from their mailbox (MMF) file. Migrated users
automatically receive a message with the attached PAB if you select the
option to “Convert Personal Address Books” from the “MS Mail
Advanced Options” dialog box of the Microsoft Mail Domino Upgrade
Service.

Migrating Microsoft Exchange personal address book information
For users migrating from Microsoft Exchange, the upgrade wizard
extracts personal address book information from two possible sources,
depending on the client mail application used. The Outlook mail client
can store address book information in a Contacts list on the Exchange
server, and in a Personal Address Book (PAB) file on the user’s worksta-
tion. The Exchange mail client stores all personal address book informa-
tion in a PAB file on the user’s workstation. The upgrade wizard obtains
the Outlook Contacts list from a temporary PAB attached to a Notes mail
message. Migrated users automatically receive this message if they had
Contacts information defined.
Migrating Microsoft Outlook Express personal address book

information
For users migrating from Microsoft Outlook Express, the upgrade wizard
provides a menu option for exporting contact and group information to a
local PAB. Users can export personal address book information at any
time. When users export personal address book information, the Micro-
soft Outlook Express upgrade wizard copies contacts and groups from
the Outlook Express personal address book to the Notes PAB.
Migrating personal address book information from the old mail

server
The Notes mail client stores personal address book information locally,
on the client workstation. However, the cc:Mail, Microsoft Mail, Micro-
soft Outlook, and Outlook Express clients each store some portion of a
user’s personal address book information on the mail server. Migrating
personal address book information from the old mail server requires
coordination between the administrative migration tools and the user
upgrade wizards that make up Domino Upgrade Services.
Domino Upgrade Services for cc:Mail and Microsoft Mail each include
options for migrating users’ personal address book information (the
Microsoft Exchange Domino Upgrade Service automatically migrates
such information when it is present). When you migrate users’ personal
address book information from the server, the Domino Administrator
automatically places an upgrade message in their Notes Inboxes.
Attached to each upgrade message is a temporary Notes Personal
Address Book (PAB), which contains the information migrated from the
old mail system.
Users who do not have personal information to migrate from the server
do not receive an upgrade message.
16-18 Upgrade Guide

Personal address book information sent in the upgrade message
The following table shows the personal address book information that
Domino Upgrade Services copy from the server into the temporary PAB
attached to the upgrade message:
Mail system Personal address book information attached to upgrade message

cc:Mail Private mailing lists
Microsoft Mail Personal Address Book
Microsoft Outlook Contacts
For information about how to migrate private mailing lists for cc:Mail
users, see the chapter “Migrating Users from cc:Mail.”
For information about how to migrate Personal Address Books for
Microsoft Mail users, see the chapter “Migrating Users from Microsoft
Mail.”
Copying personal address book information to the Notes Personal

Address Book
To update a user’s Notes Personal Address Book with information
migrated from the old mail system, the upgrade wizards copy personal
address book information stored on the old mail client or in temporary
Public Address Books sent to users in an upgrade message. The follow-
ing table shows the sources the upgrade wizards use to obtain address
book information:
Source of migrated cc:Mail Microsoft Microsoft Microsoft

information Mail Exchange Exchange
Outlook client client
Server (temporary Private Personal Contacts —
PAB sent in upgrade mailing lists Address
message) Book
Client workstation Private — Personal Personal
addresses Address Book Address
(PRIVDIR.INI) Book
Migrating personal address books during Express or Custom

upgrades
During an Express upgrade, the upgrade wizards migrate all the
personal address book information that is available for a user (that is,
information from both the Server and Client rows of the preceding table).

During a Custom upgrade, users can choose whether they want to
migrate personal address book information. Users of cc:Mail 2.x or
cc:Mail 6.x can independently migrate their private addresses and
private mailing lists. cc:Mail 8.x users can only migrate private mailing
lists.
The upgrade wizard for Microsoft Mail provides the option to migrate
Personal Address Books.
The upgrade wizard for Microsoft Exchange provides a single option for
migrating Contacts and Personal Address Books together. Although
Outlook client users may maintain separate Contacts and Personal
Address Books files, users cannot migrate these items separately.
Migrating information obtained from the mail server

When migrating information from the old mail server (refer to the
preceding table) the upgrade wizards search the user’s Notes Inbox for
an upgrade message. After locating a message, the wizards detach the
temporary PAB from it, and copy the information in the temporary PAB
to the PAB on the user’s workstation (NAMES.NSF). The original
upgrade message remains in the Inbox, and may be deleted after the user
verifies that the information has been migrated successfully.
Migrating information directly from the workstation

To migrate information from a cc:Mail client workstation, the upgrade
wizard searches the cc:Mail user directory on the workstation to locate
the PRIVDIR.INI file. Similarly, the upgrade wizard for Microsoft
Exchange searches the workstation for the Exchange Personal Address
Book (PAB file) specified in the user’s MAPI profile. After locating the
files, the wizards copy the address book information in them to the Notes
PAB.
The e-mail addresses listed in Contact documents in the Notes PAB may
conform to any of several mail system types. Lotus Notes assigns the
mail system type “Internet Mail” to the addresses that the upgrade
wizard migrates from other mail systems. In converting e-mail addresses
migrated from cc:Mail, the migration tool applies the gateway mapping
information contained in the upgrade notification message.
Translating gateway names in cc:Mail private addresses

Messages sent to addresses outside your company’s cc:Mail system pass
through a gateway post office, which directs the messages to their desti-
nations. When users create a private address entry for a user on an exter-
nal mail system, the gateway that routes the message becomes part of the
address. For example, the following cc:Mail address includes the name of
a gateway post office called INTERNET, which is used to route messages
to their destination: name@company.domain AT INTERNET.
16-20 Upgrade Guide

After you move users to Lotus Notes, cc:Mail gateways referred to in
address book entries are no longer available for routing messages. The
cc:Mail to Lotus Notes upgrade wizard automatically updates the
gateway name in each address according to the gateway mapping speci-
fied in the upgrade message sent by the upgrade tool in the Domino
Administrator.
Personal Address Books migrated from Microsoft Mail or Microsoft
Exchange are not automatically updated with the names of Notes
gateways. Users might need to edit addresses to make sure they refer to
the correct Notes gateway.
Migrating personal address book information in Microsoft Outlook

Express
The Microsoft Outlook Express upgrade wizard adds a Lotus Notes
Personal Address Book option to the Address Book Export Tool dialog
box. To access the dialog box, users choose File - Export - Other Address
Book. The Microsoft Outlook Express upgrade wizard exports all
contacts and groups from the Outlook Express personal address book to
the Notes PAB. After exporting personal address book information, users
should check their PABs to ensure that information was exported
correctly.
After the upgrade wizard finishes processing

If the upgrade wizard encounters errors as it processes archive files or
directory information, it skips to the next record and continues. Failures
are logged, and after the wizard finishes processing all of the
information, it displays a status message reporting the number of
messages processed.
Users may find that the message count of the migrated archive is lower
than the message count in the original archive. If there were multiple
copies of one message in the original archive, or in different archives,
only one copy of the message is migrated.
After the upgrade wizard finishes converting data from the old system
into Notes data, users should complete the following tasks:
• Check the Miscellaneous Events in the Notes Log (LOG.NSF) to see if
there are any problems that require further attention.
• Verify that all messages in the source archives migrated successfully
to the Notes mail archive.

• Remove the obsolete cc:Mail, Microsoft Mail, or Microsoft Exchange
files from their workstations. Refer to the appropriate documentation
for the old mail system for more information. Before users delete any
data, it is recommended that they back up their old mail files.
(Microsoft Mail or Microsoft Exchange users) Edit gateway information if
necessary, before using migrated addresses to send mail. External
addresses in PABs and archives migrated from Microsoft Mail or Micro-
soft Exchange are not automatically updated with the names of Notes
gateways.
16-22 Upgrade Guide

Chapter 17
Migrating Users from Microsoft Active Directory
This chapter describes how to migrate users from a Microsoft Active

Directory to a Domino Directory using the Active Directory Domino
Upgrade Service.
Migrating Microsoft Active Directory users and groups

Using the Active Directory Domino Upgrade Service, you can migrate
people and groups from a specified Microsoft Active Directory domain
into a Domino Directory and register those people as Notes users. The
migration process:
•
Imports people and groups from an Active Directory and creates
Person documents for each user in the Domino Directory
• Creates Notes IDs and mail files for registered users
Optionally, you can choose to create unregistered users (that is, users
without Notes IDs and Notes mail files). However, if you do, those users
will have limited access to Domino resources.
The Active Directory Domino Upgrade Service supports migration of
people and groups from an Active Directory domain or from a specified
container.
The Active Directory Domino Upgrade Service also supports LDAP
searches, so you can determine which users and groups to migrate using
a search base, field mapping options to define an LDAP search, and any
custom LDAP filter (using a standard LDAP filter syntax).
To migrate users from an Active Directory, follow this procedure:
• Specify the Active Directory domain to migrate from
• Set the migration options for Active Directory users
• Optionally specify advanced options for importing Active Directory
users
• Import Active Directory users into the Notes registration queue and
register them
17-1
Importing Active Directory names and passwords into the Domino
Directory
Before you migrate Active Directory entries into the Domino Directory,
note the following:
• When you migrate people from an Active Directory, the Active
Directory Domino Upgrade Service parses the Active Directory name
components — First name, Last name, and so on - into Notes name
components.
• The Active Directory Domino Upgrade Service does not import
passwords from an Active Directory into a Notes Person document.
By default, the “Generate random passwords for users with no
passwords” migration option is selected to create passwords for
Active Directory person entries. If you deselect this option, you must
supply each user with a password.
Search base, LDAP filters, and containers

The Active Directory Domino Upgrade Service uses one of these three
methods for migrating users from an Active Directory to a Domino
Directory. The following table described these options.
Option Description
Containers Containers for the Active Directory domain are listed in a
filter. When you use a container filter, all users and
groups in the container are retrieved, but users and
groups from subcontainers are not retrieved.
Search base alone By default, the search base is the entire Active Directory
domain. The Search base is used with the All users, All
groups, and All users and groups filters. It retrieves all
users and groups, including those in subcontainers.
Search base with LDAP filter syntax is Internet RFC. You can find
LDAP custom filter examples of LDAP filters in the Microsoft Active
Directory documentation. The following example
retrieves all users and groups whose names start with
“a” and who belong to the Sales department:
"&(cn=a*)(department=sales)"
17-2 Upgrade Guide

Preparing to migrate Active Directory users and groups
To prepare for a successful migration, complete the following tasks:
• Determine the order in which you want to move users from the
Active Directory domains to Lotus Notes. This should be your
migration schedule.
registering users.
• Log into Windows 2000 as an Administrator or Account Operator of
the domains you want to import users from. To migrate Active
Directory users to Notes, the computer where you run the Domino
Administrator must be running Windows 2000.
• If you are creating Notes mail files for imported users, log in to Notes
from the administrative workstation using a Notes ID that has
“Create database access” on the Mail server.
• On an administrative workstation running Windows 2000, install the
Domino 6 Administrator client and the Active Directory migration
tool. You must perform a custom installation to install the migration
tools component.
Note The Active Directory Domino Upgrade Service requires Lotus
Domino 6.
• Verify that you have Read/Write/Update access to the Domino
Directory on the server used for migration.
For information about setting default registration preferences, see the
For information about adding migrated users to a group, see the
Specifying the Active Directory domain to migrate from

The following procedure explains how to connect to an Active Directory
domain to retrieve the domain list. After you retrieve the domain list,
you can select the people and groups to migrate to the Notes registration
queue.
Migrating Users from Microsoft Active Directory 17-3

Note To migrate Active Directory users, the computer on which you
run the Domino Administrator must run Windows 2000 server or
Windows 2000 Professional connected to a Windows 2000 server. The
Active Directory Domino Upgrade Service does not support other
Windows operating systems.
1. In the Domino Administrator, click the People and Groups tab.
2. From the Tools pane, choose People - Register.
4. From the Basics pane of the Register Person - New Entry dialog box,
select a registration server.
5. (Optional) If you do not want to create Notes IDs and Notes mail
files for the migrated users, follow these steps. Note that these
options apply to all users that you import during this session.
• In the Mail System field of the Basics tab, select None.
• Deselect the “Create a Notes ID for this person” check box.
6. On the Basics pane, click Migrate People.
7. In the Foreign Directory Source field of the People and Group
Migration dialog box, select Active Directory from the list.
8. In the Active Directory DUS dialog box, select or browse for the
Active Directory domain, then click OK.
9. In the Filter field of the People and Group Migration dialog box,
select a filter from the list or enter the name of your custom LDAP
filter, then click Go! to display entries in the Available
people/groups box.
10. Set migration options for Active Directory users.
Setting migration options for Active Directory users

You can set migration options to determine what information the Active
Directory Domino Upgrade Service imports from the Active Directory
domain list. Note that the Active Directory Domino Upgrade Service
does not import user passwords from an Active Directory. The migration
options that you choose apply to all users imported during this session.
For more information about migration options, see the chapter
1. In the People and Groups Migration dialog box, click Options, then
select the option settings. The following table lists the defaults for
each option.
17-4 Upgrade Guide

Option Default setting
Generate random passwords for users with no On
passwords
existing passwords)
Add full name provided to the Notes person document Off
Convert mail Off
Add administrator to mail file access control list Off
Convert mail ONLY (Notes users and mail file must Off
already exist)
Note If you disable the “Generate random passwords for users with
no passwords,” you must supply passwords for each user imported
to the registration queue before you can register them.
2. Click OK.
3. Continue to one of the following topics:
If you want to specify a search base or to map Active Directory attributes
to Domino Directory attributes, see the topic “Specifying advanced
migration options for Active Directory users” later in this chapter.
If you want to import users, see the topic “Importing Active Directory
users into the Notes registration queue” later in this chapter.
Specifying advanced migration options for Active Directory users

Specifying advanced migration options is optional.
2. (Optional) In the General Options tab of the Active Directory
Migration Options dialog box, select a search base.
3. In the “Register security groups in Notes as” field, select an option
from the following:
• Multi-purpose
• Mail only
• Access Control List only
• Deny List only
4. In the “Register distribution groups in Notes as” field, select an
option. These options reflect the ones listed in Step 3.
Migrating Users from Microsoft Active Directory 17-5

5. (Optional) By default the “Synchronize mapped attributes for new
users and groups” check box is selected. Clear the check box if you
do not want to synchronize attributes for new users and groups.
6. Click the Field Mappings tab.
7. In the “Field mapping for object class” list, select an object class.
8. In the list box below, select the Active Directory column, then select
an attribute.
9. Beside the Active Directory attribute in the Domino Directory
column, enter or select a Domino Directory attribute.
10. If you want to map more than one attribute, click Apply, then repeat
Steps 6 to 8 as necessary.
11. When done, click OK.
12. Import Active Directory users into the Notes registration queue.
Importing Active Directory users into the Notes registration queue

After setting the migration options and/or the advanced migration
options, you can import users from the Active Directory to the Notes
registration queue.
1. In the Available people/groups box of the People and Groups
Migration dialog box, select the users and groups to migrate, then
click Add. To add all users and groups, click Add All.
2. If you added a group, complete the Group Migration Options dialog
box, then click OK.
3. Click Migrate, then click OK to close the message box that indicates
the number and status of the people and groups queued for
registration.
4. Click Done. If you imported a group, it is now added to the Domino
Directory on the Registration server.
5. Select the person entries in the Registration Queue that you want to
register, then click Register. To register all entries, click Register All.
For more information about setting user registration options, see the
For more information about verifying a migration, see the chapter
17-6 Upgrade Guide

Chapter 18
Migrating Entries from an LDAP Directory Server
This chapter describes how to migrate people and groups from an LDAP-
compliant directory to the Domino Directory using the LDAP Domino
Upgrade Service.
Migrating entries from an LDAP directory server

You use the LDAP Domino Upgrade Service to migrate users and groups
from an LDAP-compliant external directory to the Domino Directory.
The LDAP Domino Upgrade Service creates a Person document for each
migrated person and a Group document for each migrated group.
Optionally, for migrated users, you can create Notes ID files and mail
files.
You can also add unregistered users (that is, users without Notes IDs and
mail files) to the Domino Directory, but those users cannot log into Notes
or gain authenticated access to Domino servers and other Domino
resources through Notes.
When you migrate groups, they are added to the Domino Directory, but
are not registered like users.
The LDAP Domino Upgrade Service offers advanced options for extend-
ing the LDAP schema. These advanced options let you add person and
group object classes and member attributes.
To migrate users and groups from an LDAP directory server, follow this
procedure:
• Specify an LDAP directory server
• Specify LDAP migration options
• Specify advanced LDAP migration options to extend the LDAP
schema
• Add users from an LDAP directory to the Notes registration queue
Alternatively, you can also migrate users from an LDAP directory using
an LDIF file. You can populate the LDIF file with entries, then migrate
those entries with the file. However, you cannot migrate groups using an
LDIF file.
18-1
For more information about migrating users with an LDIF file, see the
chapter “Migrating Users from an LDIF File.”
Migrating person entries

Before you migrate people to a Domino Directory, you must specify a
certifier to use for migrating person entries, even if you choose not to
create Notes IDs and mail files for the entries. The value of the leftmost
portion of the original distinguished name is retained as a cn attribute
value and the remainder of the distinguished name is determined by the
certifier. For example, if the distinguished name for an entry in the origi-
nal LDAP directory is “uid=jdoe,o=companyx”, and the name of the
Notes certifier is “o=acme,” the dn in Domino becomes “cn=jdoe,
o=acme.”
You can preserve the original distinguished names from the LDAP direc-
tory as secondary entries in the User Name field in the Domino Directory
Person documents. To do this, select the “Options” button on the People
and Groups Migration dialog box, and check “Add full name provided
to the Notes Person document.”
If there is more than one entry in the original directory with the same
leftmost value in the distinguished name, then the names for the entries
will be considered as duplicates in the case where one certifier is applied
to them. As a result, only one of the entries will be registered. For
example, suppose there are two entries in the original directory with
these distinguished names: “cn=kathy brown, ou=marketing, o=compa-
nyx” and “cn=kathy brown, ou=sales,o=companyx.” If you import both
of them using the Notes certifier “o=acme,” the resulting distinguished
names will still be identical — “cn=kathy brown, o=acme” — and only
one will be registered.
Names are also considered duplicates if there is more than one entry in
the original directory with the same leftmost value for the distinguished
name, but more than one Notes certifiers are supplied. Using the previ-
ous example, suppose there are two entries in the original directory with
these distinguished names: “cn=kathy brown, ou=marketing, o=compa-
nyx” and “cn=kathy brown, ou=sales,o=companyx.” If you import one of
them using the certifier “companyw”, and the other using the certifier
“acme,” the administration client will still consider these names to be
duplicates, and only one will be registered.
18-2 Upgrade Guide

Requirements for the original person entries
A person entry in the original directory must include a distinguished
name. By default the LDAP Domino Upgrade Service imports all person
entries with at least one of the following object class definitions:
• person
• organizationalPerson
• inetOrgPerson
You can extend the LDAP schema to specify additional person object
classes using the Advanced LDAP Migration Options dialog box.
For more information about extending the LDAP schema, see the book
If person entries in the original directory do not have surname attributes
(sn, s, or surName), you can’t register the entries in Domino until you
specify a last name for each entry.
Imported person entries defined as Domino person entries

After you migrate person entries, they are defined by the dominoPerson
object class. This is meaningful if you use the LDAP service and LDAP
clients search the directory. The dominoPerson object class inherits from
inetOrgPerson, organizationalPerson, and person, which means that
searches on any of these object classes return attributes from Domino
Person entries.
Attribute mapping for person entries

You can only migrate attributes that are defined in the Domino schema.
To migrate attributes that don’t exist in the Domino schema, you must
extend the schema before you migrate. The following table shows how
some common LDAP name attributes in the original entries map to fields
in Domino Directory Person documents.
LDAP attribute Field in Person document

givenName First name
sn, s, or surName Last name
cn Secondary values in User Name field
uid Short name
dn Primary value in the Fullname field
Processing attributes that have multiple values

All attributes containing multiple values are processed, except for attrib-
utes that map to the following fields:
• First Name
Migrating Entries from an LDAP Directory Server 18-3

• Last Name
• Middle Initial
• Short Name
• Internet Address
In the preceding five cases, only the first instance of the attribute is
added. All subsequent attributes are ignored, and the following message
is logged to the Miscellaneous Events view of the local Notes Log file:
LDAP_DUS: Attribute "xxx" already exists, adding first value
only
Passwords are not imported

The LDAP Domino Upgrade Service does not import passwords from the
original LDAP directory. If you attempt to import passwords, the follow-
ing message is logged to the Miscellaneous Events view of the local
Notes Log file:
LDAP_DUS: Cannot migrate attribute password. Passwords can
be set in the registration dialog
mailSystem and altFullNameLanguage attributes not imported

If you are migrating from another Domino LDAP directory, the mailSys-
tem and altFullNameLanguage attributes are not imported. These attrib-
utes, which define the mail system and a certified alternate name to use
in Domino are created automatically through Notes registration.
Migrating group entries

To be migrated, a group entry in the original directory must include a
distinguished name (dn). By default LDAP Domino Upgrade Service
imports all group entries with at least one of the following object class
definitions:
• groupOfNames
• groupOfUniqueNames
• Group
You can extend the LDAP schema to include additional group object
classes using the Advanced LDAP Migration Options dialog box. You
can only migrate attributes of groups that are defined by the Domino
schema of the registration server. To migrate attributes that don’t exist in
the Domino schema, you must extend the schema before you migrate.
For more information about extending the LDAP schema, see the book
18-4 Upgrade Guide

Migrated group entries defined as Domino groups
After you migrate group entries, they are defined by the dominoGroup
object class, which inherits from both the groupOfNames and the
groupOfUniqueNames object classes. LDAP searches of any of these
object classes return attributes from Domino Group entries.
Original names of groups retained by default

When you migrate a group, the original distinguished name for the
group is retained in Domino by default. The certifier doesn’t control the
name as it does for person entries. You can override this default and
specify a different name for each group in Domino individually using the
Group Migration Options dialog box.
For more information about the Group Migration Options dialog box, see
Attribute requirements for members

Members must be defined by the member or uniqueMember attribute.
These are LDAP-standard attributes with a syntax type of DN (distin-
guished name). You can extend the LDAP schema to include addition
member attributes.
Specifying an LDAP directory server
The following procedure explains how to connect to the LDAP directory
server. To migrate users from a foreign LDAP directory, you must know
the host name the LDAP directory server.
2. From the Tools pane, choose People - Register.
3. When prompted, choose the certifier ID and enter the password.
4. In the Basics tab of the Register Person dialog box, click Registration
Server, then select the Domino server that contains the Domino
Directory in which you want to register the entries, then click OK.
5. (Optional) If you are importing person entries and do not want Notes
IDs and mail files created for the entries, do the following:
• In the Mail System field of the Basics pane, select None.
• Deselect the option “Create a Notes ID for this person.” Select a
certifier from the Certifier Name list to use for the name.
6. Click Migrate people.
7. In the People and Groups Migration dialog box, select LDAP in the
Foreign Directory Source field.

8. In the dialog box that opens, complete the fields for selecting the
LDAP directory server according to the tables below.
Field Description
LDAP Hostname Host name of the LDAP directory server that stores
the entries you want to migrate.
LDAP port Port number to use to connect to the LDAP directory
server. The default 389 is the industry standard port
for LDAP connections over TCP/IP. The default 636
is the industry standard port for SSL connections over
TCP/IP.
Base DN for search Search base to specify the location in the directory
tree at which to begin the import. Some LDAP
directory servers require a search base, for example:
o=Acme
o=Acme, c=US
Time Out (seconds) The maximum number of seconds the client will wait
for an answer from the LDAP directory server.
Default is 60 seconds. If you don’t want to impose a
limit, enter 0.
Note The LDAP server may also impose a limit on
how long it can take to answer clients, and this server
limit is never exceeded, regardless of the client
setting.
Bind to LDAP This option connects to the LDAP directory server
anonymously anonymously. Note that some LDAP directory
servers do not allow anonymous connections or do
not allow directory access to anonymous users.
Bind DN for If you don’t bind anonymously, enter a distinguished
authentication name, for example:
cn=Directory Administrator,o=Acme
that the server should use to authenticate you. The
name must correspond to an entry in the directory
and must have the necessary access to search the
directory.
Bind DN password If you enter a Bind DN for authentication, enter the
password associated with the distinguished name.
SSL Enabled Creates a secure connection using the Secure Sockets
Layer (SSL) protocol to connect to the LDAP directory
server.
continued
18-6 Upgrade Guide

Field Description
SSL Protocol Determines which version of the SSL protocol to use:
version • “Negotiated” allows SSL to determine the
handshake and protocol to use
• “V2.0 only” uses SSL V2.0 handshake and protocol
only
• “V3.0 handshake” uses SSL V3.0 handshake and
negotiated protocol
• “V3.0 only” uses SSL V3.0 handshake and protocol
only
• “V3.0 and V2.0 handshake” users SSL V2.0
handshake with negotiated protocol
Accept SSL Accepts a certificate from the LDAP directory server.
Certificates
Verify account Requires that the subject line of the remote server’s
server name with certificate include the LDAP directory server host
remote server’s name. For this option to work properly, the subject
certificate line in the remote server’s certificate must include the
server’s DNS host name. Enable this option if you are
sure the X.509 certificate of the remote directory
server to which your server is connecting contains the
remote server’s host name in the appropriate format.
Send SSL Sends certificates to the server if the server requests
certificates when them. Clear this option if you want to send certificates
asked (outbound on request.
only)
Attempt If you select the option directly above, you can select
authentication this option to request the server’s certificate to verify
using SSL that the server’s identity is the same as the server’s
certificates first name to which you are connecting. Clear this option
if you do not want to perform this check.
9. (Optional) Select “Display status in log.nsf” to record in the Notes

Log file on the local Domino Administrator client information about
how the attributes of imported entries map to Domino. If you select
this option, the Log file shows messages such as the following:
LDAP_DUS: Attribute: ldap attribute, mapped to Notes
attribute: notes attribute
LDAP_DUS: Attribute ldap attribute did not map to Notes
attribute
10. Click OK. If you selected “Bind to LDAP anonymously,” a warning
message appears. Click Yes to continue. Optionally, you can select
“Do not show this warning again” before clicking Yes.

11. In the Filter fields of the People and Groups Migration dialog box,
select a filter from the list.
12. Click Go! to display the LDAP directory entries in the Available
people/groups box.
13. (Optional) If in Step 12 you selected “All users and groups,” you can
click “Show only groups” or “Show only people.”
14. Set options for migrating users from an LDAP directory.
Setting options for migrating users from an LDAP directory

You can set options to determine what information the LDAP Domino
Upgrade Service migrates from the foreign LDAP directory. The options
you specify apply to all users imported from the LDAP directory during
this session. Note that the LDAP Domino Upgrade Service does not
import passwords.
1. In the People and Groups Migration dialog box, click Options, then
select migration options. The following table shows the options
available to you and their default settings.
Option Default setting
Generate random passwords for users On
with no passwords
Generate random passwords for all Off
users (overwrite existing passwords)
Add full name provided to the Notes On
person document
Allow addition of empty groups to On
Notes
2. Click OK.
3. Continue to one of the following:
To set advanced LDAP migration options, see the topic “Specifying
advanced LDAP migration options” later in this chapter.
To import users into the Notes registration queue, see the topic “Adding
users from an LDAP directory to the Notes registration queue” later in
this chapter.
18-8 Upgrade Guide

Specifying advanced LDAP migration options
You can specify advanced migration options to search for extended
person and/or group object classes as well as extended member attrib-
utes. By default, the LDAP Domino Upgrade Service searches the speci-
fied foreign LDAP directory using the following set of common person
and group object classes and group member attributes:
• Person: person, inetOrgperson, organizationalPerson
• Group: groupOfNames, groupOfUniqueNames, Group
• Member: Member, uniqueMember
The foreign LDAP directory may contain entries whose object class types
differ from the standard LDAP object class types. From the Advanced
LDAP Migration Options dialog box, you can define customized lists of
people and group object classes.
Group entries in the LDAP Domino Upgrade Service are created when
you select a group to migrate. Based on the options that you choose in the
Group object classes section of the Advanced LDAP Migration Options
dialog box, the members contained in those groups may also be migrated.
If the schema in the foreign LDAP directory has been extended, and the
member attribute name has been extended to something other than the
default of “Member” or “uniqueMember,” you can specify extended
member attributes in the “Member attributes” section of the dialog box.
Follow this procedure to create new person and group object classes or to
add member attributes.
2. If you want to migrate entries whose person or group object classes
have been extended in the foreign LDAP directory, follow these
steps:
• In the Advanced LDAP Migration Options dialog box, select the
“Extended person object class” and/or the “Extended group
object class” check box.
• In the text field beside the check box, enter the customized object
class.
• (Optional) To add more than one extended object class, repeat
Step 2, then click “Add To List” for each entry.
3. If you want to migrate group entries whose member attributes have
been extended in the foreign LDAP directory, follow these steps:
• Select the “Extended member attribute” check box.
• In the text field beside the check box, enter the customized
member attribute.

• (Optional) To add more than one extended member attribute,
repeat Step 3, then click “Add To List” after each entry.
4. Select additional options. The following table describes each option.
Option Description
Foreign member Adds foreign group members who do not exist in
attributes the specified foreign LDAP directory to the
migrated group member list.
Save advanced Saves the extended person or group object classes
settings for future and the extended member attributes as default
queries search criteria for future migration requests.
Reset dialog warnings Enables the dialog warnings that you disable. If
you selected the “Do not show this warning again”
check box in the “Anonymous Bind Warning” and
“Advanced Dialog Warning” boxes, then you
disabled the warnings.
5. Click OK.
6. Add users from the LDAP directory to the Notes registration queue..
Adding users from an LDAP directory to the Notes registration

queue
After setting migration options and advanced LDAP migration options,
you can import users into the Notes registration queue.
1. In the Available people/groups box of the People and Group
Migration dialog box, select the users and groups you want to add to
the Notes registration queue, then click Add. To migrate all entries in
the Available people/groups box, click Add All.
2. If you added a group, complete the Group Migration Options dialog
box, then click OK. For more information about the group migration
options, see the topic “Setting Group Migration Options.”
3. Click Migrate, then click OK to close the message box that indicates
the number and status of the people and groups queued for
registration.
4. Click Done. If you migrated a group, it is now added to the Domino
Directory on the Registration server.
5. Select the person entries in the Registration Queue that you want to
register, then click Register. To register all person entries, click
Register All.
For more information about registering users, see the book Administering
the Domino System.
18-10 Upgrade Guide

Index
upgrading, 1-11, 6-1 migrating private mailing

A Archives, mail lists, 11-25, 11-33
Accent-sensitive sorting conversion options, 16-12 to 16-13 cc:Mail Admin
setting, 6-13
migrating, 16-11 to 16-12, deleting files with, 11-36
Access rights 16-14 to 16-15 cc:Mail CHKSTAT
migrating mail, 11-6 naming, 16-14 account reporting with, 11-9
Account records
preserving folder hierarchies deleting messages with, 11-36
Internet mail, 4-17 in, 16-15 cc:Mail migration
Active Directory. See Microsoft Archiving access rights, 11-6
Active Directory
Organizer data, 11-20 adding names to Person
Address books Attachments documents, 11-12
migrating, 16-16 sending Notes Personal Address adding users to Notes, 11-1
Addresses
Book, 16-18 adding users to registration
creating for Internet mail, 2-20 Authentication queue, 11-21
in a mixed-release flat organizations and, 9-14 aliases, 11-26
environment, 2-18
in a mixed-release backing up Domino files, 11-14
ADMIN4.NSF environment, 8-2 bulletin board
upgrading, 2-13, 6-7 Internet/intranet clients, 8-2 conversion, 11-26, 11-41
Administration clients
third-party certificates and, 8-3 connecting to post office, 11-21
upgrading, 1-5, 1-38 Convert Mail Only, 10-16, 11-37
Administration Execution Control B deleting user files, 11-36
List Backing up
directory
default security and, 4-15 files on Notes client before conversion, 11-39 to 11-40
Administration Process upgrading, 4-4 disk space required, 11-8
converting flat names Bookmarks
error threshold, 11-32, 11-34
with, 9-1, 9-12 described, 4-16 files, 11-2
creating mail files with, 10-22 workspace conversion and, 4-16 forwarding mail, 11-37
renaming flat server names, 9-6 Browsers
forwarding mail to Notes, 11-33
renaming users with, 9-1 default Web templates and, 6-16 gateway names in private
Administration Requests database Bulletin boards addresses, 16-20
upgrading, 2-13 cc:Mail, 11-41
language code
Administrative preferences
setting, 10-19 C page, 11-15, 11-24, 11-29
location codes, 11-33, 11-37
AdminPInterval setting, 2-32 Calendar and scheduling
in mail, 2-40 mobile users, 11-22, 11-26
AdminPModifyPersonDocumentsAt MTA requirements, 10-3,
setting, 2-32 Internet mail and, 4-18
meetings, 4-17 11-12 to 11-13, 11-38
Agents
Cascading Domino Directories name conventions, 11-10
testing, 1-13 name formats, 11-11
Aliases directory assistance table and, 3-8
upgrading to directory naming conventions, 11-9
migrating cc:Mail, 11-26
assistance, 3-8 Notes equivalents for migrated
user names and, 10-14 data, 11-2, 11-4, 11-10, 11-41
Application servers Web client authentication, 3-10
Case-sensitive sorting options, 11-22 to 11-24
upgrading, 1-5
setting, 6-13 Organizer data and, 11-14,
Applications 11-16 to 11-17, 11-19
documenting, 1-11 cc:Mail 6.3
mail template for, 11-32 Organizer files, 11-2, 11-4
testing, 1-13
passwords, 10-14, 11-7
Index-1
Person documents, 11-12 Condensed Directory Catalogs DNS
post office, 11-13, 11-20 full-text indexes, 3-5 server common name, 2-2
private mailing lists, 11-3, 11-25 Config_DB setting, 2-32 Document libraries
registering users, 11-34 Configuration Settings document upgrading, 6-14
removing inactive accounts, 11-9 enabling native SMTP, 2-16 Domain Catalog
tasks, 11-7 Conversion replacing database catalog, 6-14
upgrade settings, 11-32 defined, 10-2 Domain Index
upgrade wizard, 11-31 migrating archives, 16-12 upgrading, 7-2
versions supported, 11-2, 11-32 Convert task Domain Indexer task
cc:Mail MSGMGR upgrading mail files, 5-3 and Domino 4.6 Web
deleting messages with, 11-36 Custom Format Pattern servers, 7-4
cc:Mail MTA using to create Internet Domain Search
bulletin board conversion, 11-27 addresses, 2-22 Domino 4.6 and, 7-4
forwarding mail with, 11-37 Custom upgrade Search Site and, 7-3
migration requirements for, 10-3, archive files and, 16-12 upgrading, 7-2
11-12 to 11-13, 11-26, 11-38 to archive migration and, 16-12 Domino 4.6
11-39, 11-41 CLUBUSY.NSF and, 1-40
CCNOTBB.NSF D Domain Search and, 7-4
Database catalogs
migrating cc:Mail bulletin boards mail server upgrade
to, 11-26 Domain Catalog and, 6-14 example, 1-10
CCPODOWN file Database design mail server upgrades, 1-7
upgrading, 6-2
deleting before cc:Mail testing applications created
migration, 11-13 Database fields for, 1-13
Central Directory increasing number of, 3-8, 6-12 UniqueNameKey table
Database format
in mixed-release and, 1-14, 3-8
environments, 1-42 maintaining, 6-4 to 6-5 Domino Administration servers
Certificates replication and, 6-5 post-upgrade tasks, 2-12
upgrading, 6-2
exchanging, 9-14 running the LDAP service, 3-6
flat, 9-14 Databases upgrading, 2-4
S/MIME and SSL, 8-3 accessing locally, 6-4 Domino Administrator
allowing more fields in, 3-8
trusted, 9-14 Domino Upgrade Services
Certification compacting, 6-3 and, 10-3
flat, 9-14 compacting in mixed-release Domino Administrator client
environments, 1-45
non-hierarchical organizations enhancements, 1-26
and, 9-14 file extensions, 6-4 new features, 1-16
Certification Log size, 6-3 upgrading, 2-13
upgrading, 1-6, 6-1
creating, 2-30 Domino Directory
troubleshooting with, 9-9 DBX files adding LDIF file person
upgrading, 2-30 migrating messages entries, 15-10
from, 16-11
Certifier IDs allowing more fields in, 3-8
flat names and, 9-14 to 9-15 DefaultMailTemplate checking Internet addresses for
recertifying, 9-19 use in migrating archives, 16-13 uniqueness, 2-23
Deletions, soft
Character sets compacting, 3-1
LDIF file, 15-2 in mixed-release clusters, 1-42 populating Internet Address
Microsoft Mail, 12-10 Desktop Settings document field, 2-20
seamless mail upgrade, 5-6
CLUBUSY.NSF template, 3-4
Domino 4.6 and, 1-40 upgrading, 3-9 upgrading, 3-1
Clusters upgrading from cascading upgrading a customized
Domino Directories, 3-8
mail files in, 1-42 directory, 3-5
Compact task Directory Profile document validating Internet Address
indirect file, 6-6 using, 3-10 field, 2-23
Distinguished names
Compacting Domino Directory Profile. See
databases, 1-45 adding to the Person document, Directory Profile
15-3 document
Index-2
Domino Directory template Fields, database Groups
using in a mixed-release increasing number adding users during
environment, 3-4 of, 3-8, 6-12 migration, 10-12
Domino Off-Line Services File extensions canceling migration of, 10-11
upgrading subscriptions, 6-11 database, 6-4 creating, 10-8
Domino server Files duplicate names, 10-6
configuring, 2-16 backing up on Notes client before migrating, 10-4 to 10-5,
enhancements, 1-26 upgrading, 4-4 10-8, 10-10
installing, 2-11 Fixup task migrating users to, 10-5
new features, 1-16 indirect file, 6-6 migration options, 10-5 to 10-6
Domino SNMP Agent Flat certificates nested, 10-5
upgrading, 2-30 deleting from IDs, 9-16 renaming, 10-9
Domino system Flat IDs
upgrading, 1-3 certificates and, 9-14 H
Domino Upgrade Services creating, 9-15 to 9-16 Hardware
upgrading requirements, 1-3
cc:Mail, 11-1 described, 9-14
importing users to the Domino recertifying, 9-16 to 9-19 Hierarchical IDs
Directory, 10-3 renaming, 9-20, 9-22 recertifying, 9-19
Hierarchical names
installing, 10-3 Flat names
LDAP, 18-1 certification and, 9-14 to 9-15 converting flat names to, 9-1, 9-11
LDIF file, 15-1 communication and, 9-14 examples, 9-4
in Person documents, 10-14
Microsoft Active Directory, 17-1 converting to hierarchical,
Microsoft Exchange, 13-1 9-1, 9-6, 9-9 to 9-12 Host names
Microsoft Mail, 12-1 described, 9-14 DNS and, 2-2
Hub servers
overview, 10-1 renaming, 9-6
specifying a foreign user, 9-11 upgrading, 1-5
directory, 10-4
Windows NT, 14-1
Folders
migrating, 10-23, 16-15
I
IBM Lotus Notes Smart Upgrade
Duplicate messages names, 10-23 See Smart Upgrade
migrating, 10-23 Upgrade Folder Design IDs
Duplicate names agent, 5-10 in a mixed-release
migrating groups with, 10-5 upgrading, 5-5, 5-7, 5-10 environment, 8-1
Duplicate Person documents Foreign directory source recertifying, 9-16
updating, 11-12 defined, 10-3 IDs, certifier
specifying, 10-4 creating, 9-15
E Forms flat names and, 9-14
ECL
testing, 1-13 IMAP
installing a Notes client, 8-4
converting mail files to use, 5-3
upgrading a Notes client, 8-4 G message storage format and, 2-37
workstation security and, 4-15 Gateway addresses
Importing
Enhancements translating, 16-15, 16-20
Domino Administrator Gateway mapping defined, 10-2
client, 1-26 between cc:Mail and groups, 10-4
Inbound relay controls
Domino server, 1-26 Notes, 16-15
Examples Gateways Domino 5 configuration, 2-27
LDIF file, 15-2 relay hosts and, 2-38 Inbound transport
shutting down before upgrading
Exchange. See Microsoft Group migration options
Exchange adding members, 10-8 MTA, 2-6
Express upgrade and multiple groups, 10-11 Inbound Work Queue
clearing, 2-7
archive migration and, 16-11 setting, 10-6
Group names Inbox folder
F specifying, 10-9 migrating, 10-23
Failover Incoming mail
Group types
in a mixed-release cluster, 1-42 migrating, 10-9 preferences, 2-24, 2-34
Index-3
Indexes Interoperability LDAP_Enforce_Schema setting, 2-32
updating, 7-2 in mixed-release LDAP_Strict_RFC_Adherence
upgrading, 7-2 environments, 1-38 setting, 2-32
Indirect file LDAP_UTF8Results, 2-32
creating, 6-6 J LDIF
iNotes Sync Manager JavaScript defined, 15-2
default Web templates and, 6-16
upgrading, 6-11 name formats, 15-2
iNotes Web Access Web browsers and, 6-16 LDIF file migration
upgrading clients, 5-9 JavaScript formulas adding names to Person
upgrading, 6-15
INOTES60.NTF documents, 15-5, 15-10
upgrading mail files to, 5-9
Internet Address Construction
L distinguished names, 15-3
Internet addresses, 15-5
Language code page
dialog box, 2-19 cc:Mail migration Notes equivalents for migrated
sample, 2-22 and, 11-24, 11-29 data, 15-4 to 15-5
Internet Address field Microsoft Mail migration object classes, 15-3 to 15-4
populating in Person and, 12-10 options, 15-8
documents, 2-19 Organizer migration and, 11-15 overview, 15-1
upgrading and, 2-18, 2-23 Language packs passwords, 15-5
using, 2-22 upgrading, 2-2 registering users, 15-9
Internet Address tool LDAP Data Interchange Format. See selecting files, 15-7
examples of addresses created LDIF subscription accounts, 15-12
with, 2-22 LDAP directory migration tasks, 15-5
using in Domino Directory, 2-19 adding groups to the Domino to multiple Notes organizational
Internet addresses Directory, 18-4 units, 15-7
assigning to users, 2-20 adding names to Person unregistered Notes users, 15-10
checking for uniqueness, 2-23 documents, 18-2 Listener task
creating, 2-22 to 2-23 adding users and groups to the MTA server and, 2-17
formats for, 2-21 Notes queue, 18-10 Local users
in Person documents, 2-19 attribute mapping, 18-3 migrating, 10-5
name formats in, 2-22 attributes with multiple Location codes
using custom format pattern values, 18-4 cc:Mail, 11-33, 11-37
for, 2-22 defining group entries, 18-5 Location documents
validating for users, 2-23 defining person entries, 18-3 Smart Upgrade and, 4-13
Internet mail member attribute
Account records, 4-17 requirements, 18-5
M
calendar and scheduling, 4-18 Mail
object classes, 18-9 addressing to Internet mail
Notes formatting and, 2-39 options, 18-8 to 18-9
routing in a mixed-release users, 2-18
overview, 18-1 converting to MIME, 2-39
environment, 2-34 passwords, 18-4 in mixed-release clusters, 1-42
storage, 2-37 person entry requirements, 18-3
third-party relay hosts and, 2-38 MIME format, 1-7
specifying a directory server, 18-5 upgrading, 5-3
upgrading and, 1-7 LDAP schema Mail addresses
Internet mail addresses deleting SCHEMA50.NTF
in a mixed-release in a mixed-release
template, 3-6 environment, 2-18
environment, 2-18 upgrading database, 3-6 upgrading and, 2-18, 2-22
upgrading and, 2-18, 2-22 LDAP service
validating, 2-23 Mail conversion utility
deleting SCHEMA50.NSF options, 5-4
Internet mail servers database, 3-6 wildcards and, 5-6
configuring, 2-16 Domino Administration server
editing Server document Mail delivery
and, 3-6 in a mixed-release
for, 2-17 NOTES.INI settings, 3-7 environment, 2-37
upgrading, 2-1 schema daemon, 3-6
Internet Site documents Mail files
LDAP_CountryCheck setting, 2-32 clusters and, 1-42
Server documents and, 1-40
Index-4
conversion, 10-16 Message counts error threshold, 12-11
creating for migrated discrepancies during migration, language code page and, 12-10
users, 10-22 16-21 migrating again after
preventing replication of, 5-8 Message format preferences registration, 12-14
quotas, 10-23 setting, 2-24 name conversion errors, 12-5
template interoperability, 5-8 Message queues naming conventions, 12-2
templates and Lotus Notes client clearing, 2-5 Notes equivalents for migrated
versions, 5-8 Messages, duplicate data, 12-2
upgrade options, 5-1 migrating, 10-23 options, 12-8 to 12-9
upgrading, 5-1, 5-3, 5-6 Messaging data registering users, 12-8, 12-12
Mail folders migrated by the user upgrade tasks, 12-5
maximum name length, 10-24 wizards, 16-2 upgrade wizard, 12-13
Mail profiles Microsoft Active Directory migration user address list, 12-7
Microsoft Exchange migration adding users to Notes registration versions supported, 12-1
and, 13-5 to 13-6 queue, 17-6 Microsoft Outlook client
Mail routing advanced options, 17-5 migrating Contacts information
in a mixed-release containers, 17-2 for, 16-18
environment, 2-34 field mapping option, 17-1 Microsoft Outlook Express
Mail rules importing names, 17-2 migrating messages from, 16-16
in mixed-release clusters, 1-42 importing passwords, 17-2 migrating personal address book
Mail servers LDAP filters, 17-2 information, 16-18, 16-21
upgrading, 1-5 LDAP searches, 17-1 short names, 16-4, 16-16
Mail storage options, 17-4 Microsoft Outlook Express upgrade
in a mixed-release overview, 17-1 wizard
environment, 2-37 search base, 17-2 upgrade methods, 16-10
upgrading and, 2-37 specifying the Active Directory Migration
Mail templates domain, 17-3 archives, 16-11, 16-14
size, 16-15 tasks, 17-3 defined, 10-2
specifying for archive Microsoft Exchange migration duplicate messages, 10-23
migration, 16-13 adding users to the registration groups, 10-5
MAIL50.NTF queue, 13-6 message archives, 16-11
as default template for archive creating Notes mail files, 13-9 nested groups, 10-10
migration, 16-13 directory, 13-5 passwords and, 10-13
MAIL6.NTF folders, 13-3 personal address books, 16-16
Upgrade Folder Design gateway names, 13-3 personal mail data, 16-1
agent, 5-10 mail files, 13-3 selecting people and groups
upgrading mail files to, 5-3 mail profiles, 13-5 to 13-6 for, 10-4
Mailclusterfailover Notes equivalents for migrated user names to Person
setting, 2-33 data, 13-1 documents, 10-14
Mailing lists options, 13-7 verifying, 10-24
migrating, 16-17 overview, 13-1 Migration options
MAPI profile PST files, 13-3 group, 10-6
Microsoft Exchange migration registering users, 13-8 setting, 10-12
and, 13-6 tasks, 13-4 to 13-5 user, 10-18
Mapping Microsoft Mail migration MIME messages
gateways between cc:Mail and ACL access to Notes mail converting in a mixed-release
Notes, 16-15 files, 12-14 environment, 1-7
Meetings, repeating adding users to Notes, 12-1 converting to Notes
upgrading mail templates address books, 12-2, 12-12 format, 2-39
for, 4-17 advanced options, 12-10 delivering to Release 4
Message archives backing up Domino files, 12-6 servers, 2-37
converting, 16-14 connecting to postoffice, 12-7 in mixed-release clusters, 1-42
Message conversion Convert Mail Only, 10-16, 12-14 MMF files
upgrading and, 2-37 Convert Mail option, 12-13 migrating messages from, 16-11
Index-5
Mobile users NNTP_Previous_X_servername OR2 files
migrating from setting, 2-33 migrating, 11-2
cc:Mail, 11-22, 11-26 NNTP_Prohibit_NEWNEWS_Comm Organizational units
MTA servers and setting, 2-33 migrating LDIF file users to, 15-7
backing up files before NNTP_PullAsServer setting, 2-33 Organizer
upgrading, 2-3 NNTPAddress setting, 2-33 compacting data, 11-19, 11-20
clearing queues, 2-7 Notes Notes equivalents for migrated
clearing SMTP.BOX, 2-6 MIME conversion and, 2-39 data, 11-4
disabling housekeeping on, 2-5 Notes client Organizer data
enabling SMTP, 2-16 backing up files, 4-4 converting to Notes, 11-25
enabling SMTP Listener task, 2-17 backing up files before secondary migration of, 11-19
installing Domino, 2-11 upgrading, 4-4 Organizer group scheduling files
post-upgrade tasks, 2-15 installing, 4-6 migrating, 11-2
shutting down inbound setting Personal Address Book Organizer migration
transport, 2-6 preferences, 4-17 addresses, 11-17
shutting down router before upgrading, 1-6, 4-1, 4-3 archiving data, 11-20
upgrading, 2-6 upgrading local indexes, 7-2 Calls sections, 11-16
upgrading, 1-7, 2-1, 2-5 upgrading workspace to category information, 11-16
MX records bookmarks, 4-16 data directories, 11-19
third-party relay hosts and, 2-38 Notes groups error logging, 11-15
creating, 10-8 forwarding mail, 11-15
N specifying during migration, 10-9 graphics, 11-17
Names Notes log language code page, 11-15
Internet address, 2-21 verifying migration with, 16-21 meeting information, 11-16
LDIF, 15-2
Notes names Notepad sections, 11-17
Names, flat. See Flat names converting cc:Mail names Notes equivalents for migrated
NAMES.NSF to, 11-10 data, 11-14, 11-16, 11-19
allowing more fields in, 3-8
converting LDIF attributes passwords, 11-15
compacting, 3-1 to, 15-4 tasks, 11-18, 11-20
upgrading, 3-1 converting Microsoft Mail names Outbound Work Queue
Naming conventions
to, 12-2 clearing, 2-7
cc:Mail, 11-9, 11-10 converting Windows NT names Outlook. See Microsoft Outlook
folders, 10-23 to, 14-5 to 14-7
imported groups, 10-9
hierarchical, 10-14 P
Internet addresses, 2-22 valid characters, 11-11 Passwords
LDIF, 15-4 Notes organizational units generating automatically, 10-13
Microsoft Mail, 12-2 importing, 10-18
migrating LDIF file
Windows NT, 14-6 users to, 15-7 information about, 10-13
Nested groups Notes short names migrating, 10-13
defined, 10-5 migrating cc:Mail users and, 11-7
generating, 14-5
migrating, 10-10 NOTES.INI file random, 10-14
New features obsolete settings, 2-32 Pending registrations
Domino Administrator saving information for, 10-20
upgrade wizard and, 16-10
client, 1-16 NT service People
Domino server, 1-16 removing before upgrading, 2-9 migrating, 10-4
New_DNParse setting, 2-33 People and Groups Migration dialog
NUPGRADE.EXE
NNTP documents upgrade wizards and, 16-9 box
removing from Domino adding administrator to mail file
Directory, 2-29 O ACL option, 10-15
NNTP_Delete_Days setting, 2-33 ODS. See Database format adding empty groups option,
NNTP_Delete_Days_Expired On-Disk Structure. See Database 10-15
setting, 2-33 format options, 10-12
NNTP_Initial_Feed_All setting, 2-33 Operating systems People/Groups to migrate list
requirements, 1-2 adding groups, 10-4
Index-6
Person documents Search
Internet Address field, 2-19 R features, 7-2
Internet address in, 2-22 R63MAIL.NTF upgrading, 7-1 to 7-2
mail template for cc:Mail 6.3
Internet mail storage format upgrading server indexes, 7-2
and, 2-37 users, 11-32 Search Site
migrating user names to, 10-14 Rebuilding views Domain Search and, 7-3
database access delays and, 6-6
updating during migration, 11-12 security, 7-3
validating Internet Registration Security
addresses in, 2-23 failure, 10-18 upgrading, 8-1
migration and, 10-17
Personal Address Book workstation, 4-15
migrating information pending, 10-20 Sent folder
from, 16-16 stopping, 12-12 migrating, 10-23
Registration Person dialog box
migrating Microsoft Mail to Server common names
Notes, 16-18 settings, 10-21 spaces, 2-2
setting preferences, 4-17 Registration queue underscores, 2-2
adding cc:Mail users, 11-21
upgrading, 4-17 Server documents
Personal mail data adding LDIF file users, 15-7, 15-9 Internet Site documents and, 1-40
migrated by user upgrade adding Microsoft Exchange users, SMTP routing information
13-6, 13-8
wizards, 16-2 in, 2-17
migrating, 16-1 adding Microsoft Mail Server files
Personal mailing lists users, 12-8, 12-12 backing up before upgrading, 2-3
adding Windows NT
migrating, 16-17 Server upgrade
Policies users, 14-4, 14-8 backing up files, 2-3
deploying client settings, 4-15 editing user names, 14-8 disabling SMTP/MIME
maintaining passwords in, 10-13
Setup Profiles and, 1-39, 4-15 housekeeping, 2-5
POP3 migration and, 10-20 installing Domino and, 2-11
message storage format and, 2-37 Registration settings post-upgrade
for migration, 10-19
Preferences tasks, 2-12, 2-15, 2-25, 2-28
Personal Address Book, 4-17 table of, 10-21 preparing a Domino 5 mail
Private addresses Relay hosts server, 2-8
configuring, 2-38
migrating cc:Mail, 16-17 preparing Domino
Private mailing lists smart hosts and, 2-38 Administration servers, 2-4
migrating, 16-17 upgrading and, 2-38 removing Domino as an NT
Renaming
migrating for cc:Mail 6.3 service, 2-9
users, 11-25 groups, 10-9 restricting clustered servers, 2-2
migrating to Notes Personal Repeating meetings feature shutting down the server, 2-9
upgrading mail templates
Address Book, 16-18 SMTP and, 2-16
PRIVDIR.INI for, 4-17 UNIX systems, 2-10
use in migrating cc:Mail private Replication upgrading Domino
database format and, 6-5
addresses, 16-17 Directory, 3-1
PST files preventing, 5-8 Server_Name_Lookup_Noupdate
migrating messages
from, 13-3, 16-11
S Servers
setting, 2-33
S/MIME
Public Address Book third-party certificates and, 8-3 converting flat names, 9-1
See Domino Directory Sametime flat certificates and, 9-14
PUBNAMES.NTF upgrading Domino servers, 2-2 recertifying IDs, 9-16
upgrading, 3-1, 6-8 Scheduling meetings renaming, 9-1
in a mixed-release upgrading, 2-1
Q environment, 4-17 ServerTasks setting, 2-33
QuickPlace Set Internet Address
upgrading Domino servers, 2-2 Seamless mail upgrade
and policies, 5-6 Domino Directory tool, 2-19
Quotas
and Setup Profiles, 5-6 Setup Profiles
mail, 10-23 policies and, 1-39, 4-15
mail files, 5-6
seamless mail upgrade, 5-6
Index-7
Shared installation Subfolders requirements for, 16-4
upgrading, 4-14 migrating, 10-24, 16-15 running, 16-4, 16-8
Windows Installer and, 4-14 Subscription accounts tasks, 16-21
Shared mail creating for imported LDIF Upgrade-by-mail
upgrading, 2-26 users, 15-12 installing the Lotus Notes
Shortcuts Subscription bulletin boards client, 4-6
running upgrade wizards migrating from cc:Mail, 11-27 overview, 4-3
from, 16-10 preparation for using, 4-4
Size T upgrade notification, 4-5
TeamRoom templates
mail file, 10-23 upgrading mail file template, 4-7
Smart hosts upgrading, 6-15 Upgrading
relay hosts and, 2-38 Templates administration clients, 1-38
JavaScript compliance, 6-16
Smart Upgrade customized Domino
assigning policies to users and specifying for archive Directories, 3-5
groups, 4-13 migration, 16-13 databases and applications, 6-1
upgrading, 6-7, 6-9
desktop policy settings Domino Administrator client,
document, 4-11 versions, 6-9 2-13
explicit policy, 4-12 Temporary Personal Address Books Domino Directory template, 3-4
mailing to users, 16-18
linking to Configuration Settings Domino SNMP Agent, 2-30
document, 4-9 Testing applications from earlier Notes/Domino
location documents and, 4-13 before upgrading, 1-13 releases, 1-3
Transaction logging
Lotus Notes Smart Upgrade Kits hardware requirements for, 1-3
template, 4-8 disk space and, 6-14 in mixed-release
maintaining, 4-14
organizational policy, 4-12
U environments, 1-38
language packs, 2-2
UniqueNameKey table
overview, 4-7 size, 3-8 Notes clients, 4-1
Smart Upgrade database, 4-8 UNIX overview, 1-1
update kits, 4-9 installation options, 2-10 post-upgrade
Windows Installer and, 4-13 UNK table. See UniqueNameKey tasks, 2-12, 2-15, 2-25, 2-28
SMTP table preparing
Foreign SMTP Domain Updall task for, 1-2, 2-4, 2-8, 4-3
documents, 1-7 indirect file, 6-6 QuickPlace, 2-2
relay controls and Domino 5, 2-27 Update kits Sametime, 2-2
SMTP Connection documents, 1-7 and Smart Upgrade, 4-9 security, 8-1
upgraded MTA server and, 2-16 Upgrade methods server indexes, 7-2
SMTP Listener task custom, 16-10 shared mail, 2-26
enabling for upgraded MTA express, 16-10 tasks, 1-13
server, 2-17 selecting, 16-10 to a partitioned server, 2-2
SMTP.BOX Upgrade notification messages UNIX servers, 2-10
clearing, 2-6 sending, 16-7 Use Custom Format Pattern
SMTPIBWQ.NSF upgrade wizards and, 16-9 in Internet Address tool, 2-22
clearing, 2-7 Upgrade wizards User IDs
SMTPRelayAllowHostsandDomains custom upgrades and, 16-12 renaming, 9-20, 9-22
setting data migrated by, 16-2 User names
and Domino 5 relay control express upgrades and, 16-11 in Person documents, 10-14
configuration, 2-28 for Microsoft Mail data, 12-13 invalid characters, 11-11
Soft deletions gateway mapping, 11-31 LDIF file, 15-2
in mixed-release clusters, 1-42 installing, 10-3, 16-5 to 16-6 Microsoft Mail, 12-2, 12-5
Sort order migrating personal address book migrated cc:Mail, 11-9
in views, 6-13 information, 16-19 migrated Windows NT, 14-8
SSL mixed-release environments Users
third-party certificates and, 8-3 and, 16-4 converting flat names, 9-1
Statistics mail-in database overview, 16-1 migrating, 10-4
upgrading, 6-16 recertifying IDs, 9-16
Index-8
registering for migration, 10-17 requirements, 14-3
renaming, 9-1, 9-12 tasks, 14-2
Windows NT service
V removing before upgrading, 2-9
View_Rebuild_Dir setting Workspace
upgrading databases, 6-14 converting to bookmarks, 4-16
Views
Workstations
character sorting, 6-13 ECL, 4-15
rebuilding, 6-6, 6-14
testing, 1-13
W
Web
JavaScript versions and, 6-16
templates, 6-16
Web Administrator
upgrading, 2-14
Web browsers
default Web templates and, 6-16
Web client authentication
cascading Domino
Directories, 3-10
secondary directories, 3-10
Web sites
subscription accounts, 15-12
WEBADMIN.NSF
upgrading, 2-14
WebAdmin_Disable_Force_GUI
setting, 2-33
WebAdmin_Expire_Cache
setting, 2-33
WebAuth_AD_Group setting, 2-33
Wildcards
mail conversion utility and, 5-6
WinAdmin
deleting cc:Mail files after
migration, 11-36
Windows Installer
shared installation and, 4-14
Smart Upgrade and, 4-13
Windows NT
user name format, 14-6
Windows NT migration
adding users to registration
queue, 14-4
advanced options, 14-5
domain list, 14-3
name conversion errors, 14-8
name formats, 14-6, 14-7
Notes equivalents for migrated
data, 14-5, 14-6
options, 14-4
overview, 14-1
registering users, 14-8
Index-9

Upgrade

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Upgrade

Uploaded by

Copyright:

Available Formats

Lotus Notes 6

Part No. CT1L4NA

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Removing NNTP documents from the

Using seamless mail upgrade . . . . . . . . . . . . . 5-6 Converting flat server names to

Upgrading databases to Lotus How the Domino Administration Process

16 Migrating Personal Mail Data . . 16-1

17 Migrating Users from

Printed documentation and PDF files

Structure of Notes and Domino documentation

Documentation for the Notes client

Documentation for Domino administration

viii Upgrade Guide

Documentation for Domino Designer

Upgrading to Lotus Notes/Lotus Domino 6

Using this guide

Preparing to upgrade to Lotus Notes/Domino 6

Operating system changes

1-2 Upgrade Guide

Supported upgrade path

Planning the upgrade

Planning the Move to Lotus Notes/Domino 6 1-3

Domino Administration server and Domino Directory or Public

Domino Administrator client

1-4 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-5

Applications and databases

How Lotus Domino 6 replaces the Domino 4.6 MTA

1-6 Upgrade Guide

Domino 4.6 mail server upgrade scenarios

Planning the Move to Lotus Notes/Domino 6 1-7

1-8 Upgrade Guide

Use a mixed MTA upgrade strategy

Planning the Move to Lotus Notes/Domino 6 1-9

1-10 Upgrade Guide

Steps for documenting applications

Planning the Move to Lotus Notes/Domino 6 1-11

Use a test environment

1-12 Upgrade Guide

The upgrade roadmap

Planning the Move to Lotus Notes/Domino 6 1-13

1-14 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-15

1-16 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-17

Administration Process and Requests

1-18 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-19

Domino Upgrade Services

1-20 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-21

1-22 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-23

1-24 Upgrade Guide

System monitoring and maintenance

Planning the Move to Lotus Notes/Domino 6 1-25

Domino server and Domino Administrator client enhancements

1-26 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-27

1-28 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-29

Domino Off-Line Services (DOLS)

1-30 Upgrade Guide

Planning the Move to Lotus Notes/Domino 6 1-31