![Vsphere 6.0 client create vm copy](https://kumkoniak.com/16.jpg)
![vsphere 6.0 client create vm copy vsphere 6.0 client create vm copy](https://kifarunix.com/wp-content/uploads/2019/07/create-new-vm-directory.png)
![vsphere 6.0 client create vm copy vsphere 6.0 client create vm copy](https://vcdx133.files.wordpress.com/2015/02/esxi_6-0_18.jpg)
The unintended automated collection may not be nefarious. Another admin who is viewing that same console can hit "paste" at a later time and retrieve the data you have accidentally left behind. Also, the clipboard contents may be retained on the guest VM console even after you have cleared the clipboard contents of your local desktop. There could be a process running to collect clipboard contents. Once your mouse hits the window, VM2 has access to your desktop clipboard. Then, you click on the console window for VM2 in order to move it out of the way. You're trying to get into an application on VM1, so you copy the password from your local desktop computer. You have consoles open in vSphere for VM1 and VM2. You don't want that available to any VM whose console window you touch. While operating your normal desktop, you may have copied sensitive data such as a password. When your mouse focus hits a console window, that VM immediately has access to your desktop's clipboard. If I understand correctly, the copy/paste being default disabled is because of the way VM tools operate. It's so useful that Microsoft lets you do it in an RDP connection, even with gigantic files. While recovering files from a clone or comprimised machine, you might not want to connect to the LAN or WAN. The copy/paste or drag/drop into a VM is useful when you can't bring the VM online due to conflicting names/IP addresses.
![Vsphere 6.0 client create vm copy](https://kumkoniak.com/16.jpg)