To resolve you use the vCenter Managed Objects Browser (MOB).
Note: When using the MOB to make changes, users will not be prompted for confirmation before making any changes, including removing roles. A custom role can not have privileges higher than the CloudGlobalAdmin role.
First to view all your existing roles in your browser go to;
In the event you are unable to upgrade before the End of General Support (EOGS) and are active on Support and Subscription, you have the option to purchase extended support in one year increments for up to two years beyond the EOGS date.
Expect this to be more costly than general support.
SLA’s are more akin to that of basic support rather than production support
Annual security patch. Includes catastrophic/critical security fixes only
Ability to create hot patches for Severity 1 issues only
Technical Guidance for vSphere 5.5 is available until September 19, 2020 primarily through the self-help portal.
During the Technical Guidance phase, VMware does not offer new hardware support, server/client/guest OS updates, new security patches or bug fixes unless otherwise noted.
For example, there was no SPECTRE/Meltdown security patches released for vSphere 5.1
It’s not only the core vSphere 5.5 products that are affected, as we can see from the End-of-Support tracking page provided by virten.net. There are other VMware solutions that you have deployed that may also need upgrading.
So I hit an interesting issue whilst performing a VMware upgrade from 4.0 to 5.5. There was a legacy issue left where vCenter had lost its knowledge/configuration of the DVS Setup.
Im not entirely sure what happened or when, as it was an existing environment, I only know I had to fix it. (Many thanks to the help from my good friend over at www.vmtechy.com for refreshing me on the ESX 4.0 command line to fix this).
Within the vCenter Client, on the host summary tabs.