No longer limited by the scope of Active Directory or TPM, server authentication has opened new perspectives for SVMs, including scaling up as well as improving the redundancy of these SVM.
In addition, Windows Server 2019 adds many other features, you can see more at Discover "new" features in Windows Server 2019
Windows Defender ATP runs on Windows Server 2019 Preview
In Windows Server 2016, Host Guardian Service (HGS) has been integrated with the configuration task for secure servers and SVMs, and provided the authentication and security code needed to operate the SVM. When HGS is disabled, and an SVM system needs to be started, failback configuration in Windows Server 2019 will provide an additional layer of protection for HGS's redundancy. A primary and secondary HGS server will be configured in the SVM so that if the primary server is having problems, the SVM will connect to the secondary HGS server to confirm the boot process.
This can help resolve remote situations, when the server suddenly collapses due to a certain reason, when the server comes back up but the local HGS servers are not online or corrupted, while the server The remote system needs the server to work again.
With failback configuration, if branch systems fail to try to authenticate to the local HGS server, these systems will connect to central HGS servers to authenticate via WAN, from there, The boot process can be conducted and this feature is an optional configuration.
See more: