You can migrate users’ Personal Address Books (PABs) from their individual client workstations to their Microsoft Exchange Server 2007 mailboxes.
You can migrate personal address books either from the Microsoft Transporter for Lotus Domino Microsoft Management Console (MMC), or from the Transporter Command Shell prompt.
The migration process involves capturing the individual personal address book files from client workstations and copying them to a central location to simplify administrator-driven migration. Notes users will in most cases have the option to synchronize their address books with the server-side database, from where you can migrate the address books individually or in bulk.
|For users who cannot synchronize their address books with the server, you must migrate their address books separately. Typically, Personal Address Book files are the NAMES.NSF files from client workstations. Shared installations on workstations should create these folders under user’s Documents and Settings directory (on Microsoft Windows-based platforms), so collection from these locations could be automated. On other operating systems, these files are generally located under the user’s home directory.
Addresses in Personal Address Books and Active Directory User Objects
Addresses stored in Personal Address Books will not be able to be replied to unless the Notes address has been copied to the associated user or contact object in Active Directory. Ordinarily, this copying of addresses will occur during Directory Synchronization tool and as part of the function of migrating users.
“Fuzzy” address matching may resolve to users whose names have been modified. For example, the following may resolve, depending on configuration setting on the Domino side:
- Contact: Bonnie L Skelly/Certifier
- Person document: Bonnie Skelly/Certifier
During user migration, all addresses in the FullName field of the Person document associated with the user being moved will be copied to Active Directory.
Generally, old names and addresses are in the FullName field, so this would not be a problem — but there may be cases when the names and addresses are not. To resolve this issue, simply create a new address on the Active Directory user or contact object.