Sun Microsystems Sun Java System Directory Server Enterprise Edition 6.0, Migration Giude

Page: 107 / 148

However, if you use the
forcepwchg
utility, you can identify affected users and force them to
change passwords again. For more information, see “Forcing Password Changes on
Windows NT” on page 116 .
■
All other attribute changes made during the migration process (at any directory source) will
be synchronized after the migration process.
Preparing for Identity Synchronization for Windows
Migration
Use one or more of the following utilities to migrate from version 1.1 to version 6.0:
■
export11cnf. A stand-alone utility that enables you to create an export configuration file
from your Identity Synchronization for Windows 1.1 configuration. For more information ,
see
“Exporting Version 1.1 Configuration” on page 107 .
The exported XML document contains the directory deployment topology and enough
information to configure the Identity Synchronization for Windows 6.0 installation.
■
checktopics. A utility that checks Message Queue synchronization topics in a 1.1
installation and determines if any undelivered messages remain in the queue.
Updates can remain in Message Queue after you stop 1.1 synchronization. You must verify
that no updates exist in the Message Queue before you proceed with the migration. For
more information, see
“Checking for Undelivered Messages” on page 114 .
■
forcepwchg. A Windows NT tool that enables you to identify users who changed passwords
during the migration process and forces them to change passwords again when the version
6.0 system is ready. Password changes made on Windows NT are not captured during the
migration process. For more information, see
“Forcing Password Changes on Windows
NT” on page 116 for detailed information.
Note –
These utilities facilitate the migration of Identity Synchronization for Windows version
1.1 to version 6.0. The migration is performed in the same environment where Identity
Synchronization for Windows 1.1 is deployed. Consequently, these utilities are available in the
Solaris/SPARC and Windows packages only.
You can find the migration utilities in the installation
migration
directory. No additional
installation steps are required.
Exporting Version 1.1 Configuration
You can use the
export11cnf
utility to export an existing version 1.1 configuration file to an
XML file and then use the
idsync importcnf
command to import the file into the 6.0 system
before installing the connectors.
Preparing for Identity Synchronization for Windows Migration
Chapter 7 • Migrating Identity Synchronization for Windows 107
Sun Confidential: Registered