After upgrading the datacenter from vSphere 4.0 to 4.1 I was unable to connect with my service account “esxuser” by putty or console or Veeam to make some backups, warning message: Access denied

I changed my password a few times.. maybe it was changed, I restarted the SSH service.. no luck.. I created a new account with shell access but still the same deny!

Solution:

Connect direct your ESX console by VI client, go to Permissions tab and add your service account with Administrator rights:

Yeah, I was able to connect again with my service account..

Since vSphere 4.1 there’s a possibility to connect your ESX server into Microsoft Active Directory, how do you configure this:

- Connect directly to your ESX host

- Make sure your DNS servers are correct configured on the host + add the host by FQDN in your DNS server in your domain;

Read more…

Today on the Dutch VMug forum somebody got some trouble to connect a ESX host after changing the “root” permissions from Administrator to Read-only. Nice problem to find a solution, I created the same situation in my test environment.

Situation:

User: Root – Role: Read-Only

You can’t connect the host anymore with your VI Client..

Solution:

… but you can still login at the console or putty session.. so what to do:

Edit the authorization.xml file: nano /etc/vmware/hostd/authorization.xml

Read more…