However, if you use the forcepwchg utility, you can identify aected 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 conguration le
from your Identity Synchronization for Windows 1.1 conguration. For more information ,
see
“Exporting Version 1.1 Conguration” on page 107.
The exported XML document contains the directory deployment topology and enough
information to congure 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 nd the migration utilities in the installation migration directory. No additional
installation steps are required.
Exporting Version 1.1 Conguration
You can use the export11cnf utility to export an existing version 1.1 conguration le to an
XML le and then use the idsync importcnf command to import the le into the 6.0 system
before installing the connectors.
PreparingforIdentity SynchronizationforWindowsMigration
Chapter7 • Migrating IdentitySynchronizationforWindows 107
SunCondential:Registered