Skip to main content

Cannot change the password of administrator@vsphere.local from the vSphere Web Client dropdown menu

  Symptoms

  • The Change Password option is greyed out in the dropdown menu when you log in as Administrator@vSphere.local.
  • You cannot change the password as an Administrator.
  • A standard user logging in to the vCenter Single Sign-On (SSO) server from the vSphere Web Client can perform a password change from the dropdown menu.
Resolution
To resolve this issue, you must change the password for the Administrator.

To change the password for the Administrator:
  1. Log into the vSphere Web Client with an SSO administrator user
  2. Click Administration.
  3. Click Users and Groups under Single Sign-On.
  4. Right-click Administrator under the Users tab.
  5. Click Edit User.
  6. Change the password for the Administrator.

    Note: If the Edit User dialog box for the Administrator@vSphere.local is greyed out, see Cannot change the administrator@vsphere.local password after upgrading from vCenter Server 5.1 to 5.5 (2061122).
Related Information
 

 

Comments

  1. Cannot Change The Password Of Administrator@Vsphere.Local From The Vsphere Web Client Dropdown Menu >>>>> Download Now

    >>>>> Download Full

    Cannot Change The Password Of Administrator@Vsphere.Local From The Vsphere Web Client Dropdown Menu >>>>> Download LINK

    >>>>> Download Now

    Cannot Change The Password Of Administrator@Vsphere.Local From The Vsphere Web Client Dropdown Menu >>>>> Download Full

    >>>>> Download LINK KZ

    ReplyDelete

Post a Comment

Popular posts from this blog

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...