vCenter Server 4.1

vCenter Server 4.1 is compatible with and may be used to manage ESX 3.0.x, 3.5 (all Updates), and 4.1.

http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf
More vQuotes

Cheaper/slower/less redundant

Saving Your ESXTOP Workspace
If there is a group of metrics you commonly add/remove in ESXTOP, you'll notice you have to configure them each time you run ESXTOP. Save your workspace permanently by running ESXTOP, choosing your preferred settings, & then hit the 'W' key to save the settings to a configuration file located at ~/.esxtop3rc or /root/.esxtop41rc. Future ESXTOP sessions will be run with your preferred settings.
More vQuotes

Network Interface Cards

VMware virtualizes two Network Interface Cards (NICs) from the hardware world:
1. The vlance adapter (a virtualized AMD 79C970 PCnet32 adapter)
2. The e1000 adapter (a virtualized Intel e1000 adapter)

The remaining vNICs VMware offers are built from the ground up, including the VMXNET3, the third generation of paravirtualized NIC adapter from VMware.
More vQuotes

VMware VI3 license files

VMware VI3 license files by default are in UNIX format, without DOS/Windows return codes at the end of each line. DO NOT edit license files using Notepad or the license file may become corrupt and unreadable by the VMware License Server. Use WordPad or a third-party text editor that supports UNIX newlines.

"Oh, and by the way," the same applies to ESX kickstart files.

http://kb.vmware.com/kb/8996281
More vQuotes

CHAP for iSCSI security

ESX can be configured to use CHAP for iSCSI security. CHAP authenticates with a 3-way handshake at the time of the initial link, and may happen again any random time afterwards. The verification is based on a shared secret (essentially, the CHAP password). CHAP provides protection against playback attacks by incrementally changing the identifier and by using a variable challenge value.
More vQuotes

Microsoft AD authentication

Integrating Microsoft AD authentication in the ESX Service Console used to be somewhat of a daunting task. Today, the steps have been greatly condensed & I find it a cinch:

1. Create a local user account on the ESX host for each AD user account you would like to authenticate
2. Use esxcfg-auth to configure the ESX host to be AD integrated

Or, implement vSphere 4.1's new AD integration feature via the vSphere Client
More vQuotes

Unable to remove a vDS

Problem: You're unable to remove a vDS.
Error: "The resource vim.dvs.distributedvirtualport xxx is in use" (but it's not!)
Resolution: It's a bug. One of the following will safely fix the condition:
1. Connect directly to the host using the vSphere client and perform the necessary removal.
2. Click on the host Configuration tab, vDS button, Manage Physical Adapters. Perform the necessary removal.
More vQuotes