I have a esxi 6.0 server setup in my lab with 2 physical drives in it.

1. Remote Desktop Client

This Post is purely to easy of vSphere Admins who want to download the VMware vSphere Client. I have athered the Download link of all versions of vSphere Client starting from vSphere Client v4.1 Update 1 to the latest release vSphere Client 6.0 Update 3. Because vSphere Client is based on the Adobe Flex platform, the operating system (OS) must have Flash installed. For vSphere 6, the vSphere Client requires. How to Deploy OVA / OVF Template Using VMware vSphere Web Client. August 22, 2014. In the past, these templates could easily be deployed utilizing the VMware vSphere Desktop Client. With the release of ESXi 5.5, VMware has been making a large push to utilize the web client.

Datastore1 = 500GB & Datastore2 = 1TB

I am trying to create a new VM with a 2 virtual disks.The 1st vdisk is 20GB and will exist with the vm machine files on Datastore1The 2nd vdisk is 500GB and will be on Datastore2.

If I use the 'old' vSphere thick client with the above detailed configuration it creates the VM exactly as it should. However when trying to create it using the vSphere web client the 2nd vdisk is created on Datastore1 even though Datastore2 is selected as the destination. Likewise if I select to create vdisk1 on Datastore2 and attempt to put vdisk2 on Datastore1 it creates both on Datastore2.

Remote Desktop Client

It would seem that it only allowing me to create vdisk's on the same datastore as where the VM machine files are being stored along with the primary vdisk.

I've heard that the 6.0 vSphere web client has some bugs in it, but I can't find anyone else reporting this odd behavior which I find surprising if it were a bug.

Has anyone seen this before or knows if there is a setting I've missed somewhere to allow virtual disks to be created on a different datastore from where the VM machine files & primary vdisk is?

1 Answer

This is definitely a bug because the API allows specifying separate locations for each virtual disks and the virtual machine files.

If you connect directly to an ESXi (located at /ui'>https://<server-hostname-or-ip>/ui) than you are using the ESXi Embedded Host Client. It is distributed as officially supported product and also as a Fling, which is VMware's apps developed by internal engineering teams but not officially supported. The good news is that you could report bugs on the VMware's flings portal at https://labs.vmware.com/flings/esxi-embedded-host-client#bugs

By the way I think this is a known issue reported by others. If you go to https://labs.vmware.com/flings/esxi-embedded-host-client#comments and search for I cannot add disk from a different datastore from where a VMis installed you'll find issue similar to yours.

Considering the issue is fixed you could upgrade your client to the latest Fling. It is distributed as a VIB which you could install on your ESXi.

Not the answer you're looking for? Browse other questions tagged esxivirtual-diskvsphere or ask your own question.

I physically can't do my fucking job with the web client

All I want in this fucking life is to add a few datastores to the vsc backup job.

That's all! 4 fucking clicks on the normal client! But what a joy, you can't use the normal client with vsc anymore and you are forced to the web class client.

30 minutes later it finally logs in and I can access the back up job, click edit and it never opens.

90 minutes. 90 long fucking minutes I am trying to do what took 4 clicks on the normal client.

I still can't do it , I'm reading commands for the vsc powershell to try and work around the shit web client.

I seriously can't understand how retarded can you be and force your clients to work with a shit web client,

The only feature the web client has is a rope to hang myself with

EDIT: Thanks for popping my gold fellow hater of shit web clients!