I have a functioning AD FS environment that consists of the following:
2 DCs (2008 R2)
1 AD FS server using WID (2012 R2)
1 AD FS WAP server (2012 R2)
Right now we are using this environment for Dynamics CRM 2013 (IFD) and it's working well. I would like to expand our on-premise infrastructure to make it redundant as we will be looking to utilize SSO and an Exchange hybrid configuration with Office365.
I've already deployed a new AD FS server and joined it to the existing farm. Configuration data has copied over successfully.
I would like to deploy an additional AD FS WAP as well, and this is where I start to hesitate because I don't want to disrupt the current working environment.
1. If load balancing isn't as much of a concern as availability is to me, is it necessary to configure a NLB, say Windows NLB, on the two AD FS servers? Is it recommended?
My research shows that in a farm configuration the primary AD FS server can go down and the secondary AD FS server will resume responsibilities; however, the database will be read-only meaning no new configuration changes can be made until either the primary comes back online or the secondary is marked as primary. Correct or no?
2. Can Windows NLB be configured on the WAPs after the initial WAP configuration is in place and functioning? What steps should be taken to minimize downtime, if any, while setting up NLB?