FIM 2010 R2 Hotfix Build (4.1.3469.0) released


On Oct. 6 2013 Microsoft released a new Hotfix for FIM 2010 R2, which is Built 4.1.3469.0.
You can find the documentation and download link in KB2877254.

IssueList taken from the original KB Article:

Issues that are fixed or features that are added in this update

This update fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.

FIM Service

Issue 1

In some rare scenarios in which the Exchange server FIM Service tries to poll approval response email messages, an “ErrorInternalServerTransientError” error is returned. In these scenarios, the FIM Service throws an exception.

After you apply this update, you can configure a retry by setting the following values in the configuration file:

mailServerSendOperationMaximumRetryCount=”3″

mailServerSendOperationRetryIntervalInMilliseconds=”1000″

FIM Synchronization Service

Issue 1

An Active Directory Management Agent runs an export run profile that is configured to also log an audit file. When there are child objects such as Active Sync devices on the user, the export fails.

Issue 2

When an ECMA2 Connector runs an export run profile that is configured to also log an audit file, no objects are exported.

Issue 3

FIM synchronization cannot deprovision computer objects in Active Directory when there are other child objects, such as printers and file share objects, present on the computer object.

Issue 4

In ECMA2, when the NoAddAndDeleteConfirmation capability is set and an exception is thrown during object export, the exception is processed incorrectly. Additionally, failed objects are marked incorrectly as successful.

Issue 5

When an additional object type is added to an already configured ECMA2 Connector, an “Object Reference Not Set” exception is thrown.

Issue 6

When you try to stop a running ECMA2 Connector from the user interface (UI), the Sync Engine may crash.

Issue 7

A Delete-Add that is sent as a Replace in ECMA2 requires the anchor to be returned from the Connector. This causes issues with the Windows Azure Active Directory Connector when the object is deleted and reprovisioned.

Issue 8

When you use an attribute Replace during export to remove the last value from a multivalued attribute, an attribute Replace without values is sent to the Connector. This causes a “The server encountered an unexpected error in the synchronization engine” error to be thrown when the Windows Azure Active Directory Connector is used. After you apply this update, the new behavior is to send this as an attribute Delete to the Connector.

Issue 9

When the Set-MIISADMAConfiguration cmdlet is used in a multidomain environment, a corrupted configuration may occur.

Issue 10

In build 4.1.3461.0, a regression occurs that causes import-only attribute flows not to be honored by the UI.

Advertisements

About Peter Stapf
Senior Consultant Identity and Access MVP (Enterprise Mobility)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s