Copy & Paste option is disabled in vSphere Client 4.1 – default

By | Tuesday, September 21, 2010

Yesterday we upgraded one of our vSphere Clusters to 4.1 – it went smoothly πŸ™‚

But today the users reported that they weren’t able to use cut % paste between the guest and their computer using the vSphere Client (Console).

After a quick google we found that VMware has tightened the vSphere security by disabling this feature. See VMware KB 1026437.

If you need the cut & paste functionality you can enable it again on the guest or host level.

For a single VM:

  • Using the vSpher Client logon to your vCenter server.
  • Poweroff the VM.
  • Edit the VM’s settings
  • Navigate to Options > Advanced > General
  • Click Configuration Parameters
  • Add the following rows, by using Add Row –  false  – false
  • Click OK twice to close the dialogs and save the changes.
  • PowerOn the VM

For all VM’s on a host ESX/ESXi

Must be done on all hosts, so you don’t loose the functionality when the VM is migrated to another host.

  • Open a SSH to the host ex. using Putty
  • Open /etc/vmware/config in your favorit editor .
  • Add these lines to the file"FALSE""FALSE"
  • Save and close the config file. Cut & Paste will work after a VM powerson, reboots or resume.

7 thoughts on “Copy & Paste option is disabled in vSphere Client 4.1 – default

  1. ubergeek

    We have SSH disabled on vSphere 4.1 (as a best practice) is there another way to edit the /etc/vmware/config file? vMA perhaps?

  2. A. Mikkelsen Post author

    Not sure.
    Couldn’t find anything on Google and haven’t tried.

    On how many hosts do you need to change the config file on?

    A. Mikkelsen

  3. Sonu

    Thanks.. was looking for this.
    But the copy paste works only one way – from VM to host. Does not work the other way around.
    Any ideas?

  4. A. Mikkelsen Post author

    For me it works both ways..
    Try using “Right Click”+ Copy / Paste.
    That’s how i do it.

    A. Mikkelsen

  5. A. Mikkelsen Post author

    Hi Andrew,

    There is no quick way of doing this for 48 hosts.

    But you may want to look at using plink through PowerCLI.
    This is you only option for automating the task, as I see it.

    We have decided not to enable it in our environment 220+ hosts πŸ™‚

    A. Mikkelsen

Leave a Reply

Your email address will not be published. Required fields are marked *