Excellent, this solves 50% of my complaints. My suggestion to VMWare it when you turn OFF Settings->Show only recent objects, then there should disappear "More VMs", "More Storage" and "More Networking" link, as those links are not needed anymore.
1) Ok.. I'm getting pretty confused which browser and which web client I should use.
3) Tab jumps to the next line
"I am curious why you chose the Windows version for a new deployment, rather than the Appliance. We have 3 v6.5 appliances joined to AD with no issues. We did however have some join issues, but it turned out we had some reverse name resolution issues. "
I chose windows version simply because I the brand new vcsa wouldnt deploy. Tried it three times and got different error message every time.
In 6.5 vCenter with this web client I am having some difficulty in figuring out how to connect a remote console to ISO on local machine so that I can power up VM and boot to the ISO.
When I right click the VM I see an error stating VM is powered off, power it on to connect.. this has never been the case in the past using thick client, not really sure about older web clients
When I look at summary tab of VM, I see the hardware drop down, I expand it and see CD ROM options to connect remote console, but none of these options allows this, all I see is the following screen shot:
I did power the VM on and launched the remote console, but the console itself doesn't offer any options the way the thick client remote console did, all I have is a view, no options.
HOW DOES ONE CONNECT TO AN ISO ON LOCAL MACHINE AND BOOT TO IT?
So it seems that mouse isnt working on web client when you open a console to VM. So you need to use host client for that. Are you fucking kidding me?!
Start up VM, mount ISO, reboot VM. vmware logic.
First of all, I have found that the host client is not much better, if at all, regarding the mouse issue - before or after VMware Tools!
A few weeks ago, another user pointed out that making the client/browser window exactly the same size as the VM helped with mouse issues. It does!
This is far from a justification or defense of a half-baked product (web-client) forced on a user community, but it is a work-around.
One no longer connects to a local ISO. It's true that the datastore ISO is faster, but the local ISO is so convenient, its loss will be missed.
Perfect example of an engineering team that either:
- Does not use the product themselves
- Does not care about the user community at all
Isn't it time that this thread/discussion got moved to vSphere 6/ESXi 6 as the issues people are discussing are current?
The removal of "attach to local ISO" is another consequence of the removal of CIP, which continually had issues with compatibility (both browser and OS versions), and intermittently working. The decision was made to remove CIP because of the issues there.
This functionality is now provided through VMRC, due to technological reasons. https://www.vmware.com/go/download-vmrc
VMRC may also have better mouse compatibility, but VMware Tools on the guest OS will also make a difference, if it's not already installed.
I totally agree. I have tried to work with it for some hours and I am close to give up. Errors and restart of browser..... it sucks.
It's gotten worse over the past few months. I actually like the layout of the web client (and prefer it over the C# client AND the HTML5 client), but the constant crashing and just weird stuff has gone over the top. At some point the client integration plugin just stopped working. No checkbox authentication, no OVA deployment, I doubt ISO connectivity will work. Multiple machines, multiple browsers. I deployed the HTML5 fling and it worked for a few days and then stopped. I upgraded my dev vCenter to 6.5 and that doesn't work either.
Get your act together, VMware. This is years of ridiculousness.
Could you post your issue regarding the Fling to the Fling's comments page here: https://labs.vmware.com/flings/vsphere-html5-web-client#comments
We'd like to keep everything in one place. In particular we'd be interested in details about your environment:
1) VC version
2) Windows vs VCSA
3) External PSC?
4) Fling version?
6) Any difference between when it worked vs now?
7) Screenshots would help too, you can post them into this dedicated thread: https://communities.vmware.com/message/2638987#2638987
Regarding the issues with the Client Integration Plugin, this is one of the primary reasons we removed it in vSphere 6.5.
Web client is horrible. They need to bring back the hard client. Response time sucks, navigation sucks.