Due to a cross forest AD/Exchange migration we are in a position where we need to update our FIMService/FIMPortal configuration as the OWA / Exchange EWS URL that the FIMService uses to send email notifications will be changing, and so will the "send" email address of the FIMService mailbox that we send notifications from.
I haven't been able to find a conclusive statement from Microsoft on how we should achieve this, but other MS forum posts that I've read suggest either updating the Microsoft.ResourceManagement.Service.exe.config file directly or running a "Change" install on the FIMService/FIMportal server. (See http://social.technet.microsoft.com/Forums/en-US/aec634d2-165e-49c9-960e-0eaa6625b040/can-mail-server-be-configure-in-fim-post-install?forum=ilm2)
I have no idea whether updating the Microsoft.ResourceManagement.Service.exe.config file is supported by Microsoft (there doesn't seem to be any recommendation either way as to whether you can or can't use this method).
A "change" install feels like the right thing to do as this feature has been built into the installer. I tried this but found the following :
The original install was FIM 2010 R2 SP1 but we have since installed patch level 4.1.3114.0. When I ran the change install it asked me for the installation media half way through (even though the only thing that was changing was the mail server address and the FIMService mailbox SMTP address). The only way I could proceed was by pointing the installer back at the original FIM 2010 R2 SP1 media, however during the process the installer then said "Copying new files" which makes me nervous as we were on a later patch level. The installer did complete successfully and after it finished the version in "Help/About" still showed as 4.1.3114.0, as did the version level when I looked at Add/Remove Programs. All seemed to be ok at this point, the FIMService was started ok, I could get into the portal, the FIM MA exports/imports/syncs all worked ok, so all seemed fine. It was just the "copying new files" that had me a little concerned.
I subsequently tried reapplying the 4.1.3114.0 patch and this turned out to be a really bad move, the installer crashed out during the database upgrade phase with an unhandled exception type error. Luckily I had backups/snapshots before I started.
So I'm in a bit of a quandary now as to whether I should just update the config file (with no clue as to whether this is supported) or go with the change install with questionmarks over file versions.
Any suggestions would be gratefully received.