Things that are broken in vSphere 6

[unsichtbare]

I put this here because there isn't a catch-all for vSphere 6. I am not complaining, I would like to start a constructive thread so, hopefully, these issues will be fixed in U1!

Currently broken by my testing:

1. vCLI session authentication vSphere 6.0 Documentation Center
2. "Use Windows session credentials" - in any interface
3. vicfg-cfgbackup
4. Virtual Machine CPU limit - applies but will not remove - supersedes Resource Pool limit, even if VM limit is greater than Resource Pool Limit

[DavoudTeimouri]

Thank you for sharing your test results and the issues.

I hope, VMware engineers read this thread and release fixes with next patch.

Please share me other issues and bugs if you found on your test environment or production.

I'm going to test it but it's not possible detect all issues on a test environment.

[David_Y]

How about the "Revert to current snapshot" button NOT being greyed out when no snapshot exists (easy way to tell there is no snapshot)

No ESXi 6.0 selection in update manager to limit patches to this version only

While I'm mentioning it the web client is still the worst piece of junk to be forced down our throat and is worthless if you have an environment bigger than 2 hosts....  The C# client should be primary and the web client as a back-up/misc user option for people that play on ipads all day.

[unsichtbare]

Hadn't noticed the snapshot thing. Thanks.

Add to the list: Lack of health status in the C# Client after join vCenter. Since Health Status exists with standalone ESXi, I have to believe that this is just punitive behavior on the part of VMware developers regarding those of us who won't/can't use the web-client!