Microsoft added recovery, backup, security for Windows Server 2019

With Windows Server 2019, Microsoft has added advanced recovery and redundancy to the Shielded Virtual Machines security controls, which have been integrated from the Windows Server 2016 version. .

Previously, protected virtual machines (SVMs) provide measures to protect the resources in the machine by isolating these resources from the hypervisor system. At the same time, it was also given the message that the systems were fully isolated and controlled. For now, improvements of SVMs in Windows Server 2019 can provide the exact recovery time of a server in the system as well as server-based and policy-based security updates.

Server authentication feature

In Windows Server 2016, the authentication code is built on the Trusted Platform Module (TPM) chip and authenticates Microsoft Active Directory. Both are great options but they all have limitations on scalability and redundancy.

The addition of Windows Server 2019 with server authentication feature will bring a security solution based on authentication, allowing organizations to use standard authentication storage mechanism to store key codes. Organizations that want to isolate SVM from TPM-based systems can continue to use TPM-based certificates.

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

Configure failback

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:

1. What does Windows Server 2016 bring to small and medium businesses?
2. Latest features of Microsoft Office 2019
3. Windows 10 Redstone 5: New features and changes are waiting for you
4. What's new in Ubuntu 18.04 LTS just released?