Hello,
It's great that you're exploring Cluster-Aware Updating (CAU) to simplify the patching process for your Hyper-V clusters. The error you're encountering with the pre-created computer object account could be due to several factors. Here are a few steps to consider and some insights into patching Hyper-V hosts:
Cluster-Aware Updating (CAU) Setup:
Service Account Permissions: Make sure that the pre-created computer object account has the necessary permissions. The computer object should have Read, Create All Child Objects, Delete All Child Objects, and Validated write to DNS host name attributes in the Active Directory.
OU or Prestaging: If you're using a pre-created computer object, ensure that it's either in the OU specified for the Cluster Name Object (CNO) or in a prestaging OU that has the permissions mentioned in your provided article.
Credential: During CAU setup, you'll need to provide the credentials for the pre-created computer object account. Ensure that the provided credentials are correct and have the necessary permissions.
Network Connectivity: Ensure that there's no network issue preventing communication between the nodes, and the nodes are correctly added to the failover cluster.
DNS Resolution: Verify that DNS resolution is working as expected for the nodes and the pre-created computer object.
Patching Hyper-V Hosts:
When it comes to patching Hyper-V hosts, you have a few options:
Cluster-Aware Updating (CAU): As you're already exploring, CAU is a Microsoft feature specifically designed to streamline patching for clustered environments. It works well for Hyper-V clusters and ensures a seamless update process.
Manual Patching: If you choose not to use CAU, you can manually patch your Hyper-V hosts. This involves scheduling downtime for each node, performing the updates, and restarting the nodes one by one.
Configuration Manager (ConfigMgr): Since you mentioned you're using ConfigMgr with the SUP role, you could also consider integrating ConfigMgr for updating. While it's different from CAU, ConfigMgr can automate the deployment of updates based on your schedules and configurations.
Automated Deployment Tools: There are third-party tools available that offer automated patch management and deployment for Hyper-V hosts. These tools can provide more flexibility and customization compared to native Windows tools.
Scripting: For more advanced users, PowerShell scripts can be used to automate the update process. PowerShell allows you to perform updates on a schedule or trigger them remotely.
Ultimately, the choice between CAU, manual patching, or using additional tools depends on your organization's requirements, resources, and familiarity with the methods. Make sure to thoroughly test any new patching method in a controlled environment before applying it to your production clusters.
I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–