Don’t use the FIM configuration migration scripts between versions

I’ve just been installing FIM R2 RC into my lab. Unfortunately I couldn’t get the portal to upgrade from R2 beta to R2 RC (and to be fair the doco doesn’t say you should be able to) so had the bright idea of using the migration scripts to do a config comparison between my beta and RC environments, and hopefully update the RC lab with my beta lab modifications.

I guess this shows I haven’t used the migration scripts all that much, because I didn’t realise they would start deleting all the new schema attributes to do with reporting!

So now I know: don’t use the FIM migration scripts between versions.

3 Replies to “Don’t use the FIM configuration migration scripts between versions”

  1. Oh yes I know I could have done that – it was more that I didn’t know ahead of time I’d need to.

  2. Actually you can use them, you just have to manually edit the changes.xml files before you commit your changes. First time around I just imported everything, which obviously didnt work so well. Manually removing all the changes to built-in bits and pieces left me with a changes.xml that only included the stuff I’ve added myself to my FIM 2010 lab environment, and that mostly worked ok when imported to 2010 R2 RC.

Leave a Reply

Your email address will not be published. Required fields are marked *


*