]]>http://blogs.microsoft.co.il/patrick/2013/02/03/fim-2010-r2-sp1/feed/0FIM 2010 R2 SP1 – BHOLD Suite SP1http://blogs.microsoft.co.il/patrick/2013/01/23/fim-2010-r2-sp1-bhold-suite-sp1/
http://blogs.microsoft.co.il/patrick/2013/01/23/fim-2010-r2-sp1-bhold-suite-sp1/#commentsWed, 23 Jan 2013 02:54:44 +0000http://blogs.microsoft.co.il/?p=1691407Microsoft 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.

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.

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.