You are correct. The C# client does not work with 6.5 and there is a long list of features (passthrough for one) that does not currently work in the HTML5 client. I won't be upgrading until that missing feature list gets drastically reduced.Someone please correct me if I'm wrong, but looks like this is the end the road for the C# client (which we were already told about). I just updated vCenter to 6.5 and the latest (last?) C# client gives a generic error when trying to login.
I agree, however if this is for a lab setup then supportability may not be an issue for alot of us."Works" and "supported" are very different things.
That was the intent of my post. I couldnt care less if my config is supported, as long as it works.I agree, however if this is for a lab setup then supportability may not be an issue for alot of us.
VMware doesn't update the HCL, the vendor does. Understandably, if you're Dell you're going to test currently shipping product first and may or may not get to EOL product at all.This may just be something that's gonna take time, but it seems that VMware may have dropped support for the Xeon 5500/5600 series processors for a lot of vendors:
VMware ESXi 6.5 - Unsupported Hardware
The very popular (on this board) Dell R610/R710 servers are on this list as not being supported in vSphere 6.5.
Though, the Dell 13th generation servers are also on this list, which makes no sense unless VMware is just lagging with validation testing.
What do you mean by 'break the license script'? You will require 6.5 keys.@ruffy91
thanks
so esxi will upgrade in place, and the vcsa will install a new vm and migrate the old vcsa in if you select it right?
anyone have an idea of if the esxi upgrade will break the license script?