VMware makes periodic updates to the ESXi Installable version you can download. This page was created to help track and locate those.

Use these numbers to determine when a system was patched last and to make sure the VMware Infrastructure Client is the right one.

Best Practice:

ESXi: Run the VMware Infrastructure Update tool from a windows management station with the VMware Infrastructure Client every month.

ESX: Use vCenter Update Manager to scan and remediate ESX hosts when new security patches are available.

How to Check the Version Numbers:

1. Download the VMware Infrastructure Client from the Web User Interface.
   For example: https://ESX-HOST-IP-ADDRESS/client/VMware-viclient.exe
2. Start the VMware Infrastructure Client
3. Click the Help Menu
4. Select “About”
5. Note the Version and Build for both the Client and Server.
6. Compare to list below to ensure they are at same release.
7. If you update the Server you should connect to the Web User Interface and download the latest VMware Infrastructure Client.

Latest Install ISO is VMware ESXi 3.5 Installable Update 4 Build Number: 153875
Released: (2009.03.20)

ESXe350-200907401-O-SG – PATCH Build 176894 (2009.05.28) – VIC 147633 – Tools 176894 <– Latest Patch

ESXe350-200906401-O-BG – PATCH Build 169697 (2009.05.28) – VIC 147633 – Tools 169697

ESXe350-200905401-O-BG – PATCH Build 163429 (2009.05.28) – VIC 147633 – Tools 158874
ESXe350-200904401-O-SG – PATCH Build 158874 (2009.04.29) – VIC 147633 – Tools 158874
ESXe350-200904201-O-SG – PATCH Build 158869 (2009.04.10) – VIC 147633 -
ESXe350-200903201-O-UG – UPDATE Build 153875 (2009.03.30) – VIC 147633 <– Update 4
ESXe350-200903411-O-BG – PATCH Build 153840 (2009.03.20) – VIC 119801
ESXe350-200901401-O-SG – PATCH Build 143129 (2009.01.30) – VIC 143129
ESXe350-200811401-O-SG – PATCH Build 130755 (2009.12.02) – VIC 119801
ESXe350-200810401-O-UG – UPDATE Build 123629 (2008.11.17) – VIC 119801 Update 3

The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the VMware Update Manager Administration Guide.

ESXi hosts can also be updated by downloading the most recent “O” (offline) patch bundle from http://support.vmware.com/selfsupport/download/ and installing the bundle using VMware Infrastructure Update or by using the vihostupdate command through the Remote Command Line Interface (RCLI). For details, see the ESX Server 3i Configuration Guide and the ESX Server 3i Embedded Setup Guide (Chapter 10, Maintaining ESX Server 3i and the VI Client) or the ESX Server 3i Installable Setup Guide (Chapter 11, Maintaining ESX Server 3i and the VI Client).

Note: ESXi hosts do not reboot automatically when you patch with the offline bundle.

Reference:

http://support.vmware.com/selfsupport/s3portal.portal?_nfpb=true&_windowLabel=SearchPatch&SearchPatch_actionOverride=%2Fportlets%2Fpatchupdate%2FfindPatchByProductVersion&_pageLabel=s3portal_pages_downloadPatch_page&version=3.5&product=ESXi%20(Embedded%20and%20Installable)

VMware Converter Standalone

VMware converter is used for migrating Physical servers to Virtual Machines, Virtual Machines to Virtual Machines.

Directions for conducting a V2V or P2V for Windows Servers

1. Update or Open a tracking ticket to track progress
2. Ensure system is documented and monitored on portal
3. Notify stakeholders via DL – setup DL if needed
4. Login to the Machine to be converted
5. Run defrag and diskcheck if possible
6. Run Microsoft Update
7. Do a reboot test to ensure machine stability
8. Download VMware Converter Standalone version 4 – VMware-converter-4.0.0-146302.exe
9. Download Sysprep tools – unzip but do not run
10. Download NewSID – unzip but do not run
11. Download and run BGinfo – apply
12. Download and run treesize free and clean up unneeded files
13. Install VMware Converter
14. Copy Sysprep files to correct location – c:\documents and settings\all users
15. Launch VMware Converter
16. Import Machine
17. Select the device type; Physical Computer, Virtual Computer from ESX or VMware Workstation.
18. Enter in the remote IP address of the target:
19. Do not select Automatically uninstall the files when the import is successful
20. Select all the drives you wish to migrate to the new Virtual Machine
21. Select ESX or Virtual Center
22. Enter the Virtual Center and user credentials
23. Select the Virtual Machine name
24. Select the ESX host
25. Select the appropriate DataStore
26. Select the appropriate network
27. Check the box install vmware tools
28. If you desire to customize the settings, check the box.
29. Select Finish
30. When completed test new machine and configure.
31. Run newsid if new host names is needed… Keep in mind you cannot have two machines with same name or IP on same network.
32. Run BGinfo and apply again.
33. Verify reboot test and monitoring is functioning.
34. Verify system time.
35. Adjust services as needed.
36. Remove old hardware’s software.
37. Notify stakeholders when old machine is off and new machine is on.

See also: http://communities.vmware.com/thread/129871

When logging into a PanoLogic virtual desktop console for the first time…

The default display resolution was 1024×768 standard 4:3 XGA

The HP w1707 LCD monitor has a native resolution of 1680×1050@60Hz 16:10 WSXGA+

Using the pano logic control panel I was only able to set the max resolution to 1440×900@69Hz 16:10 WSXGA

http://www.panologic.com/

List of Supported Reslutions: http://help.panologic.com/2.6/wwhelp/wwhimpl/js/html/wwhelp.htm#href=Introduction/Supported_Monitor_Resolutions.html

http://www.vmware.com/support/product_renaming.html

Old Name –> New Name

VMware VirtualCenter –> VMware vCenter Server

VMware Lifecycle Manager –> VMware vCenter Lifecycle Manager

VMware Converter –> VMware vCenter Converter
(for the version integrated into vCenter)

–> VMware vCenter Converter Standalone
(for the separately downloadable version)

VMware Lab Manager –> VMware vCenter Lab Manager

VMware Stage Manager –> VMware vCenter Stage Manager

VMware Update Manager –> VMware vCenter Update Manager

VMware Site Recovery Manager –> VMware vCenter Site Recovery Manager

VirtualCenter Foundation –> vCenter Server Foundation

VMFS –> VMware vStorage VMFS

VMware Virtual Desktop Infrastructure –> VMware View

Virtual Desktop Manager (VDM) –> VMware View Manager

VMware Administrator Interface –> VMware View Administrator

VDM Agent –> VMware View Manager Agent

VDM Web Access –> VMware View Portal

VDM Client for Windows –> VMware View Client for Windows

VDM Client for Linux –> VMware View Client for Linux

Refer to page 136 of http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_resource_mgmt.pdf

Some examples:

With 1 vcpu and 256MB of RAM; the VM kernel requires 87MB for 32 bit VM’s and 108MB for 64 bit VM’s.

With 8GM of RAM and 1 vCPU you’ll need 188MB and 209MB for 32 and 64 bit.

With 4 vCPU’s and 8GB of RAM you’re looking at ~360MB for a 32 bit VM and 431MB for a 64 bit VM.

Note: memory overhead for 32-bit VMs generally increased between 3.0.1 and 3.5 while 64-bit overhead generally decreased.

ESX 3.5 Overhead

ESX 3.0 Overhead

Here’s an example hosts.allow:
#begin
sshd:management.host.com:allow
sshd:ALL:deny
xinetd:management-host-ip-or-fqdn-hostname:allow
xinetx:ALL:deny
httpd:management-host-ip-or-fqdn-hostname:allow
httpd:ALL:deny
#eof
But even this may be too simple.

Reference:

http://www.dell.com/downloads/global/…/tnc/dell_vmware_certified_deploy.pdf

http://communities.vmware.com/thread/182964?tstart=0

What this will do is allow all hosts to ssh into the system while only allowing VI client connections from the virtualcenter server. This means you pretty much have to go through virtualcenter to manage the system.