• VMware ESX
  
• VMware Thinapp
  
  
• VMX Syntax
  
• VMware Files
  
• VMware Logging
  
• VMDK Repair
  
• VMware Player
  
• VMware Workstation 5.5 Linux
  
• VMware Workstation 5x Video Acceleration
  
  
• Offline Domain Controller Maintenance
  
• FreeSCO Router
  

• VMware Server 1.0.x - Ubuntu
  
• VMware Server 1.0.8 - Ubuntu Hardy
  

VMware Server URL:
	https://hostname:8333/
	https://hostname:8333/vmware/en/

	The VMware Management Console connects to the VMware Server service
	by default on TCP 902. This is not the web MUI port.

Create VMware VMs Online for VMware Player:
	http://www.easyvmx.com/

VMX File Parameters:
	http://sanbarrow.com/vmx.html

Tips and Hints:
	http://trivore.com/vmware/esx20.html

To Configure VMware Management Interface:
	/usr/bin/vmware-config-mui.pl         (linux)
	/usr/local/bin/vmware-config-mui.pl   (debian)
	https://hostname:8333/

VMWare Appliances directory:
	http://www.vmware.com/vmtn/appliances/

--------------------------------------------------------------------------------

VMware Workstation 5
Setting a Clone Template

Choose: VM > Settings > Options > Advanced

When you create a linked clone of a virtual machine, the clone depends on the
parent virtual machine to function. If a linked clone is unable to access the
parent virtual machine or the snapshot on which the clone is based, the clone
no longer operates. You can avoid this problem by designating the parent virtual
machine of a linked clone as a template.

Normally, to clone a virtual machine, you must have write access to that virtual
machine. A virtual machine that is designated as a clone template may be cloned
by users who do not have write access to the template virtual machine.

To designate this virtual machine as a template, select Enable Template mode.

In order to protect linked clones, a template virtual machine cannot be deleted
or added to a Team, nor can any of the template's snapshots be deleted. For
more information on linked clones, see Snapshot Details and the Workstation
User's Manual.


Note:
	When you take a snapshot of a running VM, you will get the VM in it's
	running state when you choose that snapshot.

--------------------------------------------------------------------------------

Cloning and Snapshots

Snapshots are sequential snapshots of a VM in time. With cloning, you can start
from a base template and branch out to different paths with different purposes,
with snapshots, each successive snapshot will be like the one before, only with
additional hard disk (VMDK) changes. Using Linked Clones is more like a binary
tree where Snapshots are more like a linked-list...

Snapshots are useful to continuously return to a certain state, for instance,
before an application is installed to troubleshoot the installation process.
Cloning is useful to run seperate VMs, all based on the same parent, to save
disk space for instance.

VMware Workstation operates more efficiently with snapshots disabled. If you do
not need snapshot functionality, disable it for better performance.

--------------------------------------------------------------------------------

Documentation Template:

Name of the VM (virtual machine).:  [vm###]
Creation date for this file......:  [dd-Mmm-yyyy / creator's name]
Last update of this file.........:  [dd-Mmm-yyyy / updater's name]
Business purpose of this VM......:  [short description]
Responsible person(s) for this VM:  [name, contact (email and/or telephone)]
OS name and version in this VM...:  [OS name, update level]
Installed core application(s)....:  [app1, app2]