I'm failing to create new Sets here. There error is: Forefront Identity Management Service is not able to serialize this XOML definition '<ns0:SequentialWorkflow x:Name="SequentialWorkflow" ActorId="00000000-0000-0000-0000-000000000000" WorkflowDefinitionId="00000000-0000-0000-0000-000000000000" RequestId="00000000-0000-0000-0000-000000000000" TargetId="00000000-0000-0000-0000-000000000000" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:ns0="clr-namespace:Microsoft.ResourceManagement.Workflow.Activities;Assembly=Microsoft.ResourceManagement, Version=4.0.2587.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"> <ns0:FilterValidationActivity FilterScopeIdentifier="06185a61-75a1-401e-a698-498351b9f9b5" x:Name="FilterValidationActivity1" /> </ns0:SequentialWorkflow>'. It's a new installation of RTM to which I've imported the schema and policy from an RC3 installation. The policy import did not complete, and I think part of the reason is that certain dependant sets were missing. However I can't create them because of this error. As far as I can tell from the MPRs I have the right to create sets. http://www.wapshere.com/missmiis

Follow-up: I actually couldn't create anything - users, groups etc. I have reinstalled and this time only imported the schema. I can now create a set. It seems that the policy import messed something up. I don't dare to do it again so I'll have to recofigure everything by hand. <sigh> http://www.wapshere.com/missmiis

hm... i don't think u can import/export with different ersion if you have a new installation of FIM RTM (not patched from previous version), then the version number should be 4.0.2592.0 fix that through AdvanceView should fix that issueThe FIM Password Reset Blog http://blogs.technet.com/aho/

So should I have installed RC3 on the new server, transferred the config, and then upgraded in place?http://www.wapshere.com/missmiis

Hi Carol, It imperative that you don't go across builds when using config migration. For example, you must not migrate the configuration from RC1 Update 3 to RTM. You need to ensure that both environments are of the same build. I believe this is documented in the config migration guide. In addition, if you're migrating an upgraded FIM instance to a clean FIM instance, you need to replace the version number in the workflow XOML with the number from the clean FIM instance. Let me know if you're still having difficulties migrating configuration.

Hi Billy. Actually I'd given up migrating in favour of rebuilding - however I did migrate the schema. There were only a small number of changes (some extra attributes, that sort of thing). Is that likely to cause problems?http://www.wapshere.com/missmiis

Hi Carol, You should avoid migrating schema across two different builds. For example, between RC1 Update 2 and Update 3, we introduced new attributes to the schema in Update 3. If we migrate schema between Update 2 and 3, the migration tool will attempt to delete the new schema introduced in Update 3 since your configuration from Update 2 is authoratative over the Update 3 configuration. However, if you're migrating schema between the same build, the go ahead. It should work normally. Billy

Hi Carol, the problem is the "Version=4.0.2587.0" bit in the XOML definition you were trying to import. That error you got is a .NET serialization error message, and not a FIM permission issue. Most likely this happened because you created the workflow on a machine with a previous (non-RTM) installation, where version 4.0.2587.0 of the assembly Microsoft.ResourceManagement was installed; then, even if you apply an update, the assembly reference in the XOML is not updated automatically. When you import the configuration on an RTM installation, where the version of the Microsoft.ResourceManagement assembly is 4.0.2592.0, the deserialization fails as it cannot find the assembly (which is strange, since the FIM service configuration file should be configured to redirect bindings to previous assembly versions to the latest). I had the same problem (even if migrating across two RTM configurations) and solved this issue by replacing 4.0.2587.0 (and other previous versions as well) with 4.0.2592.0 in the xml file with the pilot installation policy configuration. I'm afraid it's too late, but just in case it happens again... Cheers, Paolo P.S: I was sure that this was mentioned in the official documentation, and now I've found it: check the FIM 2010 Release Notes , under "Migrating configurations from an environment with upgrades to a clean install of RTM requires updating version numbers". Paolo Tedesco - http://cern.ch/idm

The document I was following was this one where it is not specifically mentioned you can't migrate cross-version: http://technet.microsoft.com/en-us/library/ee534906(WS.10).aspx But it's not a big deal - I don't imagine there are that many people trying to transfer configurations from RC3. The RTM lab I have running now seems to be working properly, despite my importing that schema. Hey Paolo, are you in GVA? If you're coming to Techdays next week do say hello. I'm presenting FIM on thursday. Carolhttp://www.wapshere.com/missmiis

Hi Carol, the schema objects (AttributeTypeDescription, BindingDescription and ObjectTypeDescription) should be immune from this problem as they contain no assembly-dependent XOML definitions. And yes, I'm in Geneva :) I'd really like to hear your presentation, but I'm not coming to techdays. I hope we shall have another occasion to meet, though. Cheers, Paolo Paolo Tedesco - http://cern.ch/idm