Wednesday June 6th saw Microsoft release a new hotfix rollup package (build 4.1.3559.0) for Forefront Identity Manager (FIM) 2010 R2. The official documentation for this build can be found on the Microsoft support website under knowledgebase (KB) article 2969673. Download link is here. This build supersedes 4.1.3510.0.
The hotfix contains one (1) update for the client add-ins; one (1) update for FIM CM; and one (1) new feature for FIM Synchronization Service.
Full details of the update, duplicated from the KB for posterity, follow. Hit the KB for the known issues and other details.
FIM add-ins and extensions
After the FIM Password Reset add-in is installed in Windows 7, the “Create a Password Reset Disk” feature is available when you press Ctrl+Alt+Del and then you click Change a Password.
FIM Certificate Management
When you try to remove a certification authority (CA) that is bound to Certificate Management (CM) by using the CLMutil -removeca command, you experience the following symptoms:
- Actions such as enroll, renew or revoke that are performed on certificates that are bound to the removed CA cause an exception to be returned.
- When you try to edit or remove a certificate template that was related to the removed CA, an exception is displayed on the CM portal.
Note. These same symptoms occur when the CA is stopped or unavailable.
Changes to the symptoms after you apply this update
- Actions such as enroll, renew or revoke that are performed on certificates that are bound to the removed CA cause a well-defined error message to be displayed.
- Removing a certificate template is possible. Removing the template for any removed CA is also possible.
- Changing a certificate template that is related to the removed CA causes a well-defined error message to be displayed.
Changes to the clmutil.exe tool after you apply this update
The following commands are added:
- Syntax: [-force] -decomissionca CA_ID
- Example 1: clmutil -force -decommissionca 1
- Example 2: clmutil -decommissionca 1
Note. You may receive the following warning message when you run the clmutil command:
There are outstanding certificates for CA 1, cannot decommission. Please use -force flag if you still want to decommission CA
- Syntax: -recommissionca CA_ID
- Example: clmutil -recommissionca 1
Note. CA_ID can be obtained by using the following command:
Changes in the Web Portal user interface after you apply this update
When you change a profile template that references a certificate template that was originally hosted by a CA and that is marked as decommissioned, the following conditions are true:
- The CA is unavailable in the Add Certificate Template dialog box.
- Users who enroll in the profile template receive the following warning message that is displayed at the top of the enrollment screen:
The Certification Authority CA2.proseware.com\FIM CM CA cannot be contacted as it is marked as decommissioned.
Note. If the profile template includes certificate templates from a disabled or re-enabled CA, users will be unable to enroll in that profile template. This causes this same warning message to be displayed.
- In the profile template properties, clicking a certificate template that was originally associated with a now-decommissioned CA displays all registered CAs that expose this certificate template. This lets the administrator select the appropriate CA.
Note. If no registered CAs expose the certificate template, the list of CAs on the screen is blank.
FIM Synchronization Service
This update includes ECMA 2.3. In this version, it is now possible to add custom schema pages that will be listed in the Synchronization Service Manager user interface. An example of how this feature is used can be seen in the Generic SQL connector.
Please be aware that the Microsoft.MetadirectoryServicesEx.dll is updated in this update. See the “Known issues in this update” section for information about how to update the configuration files to reflect this change.
Known issues chopped from the KB as the above references it…
Known issues in this update
After this update is installed, rules extensions and custom management agents (MAs) that are based on Extensible MA (ECMA1 or ECMA 2.0) may not run and may produce a run status of “stopped-extension-dll-load.” This issue occurs when you run such rules extensions or custom MAs after you change the configuration file (.config) for one of the following processes:
For example, you changed the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service MA.
In this case, the synchronization engine installer for this update intentionally does not replace the configuration file. This avoids deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update do not exist in the files. Therefore, the synchronization engine does not load any rules extension DLLs when the engine runs a Full Import or Delta Sync run profile.
To resolve this issue, follow these steps:
- Back up the MIIServer.exe.config file.
- Open the MIIServer.exe.config file in a text editor or in Microsoft Visual Studio.
- Find the <runtime> section in the MIIServer.exe.config file, and then replace the content of the <dependentAssembly> section with the following:
<assemblyIdentity name=”Microsoft.MetadirectoryServicesEx” publicKeyToken=”31bf3856ad364e35″ />
<bindingRedirect oldVersion=”220.127.116.11-18.104.22.168″ newVersion=”22.214.171.124″ />
- Save the changes to the file.
- Find the Mmsscrpt.exe.config file in the same directory and the Dllhost.exe.config in the parent directory. Repeat steps 1 through 4 for these files.
- Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
- Verify that the rules extensions and custom management agents now work as expected.