You may see ‘Adobe Flash Player Out of Date’ on Chrome when you open vSphere Web Client. Click the text Chrome will update Flash Player automatically. But in some cases it doesn’t work due to maybe your Chrome is controlled by company policy or internet problem to Adobe.com. I found an article to show how to offline fix the issue. You can download Flash Player for Opera and Chromium-based browsers – PPAPI in official Adobe KB article.
You may also want to check out my other articles about Flash issue on browsers.
Flash menu appears when right click on vSphere Web Client in Chrome
Cannot open vSphere Web Client on IE11 on Windows 8.1
There is a KB describes how to fix right click issue in IE on vSphere Web Client. But my problem was in Chrome. I searched a lot in internet but no lucky till today.
The problem was flash menu appears when I right click anything in vSphere Web Client in Chrome. I have two computers that both has Chrome installed but one has issue, other one works fine. I compared version of Chrome, noticed working one was 55.x, problematic one was 49.x. The issue gone after upgraded to 57.x.
After dig into that problem, looks like Google fixed the problem on version 54.0.2840 that there was a bug related to right click. Check out release notes here.
Just noticed a issue that nothing reported in ‘Hardware Status‘ tab of ESXi hosts in vSphere Web Client. KB 2112847 gives a solution but not works for me. The feature can be used to monitor hardware failures. I figured out a way to workaround it. You just need to login by Administrator account and click ‘Update‘ button under ‘Monitor‘ – ‘Hardware Status‘ for each ESXi host. You will get the status after few minutes.
You may see following error when you scanning ESXi hosts by vCenter Update Manager.
Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and
firewall setup, and check esxupdate logs for details.
You also see similar logs in /var/log/esxupdate.log.
[Errno -2] Name or service not known
The root cause could be following:
- ESXi host cannot resolve DNS name of vCenter Update Manager Server.
- One of the DNS servers incorrect if you set multiple DNS servers on ESXi host.
Virtual appliance is future of how VMware delivery their product to customers. It’s pain to migrate from vCenter Server Windows version to virtual appliance. The only way was build up new virtual appliance and move everything out of Windows vCenter Server. The challenge is you lost data if you have integrated vCenter Server with other VMware products, or using DVS.
VMware released vCenter Server Migration Tool after VMworld 2016. It gave me confidence to give it a try. I assume vCenter Server is embedded SSO. I did the migration 2 or 3 times, following is summary of my experience. The migration tool only support migrate vCenter Server 5.5 windows edition to vCenter Server 6.0 U2.
- vCenter Server is more like core services today since lot of 3rd party software call vCenter API to interactive with VMs. You may have some products integrated with vCenter Server already. Please upgrade to vCenter 6 compatible version before migration.
- I suggest create a local account on source vCenter Server if your server is domain member. You can login back source vCenter by local account in case migration failed.
- vCenter Server Migration Tool applies temporary IP address on destination vCenter virtual appliance during migration. It’s used to communicate with source vCenter. Please register a temporary IP address for destination vCenter Server.
- A helper VM is required to run migration image. Please make sure you have a free Windows VM be ready to mount migration image.
- SQL database is exported to source vCenter Server if you want migrate performance and event data. So you need to make sure enough space on C: drive on source vCenter. The free space should be much bigger than vCenter database size.
- Of course you need a vCenter Server 6 license key since old key doesn’t support the version.
- Some cases show migration process stopped during export SQL database. That’s because memory of source vCenter is too small. Please make sure RAM of source vCenter should be equal or greater than destination vCenter Server.
- The other tricky is database table. You may see migration processes is completed but destination vCenter Server doesn’t come up, and no data actually imported. That’s because ‘checksum‘ column existing in table [dbo].[VMO_ResourceElementContent] in vCenter DB. You can run following SQL query to remove it before migration.
alter table dbo.VMO_ResourceElementContent drop column checksum;
The items above can be done anytime before the migration window. Following steps should be token during migration.
- You need to disable firewall and anti-virus software on old vCenter to avoid communication issue between Migration Assistant and new vCenter Server.
- To avoid any unstable, resource contention, or potential network connectivity lost issue, I suggest temporarily disable DRS and HA on source and destination cluster if they are virtual machine.
- Copy Migration Assistant from migration image to old vCenter.
- Take snapshot on old vCenter and backup database of old vCenter.
- Connect to console of source vCenter and run Migration Assistant.
- Mount vCenter Server 6 U2m image on helper VM. Launch vCenter migration. The migration process is straightforward. I wouldn’t introduce more here.
Basically you need to revert all the temporary changes made before. Such as delete snapshot and DB backup, enable DRS and HA, and disable vNIC on source vCenter Server to avoid any human error.
You may see that error message “To view this page ensure that Adobe Flash Player version 11.5.0 or greater is installed. ” when you open vSphere Web Client 6.0 on IE 11 on Windows 8.1. The login fields still visible, but the page go to blank after you login.
某日，vCenter Server突然无法搜索虚拟机了。在vSphere Client中搜索时会提示 Unable to connect to web services to execute query. Verify that the ‘VMware VirtualCenter Management Webservices’ service is running on https://vCenter_Server_FQDN:10443。没过几个小时用户就开始抱怨vSphere Web Client也出问题了，总是提示错误 Client is not authenticated to VMware Inventory Service – https://Inventory_Service_FQDN:10443。