I wrote an article talk about how to find out which services lockout domain accounts on vCenter Server. It only applies to the scenarios that domain accounts very frequently lockout. Like every 1 second. If it’s minutes, it will be hard to find out as it’s manually processing.
The other way to identify source is to use vSphere Web Client. The trick was told by VMware BCS team.
Log in to vSphere Web Client. Go to the main page and the Events node. Search for “authen” you may see some error events. The real source is red text.
User CONTOSO\firstname.lastname@example.org .....
网上有很多关于如何在VMware Workstation上部署vCenter Server VCSA的文章，但根据这些文章在部署过程中总是会遇到各种各样。以下是几点我总结出来的要点，仅供参考。
- vCenter Server安装好后第一次启动的时候会检测FQDN。如果你没有DNS服务器，FQDN检测会失败。所以在安装vCenter Server时要确保“Host Network Identity”输入的是IP地址。
- 第一次启动耗时大约15至20分钟，在没有完全启动完毕前虚拟机的控制台界面是不现实IP地址的。另外一个vCenter Server准备就绪的表现是IP地址ping得通了。
- vCenter Server第一次启动后，需要打开 https://vcenter_ip:5480 继续完成vCenter Server的配置。
- Administrator@vsphere.local 的密码就是你在OVA导入界面里输入的密码。
- 重启vCenter Server虚拟机。
- 在第二行结尾加入”rw init=/bin/bash“。具体参考这里。
- 运行命令”pam_tally2 –user root“检查root密码输入错了多少次。
- 如果输入错误次数大于1，运行命令 “pam_tally2 –user root –reset” 解锁root账号。
在以上步骤的第四步中，登陆后你应该会看到vCenter Server安装向导。如果你的vCenter Server只想用IP地址，请确保“System name”项填写的是IP地址。
There are a lot of articles introduce how to deploy vCenter Server virtual appliance on VMware Workstation. I tried but somehow it’s failed. Following are some notes for your reference if you want to deploy vCenter Server virtual appliance on VMware Workstation real quick.
I assume you don’t have DNS or domain servers. Native DHCP services of VMware Workstation is used. You just want to use vCenter Server for some quick testings purpose, and “host-only” NIC you want to select.
- vCenter Server installer validates FQDN when it’s first boot up. The process fails if FQDN doesn’t work. So please make sure “Host Network Identity” is IP address of the VM when you set the OVA options.
- The VM is immediately booted up after importing the OVA file. But VM NIC is “disconnected” status sometimes. You have to enable the NIC in VM properties real quick.
- You have to wait for about 15 – 20 minutes after first boot. Console screen doesn’t show IP address before it’s fully ready. The indicator of readiness is the IP address of the VM is responding to ping.
- Login https://vcenter_ip:5480 to continue vCenter Server installation after the first boot is ready.
- The password of Administrator@vsphere.local is same as you set during importing the OVA.
Updates 28th May 2018:
Root authentication on step 4 above maybe failed. It’s caused by root account locking. Please follow the procedures below:
- Reboot vCenter VM.
- Press “e” when you see the Photon booting screen.
- Add “rw init=/bin/bash” to the end of the 2nd line. Refer here for detail.
- Run “passwd” to change root password when you see # prompt.
- Run “pam_tally2 –user root” to check how many failures root hits.
- Run “pam_tally2 –user root –reset” to unlock root if you see more than 1 in step 5.
- Reboot. You should be able to login root now.
Updates 31st May 2018:
You should see the installation wizard in step 4. Please make sure “System name” field is IP address if you only want to use IP for vCenter Server.
Updates 5th Sep 2018:
You may see the following error during installation.
Could not connect to VMware Directory Service via LDAP
It indicates vCenter Server FQDN doesn’t work. If you’re a home lab, you may want to add the DNS entries in the hosts file.
When you upgrade or patch vCenter Server 6.0 for Windows, you may see following symptoms:
“The older version of cis-upgrade-runner cannot be removed. Contact your technical support group.”
Or error code 1063:
“Installation of component VMware CIS upgrade runner failed with error code ‘1063’”
That means the vCenter Server installer cannot find MSI files of existing vCenter Server services. It could be following reasons:
- You delete MSI files in “Temp” folder of the profile you used to install vCenter Server.
- The account you used to login and install vCenter Server was roaming profile. The profile’s “Temp” folder was automatically deleted when you reboot/logoff the server.
vCenter Server 6.0 for Windows is consist of lot of standalone package. The upgrading process usually uninstall old packages, and then install newer packages. So the failure doesn’t impact to database or inventory data. You can re-initiate the upgrading again.
But you cannot manually uninstall old package since upgrading process brings down vCenter services first then uninstall old packages. If you already uninstalled old packages, the upgrading process will be stuck on bring down vCenter Services stage since some processes may already be removed. For example “vmware-python” it maps to “VMware vCenter Configuration Service”. If you manually uninstalled it before launch upgrading. It removes the service. Upgrading is not able to check status of the service.
Easiest way to get ride of this problem is
- Open Registry Editor (regedit) and go to the path: “HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products”
You would see lot of keys are there.
- Search keyword “vmware-“. These keys store package info of vCenter Server.
- Expand one of the keys. Go to “SourceList”.
- The value of “LastUsedSource” is path of MSI file of old vCenter Server installer.
For example my value is “m;1;X:\vcenter-server\packages\”.
- Make sure your server has the path mentioned in previous step (My case it’s X:\vcenter-server\packages\) and old MSI files are available in the path. If it’s a CD-ROM letter, you just need mount old vCenter Server image to the drive.
- Copy new vCenter Server image to a local folder, uncompresse and launch installer locally.
- Now the upgrading process can read original packages on the mentioned path in step 4. It will automatically remove old packages by the old MSI files.
There are two other workarounds. One is modify the value of “LastUsedSource” to reflect a new location of packages. But you still need the old MSI files be there. Another way is delete the key after you find it in step 2. (I never tested this way but it should work as it let vCenter Server installer thinks the server is brand new so installer can override the existing folders)
I also wrote another article for upgrading error on vCenter Server 5.5 for your reference:
CustomAction VM_InstallJRE returned actual error code 1624
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.
Continue reading “Cannot open vSphere Web Client on IE11 on Windows 8.1”