VMware – Cannot Cut, Copy, or Paste to VM’s

KB ID 0000515

Problem

Ever since ESX 4.1 this feature has been disabled and you have been unable to paste to VM, VMware say in their own documentation:

Source (Page 215 – ESX Configuration Guide ESX 4.1 vCenter Server 4.1).

To turn this feature back ON you have a few choices.

Please be aware: We are talking about copy and pasting TEXT to and from a guest VM NOT files and folders.

Solution

ESX Option 1 (Enable Copy and Paste to VM an individual Guest machine)

Using vSphere 8 or Above

Firstly, you need to shut the virtual machine down > Right Click it > Edit Settings >  Advanced > Add the following TWO attributes and values.

Add in the following two;
Attribute: isolation.tools.copy.disable, Value: false
Attribute: isolation.tools.paste.disable, Value: false

Click OK >  Power the VM back on.

Using HML5 Web Client (Enable Copy and Paste to VM)

Firstly, you need to shut the virtual machine down > Right Click it > Edit Settings > VM Options > Advanced  > Scroll down.

 

Edit configuration > Add configuration params;

Add in the following two parameters then click OK

Name: isolation.tools.copy.disable, Value: false
Name: isolation.tools.paste.disable, Value: false

Using Flash Web Client.

Firstly, you need to shut the virtual machine down > Right Click it > Edit Settings > VMware Option Tab > Advanced > Edit configuration > Add in the following;

Name: isolation.tools.copy.disable, Value: false
Name: isolation.tools.paste.disable, Value: false

 

OK > OK > Power on VM

Using VMware Client (Enable Copy and Paste to VM)

1. Firstly, you need to shut the virtual machine down > Right Click it > Edit Settings > Option Tab > Advanced > General > Configuration Parameters.

2. Select “Add Row” and add the following two options:

[box]isolation.tools.copy.disable

isolation.tools.paste.disable [/box]

Set both these values to FALSE > OK > OK > Power the VM back on again.

Note: Even without these values set, if a VM is vMotioned to an ESX host that has the copy.paste options set in it’s config file (see below) then these features are automatically enabled.

Option 2 (Enable Copy and Paste to VM on an individual Guest machine)

1. You can also achieve the same as above by directly editing the .vmx file for the virtual machine, Add the following two values as shown below:

[box]isolation.tools.copy.disable=”FALSE”

isolation.tools.paste.disable=”FALSE” [/box]

Note: Even without these values set, if a VM is vMotioned to an ESX host that has the copy.paste options set in it’s config file (see below) then these features are automatically enabled.

Option 3 (Enable Copy and Paste on the ESX host for all the VM’s on that host)

Note: This procedure will be removed/reset after an ESX upgrade. (You will need to carry out this procedure again post upgrade).

1. Connect to your ESX server, either directly on the console, or via SSH. and execute the following command:

[box]vi /etc/vmware/config[/box]

 

2. Press i to insert text and paste in the following two lines:

[box]isolation.tools.copy.disable=”FALSE”

isolation.tools.paste.disable=”FALSE” [/box]

Press Escape > then type :wq to save the changes.

Additional Steps for Linux / Ubuntu to allow Copy and Paste to VM

1. Assuming you have the VMware tools installed in your Linux guest VM, if not execute the following command:

[box]sudo apt-get install open-vm-toolbox[/box]

To enable copy paste on the guest execute the following command:

[box]vmware-toolbox &[/box]

One the VMware tools properties page pops up you will be able to copy and paste.

Enabling Copy and Paste in VMware Workstation

Out of the box, this functionality is switched on. However if you lose it then open the virtual machines settings > Options tab > Guest Isolation > Enable the Copy and paste option.

Related Articles, References, Credits, or External Links

NA

VMware Fusion: Not Enough Physical Memory

KB ID 0001715

Problem

I upgraded to macOS Big Sur this week, and was surprised everything still worked! That was until I tried to start up my Windows 1o Virtual machine.

“Not enough physical memory is available to power on this virtual machine with its configured settings.”

Solution

Though it took me a while to ‘fix’, the fix is quite straight forward, I was running version 11 (see Below).

As soon as I upgraded to version 12.

Everything worked correctly. Only version 12 is fully supported on macOS Big Sur.

Related Articles, References, Credits, or External Links

NA

VMware Fusion: Windows 10 ‘Lost’ Mapped Drive to the Host

KB ID 0001394

Problem

My Windows 10 VM decided it was going to do a major update last night, so I let it get on with it. However today I can no longer access the ‘shared’ drive that it had back to the host (my MacBook).

Solution

I’m pretty sure this is the second time this has happened, so after berating myself for not documenting the fix last time, this is the fix. Run Regedit (Windows Key+R > regedit {Enter})

Navigate to: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > NetworkProvider > Order

Locate the PROVIDERORDER entry;

Move the ‘vmhgfs‘ entry, so that it is the first one in the list > OK > Exit the registry editor.

That’s it, no reboot or anything, your drive should start working again.

Related Articles, References, Credits, or External Links

NA

Booting USB: Boot VMware Guest from USB

KB ID 0000250

Problem

Booting USB: Last week I wrote an article about installing Windows PE on a USB thumb drive, after making several trips across the room to test my progress by booting the spare PC with said USB drive, I thought “there must be a simpler way to do this?”.

VMware Workstation guest VM’s do not support booting from USB devices, (its not built into their “BIOS”). However there’s nothing to stop you booting to CD then using that to boot to USB.

Booting USB

1. Download the PLoP Boot manager.

2. When you have downloaded the .zip file extract it, and inside you will find an ISO image called plpbt.iso that’s all we need you can get rid of everything else.

3. Set your virtual machine to use this .iso file as its CD drive.

4. Connect your USB drive to the guest VM by clicking VM > Removable Devices > The device you wish to connect > Connect.

5. Boot the VM with your PLoP CD, image and select USB from the boot options.

 

 

Related Articles, References, Credits, or External Links

NA

VMware ESX Error “cmd addnode failed for primary node: Internal AAM error”

KB ID 0000298 

Problem

Seen in a Virtual Center HA environment – even after selecting “Reconfigure for HA” on the ESX host.

Errors:
cmd addnode failed for the primary node:Internal AAM error – agent could not start – Unknown HA error.
Cannot complete the configuration of the HA agent on the host – See the task details for additional information. Other HA configuration error.

 

Solution

1. How you proceed depends on your infrastructure. If possible, using vMotion/Migrate all the guest machines on this host, to your other ESX hosts. (Note: if that’s no an option you will need to shut down the guest machines).

2. Put the offending ESX host into maintenance mode (Right click it enter select maintenance mode).

3. Assuming you are connected to the Virtual Center, right click the offending host and select “remove”.

4. Then add it back to the cluster (Right click the cluster and select “Add Host”).

5. HA will be reconfigured on the host as its added back in.

 

Related Articles, References, Credits, or External Links

NA

VMware – Ubuntu Screen Resolution Problem

KB ID 0000411 

Problem

I have a guest VM on my vSphere test rig that’s running Ubuntu 10.10. That I use for testing, for a while I could not get the screen resolution above 854×480 (For wide screen or 16:9 format).

 

Solution

Note I’m assuming you already have the VMware tools installed!

1. Shut down your guest machine, open the VMware VI client and go to the settings of the guest machine. go the the hardware tab and select video card. By default it will be set to auto detect, change it to a nice high resolution, and click OK.

Note: For VMware workstation the setting is under “Display” see below.

2. Power the guest VM back on again and now you should have a better range of resolutions.

 

Related Articles, References, Credits, or External Links

NA

Possible bug in VMware Client

KB ID 0000413

Problem

Unable to use multiple console sessions in Windows 7.

1. Seen on Windows 7 x64 Ultimate, with and without aero enabled, on two separate machines.

2. Happens if connected to VCenter OR directly to ESXi (build 4.1.0, 260247)

3. Does NOT happen with the same software from Server 2003. (Same systems, same vesion of the VI client).

4. Does NOT happen on Server 2008 R2 Standard x64 (Same systems, same version of the VI client).

5. Does NOT happen on Server 2008 R2 Standard x64 with Service Pack 1 (Same systems, same version of the VI client).

6. Does NOT happen on Server 2008 R2 Standard x64 aero Enabled with Service Pack 1 (Same systems, same version of the VI client).

7. Does NOT happen on Windows 7 Enterprise (Service Pack 1) x86 (Same systems, same version of the VI client).

Description

 

Related Articles, References, Credits, or External Links

NA

vSphere – Guest VM is shown as (Orphaned)

KB ID 0000414 

Problem

I’ve seen this happen a few times now, while looking at your Virtual infrastructure, one or more client machines is greyed out and shown as (Orphaned).

Solution

If you have many guests VM’s on one host with this problem, you can cure this by removing the parent host and re-adding it to the cluster, then right clicking it and select “Reconfigure for HA“.

Or you can do the following, on a machine by machine basis.

1. Right click the affected VM and select “Remove from Inventory” (nothing gets deleted don’t worry.)

2. Select one of your ESX hosts > Configuration > storage > Right click the storage that holds the virtual machine we are dealing with and select “Browse Datastore” > Locate the machines .vmx file > Right click > Add to inventory > Follow the instructions.

Related Articles, References, Credits, or External Links

For VMware View machines click here

Setup and Configure HP Wireless E-MSM720 Wireless Controller with HP E-MSM430 Access Points

KB ID 0000692 

Problem

We got some ‘demo stock’ in the office this week, I don’t do a lot of wireless, so I thought I would get it setup and have a look to see how easy/difficult it was.

Hardware used

HP E-MSM720 Premium Mobility Controller (J9694A)
HP E-MSM 430 Wireless N Dual Radio Access Point (J9651A)
HP HP 2915-8G-P-o-E Switch (J5692A)

The switch and controller are ‘tiny’ so if you want to put them in a cabinet you will need some ‘big brackets’, (or a shelf). I was disappointed that the controller didn’t have PoE on it (hence the reason we were supplied the switch). I was also disappointed the Access Point didn’t come with a network cable (seriously these things are pennies – and if a client buys hundreds of these things, someone will forget they also need an equal amount of network cables). In addition they are PoE, so you don’t get a power cable (or power injector) – so you cant even power them on without the network cable. That said all the gear is typical good quality HP Stuff. The documentation consists of a “quick setup sheet” for each piece of hardware and all the manuals are Online. I’m not a fan of manufacturers documentation at all, and HP’s is the same as most major vendors, to long, too complicated and to difficult to find what I’m looking for – I spent half a day reading pdf documents just trying to get the guest network working (a feat I will accomplish below with about three sentences and the same amount of pictures!)

Also See: Manually Configuring HP Wireless (MSM 720 controller) for Public and Private Wireless Networks

Solution

Initial Setup E-MSM720 Wireless Controller

1. Connect the controller to your network (Note: Don’t use the two dual personality ports 5 and 6).

2. The controller sets itself up on 192.168.1.1 put yourself on the same network range (see below).

3. Connect to https://192.168.1.1.

4. The MSM720 Default username and password are both admin.

5. Accept the EULA > Skip Registration > Set country > Save > Set the new password > Save.

6. Configure Initial Controller Settings > Start.

7. Set System name > Location > Contact > Login Message > Next > We’ve just set the Password so leave it blank > Next.

8. Enable/disable management interfaces > Next > Configure the network interfaces > Next.

These are allocated as follows, (out of the box!)

And are controlled by these two settings,

9. Set the time and timezone > Next > Apply.

Configure a Corporate WLAN with the E-MSM720 Wireless Controller

1. If not already there, select ‘Automated Workflow’ > Configure a wireless network for employees > Start.

11. Create an SSID > Next > Set the WPA Key > Next.

12. Choose what access points to apply these settings to > Next > Apply.

Note: At this point I had not powered on or touched the access points, so I just selected ‘All’.

Configure a ‘Guest’ WLAN with the E-MSM720 Wireless Controller

I had a nightmare getting this running, until I fully understood the VLAN, IP address and interface allocation, but if you set things up as specified above it will just work.

1. Automated Workflows > Create a wireless network for guests > Start.

2. Create and SSID > Next > Configure guest authentication (or leave open) > Set IP Settings for clients > Next.

3. Select APs to apply to > Next > Apply.

Setup the HP E-MSM 430 Wireless N Dual Radio Access Point

Well you have already done all the work! Simply connect the AP to a POE capable network outlet.

By default the AP is in ‘Controlled’ mode, so it will start looking for a controller as soon at it powers on, it can take a little while to boot (go get a coffee), you will see it appear in the controllers web interface when its pulled its configuration down.

Updating Firmware MSM70 and MSM430

Very slick! update the firmware package on the controller, and it will update all the access points for you.

Final thoughts

This is good quality gear, it has built in support for IPSEC, SSL, RADIUS and a myriad of other features that you would expect to find on an enterprise class wireless solution. HP might be concerned by their lack of wireless sales, but they could make the experience with these things better by making the web interface easier to navigate, (ask someone who has never used it before to delete a wireless network! – over 90 minutes it took me to locate the VSC bindings section to remove that!) I’ve already mentioned the documentation, I appreciate that it needs to be comprehensive but come on!

Related Articles, References, Credits, or External Links

HP E Series Wireless – Cannot Access Local LAN

Manually Configuring HP Wireless (MSM 720 controller) for Public and Private Wireless Networks