You may see following problem if you login vCenter Server 6.0 by vSphere Client:
Login to the query service failed.
The server could not interpret the communication from the client. (The remote server returned an error: (500) Internal Server Error.)
That’s because “Use Windows session credentials” checkbox is selected. Deselect it and give it a try.
Refer KB Searching the Inventory with the vSphere Client fails (2143566)
VDP在未来的vSphere版本中将不再继续更新。在2022年以前对于现有的VDP客户没有影响。如果客户想迁移到其他备份方案，VMware提供限定时间内的免费迁移至Dell EMC Avamar Virtual Edition的促销。客户依旧可以通过vCenter的存储API把第三方备份解决方案和vCenter整合。
Just a quick update that VDP will discontinued in future release of vSphere. It doesn`t impact to existing customers till 2022. VMware offers free migration to Dell EMC Avamar Virtual Edition in limited time if customers want to move to other backup solution. Customers can also use other 3rd party backup solutions to integrate with vCenter Server via storage API.
Read this FAQ for detail. VMware products lifecycle matrix for your reference.
vCenter Server 5.5 Update 2e contains fix of Storage Monitor Service. It’s also a stable version since 5.5 Update 1. I got a problem when I upgraded my development vCenter Server last weekend. I’d like to share the solution since VMware doesn’t document that problem. (Maybe I didn’t find it. :-)) It’s kind tricky.
vCenter Server 5.5 Update 2e包含SMS服务的bug修复，它也是当前比较稳定的版本。上周我在升级vCenter Server到这个版本时遇到了一个问题。此问题不是那么容易修复因为VMware的KB并没有提供解决方案，我在这里把我的方法共享出来。
You probably will see similar issue below if you upgrade vCenter Server from 5.x to 5.5.
vSphere Client show following error when login to vCenter Server by domain account.
The vSphere Client could not connect to vCenter server. The server vCenter server took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
That’s a very small problem but it struggles you if you are enterprise datacenter administrator. As you may know the best practices to run application is by service account. But sometimes you may testing applications by your own domain account and forget remove it.
Few days ago, my domain account locked out on domain controller. The audit report indicated it locked out by vCenter Server every 5 seconds. Then I logged in the vCenter Server, checked out Task Scheduler, Services, Task Manager…etc. Nothing was running under my domain account. I stopped applications one by one on the vCenter Server and related plugin services. No help, I felt so frustrated!!!
Here is how I figured it out eventually.
- Download TCPView from Microsoft website.
- Run it on the vCenter Server.
- Sort by Local Address.
- See which foreign address is connecting the vCenter Server.
After the steps above I finally figured out that root cause was my VMware View LAB VM tried to authenticate on vCenter Server by my domain account and stored old password. I powered up the old VM few days ago.
- 从微软网站下载TCPView 。
- 选择以Local Address（本地地址）排序。
- 查看连接到vCenter服务器的Foreign Address（外部地址）。
If you have set of group VMs and particular group can access each set VMs, you should grant access on vSphere Client or vSphere Web Client.
SSO is slowly sometimes, you could use following CLI to do it more efficient.
New-VIPermission -Entity “Folder Name” -Principal “Domaingroup name” -Role “Role name”
You could do it faster for regular folder name or group name by excel and notepad:
New-VIPermission -Entity “
” -Principal “
” -Role “Role name“
Guess how to do it.