This chapter provides an overview of the updates made to the software and documentation for the Microsoft Exchange connector in release 9.0.4.17.
See Also:
The earlier release of this guide for information about updates that were new in that release
The updates discussed in this chapter are divided into the following categories:
This section describes updates made to the connector software.
Documentation-Specific Updates
This section describes major changes made to this guide. These changes are not related to software updates.
The following sections discuss software updates:
The following are issues resolved in release 9.0.4.1.1:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6891695 |
The status of an Exchange resource stays at |
This issue has been resolved. When you delete an OIM User, the status of that user's Exchange resource changes to |
The following are issues resolved in release 9.0.4.2:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6877390 |
If you delete a mailbox by using the Microsoft Active Directory console, then the Microsoft Exchange attributes of the user are also deleted. However, if you performed a Delete Mailbox provisioning operation from Oracle Identity Manager, then the Exchange attributes of the user were not deleted. |
This issue has been resolved. When you perform a Delete Mailbox provisioning operation, the Microsoft Exchange attributes of the user are also deleted. |
There are no software updates in release 9.0.4.3.
The following are issues resolved in release 9.0.4.4:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6998281 |
During a Delete Mailbox provisioning operation, the |
The issue has been resolved. The |
The following are issues resolved in release 9.0.4.5:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7014860 |
If you provisioned an Exchange mailbox to an OIM User, then some attribute values of that user's Active Directory account were overwritten with incorrect values. |
This issue is now resolved. When you provision an Exchange mailbox to an OIM User, attribute values of that user's Active Directory account are not overwritten. |
The following are issues resolved in release 9.0.4.6:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6839860 |
A reconciliation run failed if you did not specify |
To resolve this issue, the |
The following are issues resolved in release 9.0.4.7:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7026049 |
A Delete Mailbox operation failed if the mailbox was provisioned without specifying values for the optional attributes. As the outcome of the Delete Mailbox operation, the Rejected status was displayed for the Delete Mailbox operation on the Resource Provisioning Details page of the Administrative and User Console. In addition, the "AD User Deletion Failed: Problem modifying object" error message was written to the log file. |
This issue has been resolved. You can now delete a mailbox even if the mailbox was created without specifying values for the optional attributes. |
The following are issues resolved in release 9.0.4.8:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6771509 and 6776924 |
Values specified for the Server Name and Store Name parameters of the IT resource were not considered during a reconciliation run. In other words, all newly created and modified mailboxes were fetched during each reconciliation run. In addition, you could not specify that you wanted to reconcile mailboxes from a specific server or store group. |
These issues have been resolved. In addition, the Store Group Name parameter has been added to the IT resource. By providing values for the Server Name, Store Group Name, and Store Name IT resource parameters, you can specify the mail stores from which mailboxes must be fetched for reconciliation. See the "Importing the Connector XML Files" section for information about using this feature. In addition, the mail store that you specify in the IT resource is displayed on the process form. |
There are no software updates in release 9.0.4.9.
There are no software updates in release 9.0.4.10.
The following are issues resolved in release 9.0.4.10.1:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7045721 |
Suppose you provision a Microsoft Exchange mailbox to an OIM User and then revoke the mailbox resource. For the same user, you again provision and revoke a mailbox. Up to this point, the connector worked as expected. If you provisioned a mailbox to the same user a third time, then the mailbox provisioned the second time is reactivated. The expected behavior was that a new mailbox should be provisioned to the user. |
This issue has been resolved. Each time you revoke an existing mailbox and then provision a mailbox, a new mailbox is created for the user. Mailboxes that have been revoked are not reused. |
There are no software updates in release 9.0.4.11.
Arabic and Danish have been added to the list of supported languages.
The following are issues resolved in release 9.0.4.13:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7298922 |
Reconciliation of deleted mailboxes was not supported. |
This issue has been resolved. If a deleted mailbox is detected during reconciliation, then the Microsoft Exchange resource is revoked from the corresponding OIM User. See "Scheduled Task for Reconciliation of Deleted Mailboxes" in the connector guide for more information about the scheduled task for reconciling deleted mailboxes. To track the time stamp at which this reconciliation run ends, the |
There are no software updates in release 9.0.4.14.
There are no software updates in release 9.0.4.15.
The following are issues resolved in release 9.0.4.16:
| Bug Number | Issue | Resolution |
|---|---|---|
|
8237825 |
The following is the format of the time-stamp filter applied to each target system record during reconciliation: timestamp_record_updated >= last_reconciliation_run_timestamp When this filter was applied, a record that was added or modified at the instant the reconciliation run ended was also reconciled. However, the application of the time-stamp filter caused the same record to be reconciled during the next reconciliation run. |
This issue has been resolved. The time-stamp filter cannot be changed to the following: timestamp_record_updated > last_reconciliation_run_timestamp As a workaround, one second is added to the time stamp recorded in the IT resource before the filter is applied during a reconciliation run. In other words, the filter is changed to the following: timestamp_record_updated + 1 second >= last_reconciliation_run_timestamp Application of this filter ensures that a record reconciled at the end of a reconciliation run is not reconciled during the next reconciliation run. |
There are no software updates in release 9.0.4.17.
The following are documentation-specific updates in revision "11" of release 9.0.4.17:
Section 2.1, "Verifying Deployment Requirements" has been removed and all the contents of this section have been moved to Section 1.1, "Certified Components" in order to make it consistent with other connector guides.
The "Usage Recommendation" section has been added.
The following are documentation-specific updates in earlier revisions of release 9.0.4.17 :
Microsoft Windows 2000 Server is no longer a supported host for the target system. All occurrences of "Microsoft Windows 2000 Server" have been removed from this guide.
In the "Verifying Deployment Requirements" section, changes have been made in the "Target systems" row.
From this release onward:
The minimum certified release of Oracle Identity Manager is release 9.1.0.1.
The minimum certified release of JDK is release 1.4.2.
See "Verifying Deployment Requirements" section for the complete listing of certified components.