The cluster identity may lack permissions required to update the object

Lucas Peñaloza 671 Reputation points
2025-12-02T20:36:56.19+00:00

Dear;

Hi have the message:

The computer object associated with the cluster network name resource 'Cluster Name'

could not be updated in domain 'xxx.xxx.xxx.xxx.xxx' during the

Password change operation.

The text for the associated error code is: The specified network password is not correct.

The cluster identity 'CLPWGIRSQL$' may lack permissions required to update the object.

Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Please tell me what I need to check

Thank you so much!!!.

Windows for business | Windows Server | Storage high availability | Clustering and high availability
Answer accepted by question author
VPHAN 44,300 Reputation points Independent Advisor
2025-12-29T21:01:36.1466667+00:00

Hello Lucas Peñaloza,

I wanted to follow up to see if you successfully completed the upgrade of the final node (PWGIRSQL1) and failing back your resources.

To summarize our last discussion regarding your final step:

The Risk: Update-ClusterFunctionalLevel is irreversible, but it is safe as long as all nodes are online, running the new OS, and you have passed the Test-Cluster validation.

The Strategy: There is no rush. You can leave the cluster in "Mixed Mode" for a few days to verify stability before running the command to lock in the new features.

If your cluster is now fully upgraded and stable, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
VPHAN 44,300 Reputation points Independent Advisor
2025-12-18T15:55:23.51+00:00

Hi Lucas Peñaloza,

You are definitely correct to be cautious about High Availability (HA). While a Windows Cluster can technically run with one node on a new OS and two on the old OS (Mixed Mode), your approach minimizes risk significantly.

By updating both Secondary nodes (PWGIRSQL2 and PWGIRSQL3) before you ever touch the Primary (PWGIRSQL1), you ensure that when you finally perform the failover:

  1. Stability: You are failing over to a new OS node (PWGIRSQL2) that already has another new OS partner (PWGIRSQL3) ready to sync.
  2. Redundancy: If something goes wrong with PWGIRSQL2 immediately after the upgrade, you have PWGIRSQL3 (also upgraded) as a safety net.

The Approved Execution Order:

  1. Update PWGIRSQL2 (OS + SQL).
    • Result: Node 2 is healthy and syncing again.
  2. Update PWGIRSQL3 (OS + SQL).
    • Result: Node 3 is healthy and syncing again.
    • State: Now you have 2 upgraded nodes waiting in the wings.
  3. Failover the Availability Group from Node 1 to Node 2.
    • Result: Your Production is now running on the New OS.
  4. Update PWGIRSQL1 (The old Primary).

This is the safest, most professional way to execute a 3-node cluster upgrade. Proceed with confidence.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Was this answer helpful?

1 person found this answer helpful.
0 comments
Answer accepted by question author
VPHAN 44,300 Reputation points Independent Advisor
2025-12-15T14:54:40.93+00:00

YES, absolutely. You must always begin your upgrade process with the Secondary Replicas. Since your cluster is now healthy, the safest rolling upgrade workflow is to upgrade the passive nodes first, leaving the active Primary (PWGIRSQL1) untouched until the very end to keep your application online.

Here is the recommended sequence:

Phase 1: Upgrade the Secondary (PWGIRSQL2)

Since PWGIRSQL2 is already a Secondary replica and you just stabilized it, it is the perfect candidate to start with.

  1. Backup: Take a full backup of your databases on the Primary (PWGIRSQL1) just in case.
  2. Suspend Data Movement (Optional but Recommended): In SSMS, you can temporarily suspend data movement for the PWGIRSQL2 replica if the upgrade will take a long time (to prevent the transaction log on the Primary from growing too large while waiting).
  3. Perform the Upgrade: Apply your Operating System updates or SQL Server patches/upgrades on PWGIRSQL2.
  4. Reboot & Validate: Restart PWGIRSQL2. Once it is back online, open SSMS on the Primary and verify that PWGIRSQL2 returns to the Synchronized (or Synchronizing) state. Phase 2: Upgrade the Next Secondary (PWGIRSQL3)

Once Node 2 is green and fully synced, repeat the process for PWGIRSQL3.

Phase 3: The Failover (Switch Roles)

Once both Secondaries (Node 2 and Node 3) are upgraded and healthy:

  1. Change the Availability Mode of PWGIRSQL2 to Synchronous Commit (if it isn't already).
  2. Perform a Manual Failover of the Availability Group from PWGIRSQL1 to PWGIRSQL2.
    • Now PWGIRSQL2 is the Primary and is running the new version.
  3. Verify applications are connecting successfully. Phase 4: Upgrade the Old Primary (PWGIRSQL1)

Now that PWGIRSQL1 is a passive Secondary, you can safely proceed to upgrade it.

VP

Was this answer helpful?

1 person found this answer helpful.
0 comments

49 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Lucas Peñaloza 671 Reputation points
    2025-12-05T03:17:33.3066667+00:00

    Hi VPHAN!!!.

    Thank you for your information!!!!.

    I need to contact the Domain Administrator and perform these validations.

    Now in the case of, to use cluster repair function, The cluster will present drawbacks????.

    Thanks!!!.

    Was this answer helpful?

    0 comments
  2. VPHAN 44,300 Reputation points Independent Advisor
    2025-12-05T12:47:41.1833333+00:00

    Good day Lucas Peñaloza,

    I hope you''ll find something useful in the following explanation, and if it helps you get more insight into the issue, it's appreciated to accept the answer.

    Using the Repair Active Directory Object function in Failover Cluster Manager is a safe, supported, and non-destructive operation when performed correctly. However, there are important operational considerations to be aware of to avoid downtime.

    Potential Drawbacks & Mitigations:

    1. The repair process will temporarily take the Cluster Name resource offline. This means client connections relying on the cluster network name (e.g., \\ClusterName\Share) will be briefly interrupted. SQL Server client connections using the SQL Server Network Name will drop and must reconnect. Schedule the repair during a maintenance window. Before starting, manually bring the Cluster Name resource offline in a controlled manner to gracefully inform connected clients.
    2. The repair action requires that the cluster nodes can communicate with each other and with a domain controller. If there are underlying network or cluster communication issues, the repair may fail or hang. You can run Test-Cluster to validate cluster health before attempting the repair. Ensure all nodes have network connectivity to a domain controller.
    3. The function resets the Reset Password and Write permissions for the cluster computer object (CLPWGIRSQL$) to the default. If your environment uses custom permissions on this object, they will be reverted to the defaults. So you need to document any custom permissions before the repair. They can be reapplied afterwards if necessary.

    For the procedure to be safe, I recommend:

    Pre-Check: In Failover Cluster Manager, under Cluster Core Resources, note which node currently owns the Cluster Name resource.

    Initiate Repair:

    Right-click the Cluster Name resource.

      Select More Actions > Repair Active Directory Object.
  
     If the option is grayed out, you must first right-click and choose Take Offline. Confirm, then the repair option should become available.
     
     Monitor: The resource will go offline, perform the repair (which resets the password and permissions in AD), and then come back online. This typically takes 30-60 seconds.
     
     Verification: After the repair, check the cluster events for a successful operation (Event ID 1207 or similar). Also, verify the cluster name resource is online and that clients can connect.

    If the repair function fails or you can't afford any resource downtime, the alternative is the manual password reset method using netdom resetpwd or PowerShell's Reset-ComputerMachinePassword from a domain controller. This can be done without taking the cluster resource offline, but it requires direct domain controller access and may need to be coordinated with the domain administrator.

    Should you have any questions, feel free to ask.

    VP

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.