A mechanism to notify and validate pending exports in FIM and AAD Sync. There is no native method to do this in the FIM Sync / AAD Sync software.Additional components in FIM like FIM Service and FIM Reporting are not always the best tools for day-to-day operational validation and notifications.Included is a sample script and sample csexport output xml file that can be run on any PC with Power Shell to get an idea of possible output that can be customized in your own environment.The example script is commented out so you can run it and get results from the sample xml file.Save the script and the xml file in c:temp and execute the script to see the output. Food Topics ADMA-2015-11-05-20-22-18Sample FIMValidation.ps1 The Fun Part – Getting Started If you want to use this script in your environment, beyond the sample provided, you’ll need to customize this to run in your FIM …Bin directory and include the name of your desired MA.
In this example, the customer wanted to pause the automated sync cycle if more than 30 of any of the following were pending export: What?
For example, outbound scoping filter rules are processed in FIM Sync, even though their configuration is written in FIM Service. Using the csexport tool and Power Shell to analyze pending exports.
CSExport is a MS provided tool in FIM Sync and AAD Sync that allows the export of connector space object data. In Part 1 we’ll explore the basics of how to get started with this method.
the option: /f:x instructs csexport to only include pending exports.
There are many good mechanisms available to notify, report and authenticate/approve changes made by FIM before they are synchronized (FIM Service, for example.) However, there is no mechanism for doing this in FIM Synchronization natively.
Many options discussed online are from the perspective of a ‘classic’ MIIS designer, often contained with compiled DLLs.