Monday, April 30, 2012 5:13 AM
I was wondering how other people handle transitioning FIM from dev to production? Our last migration was a manual process, but I'm now looking at ways to make it a little more stable and less prone to human error, particularly as our configuration starts to get more and more complex.
I've read through the Configuration Migration Deployment Guide at http://technet.microsoft.com/en-us/library/ee534906(v=ws.10).aspx, and while it looks quite good there's some things that I'm not sure how it would handle. In particular, how to deal with the domain-specific portions of configuration (our dev and production environments are in different domains). Does this just mean doing a find-and-replace in the export files for references to the domain (in things like OU strings for sync rules, domain attributes for objects etc), or importing as-is and changing them manually or through a separate script, or is there some neater way of handling this?
This is important to us not just for large-scale migrations, but also for deploying small changes, so I'm looking for something reasonably simple if it's at all possible.
- Changed Type Markus VilcinskasMicrosoft Employee, Owner Sunday, March 17, 2013 2:28 PM