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.
These “interesting” configuration elements are really the meat of this article, along with a few other recommendations. Our intention is to first deploy and configure the Share Point 2013 elements required for hosting the FIM Portal.
First things first, we need our FIM service accounts.
Whilst coming soon, those building Id M solutions now face either a mix of host operating systems for the various FIM components, or a move to Share Point 2013.Firstly Share Point’s overall addressing architecture along with some shockingly bad deployment guidance which focuses primarily on small scale, often single server deployments.Thus farm deployment aspects are generally not well understood by FIM practitioners which leads to a number of common deployment and operational challenges.The harsh reality is that Share Point 2013 in and of itself offers no value whatsoever in terms of functionality for the FIM Portal.Sure some may argue it can leverage infrastructure improvements, but such arguments are tenuous at best.