Security is at the forefront of many administrator's minds and with Failover Clustering, we did some improvements with Windows Server 2019 and Azure Stack HCI with regards to security.
Sinc...
Updated Jun 06, 2022
Version 3.0
Blog Post
John Marlin thank you for sharing these insights.
When looking at the upcoming projection of AD-less Failover Clusters with Windows Server 2025 - as per Windows Server Summit 2024 - we would have no requirement for Domain Controllers, is this correct?
Could you explain, eventually in a follow-up blog, how authentifcation, signing, Livemigration will work without Domain Controllers Kerberos?
Since today it's a security best practice using a seperate domain instance only for the Operation and management of core services like Failover-Cluster for Hyper-V / S2D / Azure Stack HCI other questions arise:
How can other Software safely communicate and authenticate like Windows Admin Center, SCVMM or Backup / BCDR Software?
Why is the NETBIOS naming convention on clustername (CNO) still a thing?
Thank you for your reply in advance!