I ran into a problem recently when configuring vMA for ESX/ESXi 4.1. I was able to join it, as well as, the ESXi hosts to the domain, but I was unable to log into the ESXi hosts with my AD credentials with either the vMA or the vSphere client. I double checked that my AD account did have Administrator permissions on the hosts, but still I could not log in. I was given the following error by the vSphere Client, as well as the vMA console:
Error connecting to server at 'https://<hostname>/sdk/vimService.wsdl':
Fault string: A general system error occurred: gss_acquire_cred failed
Fault detail: SystemErrorFault
The interesting thing is this: If i manually specified which account to use, instead of checking the box to use the account I was logged in with. I could connect and perform the actions I wanted to do. If I checked the box, then I got the error: “gss_acruire_cred failed”. The was was true with vMA. If I used the –passthroughauth option the command would fail, but if I allowed vMA to prompt me for a username and password the command would succeed. Only Integrated Authentication between windows and the vmware software was failing.
I did some research, and it turns out that when ESXi is installed on USB Drive, or SD card, or flash memory it does not automatically create Persistent Scratch space. This is the space that’s used to store temporary data among other things. This lack of persistent scratch space was somehow effecting the login process, but only when trying to pass credentials from a windows session and not by typing them in manually.
Here is how you can configure Persistent Scratch space on either local storage or a vmfs volume using the vSphere client:
- Connect to vCenter Server or the ESXi host using the vSphere Client.
- Select the ESXi host in the inventory.
- Click the “Configuration” tab.
- Click “Storage”.
- Right-click a datastore and select “Browse”.
- Create a uniquely-named directory for this ESX host (ex.
- Close the Datastore Browser.
- Click “Advanced Settings” under “Software”.
- Select the “ScratchConfig” section.
- Change the
ScratchConfig.ConfiguredScratchLocationconfiguration option, specifying the full path to the directory. For example:
- Click “OK”.
- Put the ESXi host in maintenance mode and reboot for the configuration change to take effect.
Once the host is rebooted you’ll be able to use vMA with the –passthroughauth flag, or login by checking the box on the vSphere client to use the account you’re already logged in with. To read more about this check out this link to VMware’s KB1033696