That's great that it's resolved - but that doesn't help me get it updated/upgraded. As I said, when I tried to install the latest update, it refused to do so because the password 'was expired'. I can't change the password because of the bug, and I can't update/upgrade because it's expired. A catch 22.
A bit it a tangent, but vCenter 6.5 is a train wreck. It has been one problem after another. OVF deployment broke horribly. Consoles crash routinely. The Flash interface crashes routinely. The consoles are hit or miss with regards to changing settings (for example, If I try to change something as simple as what network the vNIC is attached to using the 'Virtual Machine Settings' in the console, sometimes it'll work, but usually, it fails and then the only way to make the change it to power the machine down and use the flash web client - there was actually at least one instance where it failed so spectacularly, I had to delete the NIC and add a new one). You'd think companies like VMWare would learn from the disaster that is Java that you should not rely on other companies (IE Adobe > Flash) for management of YOUR product and expect it to be acceptable. The C# client was SOLID. While I'm running 6.5 in my home 'sandbox' via my VMUG subscription to learn it, based on my learning, there are ZERO plans on the roadmap at this time to move to 6.5 in my customer facing datacenter environment. VMWare should NEVER had canned the C# client. Develop the Web client, for those that want to endure it's suckiness, but keeping the far superior client for those that want to use it.
