Thursday, August 29, 2013

FIM without SharePoint

A funny thing happened a while back.  it was time to deploy our FIM solution to the production servers and I connected to the servers for the first time.  Our deployment is automated of course so should not have taken more than a few minutes but something caught me by surprise once I’d logged on; no Start button!

Call me a button monkey but I’d been expecting to get a few clicks in on the same OS we’d used for development and testing (Windows Server 2008 R2).  Low and bhold I was staring down at Windows Server 2012.  I asked my manager if we should correct this and was told we should proceed with the latest OS release (fair enough).

This could have thrown a wrench into my deployment but lucky for me this deployment does not use the FIM Portal.  We have a custom (and beautiful) web application (obviously I can’t take credit for the UX design or web programming). This custom UI only depends on IIS, which happily installs on Server 2012 with a simple PowerShell command.

So off I went installing the FIM Service and IIS, then deploying my web app and FIM Service configuration, and voila, the job was done.

FIM is supported on Server 2012 but, but it gets a little tricky because SharePoint 2010 is not supported.  To run the FIM Portal on Server 2012 you have to run SharePoint 2013 and configure it just so (this is covered in a TechNet article by Microsoft, but I found it difficult to get it working).  Anyhow, it is supported but luckily I didn’t need to do the hard part because we simply don’t use the FIM Portal.  To be honest, we do use the FIM Portal but only for administrative purposes.  It runs on a small VM somewhere running Server 2008 R2 and SharePoint 2010, and users don’t have access to it.

No comments: