'''Error connecting: Cannot connect to host...''' or '''Can't connect to MKS...'''
* This is caused by a TCP connection failure to the ESX server the VM is hosted on. Using telnet or a port test utility, confirm you can connect on both TCP 902 and 443 from your machine to the ESX server.
* If the problem is affecting a single ESX that previously worked, [[ESX#VMware_Management_Agent_Restart|restart the management services]] on that ESX
== Can't Deploy VM ==
#* EG <code> scsi0:0.fileName = "MyVM-flat.vmdk" </code> ←←←←←← Base disk file ''(no snapshot running)''
# If there's no snapshots running, but snapshot files exist then the files can be deleted (if you're sure!)
== Can't Customise ==
** The virtual hardware has changed (especially disk type) since the original machine was created
** Sysprep can't customise the machine because it doesn't have administrator rights, this can occur where a DC's users have been offloaded to [[Acronyms#L|LDS]]
== VMTools Automatic Cursor Release Not Working ==