You go to create a new synchronization rule.  You reach the Scope tab.  You notice that all the drop-down boxes contain no data.  Another possibility is that you can see some data, but do not see a new management agent that you created in the Synchronization Service Manager. 


This problem is caused because the Forefront Identity Manager (FIM) Synchronization Service cannot communicate with the FIM Service.  In most cases, this problem is most likely caused by the different pieces of the Forefront Identity Manager (FIM) product being at different builds.  As an example, if you have the FIM Portal and FIM Service at build 4.00.3576.2 and the FIM Synchronization Service at 4.00.2592.2 then you will experience this issue.


The issue is easily resolved by bringing all the pieces of FIM to the same build.

If the above resolution item does not resolve the issue for you, here are a few other items that you can do to see if the issue is resolved.

1. Refresh the schema of the FIM Service Management Agent
2. Validate that the account used in the FIM Service Management Agent is the same as the one specified in the registry that was setup during installation.

On the FIM Service Machine, open the Windows Registry
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMService
Review the SynchronizationAccount string property


1. Updated all of FIM from 4.0.3558.2 to 4.0.3576.2
2. Restarted both the FIM Service and FIM Synchronization Service
3. Refreshed the Schema to the FIM Service Management Agent
4. Validated the requests by Searching the Requests
5. Tested the creation of the synchronization rule