The vSphere Client could not connect to “vcenter server name”. Connecting to Virtual Center server is not supported by this client. You can use it to connect only to ESX server. in vSphere 6

In my environment when i tried to connect with vCenter Server version 6 from vSphere Client version 6, i received this error message was popped up "The vSphere Client could not connect to “vcenter server name”.  Connecting to Virtual Center server is not supported by this client.  You can use it to connect only to ESX server.”

Then i verified my vSphere Client Version, whether it is 6 or not. It was Version 6 as well.

Then i tried to install the latest version of vSphere Client Version 6
1. Open the Web Browser
2. Https://YourESXiHostFQDN
3. Downloaded the vSphere Client
4. Triggered the Installation

Voila.....Issue is resolved....Now i can connect with my vCenter Server Version 6 From vSphere Client Version 6

Controlling “All Users’ Tasks” for performance in vSphere 6

We know that the All Users’ Tasks view of Recent Tasks is an important feature, but it also turns out to be an incredibly “heavy” feature, which can quickly spiral out of control and impact vCenter Server performance. The focus of this version of vSphere Web Client was improving performance and giving you more control on customizing your experience. In order to achieve both of these goals, we had to make it a bit harder to get to All Users’ Tasks. This will help ensure that your systems will run smoother out of the box, with the option to enable the feature if you need it. 

Solution:-
A) Click More Tasks in the Recent Tasks panel to view all users’ tasks.

OR

B) Edit the webclient.properties file and change the “show.allusers.tasks” setting. For large vSphere environments, changing the “show.allusers.tasks” setting can potentially impact performance.

1. Locate the webclient.properties file

For the vCenter Server Appliance, the file is located in the /etc/vmware/vsphere-client/webclient.properties directory.

For vCenter Server on Windows, the file is located in the C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\webclient.properties directory.

2. Edit the file using a text editor and change show.allusers.tasks=false to show.allusers.tasks=true.

3. That’s it! No restart of anything should be required. Go to vSphere Web Client, select “All Users’ Tasks” and it should work.

Forcibly Stopping Virtual Machines with EXCLI

In some cases, virtual machines do not respond to the normal shutdown or stop commands. In these cases, it might be necessary to forcibly shut down the virtual machines. Forcibly shutting down a virtual machine might result in guest operating system data loss and is similar to pulling the power cable on a physical machine.

 To forcibly stop a virtual machine

1	List all running virtual machines on the system to see the World ID of the virtual machine that you want to stop.

esxcli <conn_options> vm process list

2	Stop the virtual machine by running the following command.

esxcli <conn_options> vm process kill --type <kill_type> --world-id <ID>

The command supports three --type options. Try the types sequentially (soft before hard, hard before force). The following types are supported through the --type option:

■	soft. Gives the VMX process a chance to shut down cleanly (like kill or kill -SIGTERM)

■	hard. Stops the VMX process immediately (like kill -9 or kill -SIGKILL)

■	force. Stops the VMX process when other options do not work.

If all three options do not work, reboot your ESXi host to resolve the issue.

Source VMware Documentation

Thumbprint Error when running ESXCLI command as vCLI Command

Issue:-
You install vCLI on a supported Windows or Linux system, and run an ESXCLI command against an ESXi host or against a vCenter Server system. An error like the following results:

The command fails because no thumbprint for the ESXi host is stored in the vCenter Server
certificate store. As a result of running the command, the thumbprint of the ESXi host appears
as part of the error message.

The error occurs because ESXCLI in vSphere 6.0 is more secure than in earlier versions of vSphere and requires a trust relationship between the system on which you run an ESXCLI vCLI command and the target vCenter Server system or ESXi host.

Solution:-
You add the ESXi host thumbprint to the certificate store on the vCenter Server system so that a

trust relationship exists between the host and the server. This trust relationship is necessary to run
ESXCLI commands.

/usr/lib/vmware-vcli/apps/general/credstore_admin.pl add -s server -t thumbprint 

Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2108416

Methods for Extracting SSL thumbprint from ESXi

Method 1:- DCUI

Method 2:- ESXi Shell/SSH
openssl x509 -in /etc/vmware/ssl/rui.crt -fingerprint -sha1 -noout

Method 3:-vMA (vSphere Management Assistant)
echo -n | openssl s_client -connect 172.30.0.252:443 2>/dev/null | openssl x509 -noout -fingerprint -sha1

Source:-
http://www.virtuallyghetto.com/2012/04/extracting-ssl-thumbprint-from-esxi.html 

You do not have permissions to view this page. You must be a member of the SystemConfiguration.Administrators group in vCenter Single Sign-On to access System Configuration. in vSphere 6

In my environment when one of the user was trying to check system configuration, he was getting the message "You do not have permissions to view this page. You must be a member of the SystemConfiguration.Administrators group in vCenter Single Sign-On to access System Configuration." In this post i will discuss, how can you resolve this issue

Solution is:-
Add the user to the SystemConfiguration Administrators Group

Compatibility list virtual hardware version to ESXi/vCenter Server version:

vROPS 6.0 Badges in vSphere Web Client

Add vROPS Badges in vSphere Web Client
Your vCenter Operations Manager license determines which badges and widgets you can see in the vSphere Web Client.

Badges that You See Depending on the Licenses

vSphere Web Client Component	Foundation License	Standard or Advanced License
Summary tab	■ Health badge	■ Health badge ■ Risk badge ■ Efficiency badge
Health tab under the Monitor tab	■ Health Trend widget ■ Workload badge ■ Faults badge	■ Health Trend widget ■ Workload badge ■ Anomalies badge ■ Faults badge

 View From Monitor Tab

View From Summary Tab

If you want to view more details about the causes for a badge score, you can click the View details icon at the upper right of the Health tab to open the VMware vCenter Operations Manager user interface.

If these Badges are not visible in vSphere Web Client then connect with vROPS interface and then

Click on Administration > Solutions > Select VMware vSphere > Click on Configure 

Select your vCenter Adapter > Select vc01 > Manage Registrations

Provide vCenter Credentials and Click on Register

 Then click on close button

Remove vROPS Badges From vSphere Web Client
If you want to remove the vROPS Badges from vSphere Web Client then Follow the same procedure given above Just Click on Unregister instead of Register.

For more info on Badges refer this link:-

https://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vcops.doc/GUID-84AD4C5B-4398-457C-9B22-A97FF72C1873.html