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. VPHAN 44,300 Reputation points Independent Advisor
    2025-12-10T15:55:51.74+00:00

    Hi Lucas,

    This is excellent progress. Your screenshots confirm that the cluster is currently stable with two nodes (PWGIRSQL1 and PWGIRSQL3) and, most importantly, your SQL Always On Availability Group (GIR_AG) is synchronized and healthy between them.

    Now, yes, the next step is to add PWGIRSQL2 back to the cluster. But since you just ran Sysprep, that machine is effectively "brand new" in the eyes of Windows. You can't add it immediately, you must prepare the operating system first.

    Here is my suggestion to bring PWGIRSQL2 back safely without breaking the existing stability:

    Phase 1: OS Configuration (Post-Sysprep)

    Because Sysprep strips configuration, PWGIRSQL2 is currently in an unconfigured state.

    Configure Networking: Assign the Static IP addresses (Management, Heartbeat, etc.) to match your original scheme. Ensure DNS points to your domain controllers.

    Join the Domain: Join PWGIRSQL2 back to the domain telecom.arg.telecom.com.ar.

    After the reboot, open Command Prompt and run whoami /user. Compare the SID (the long alphanumeric string) with the SID of PWGIRSQL3. They must be different now. If they are different, the Sysprep was successful.

    Install Prerequisites: Install the Failover Clustering feature via Server Manager or PowerShell: Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools.

    Install the NET Framework 3.5 if your SQL Server version requires it.

    Phase 2: Add the Node

    Do not use the "Validate a Configuration" wizard on the entire cluster yet (to avoid the freezing you saw earlier). We will add the node directly, as we know the other two are healthy.

    Open Failover Cluster Manager on PWGIRSQL1.

    Right-click the Nodes folder and select Add Node.

    Enter PWGIRSQL2 and follow the wizard.

    The wizard might ask to run validation. You can choose "No, I do not want to run validation support test" to skip it and add the node immediately. Given the network sensitivity in your environment, skipping validation for now is acceptable to get the node joined, provided you are certain the network settings are correct.

    Phase 3: SQL Server Re-installation

    Adding the node to the Windows Cluster does not automatically add it back to SQL Server.

    Once PWGIRSQL2 is "Up" in Cluster Manager, you must run the SQL Server Installation Center on Node 2.

    Select "Add a node to a SQL Server Failover Cluster" (if using FCI) or simply install the Standalone SQL Server instance (if using Always On Availability Groups, which appears to be your case).

    Once SQL is running, you will then use SQL Management Studio (SSMS) on the Primary (PWGIRSQL1) to add PWGIRSQL2 back as a Replica in the Availability Group wizard.

    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 then. Should you have more questions, feel free to leave a message. Have a nice day!

    VP

    Was this answer helpful?

    0 comments
  2. Lucas Peñaloza 671 Reputation points
    2025-12-10T19:35:30.0633333+00:00

    Vphan!!!.

    Yes, We are a little more relieved!!!.

    Look:

    hostname PWGIRSQL1

    PS C:> whoami /user

    USER INFORMATION

    User Name SID

    =============== ==============================================

    oneteco\w919857 S-1-5-21-1234520961-3768318638-3525749049-9341

    ---------------------------------------------------------------------------------------------------------hostname PWGIRSQL2

    PS C:> whoami /user

    USER INFORMATION

    User Name SID

    =============== ==============================================

    oneteco\w919857 S-1-5-21-1234520961-3768318638-3525749049-9341

    PS C:>

    hostname PWGIRSQL3

    PS C:> whoami /user

    USER INFORMATION

    User Name SID

    =============== ==============================================

    oneteco\w919857 S-1-5-21-1234520961-3768318638-3525749049-9341

    PS C:>

    I can't believe this!!!

    What can we do in this case?

    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.