vmware-system-user local Linux account for VCF Services Runtime 9.1 and VCF Automation 9.1 (VCFA)vmware-system-user account is not possible.Note:
vmware-system-user password via the Fleet Management UI/API.
The procedure requires multiple steps:
VCF Operations interface at https://<vcf_operations_fqdn> as a user assigned the Administrator role.Build > Lifecycle > VCF Management.vSphere Client where the cluster is deployed and find the virtual machine. Open a virtual console.Power, then Restart Guest OS.e.rw init=/bin/bash to the end, then press F10 to continue the boot procedure.useradd temp
passwd tempecho "temp ALL=(ALL) ALL" >> /etc/sudoers.d/90-cloud-init-usersreboot -fsudo su -CLUSTER=$(kubectl get configmap global-config -n vmsp-platform -o jsonpath='{.data.cluster\.name}')
read -sp "Enter password: " NEW_PASSWORD
export NEW_PASSWORD
HASH=$(printf '%s' "${NEW_PASSWORD}" | vmsp passwd --password-stdin | tr -d '\n' | base64 -w0)
kubectl patch secret "${CLUSTER}-ssh-password-secret" -n vmsp-platform --type=merge -p "{\"data\":{\"sshPassword\":\"${HASH}\"}}"
Upon successful validation of the password criteria, the system displays a response similar to the following:
2026/##/## 10:##:##/opt/vsp/password-policy.json not exist
2026/##/## 10:##:## validating password against local pwquality.confvmware-system-user can now loginsudo userdel temp
Note: Step 8 will immediately trigger all the virtual machines in the cluster to update the password for vmware-system-user.
If the Control Plane node is not visible in the UI, identify the target node using memory allocation metrics:
Open the vCenter and locate the directory containing the Virtual Machines (VMs).
Inspect the resource consumption metrics for all VMs within that folder.
Identify the VM with the lowest memory usage—this instance corresponds to the affected Control Plane node.