The password_hash property is a tracked element of the vSphere Configuration Profile. When a password is changed locally (via UI, API, or 3rd-party tools), it triggers a non-compliance status because it no longer matches the hash stored in the cluster configuration.
Export the Current Desired Configuration In vSphere Client:
Go to the Cluster > Updates > Configuration tab.
Click EXPORT > Reference host configuration
Note: This will give you a JSON file representing the current config of the reference host of your choosing.
Edit the JSON File:
Open the exported JSON file.
Look for the following section:
"authentication": { "user_accounts": [ { "name": "root", "password_hash": "########", "description": "Administrator" } ] }Update the "password_hash" field with the new root password hash.
Note: You can create a password_hash using openssl as shown below.
openssl passwd -6
openssl passwd -6Password:Verifying - Password:########Save the JSON file.
Import the Updated Desired Configuration In vSphere Client:
Create a Draft.
Select the Cluster > Configure > Desired State > Configuration > Draft.
Import your JSON file.
Click Import from file in the ... dropdown on the far right.
In the Import Configuration File Pop-up, click on BROWSE button > Select your JSON file > then IMPORT.
PRE-CHECK.
Click on RUN PRE-CHECK in the right pane under Configuration tab and you will see Running draft pre-check.
Note: You should see Draft pre-check completed and found no errors message if successful.
Apply Changes.
Next, click on APPLY CHANGES which will open a Remediate Pop-Up window.
Review the Remediation.
Review the Pre-Check and Review Impact tabs in the Remediate Pop-Up window before applying the configuration changes.
Under SUMMARY it shows high level details like if host will be put into maintenance more or if reboot is required.
Under HOST-LEVEL DETAILS you can review all the impact or changes that will be made on each of the hosts within cluster.
If impact is acceptible, click on REMEDIATE.
Verify the password has been updated successfully.
Your hosts in this cluster should now all have the same password hash configured under Cluster > Configure > Desired State > Settings > Authentication > User Accounts.