Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Upgrade and Migration Guide 11 g Release 1 (11.1.1.5.0) |
Part I Patching Directory Server Enterprise Edition 7 to 11g Release 1 (11.1.1.5.0)
2. Patching Directory Server Enterprise Edition 7 to Version 11g Release 1 (11.1.1.5.0)
Part II Upgrading Directory Server Enterprise Edition 6 to 11g Release 1 (11.1.1.5.0)
3. Upgrading Directory Server Enterprise Edition 6 to Version 11g Release 1 (11.1.1.5.0)
Part III Migrating Directory Server Enterprise Edition 5.2 to Version 11g Release 1 (11.1.1.5.0)
4. Overview of the Migration Process for Directory Server
5. Automated Migration Using the dsmig Command
6. Migrating Directory Server Manually
7. Migrating a Replicated Topology
8. Architectural Changes in Directory Server Since Version 5.2
9. Migrating Directory Proxy Server
10. Migrating Identity Synchronization for Windows
Before You Migrate Identity Synchronization for Windows
Preparing for Identity Synchronization for Windows Migration
Exporting Version 1.1 Configuration
Inserting Clear-Text Passwords
Sample Export Configuration File
Checking for Undelivered Messages
Forcing Password Changes on Windows NT
Preparing to migrate from version 1.1, and 1.1 SP1, to version 6.0 SP1
Uninstalling Identity Synchronization for Windows
To Uninstall Identity Synchronization for Windows Version 1.1
Installing or Upgrading the Dependent Products
Installing Identity Synchronization for Windows 6.0 SP1
To install the Identity Synchronization for Windows 6.0 SP1 components:
What to Do if the 1.1 Uninstallation Fails
Manually Uninstalling 1.1 Core and Instances from Solaris
To Manually Uninstall Core From a Solaris Machine:
Manually Uninstalling 1.1 Core and Instances from Windows 2000
To uninstall Core from a Windows 2000 machine:
Manually Uninstalling a 1.1 Instance from Windows NT
Multi-Master Replication Deployment
After migration, check the central audit log for messages indicating a problem. In particular, check for Directory Server users whose password changes may have been missed during the migration process. Such errors would be similar to the following:
[16/Apr/2004:14:23:41.029 -0500] WARNING 14 CNN101 ds-connector-host.example.com "Unable to obtain password of user cn=JohnSmith,ou=people,dc=example,dc=com, because the password was encoded by a previous installation of Identity Synchronization for Windows Directory Server Plugin. The password of this user cannot be synchronized at this time. Update the password of this user again in the Directory Server."
You will not see this log message until after you start synchronization in Identity Synchronization for Windows 6.0 SP1. This is why checking the logs is the last step of the migration procedure.