"Error: You don't have permission to execute this command" - Append sudo to command line
"Error: Failed to add users" - Make sure your username parameter has a double "\". Note the red "\" . It is NOT a typo.
Eg: sudo vifp addserver vcenter.addomain.com --authpolicy adauth --username addomain\\adusername
Monday, April 1, 2013
vSphere Management Assistant (vMA) 5.1 hostname not sticking
This is a frustrating problem. Don't understand why in my company's production systems, the standard VMware installation instructions don't work.
I had no issues on my home lab. (hair pulling)
You configure the new hostname using the instructions from the vMA user guide, configuration is done through the web interface on port 5480 and/or directly from the VM console, and/or from a SSH session.
The moment you reboot the system, it reverts back to localhost.localdomain. It does not matter if you initiate the reboot from the web interface on port 5480 or from a shell session.
Anyhow, to fix this problem, create an "A" record on the AD DNS server, then from shell run "sudo -i" (this will drop you into a root session (text color will change to red), then run Suse's network configuration utility "system-config-network-tui"
Reference: http://communities.vmware.com/message/2159792?tstart=0
Edit (4/4/2013):
Same thing happened to my home vMA.
I had no issues on my home lab. (hair pulling)
You configure the new hostname using the instructions from the vMA user guide, configuration is done through the web interface on port 5480 and/or directly from the VM console, and/or from a SSH session.
The moment you reboot the system, it reverts back to localhost.localdomain. It does not matter if you initiate the reboot from the web interface on port 5480 or from a shell session.
Anyhow, to fix this problem, create an "A" record on the AD DNS server, then from shell run "sudo -i" (this will drop you into a root session (text color will change to red), then run Suse's network configuration utility "system-config-network-tui"
Reference: http://communities.vmware.com/message/2159792?tstart=0
Edit (4/4/2013):
Same thing happened to my home vMA.
Subscribe to:
Posts (Atom)