"So do I have vmware tools installed or not ?"
a) Can you share what the Guest OS is (version helps)?
b) Did you recently install VMware tools onto the Guest OS?
c) I was told that it's possible that restarting the "vmtoolsd" service in the Guest OS may remove the issue.
Can you paste a screenshot of the Action Menu (Right Click) you get on an orphaned VM, for our reference?
Already removed the orphaned ones. Everything was grayed out in the Action Menu. Could not even drag & drop them to different folder so I could've removed the folders with the VMs as instructed in some KB.
While migrating VMs "details" column in Recent tasks is empty. However, details are shown in monitor -> tasks&events -> tasks.
Also, selection of columns in "recent tasks" reset every time you restart the browsers.
If you have further feedback, you can send me a direct message and then I can provide you my email address to make it easier to communicate.
I've noted both of these issues and we'll see if we can fix them in the HTML5 based vSphere Client.
I don't wanna be mean or anything but the HTML client is so annoying to use. When I create a VM and want to attach VMDKs, I have to create them as thin-provisioned with less than the remaining amount of space on datastore1 (1TB SSD for ds1 with 70GB remaining) so 16GB thin for each of my 6TB HDDs (even though they are BLANK), then manually change them to the full size AFTER I have specified that they are thin then change them to thick (if I so desire, which I do). After I did this and specified to create each new VMDK on each individual datastore (ds2 through ds7), I find out that it put all the VMDKs on ds1... really? That is not what I asked for at all.
Then there's another longstanding issue where if I edit a VM multiple times, I have to relaunch my browser because I keep getting this error thrown up for no reason: http://i.imgur.com/ikyZM6x.png
So annoying. I want to love the client but it's just so hard when these annoying things happen. So frustrating for what is supposed to be an enterprise product. Both of these bugs happen on Firefox and Chrome. This is practically unusable.
I really want to love this client but you guys are making it so hard. VMware, please make this web client something we can all love.
How do you migrate lest say 50VMs out of 100 from one host to another with web client? Didn't find any other way that migrating them one by one.
NVM: Found it. Altough for some reason "recent tasks" freezed and doesn't show any actions any more.
Strange errors like that are one of the reasons we're trying to step away from the Flash plugin, but that's one I haven't seen before.
Can you describe a little more about this VMDK attaching issue? It sounds like:
1) You created a VM
2) You want to add multiple harddisks on it using the new HTML5 based vSphere Client for vCenter (or are you speaking about the Host Client for managing single hosts?)
3) You do so by going to the VM and clicking "Edit Settings" and adding new disk
4) When adding the new disk, you specify that it should be Thin provisioned, and the Location should be on another Datastore (not "Store with the virtual machine").
Please correct me if my understanding is wrong.
a) What versions are you on: Host, vCenter if applicable?
b) Did this flow work differently on the Desktop client?
c) I didn't quite understand the situation with your datastore's free space and your Thin/Thick decisions. It sounded like your ds1 is a 1TB disk with 70 GB remaining, and you want to create additional VM harddisks which are 6 TBs? I'm sure I missed something here.
d) What prevents you from specifying Thick provisioning when creating the VM: does the UI report an error? What error?
e) When you do change the location (in Step 4), does this new location fail to hold, and the VMDK actually ends up in the same location as the root disk?
I will provide as much information as I can think of. I have a server with a 1TB SSD that ESXi installed onto combined with a datastore with 3 VMs - two tiny VMs and one main VM. I had to re-create my main VM as it got corrupted and required a complete installation. I also have 6 of the same 6TB disk that I use for RAID 10 on that main VM. I create a thick lazy-zero VMDK for the OS on the SSD DS (ds1) however, no matter how I attempted to create VMDKs on the other DSes (ds2 through ds7 all being the HDDs, I attempted thick and thin VMDKs), the web client always put the VMDK files on the original SSD DS if it was thin and if it was thick it simply would not work and would say not enough space (because it attempted to put the VMDKs on ds1 despite me specifying ds2 through ds7 for each of the VMDKs). I have done this same setup before using the web client on a much older version however on this newer version (1.19.0) on ESXi 6.0U3 with the latest patch released on June 6, it does not seem to be work properly anymore. My workaround was to use the desktop client to create thin VMDKs on each of the datastores which did work as expected unlike the web client, although it is unfortunate that I could not create thick VMDKs because of the 2TB VMDK limit of the desktop client. It didn't matter if I attempted to create the VMDKs on the other datastores during creation of the VM or after the VM was already created, the web client still had the same bug - it always put them on /ds1/VMName/VMName_disknumber.vmdk.
As for my other bug, I hope that you are able to replicate (and eventually fix) that as well, as pretty much every time I edit a VM's settings too frequently, it ends up giving an integer overflow as seen in my screenshot here: http://i.imgur.com/ikyZM6x.png.
As for the "flash plugin", I wasn't aware that the HTML 5 client (v1.19.0) made use of a Flash plugin? Am I reporting these errors in the right thread?
Thank you for the details. From the screenshot and description you're definitely talking about the single host management client, we generally call the Host Client. We oftentimes have mixups between Host Client and the vCenter based Web Client and new HTML5 based vSphere Client for vCenter.
We often have different bugs and such from each one so thank you for the details. I will check on this, but 1.19 does look like you're pretty up to date.
Thanks for looking into the bug, I am very glad it is fixed now as of the latest fling version (1.21.0).
Sadly, I agree to the top. It sucks.
IMHO, some things are not meant to be web based.
Here we are 3 years later and are now forced to use a flash based web client to manage 6.5 and the HTML web client is still not fully finished. It takes 5 extra clicks to do anything compared to the thick client.
Not sure why you couldn't port the thick client feel to HTML but you pretty much failed and released a buggy piece of shit product.
VMware likes taking our money but doesn't listen to its community. You should really take note of how Veeam is running a company, they listen to its user community.
Just throwing in my $.02 to tell Vmware how much I despise the web client. I have tried and tried to use it and every time I end up going back to the old Vcenter client.
The web client is slow, buggy, clunky, requires extra clicks to do the same things I can do in the older Vcenter client, and I just can't do "real work" with the web client. I can't imagine using only the Vcenter web client to setup a fresh ESXI environment with even the slightest layer of complication to it.
It reminds me of Outlook Web Access - fine for a quick check of your email when you're on someone else's computer, and good for quick replies and making some minor calendar adjustments, but I'd go crazy if I had to use it as an all day replacement for the Outlook executable that comes with Office.
I wish VMware would just get rid of this web client and stop pushing sysadmins to use it. It's not as popular as VMware thinks it is. My last Vmware conference it was a running joke about how they're were going to do a best practices on it but not enough people would have signed up for it.
When I say "I want a standalone program", I don't mean some cobbled together junk that simply replicates the website look/feel/performance but wraps it in an executable. Don't take the existing crappy web client and make it into a slightly less crappy HTML5 version. The whole "administer your ESXI environment from a web page" is the problem. Take the old VCenter client we all know and love and have been trained on for years and modify the options and tabs so every feature works with 6.5.