I've tried to migrate schema and policy from one environment to another. Everything went fine, but then I've found that if I try to create new synchronization rule I get an error message "There's an error in the SynchronizationRule display configuration. Please contact your system administrator." The similar problem is also with person display configuration. I've checked those RCDC xml files multiple times and they look OK to me. I've also tried to replace them with the default xml files but it doesn't work. What is more confusing is that RCDC for person is working correctly when I click on view button or somewhere on the reference pointing to that user. So using url like .../identitymanagement/aspx/Users/EditPerson.aspx?id=xxxx gives me the error but using url .../IdentityManagement/aspx/customized/PopupCustomizedObject.aspx?type=Person&id=xxx works fine. (I've got one RCDC for person which applies to edit and also view). I'm 100% sure that these xml files are correct. There is also nothing suspicious in event log. Any ideas how to solve this or at least how can I debug this. thanks.

Can you check if you have multiple Sync Rule Designer RCDCs? Can you post here the object identifiers (GUID) and the modes (Create/Edit/View) that these Sync Rule Designer RCDCs apply to, in your system? thanks

Hi, Can you check if the RCDCs in both source and target environment are the same? The portal relies on RCDCs that have fixed object identifiers. It could be the case that the config migration tool has deleted and recreated the Sync Rule RCDC if they failed to join up (say if you changed the display name). See the following thread: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/7afb0870-4d01-4b07-8a5f-501ce196bdfb/#7359ffc2-e573-477c-bc1b-32b08156c9e0 Billy

Thanks a lot. It seems like the GUID issue you posted above. I've also found in request history that the migration process replaced these xml configurations, although I haven't changed the displayname. Anyway this seems like a very nasty bug and I hope it will be fixed soon. And this is another reason why I'm not trying to use migration tools at the production environment. For me it's still a little clumsy.