Validating identity in wireless truth internet dating
The flies in the ointment are a couple of pretty common Share Point traits.
Firstly Share Point’s overall addressing architecture along with some shockingly bad deployment guidance which focuses primarily on small scale, often single server deployments.
We will also cover how to prepare Share Point 2013 for the deployment of the FIM Portal, and finally the installation of the Portal itself.
This article assumes that you are familiar with the functional decomposition of the FIM product and its logical architecture components.
Of course we need Active Directory Domain Controllers, Exchange Servers and SQL Servers in our environment.
There will also be a separate machine hosting the FIM Sync service.
The FIM Portal is a good example of a composite application built upon Share Point.
However in the journey to the cloud this model is effectively being deprecated in favour of the loosely coupled, off box approach to customization (a.k.a. Of course aligning such disparate strategy across wildly different release cycles is impossible, and it’s both unfeasible and unnecessary for the FIM Portal to be re-implemented at this stage in line with the new world order.
The harsh reality is that Share Point 2013 in and of itself offers no value whatsoever in terms of functionality for the FIM Portal.
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.
Thus farm deployment aspects are generally not well understood by FIM practitioners which leads to a number of common deployment and operational challenges.