none
Is there a short-cut to switching MIM 2016 Portal to use FimService database on a different SQL server than at original install? RRS feed

  • Question

  • MUST we have to uninstall/re-install MIM just to use a different SQL server?

    As part of disaster recovery/high availability plans we have 2 geographically distinct centers hosting the MIM servers. The failover SQL server is maintained via log shipping.

    It seems, to activate the 2nd MSQL for MIM usage I must uninstall MIM and then re-install MIM. This seems amazing for such a trivial change. The data hasn't changed, the databases haven't changed, just the SQL host server is now a different machine.

    Surely there are configuration files and/or registry settings holding this stuff. I mean, wtf does FIMService service do at initialization? It must find out its sources from somewhere.

    Friday, December 8, 2017 2:03 PM

All replies

  • Yes there is, create a CNAME=OLD SERVER NAME, that points to NEW SERVER NAME.

    Nosh Mernacaj, Identity Management Specialist

    Friday, December 8, 2017 3:10 PM
  • CNAME will probably break Kerberos between the MIM server and SQL. You can use a SQL Alias, though. Alternately, the database connection details are stored in the registry on the MIM server. It's either under HKLM\System\CurrentControlSet\Services\FIMService\Parameters or HKLM\Software\Microsoft\Forefront Identity Manager. I forget which one offhand, though I believe it's the former.

    Thanks,
    Brian

    Consulting | Blog | AD Book

    • Proposed as answer by Borys Majewski Friday, December 15, 2017 11:20 AM
    Saturday, December 9, 2017 11:20 PM
    Moderator
  • SQL ALIAS does not work either, as the format has to be SERVER\ALIAS;

    CNAME is not a good idea, seems, since the other server is still in the network.  I thought they decommissioned or something.

    What they need for the long run is really a CNAME that points to the ACTIVE SERVER and is changed for DR to point to the BACKUP server.  They do need to run the install once, to change the SQL To the CNAME and then never again.


    Nosh Mernacaj, Identity Management Specialist

    Sunday, December 10, 2017 1:25 PM