Deprecated Features And Planning For The Future
This topic describes the deprecated features of the FIM synchronization service that are still available in FIM 2010 R2. These features are scheduled to be removed in a future release of FIM. You should not use deprecated features in new applications.
| 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:
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. |