Are you using Windows Internal Database or SQL Server?

So I had this project for a customer lately, and everything was working as inteded until I was expanding the ADFS Farm with a second ADFS Server.

It continuely told me I couldn’t add the Server to the ADFS Farm, because I was using a SQL Database Instance. But I was so sure I haven’t installed any SQL Server or configured the first ADFS Server with any SQL Database Instace.

Even today, I don’t know how this could have happend, but with PowerShell command Get-ADFSproperties we can see wether we use WID or SQL.

SQL Express, which is free and gives more the WID will have this settings:

ArtifactDbConnection      : Data Source=SERVERNAMESQLEXPRESS
                                             ;Initial Catalog=AdfsArtifactStore;
                                             Integrated Security=True;Min Pool
And if your using WID the settings will look like this:
See specificly the Data Source=np:\.pipemicrosoft##wid
I then managed to activate Remote Connections for the SQL Express, opened the firewall and could connect my second ADFS Server to the ADFS Farm with the credentials ADFS was installed with.
Stick around and I will find out why it without my knowledge got installed on SQL Server 🙂


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