none
MIM 2016 - recommended scaleout for high volume installations RRS feed

  • Question

  • We have a scenario where we are looking at a installation of several thousands of users, what are the scaling recommendations for MIM 2016?

    I mean like installing the components by them selves is a thought we have at the moment to do:

    1+ windows 2012 server - mim sync

    1+ windows 2012 server - mim service

    1+ windows 2012 server - mim portal

    Is it maybe wise also to have different database hosts for the MIM sync / service databases?


    Thursday, August 4, 2016 1:02 PM

All replies

  • How many thousands? How many groups? are you implementing SSPR or other sepf service functionalities?

    Nosh Mernacaj, Identity Management Specialist

    Thursday, August 4, 2016 1:31 PM
  • Hi Endre,

    A good source for scaling recommendations is the FIM Capacity Planning Guide. Also take note of Microsoft's performance testing of a medium sized organization, which may be similar to your environment. 

    One  advantage you will have by separating the sync service from its database is being able to take down the sync server for patching/maintenance and essentially fail over to warm standby sync server. If you do split the database off on its own server, avoid placing it on an already busy corporate SQL cluster and follow documented best practices as listed here -- especially all the SQL ones. We also try to consolidate best practices that we've found by experience and/or in documentation in the Operations and Best Practices chapter of the Microsoft Identity Manager 2016 Handbook. Hope that helps.

    Best,

    Jeff Ingalls

    Thursday, August 4, 2016 2:03 PM
  • It's about allmost 20k+- users in AD / Metaverse @nosh. About the number of groups I reckon a fair bit meaning a couple of hundred groups at least

    Number of users: est 20k +-

    Number of groups: est 2k + I think are safe assumptions

    Self service (SSPR) yes

    Number of authorative / source systems 2-3

    Number of destination systems incl AD: unknown but north of 10+

    So yes @jeff your links to the things was nice :)

    Friday, August 5, 2016 9:54 AM
  • It sounds a lot of groups for the number of users, but that's another story.

    I would not follow your model, instead, I would put service and portal on same server, but have 2 servers HA\Load Balanced, since you have SSPR and other user facing modules.


    Nosh Mernacaj, Identity Management Specialist

    Friday, August 5, 2016 2:33 PM
  • Medium-size org as mentioned in my first reply sounds sufficient for what you've told us thus far.  Following best practices on SQL during implementation will save you a lot of time in the future. 

    Best,

    Jeff Ingalls

    Friday, August 5, 2016 9:35 PM