We're deploying an ADFS 2.0 farm on 2008R2 servers utilizing mirrored SQL 2012 databases and getting an error when attempting to 'migrate' the ADFSArtifactStore database to SQL. Being unable to run the ADFS 2.0 FSconfig scripts to initially configure it for SQL instead of WID (due to an apparent compatibility issue), we had to resort to using the ADFS configuration wizard then migrating the local WID databases SQL. I'm following the steps from the "AD FS 2.0: Migrate Your AD FS Configuration Database to SQL Server" TechNet article and cannot get beyond Step 3, task 7:
7. Change the artifact connection string to point to the new SQL Server-based artifact data location. Open a Windows PowerShell command-line, type the following command-line syntaxes in order, and then press ENTER after each one. In SQLServer\SQLInstance below, type in the appropriate SQL Server and SQL Server instance name where you are migrating the artifact data to. For example, contososrv01\adfs-artifact.
Add-pssnapin microsoft.adfs.powershell
Set-adfsproperties –artifactdbconnection “data source=<SQLServer\SQLInstance>; initial catalog=adfsartifactstore;integrated security=true”
My syntax (using the default SQL instance):
Set-adfsproperties -ArtifactDbConnection "Data Source=sql1;Failover Partner=sql2;Initial Catalog=AdfsArtifactStore;Integrated Security=True"
Resulting error:
Set-ADFSProperties : Exception of type 'Microsoft.IdentityServer.PolicyModel.Client.StorageOperationException' was thro
wn.
At line:1 char:19 + Set-adfsproperties <<<< -ArtifactDbConnection "Data Source=sql1;Failover Partner=sql2;Initial Cata
log=AdfsArtifactStore;Integrated Security=True"
+ CategoryInfo : InvalidData: (:) [Set-ADFSProperties], StorageOperationException
+ FullyQualifiedErrorId : Exception of type 'Microsoft.IdentityServer.PolicyModel.Client.StorageOperationException
' was thrown.,Microsoft.IdentityServer.PowerShell.Commands.SetServicePropertiesCommand
Everything up to this point has been successful, the databases have been migrated/updated and mirrored. The ADFS service starts fine with the migrated ADFSConfiguration SQL 2012 database. I have tried entering this CMDlet six ways from Sunday (including using FQDNs) and nothing works. I have also deleted the databases and started the migration from scratch with the exact same results. What am I missing?
Is ADFS 2.0 actually compatible with SQL 2012/is this configuration supported by Microsoft?
Once I cross this hurdle, I plan to go back to FSConfig to add the other ADFS servers to the farm.
Thanks,
Dave
***UPDATE***
SQL 2012 is not supported for use with ADFS 2.0 per Microsoft support. I don't believe this is actually documented anywhere, but finally, a support rep declared that SQL 2012 is not supported for use with the ADFS Artifact database, in particular.