Windows 10 V1809: Compatibility update KB4489491 (03 01 2019) - Enhancing the Performance and Stabil

[German]Here is a strange observation of a blog reader on Windows Server 2016 systems running as failover clusters (SQL). After the February 2019 updates have been installed, virtual accounts can no longer be registered in the DNS. An error entry with ID 3019* is entered in the event logs.

I have encountered an issue here in the company where I am interested in whether there have been more reports about this. A [Windows Server 2016] failover cluster (SQL) updated with February 2019 can no longer register virtual accounts in the DNS. Errors 3019* occurred when registering DNS in the cluster event log.

Windows 10 V1809: Compatibility update KB4489491 (03 01 2019)

Download File

Cluster node 01 has thus retained its roles instead of returning them to cluster node 02 via script after the server has been restarted. In addition, it was not possible to install the update for [Cluster node] 02. So this means: [Cluster node] 01 with February [2019] update and [Cluster node] 02 with January [2019] update. Active was the [Cluster node] 01 with February update. 2ff7e9595c