Quick backstory, my company hired consultants to setup our MIM environment and left me the keys to our solution. I took a training course in MIM and learned the rest as I went. I have become very capable and comfortable with SQL, C#, PowerShell, Synchronization
and Portal Service which I think is pretty good given how spread out documentation for MIM seems to be. Where I am lacking is Sharepoint because I have never had to do anything beyond putting the Portal into "Maintenance" mode or running IISRESET.
In production we have 1 Synchronization server and 2 Portal servers. In dev we have 1 Synchronization server and 1 Portal server. I recently put together a bunch of changes in Dev along with upgrading to Hotfix 4.5.412. This week I attempted to rollout
the Hotfix and the configuration changes to Production and immediately hit an issue with the hotfix. I could no longer access the MIM Portal with our load-balanced address or pointing directly at the servers.
Looking in the event logs I found the following error
The Portal cannot connect to the middle tier using the web service interface. This failure prevents all portal scenarios from functioning correctly.
The cause may be due to a missing or invalid server url, a downed server, or an invalid server firewall configuration. Ensure the portal configuration is present and points to the resource management service.
I googled the error and tried everything I understood in the search results but had no luck resolving the issue so I had to rollback to my snapshots and SQL Backups. I copied all the .config files I kept seeing referenced in the search results on my non-working
servers before doing this. The only difference in prod is the fact that we have 2 Portal servers instead of 1 so I suspected these were causing my problems.
What I discovered was in the C:\InetPub\wwwroot\wss\VirtualDirectories\80\web.config file, after applying the hotfix the value of resourceManagementClient resourceManagementServiceBaseAddress changed from "http://server1.domain.org:5725" and "http://server2.domain.org:5725"
to our load balanced address of "http://manageidentity.webdomain.org:5725".
I am fairly confident this is the cause of my issue, however in trying to understand why, I found this https://social.technet.microsoft.com/wiki/contents/articles/10186.fim2010-troubleshooting-fim-service-is-not-available.aspx#APPENDIX_B which
says "Essentially the value for resourceManagementServiceBaseAddress should match the same thing in the FIM Configuration File ( resourceManagementClient and resourceManagementServiceBaseAddress )". When I look at the MIM config i see the load balanced
address of "http://manageidentity.webdomain.org:5725".
I have also seen that the web.config file should be the same on all the servers on the farm, but that was not the case with our working MIM solution as the 2 respective servers both referenced themselves in resourceManagementServiceBaseAddress.
I feel I am either misunderstanding the documentation/blogs or our production Portal servers were setup improperly.
Can anyone shed light on the resourceManagementServiceBaseAddress value when you have multiple portal servers? Or know of good documentation on setting it up so I can make sure my environment is setup correctly?