Sharepoint user validating lattest dating site in the world
Thus farm deployment aspects are generally not well understood by FIM practitioners which leads to a number of common deployment and operational challenges.Indeed the FIM documentation strongly suggests a “stand alone” installation of Share Point is best, as it insulates the practitioner from a lot of the deployment steps.Second are the various things that Share Point 2013 does or promotes which FIM doesn't like.The best example of this is that the FIM Portal requires the use of Classic Authentication mode (which is deprecated in Share Point 2013). These two traits make something that should be straightforward a bit more “interesting”. Tech Net leaves a lot to be desired here (which is unusual for FIM documentation) including errors in scripts and so on, so this article represents a tested, repeatable and reliable cheat sheet for deployment of the FIM Portal on Share Point 2013.FIM 2010 R2 SP1 introduces support for Windows Server 2012, and this is something we definitely want to leverage for our Identity Management platform.The problem is however that Share Point 2010 doesn’t run on Windows Server 2012 yet, for that we need to wait for Share Point 2010 Service Pack 2.
Instead of the FIM team building out their own hosting infrastructure and site plumbing, they built a bunch of customizations on top of Share Point.
This post is not intended to introduce those concepts and therefore is intended for FIM practitioners more so than Share Point professionals new to FIM.