Installing MIM and all its bits (especially Sharepoint) is SOOO easy… if you get *every* *single* *thing* *right*. But make even one tiny mistake and you’ll be debugging it for hours.
Here are my self-reminder notes, covering the strange things I’ve found, and the things I seem to get wrong every time:
- The prerequisites can be installed by a domain admin if that works out easier.
- Pre-requisite problems?
- Add-WindowsFeature NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-Pipe-Activation45,NET-WCF-HTTP-Activation45,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Asp-Net45,Web-Net-Ext,Web-Net-Ext45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Xps-Viewer -verbose
- Turn on .NET 3.5 feature
- Install Sharepoint (and create the farm and CA) as the MIMAdmin user, even if it has to be temporarily made a local admin in order to do so.
- Get the installers from https://my.visualstudio.com/Downloads
- Get the license key for testbed installs from https://my.visualstudio.com/ProductKeys
- MIMAdmin needs sysadmin rights in SQL.
- When building a single node testbed with ADDS on the same server, remember that “local” group memberships are configured in the Builtin container in AD.
- Make sure that the MIMSharepoint user has “login as a service” rights. Then make sure it doesn’t have “DENY login as a service” rights.
- Always do the post-installation configuration (Farm and Central Admin creation) using a powershell ISE window that is Run As Administrator.
- Once the permissions and rights issues have all been solved, usually the farm still can’t be created due to persistent rubbish. Remove Sharepoint altogether, delete the databases, reboot and reinstall it from scratch.
- After a failed attempt to install the MIM Service + Portal, it’s often necessary to delete and recreate the whole Sharepoint WebApp before trying again. I’ve even had to resort to uninstalling and reinstalling Sharepoint entirely!
- This is certainly a weird one – when installing MIM on a domain controller it looks like the MIM Service account needs to have local admin privileges, otherwise MIM Sync cannot impersonate it when connecting to the FIMService database during setup of the MIM Service MA. It just reports “The credentials provided for accessing Forefront Identity Manager are invalid” in the Forefront Identitity Manager Management Agent event log otherwise.
And here are my helpful scripts for the Sharepoint configuration steps:
Create-MIMPortalSPWebApp-example.ps1
*** This Is A Work In Progress ***