You can now use your certificates to connect to the failover web console. See Use a custom certificate for communication with the failover web console.

You can use custom locations for the data and log files of the SQL Server databases. See Configuring the failover cluster without database replication.

You can now configure XProtect Management Server Failover and a failover recording server in a workgroup environment. See Prerequisites for installing a recording server on the primary or secondary computer.

To see a list of the most common issues with XProtect Management Server Failover, go to Troubleshooting XProtect Management Server Failover.

You can now install a recording server on the failover cluster nodes. See Prerequisites for installing a recording server on the primary or secondary computer.

You can now connect the XProtect Management Server Failover to your external SQL Server. See Configuring the failover cluster without database replication.

You can now configure the failover cluster in a workgroup environment. See Network and computer prerequisites.

User certificates are no longer required to log in to the failover web console. To log in to the failover web console, you must now install a server certificate and authenticate with a user name and password. See Open the failover web console.

You must authenticate with a password to log in to the failover web console.

You can set a node to always stop or start after restart, see Change the behavior of a node after restart.