Changing AD credentials on vSAN 8.0 File Services fails with "AD domain, organizational unit, and username can not be changed after they have been configured"
search cancel

Changing AD credentials on vSAN 8.0 File Services fails with "AD domain, organizational unit, and username can not be changed after they have been configured"

book

Article ID: 420175

calendar_today

Updated On:

Products

VMware vSAN VMware vSAN 8.x

Issue/Introduction

  • There are no shares created on an vSAN 8.0 File Services instance.

  • AD credientials are configured on the vSAN 8.0 File Services

  • Editing the AD credentials on vSAN 8.0 File Services fails with error:

    "AD domain, organizational unit, and username can not be changed after they have been configured"

Environment

VMware vSAN 8.x

Resolution

To change AD credentials on vSAN 8.x File Services, it is necessary to 

1) edit the File Services configuration to remove the existing credentials

2) edit the File Services configuration to add the new credentials

 

Note: this is supported only where there are no vSAN File Services Shares.

Additional Information

See: 
Supported re-configurations of vSAN File Service Domain
Edit vSAN File Service

Note:
If vSAN File Services have been disabled and the old AD credentials are no longer valid, re-enabling Fileservices with new AD credentials will fail the same error ("AD domain, organizational unit, and username can not be changed after they have been configured").

To workaround this issue, first, enable File Services with no AD credentials specified. Subsequently, edit the File Services configuration to specify the new AD credentials.