Tuesday, April 22, 2014

Installing FIM on SharePoint 2013 SP1

Couldn’t help but try installing FIM now with this setup:

  • Windows Server 2012 R2
  • SQL Server 2012 R2
  • SharePoint 2013 Foundation SP1
  • FIM 2010 R2 SP1

Prior to SharePoint 2013 SP1 I was not able to get SharePoint installed on Windows Server 2012 R2 due to issues with the prerequisites installer.  Yes, I could have sorted it out by following the wisdom of the smart folks that figured out the workaround but I just don’t enjoy SharePoint enough to spend that much time on said workaround. 

Anyhow, I installed the above today and voila!  It worked!  The bonus was that it mostly worked with my existing automation script on a Hyper-V Generation 2 virtual machine.

Next step is to try it in my Azure VMs, which I expect to be no different except for the source of the installation media since I still use ISO files in Hyper-V, where in Azure we have to use VHD files.


Jay Van Der Zant said...

Doh, I've just ruled out SP2013 on my current project because I too don't like messing about with SharePoint any more than I have to. Thanks for the headsup, will have to give it a spin.

Craig Martin said...

SharePoint 2013 worked fine on Windows Server 2012, just not on Windows Server 2012 R2.

The best way to stop messing with SharePoint for FIM is to automate it. Got that mostly working and have hated SharePoint a lot less since.

Oliver Hanappi said...

I stopped using SharePoint 2013 because when creating workflows (at least approval workflows) the designer references the wrong version of Workflow Foundation (4.0 instead of 3.5) such that I needed to correct the XOML each time. For details see http://blogs.technet.com/b/server-cloud/archive/2014/04/23/forefront-identity-manager-vnext-roadmap-now-microsoft-identity-manager.aspx

Craig Martin said...

Oddly I haven't hit that but I almost never create FIM Workflow objects using the FIM Portal, I script them using the FIM PowerShell Module:


Jay Van Der Zant said...

Also, I would urge caution with using Windows Server 2012 R2 as it's not a supported platform for FIM and I've actually had push-back on this with a project as Microsoft said they wouldn't support it (and probably won't as their attention lies on MIM) and so we're reprovisioning some servers back on to Server 2012. Hardly an ideal situation.

Craig Martin said...

Good point Jay. I'm not using this combination in production anywhere yet, just can't resist adjusting the automation to use the latest bits and find the issues.