Well, while working on a way to get Alterisâ€™ RDP product to automate the install of a VMWare guest, I came across this note in VMWareâ€™s KB:
VMware GSX Server 3.1
To automate the installation of VMware Tools in a Windows guest operating system, you can use the Microsoft Windows Installer runtime engine to install the software silently (in quiet mode). If you are installing VMware Tools in a number of Windows virtual machines, you may want to use the silent install features.
The guest operating system in which you are installing VMware Tools must have Microsoft Windows Installer runtime engine version 2.0 or higher installed. This version is included with Windows Server 2003 and Windows XP. If you are installing VMware Tools in other Windows guest operating systems, check the version of this file:
If you need to upgrade the engine, run instmsiw.exe (instmsia.exe for Windows 95 or Windows 98 guests), which is included with the VMware Tools installer.
For more information on using the Microsoft Windows Installer, go to the Microsoft Web site â€” msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/about_windows_installer.asp.
To install VMware Tools silently in a Windows guest, first make sure the virtual machine's CD-ROM drive is connected to the VMware Tools ISO image (windows.iso, located in the directory where you installed GSX Server) and configured to connect when you power on the virtual machine. Then, run the silent installation on the extracted installation packages. At the command prompt, on one line, type:
msiexec -i "D:\VMware Tools.msi" ADDLOCAL=ALL /qn
The ADDLOCAL option defaults to install all VMware Tools components. You can customize the installation using a combination of the ADDLOCAL and REMOVE options. For information about the features of VMware Tools, see About VMware Tools. You can include or exclude the following features:
ï‚·Â Toolbox â€” the VMware Tools control panel and its utilities. Excluding this feature prevents you from using VMware Tools in the guest operating system, and is not recommended.
ï‚·Â Drivers â€” this includes the SVGA, Mouse, BusLogic and vmxnet drivers.
o SVGA â€” the VMware SVGA driver. Excluding this feature limits the display capabilities of your virtual machine.
o Mouse â€” the VMware mouse driver. Excluding this feature decreases mouse performance in your virtual machine.
o Buslogic â€” the VMware BusLogic driver. Excluding this feature prevents you from using this driver in your virtual machine. If your virtual machine is configured to use the LSI Logic driver, then you may want to remove this feature.
o VMXNet â€” the VMware vmxnet networking driver. Excluding
this feature prevents you from using this driver in your virtual machine.
o MemCtl â€” the VMware memory control driver. This feature is recommended if you plan on using this virtual machine with VMware ESX Server. Excluding this feature hinders the memory management capabilities of the virtual machine running on an ESX Server system.
ï‚·Â Hgfs â€” the VMware shared folders driver. This feature is recommended if you plan on using this virtual machine with VMware Workstation. Excluding this feature prevents you from sharing a folder between your virtual machine and the Workstation host.
To include a feature, use it with the ADDLOCAL option.
To exclude a feature, use it with the REMOVE option.
For example, to install everything but the shared folders driver, type the following on the command line:
msiexec -i "D:\VMware Tools.msi" ADDLOCAL=ALL REMOVE=Hgfs /qn
The SVGA, Mouse, BusLogic, vmxnet and MemCtl features are children of the Drivers feature. Thus, on the command line, if you type:
msiexec -i "D:\VMware Tools.msi" ADDLOCAL=ALL REMOVE=Drivers /qn
You also skip installation of the SVGA, Mouse, BusLogic, vmxnet and MemCtl drivers.
The drivers installed by VMware Tools are not signed by Microsoft. When you install VMware Tools, you are asked to confirm the installation of these drivers. You can prevent these messages from appearing in the guest operating system during installation by completing the following steps.
Now, I am using ESX but it doesnâ€™t seem to matter.Â Yippie!