FIM 2010 R2 - Deployment with partitioning
Hi all, we are designing a fairly large FIM 2010 R2 architecture. We would like to achieve FIM service partitioning as per http://social.technet.microsoft.com/wiki/contents/articles/2363.understanding-fim-service-partitions.aspx The article refers to FIM 2010. There have been any changes in R2 related to this configuration? Into the article there is no guidance about SharePoint. We would like to use Foundation 2010. Now the question is whether to have a single SharePoint Farm or having multiple Farms (one per partition). I remember that with 2010 there were some implication related to FIM patching. Is there any guidance in this regard? Any help is highly appreciated. --- Vincenzo Sciarra http://www.vincenzosciarra.tk
November 7th, 2012 4:54am
I'm not aware of any changes with regard to partitioning; however, first and foremost, it would be useful if Microsoft could provide some quantitative data on how more FIM Service instances might affect response time based on different workloads. Supposing the bottleneck turns out to be the (single-instance) SQL database, adding more FIM Service instances would likely result in greater maximum latency. If you search this forum, there are some earlier discussions about only Sharepoint Foundation 2010 being supported. If I recall from that thread, there is no benefit to a SP farm deployment for the FIM Portal.
November 7th, 2012 9:12pm