Some time ago former FIM MVP Thomas Vuylsteke blogged this really helpful post on the above subject. I figure my customer isn’t the only one stuck in a pre-R2 limbo as we barrel towards the October 2017 FIM 2010 EOL deadline.
Seven months earlier I alerted colleagues to a number of pitfalls that I had encountered in the upgrade process, and with the forthcoming EOL for all things FIM 2010 I thought now is as good a time as any to remind everyone about these.
- Considerations for Upgrading to FIM 2010 R2
- FIM 2010 R2 Search Changes – change in the support for the “contains” operator – see also Carol’s post on the same topic;
- FIM 2010 R2 Schema and Object Visualization Configuration Changes – New schema elements in FIM 2010 R2;
- Composite query filter returns no results for explicit guid – 2 queries same result prior to R2, then different results ; and
- One cannot do an in-place upgrade if the FIM Service was originally installed from MSDN media. (Listed as a known issue on the upgrade instructions, but as a footnote so easy to miss.)
Also, even if your site is already on FIM R2, remember that when considering an in-situ upgrade that you may not be doing anyone any favours by remaining on an old platform (e.g. Win 2008), in which case the process outlined by Thomas above is definitely the way to go. With MIM 2016 supporting so many platform versions, it may be tempting to linger just a bit too long where you don’t really want to be.
If anyone else has something to throw into the mix feel free to comment on this post for the benefit of everyone else.