Hello all,
I have a 2012 R2 ADFS server farm consisting of 2 servers using WID. When I added the second server to the existing server, it completed the tasks just fine without any errors and shows in the ADFS management console as a secondary server to the primary.
My issue is that I cannot validate the functionality of the secondary server without taking the primary offline, which would cause an outage for my SSO users. When I try and perform the basic URL tests against the secondary server (the idpinitiatedsignon.aspx, etc.) , I get the "website not found" messages back from the browser with no events in the Event Logs. I cannot verify it's operation via PowerShell, as that generates the message that the commands cannot be executed on a secondary server. I see nothing but the usual messages in both the primary and secondary event logs so maybe this is "normal" or "as designed" behavior for v3.0?
Also, I noticed that contrary to what you would normally see in a ADFS 2.1 farm deployment in the management console, with v3.0 you do not see any configuration items in the secondary server's console. Just the message that it is a secondary server and that all changes must be made on the primary.
How do I know this farm is working? How do I test the secondary without incurring an outage?
Thanks for the help.