vSphere Client Caching

vExpert Guest Post: Jason Boche

Are you a full time VI Administrator? Managing a large environment with several vCenter Servers? Is providing vSphere Client connection parameters on a regular basis giving you Carpal Tunnel Syndrome? Following are a few tips which may help you out by reducing the amount of data entry you have to perform each time you reach for the vSphere Client

Tip #1: Leverage the “Use Windows session credentials” option wherever possible. This prevents you from having to type in your User name and Password for the connection:

Tip #2: Make use of the IP address / Name pull down box when possible. The values in this box are stored in the registry in the following key (you can pre-populate this key with connection points throughout your infrastructure when deploying the vSphere Client to administrative desktops):
HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences
RecentConnections

Tip #3: Alternatively, you can use the -s parameter to pre-populate the IP address / Name field (ie. “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe” -s myhost):

Tip #4: What if you can’t use integrated Windows session credentials with the vCenter Server you’re connecting to? Launch the vSphere Client with the -u parameter to pre-populate the User name field (ie. “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe” -u jason):

Tip #5: Here’s an option I’d advise you to use very cautiously – caching the password portion of your credentials. Launch the vSphere Client with the -p parameter to pre-populate the Password field (ie. “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe” -u jason -p test123):