Unable to connect to wireless network validating identity

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.We will be focusing almost exclusively on the FIM Service and Portal components in this article and not talking to the FIM Sync service, Reporting or Certificate Management.As we know the FIM Portal is based upon Share Point and installs into an existing site collection, thus Share Point is a pre-requisite for the FIM Portal.However there are a number of configuration aspects which must be present and correct, and these differ significantly from what would be considered Share Point “best practices” and in some cases supported Share Point configuration.Sure some may argue it can leverage infrastructure improvements, but such arguments are tenuous at best.The FIM Portal works perfectly well today in Share Point 2010, and needs none of the new end user capabilities, or shudder at the thought, a Modern UI.

To keep things simple, the FIM Service and FIM Portal components will run on the same machines.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.In addition there are a number of security and availability considerations.The FIM Portal is a good example of a composite application built upon Share Point.

Leave a Reply