Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following sections explain how to use Forefront Identity Manager Synchronization Service (FIM Synchronization Service) rules extensions.
| Section | Description |
|---|---|
Describes the example infrastructure that is used as the basis for the examples in this section. |
|
Shows how to create and test management agent and metaverse rules extensions. |
|
Shows how to use rules extensions to transform data between the connector space and metaverse. |
|
Shows how to use a rules extension to create unique attribute values. |
|
Shows how to use a rules extension to provision connector space objects for different connected directories |
|
Shows how to use a rules extension to deprovision connector space objects because of a metaverse object change or deletion. |
|
Shows how to use a rules extension when the Synchronization Service Manager is configured for manual precedence. |
|
Shows how to use a rules extension to move connector space objects to another container because of a metaverse change or deletion. |
|
Shows how to use a rules extension to set an initial password when you create new accounts. |
|
Provides other rules extension examples. |
|
Working with Rules Extensions Created in Earlier Versions of Visual Studio |
Shows how to run existing rules extensions that you created using earlier versions of Visual Studio on Microsoft Identity Integration Server 2003 SP2 (ILM 2007) without recompiling your projects. |
Warning
Rules extensions are run in the FIM Synchronization Service Engine's process, which is a 64-bit process. 32-bit only rules extensions are not supported in FIM. Rules extensions must be compiled to run in a 64-bit process.
See Also
Concepts
Using Forefront Identity Manager Synchronization Service
Compiling Rules and Data Source Extensions