Help documentation for BizTalk Server 2013
Installation guides
General guides
Download BizTalk Server 2013 Evaluation Edition
SharePoint User Profile and Generic LDAP Connectors (Release Candidate) are available on Connect for download.
This Release Candidate includes two new Connectors for FIM Synchronization Service.
- SharePoint User Profile Connector
- Generic LDAP Connector for Open LDAP
The download also contains a new build for FIM Synchronization Service required for these two Connectors to operate correctly.
If you are subscribed to FIM 2010 on Microsoft Connect you can download the connectors at the following link: SharePoint User Profile and Generic LDAP Connectors Release Candidate
A hotfix rollup package (build 4.1.3419.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2.
Download kb2814853
The last month, SP1 of FIM 2010 R2 was released but available for download only on MSDN.
From the last week, the SP is officially released and now available for download here.
For more information: Announcing Forefront Identity Manager 2010 R2 Service Pack 1
What's New in Forefront Identity Manager 2010 R2 SP1
Microsoft BHOLD Suite Service Pack 1 (SP1) contains significant improvements and additions to the previous version of BHOLD Suite. For this reason, it is not possible to upgrade an existing BHOLD Suite installation to BHOLD Suite SP1. If you have already installed BHOLD Suite, you must uninstall all BHOLD Suite components before you can install BHOLD Suite SP1. You can retain and upgrade your existing BHOLD database, however, so you do not have to recreate your role model after you install BHOLD Suite SP1.
Replacing BHOLD Suite with BHOLD Suite SP1
| Category | Deprecated Feature | Replacement and Comment |
| Programmatic Configuration | Web Service configuration interface | The ability to configure the FIM synchronization service through the FIM service web service by changing MAdata and MVdata will be removed in a next version. The functionality of this feature will be provided by new PowerShell cmdlets. |
| Management Agents | Built-in MAs | The following MAs will be removed in next version: - MA for FIM Certificate Management
- MA for Lotus Notes
- MA for SAP R/3
The Lotus Notes and SAP R/3 MAs have been replaced with new versions. For more details, see Management Agents in FIM 2010 R2 |
| Management Agents | ECMA1 | The ECMA1/XMA extensibility framework has been replaced by the ECMA 2.0. You should plan on replacing existing ECMA1 management agents with ECMA2.0 connectors. |
| Management Agents | Running Connectors out-of-proc | This feature will not be replaced. The synchronization service will always call the connector in the same process. If the connector has a dependency on a 32-bit library or must for some other reason run out-of-proc, it is the responsibility of the connector to start and manage the other process. |
| Management Agents | Configure partition display name | This feature will not be replaced. This option was only used to provide an alternative name for a partition in the WMI interfaces. |
| Run profiles | Combined profiles | The combined profiles delta import/sync, full import/delta sync, and full import/sync will be removed. You should use run profiles with two steps instead. |  Note
| | You should keep combined run profiles only in environments where the performance would be impacted by a very large number of existing disconnectors. | |
| Attribute Precedence | Multi-mastery/equal precedence | Equal precedence will be removed. There is no replacement for this feature. You should configure manual precedence instead. You can continue to use this feature if your environment has a FIM Service management agent deployed (this management agent does not provide manual precedence) and to avoid export-not-precedent for declarative provisioning. |
| Join Rules | Join on “Any” object type | This feature will not be replaced. All join rules should explicitly define the metaverse object type they are trying to join to. |
| Attribute flows | Unselect “allow nulls” for exported values | This feature will not be replaced. “Allow Nulls” will always be selected. You should make sure that you have “Allow Nulls” selected in your current environment. |
| Attribute flows | “Do not recall attributes” | This feature will not be replaced. Attributes will always be recalled, which is the best practice. You should make sure that you don’t have dependencies on attributes that ought to be not recalled. |
| Rules Extension | Running metaverse and ma rules extension out-of-proc | This feature will not be replaced. The metaverse and attribute flow rules will run in the same process as the synchronization engine. |
| Rules Extension | Transaction properties | This feature will not be replaced. You should avoid passing data between inbound, provisioning, and outbound synchronization using this utility class. |
| Rules Extension | ExchangeUtils:Create55* methods | The methods to create objects for Exchange 5.5 servers will be removed. |
| Interface | Mms_Metaverse | All ClmUtils class members will be removed in a next version. |
Link to the Original article
SP1 of FIM 2010 R2 has been released and is available for download on MSDN only.
- Forefront Identity Manager 2010 R2 with SP1 (x86 and x64) - DVD (Multiple Languages) – full installation including SP
- Forefront Identity Manager 2010 R2 SP1 (x86 and x64) - DVD (Multiple Languages) – SP only
- BHOLD Suite with SP1 (x86 and x64) - DVD (English, Dutch, German)
Hotfix rollup package (build 4.1.2548.0) is available for Forefront Identity Manager 2010 R2
Download from here (KB2750671)
Using WMI with FIM Synchronization Service is very useful and I want to show some examples to HOW and WHY..
1: using System.Management;
Example 1 – Check Management Agent is running
This example is useful at the Provisioning step using .NET (MVExtension.dll) so you could control when exactly to provision the object in the target MA by the current running Management Agent.
1: public static bool IsMamagementAgentRunning(string MAName)
2: {
3: try
4: {
5: ConnectionOptions opt = new ConnectionOptions();
6: opt.Authentication = AuthenticationLevel.PacketPrivacy;
7:
8: ManagementScope myScope = new ManagementScope("root\\MicrosoftIdentityIntegrationServer", opt);
9: SelectQuery myQuery = new SelectQuery("MIIS_ManagementAgent", "Name='" + MAName + "'");
10: ManagementObjectSearcher searcher = new ManagementObjectSearcher(myScope, myQuery);
11: foreach (ManagementObject ma in searcher.Get())
12: {
13: if (String.Compare((String)ma.InvokeMethod("RunStatus", null), "in-progress", true,
14: System.Globalization.CultureInfo.InvariantCulture) == 0)
15: {
16: return true;
17: }
18: }
19: }
20: catch (Exception ex)
21: {
22: Console.WriteLine("Error: " + ex.Message);
23: }
24: return false;
25: }
Example 2 – Check if the Management Agent successfully terminated
The following code shows how you could track FIM Synchronization Service success status – in the same way you can track any other existing status (click here to retrieve the list of statuses). In this example I decide to configure completed-sync-errors status as a success status also.
1: public static bool IsMamagementAgentStatusSuccess(string MAName)
2: {
3: try
4: {
5: ConnectionOptions opt = new ConnectionOptions();
6: opt.Authentication = AuthenticationLevel.PacketPrivacy;
7:
8: ManagementScope myScope = new ManagementScope("root\\MicrosoftIdentityIntegrationServer", opt);
9: SelectQuery myQuery = new SelectQuery("MIIS_ManagementAgent", "Name='" + MAName + "'");
10: ManagementObjectSearcher searcher = new ManagementObjectSearcher(myScope, myQuery);
11: foreach (ManagementObject ma in searcher.Get())
12: {
13: if (String.Compare((String)ma.InvokeMethod("RunStatus", null), "success", true,
14: System.Globalization.CultureInfo.InvariantCulture) == 0)
15: {
16: return true;
17: }
18: else if (String.Compare((String)ma.InvokeMethod("RunStatus", null), "completed-sync-errors", true,
19: System.Globalization.CultureInfo.InvariantCulture) == 0)
20: {
21: return true;
22: }
23: }
24: }
25: catch (Exception ex)
26: {
27: Console.WriteLine("Error: " + ex.Message);
28: }
29: return false;
30: }
Example 3 – Clearing the Run History Log
It is very important to clear the Run History log on a regular basis. leaving the history without any maintenance will cause FIMSynchronizationService database to grow to a very high dimension. So, if your FIM Sync database is too big try to clear the history log – that will make the difference…
1: public static void ClearRunHistory(int DaysBackToClear)
2: {
3: try
4: {
5: ConnectionOptions opt = new ConnectionOptions();
6: opt.Authentication = AuthenticationLevel.PacketPrivacy;
7:
8: ManagementScope myScope = new ManagementScope("root\\MicrosoftIdentityIntegrationServer", opt);
9: SelectQuery myQuery = new SelectQuery("MIIS_Server");
10: ManagementObjectSearcher searcher = new ManagementObjectSearcher(myScope, myQuery);
11: DateTime dDate = DateTime.Now.AddDays(-DaysBackToClear);
12: string sDate = dDate.ToString("yyyy-MM-dd");
13: foreach (ManagementObject server in searcher.Get())
14: {
15: server.InvokeMethod("ClearRuns", new object[1] { sDate });
16: }
17: }
18: catch (Exception ex)
19: {
20: Console.WriteLine("Error: " + ex.Message);
21: }
22: }
Using WMI on a remote server require to enter credentials:
1: opt.Username = "domain\\username";
2: opt.Password = "password";
3: ManagementScope myScope = new ManagementScope("\\\\SERVER_NAME\\root\\MicrosoftIdentityIntegrationServer", opt);
Can be applied on all versions:
- Microsoft Integration Server 2003
- Identity Lifecycle Manager 2007
- Forefront Identity Manager 2010
- Forefront Identity Manager 2010 R2
Reference: WMI Provider Return Strings
THIS POSTING IS PROVIDED "AS IS" WITH NO WARRANTIES
A hotfix rollup (build 5.0.520.0) is available for Forefront Identity Manager 2010 Lotus Domino Connector
http://support.microsoft.com/kb/2741896
WMI Code Creator 1.0 is available for download.
The WMI Code Creator tool allows you to generate VBScript, C#, and VB .NET code that uses WMI to complete a management task such as querying for management data, executing a method from a WMI class, or receiving event notifications using WMI.
In relation of MIIS\ILM\FIM, you can simply involve connection to WMI via .NET using WMI Code creator: WMI Provider Overview MIIS\ILM\FIM Class – refer to the following link.
More Posts
Next page »