ADFS 3.0 Configuration Fail

Scheduled an installation for ADFS 3.0 towards Salesforce today. Nothing out of the usual Project, but as we learn the hard way everytime, no customer is the same.

So after installing ADFS 3.0, without no errors, I proceeded to configure ADFS 3.0 and this is where it all started to go wrong.

Event ID: 102, 220 and 7000.

Read all over the internet, and nothing made seens, so when you are reading this blog, it might not be the solution for you either.

My Solution: Install SQL Express 2012 R2 Standard.

Cause: Windows Internal Database wants to create and use MSSQL$MICROSOFT##WID as Service Accont, but this customer uses GPO to controll which users who can Logon as a Service.

Possible Solution: Change WIDs Service Account, but it wasn’t that easy. It was allways changed back when you needed to restart the server. Because the WID installation would fail. Upon restart the service wasn’t installed anymore.

Second solution: Make an exception for the ADFS Servers, so ALL SERVICES will have Logon as a Service rights.


I am Roy Apalnes, a Microsoft Cloud Evangelist working av Sopra Steria. Main focus in Microsoft Security and Endpoint Management, with a bigger picture in mind.

Featured Posts