Hi aloof,

Not sure what you mean by the example you gave. The free version of ESXi can only be managed using the corresponding management client which only allows management of a single server. To manage multiple servers using vcenter as well as to get read/write access to the hypervisor APIs so you can invoke them directly, you must upgrade to one of the paid licenses.

Not sure what you mean by the example you gave

He's pointing to the fact that:

* ESXi 5.5 creates version 10 Virtual Machines

* Version 10 virtual machines can only be edited by the Web Client, not the "legacy client", as version 10 machines are "new features".

* The Web Client cannot be used on the free edition

* Ergo, the free edition creates machines it can't use

It seems to be a known problem, and a glaring one at that.

Hmm...VC can be evaluated for 60 days.. if you don't want to go the Windows route you can try using the virtual appliance.

Regards

Girish

Also found this blog post:

VMware Front Experience: How to update your standalone host to ESXi 5.5 - beware of missing drivers and do NOT upgrade v…

"What if it is too late? You have ignored the warning in the vSphere Client and have upgraded the virtual hardware and can now no longer edit its hardware? There is no menu item available todowngrade the virtual hardware of a VM, so we need to use some workaround. I'm sure that there are several ways to fix that, but what will definitely work is the following: Create a new VM with the same hardware specifications (no. of vCPUs, RAM size, disk and network controller type) than the original upgraded one. Then attach the hard disk(s) of the original VM to the new VM. The new VM will have a different MAC address (which can be manually set to the original value) and BIOS UUID, but this is better than nothing ..."

Regards

Girish

You can use the latest version of VMware Workstation to manage VMs on a standalone esx 5.5 host.  Not a free solution but it beats reloading vcenter every 60 days just for the web gui.

You can use every Vmware prodoct free for only 60 days ..with all feature.

Yours, Phillips

If I were you I would download and install the free vCenter Converter tool.  You can then connect to your host and "convert" your VM from the new hardware version to an older hardware version.  This process is also mentioned in this KB article:  VMware KB:    Downgrading the virtual machine hardware version

Josh26, ESXi 5.5 does not actually create VM's with V. 10 hardware.

You can not select it in the creation process either (GUI) .  Highest versjon you can select is V8.

So when you create a VM it s max HW V. is 8.

You have to manually "Upgrade Virtual HW" to 10, to get a v. 10 HW VM.

Anyway, if you dont have vCenter or vCenter is unavailable for some reason, you can not edit v. 10 VMs!

I think VMware really messed this up. Either vSphere client should be able to edit v 10 VMs, or they sould provide a web interface directly on the host.

Unless they are phasing out the free ESXi.. To me it seems like they are heading that way, since they releasing 5.5 with this "issue".

Thanks tpatterson this worked for me!

Just leave it at Version 8/9. In ESX5.5 while creating the machines you can select which version to make the hardware.

Simply don't select V10...and you're fine.

But if you need to manage your Version 10 VMs, you can use VMWare Workstation to connect to ESXI, then you can right click -> edit the properties of the V10 VMs.

Edit: Just saw Josh's post. Right on.

Guys :-

Here is the thing. We need to get down a step beneath the internet facts friends.

.vmx is just a file that contains the information of Virtual Hardware, memory , mac etc. Remember the VMDK or the disk has nothing to do with the Hardware version.

If you have a VM made with version 10 , all what needs to played around is the VMX file. Here is what you should do:-

( I have took an eg for a VM named TST1 and VMDK name tst1.vmdk

The VM is powered off at this point:-

1) Browse the folder on Datastore where the VM is residing

2) Copy your VMDK for the VM to a diff location / Datastore

3) Remove the the VM from inventory and delete the remaining VM files and Folder.

4) Create a new VM same name and specs HW version 9 or below ( NOT 10).

5) Now attach the same disk from the older machine

6) Power on the VM and take a deep breath

Let me know if in case someone needs any more help on this..