The primary main connection protocols that customers use to connect to their virtual desktop infrastructures include PCoIP, BLAST, and to a lesser extent, RDP. Our front line tech support engineers have compiled this list of articles which cover the most common issues with PCoIP and BLAST:
Today we'd like to talk about some common issues that have been seen when customers were upgrading to the latest version of our vSphere Web Client.
Perhaps you, during an upgrade, missed some products that were no longer supported (ie: removing plugins that are no longer supported), and now are proving to be reluctant to be removed. Most of these are not production stopping, though they are problematic when it is not expected.
KBs 2111224 and 211292 For customers who have upgraded and may have not seen the documentation on what other products are no longer supported in vSphere 6.0.
KB 1025360 Helps with removing plugins that are no longer compatible with vCenter 6.0.
KB 2119011 To help introduce customers to the feature changes in the vSphere Client and vSphere Web Client in 6.0 and any corresponding errors.
KB 2121185 After upgrading to vSphere 6.0 you may run into items no longer appearing in your inventory. This KB assists in troubleshooting to the services to find the cause.
KB 2121717 Troubleshoots login issues that customers may see in the vSphere environment using the Use Windows Session Credentials check box.
Horizon View Administrators continue to open support requests with issues surrounding SSL certificates in the product configuration. Nobody really enjoys setting up SSL and all the other security aspects that go along with it - it's a necessary evil. Maybe that explains why, when running into issues with it, the first reaction is to get VMware on the phone. After all, doing a Google search on the topic returns scads of content on the topic.
Here's what we're doing about it. We have a troubleshooting KB article, written by our support engineers, to cover all the common configuration issues: Troubleshooting SSL certificate issues in VMware Horizon View 5.1 and later (2082408)
The same engineer suggested we also share this KB, as it also touches a good majority of cases we see coming in: Generating and importing a signed SSL certificate into VMware Horizon View 5.1/5.2/5.3/6.0 using Microsoft Certreq (2032400)
After upgrading or deploy the vCenter Server 6.0 or vCenter Server Appliance 6.0, some customers are being denied access to some features. Namely-
- You are unable to access or see the Single Sign-On administration section
- When attempting to access the System Configuration (located at: Administration > System Configuration) section, you are presented with:
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.
- When attempting to access the Licensing administration (located at: Administration > Licensing > Licenses or Administration > Licensing > Reports) section, you are presented with:
To view and manage licenses, you must have the Global.Licenses privilege on the vCenter Server system where this vSphere Web Client runs.
If you are encountering any of these messages you will want to check out this recent KB article:
Unable to access new Administration and Licensing features in the vSphere Web Client 6.0 (2120255)
VMware has become aware of situation whereby hard disks and/or nics may be removed from a virtual machine when reconfiguring VM workflows in vRealize Automation.
We have identified two distinct scenarios where this might happen and so have create two separate KB articles. Please familiarize yourself with both articles so that you can avoid these situations.
- When performing reconfigure operations in multiple browser tabs In VMware vRealize Automation, the hard disks and NICs are removed unexpectedly (2124198)
- In VMware vRealize Automation, the hard disks are removed unexpectedly when reconfiguring a virtual machine that has RDM disks (2124657)
Any updates to this information will be made in the KB articles themselves. The Additional Information section details how to receive these updates.
Normally, View Administrators can recover from errors that occur during provisioning or other operations by removing or resetting a desktop virtual machine using View Administrator. On rare occasions, the information in the different databases about a machine that is in an error state might become inconsistent and it is not possible to recover from the error using View Administrator. In situations where database inconsistencies cause a desktop machine to be in an unrecoverable error state or prevent a View Administrator task from completing successfully, you can use the ViewDbChk command to resolve the inconsistencies.
In a View environment, information about desktop virtual machines is stored in three places:
- The LDAP database
- The View Composer database
- The vCenter Server database
We've created a new Knowledgebase article specifically for this tool: Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions (2118050).
Note: For Horizon View 6.1 and later, the ViewDbChk tool is included with your View Connection Server installation. For Horizon View 5.3 and 6.0, you must download the tool from the VMware Labs ViewDbChk fling page.
The world’s next leap second adjustment is scheduled for 30th of June 2015 at 23:59:60 UTC.
System administrators need to be aware that this may cause issues on NTP synchronized devices and operating systems. For information on Leap Second and its impact on VMware products, please review the KB article-
Implications of not upgrading your kernel or enabling Time Skew:
Not all customers will be affected, but those who forgo updating VMware Appliance’s operating system kernel or enable time skew may observe the following issues:
- First issue that may be observed is the kernel (simplistically, the Linux operating system) can become hung and require a reboot.
- The second issue that may be observed is higher than normal CPU consumption on their Linux appliances where JVM's are utilized. In the vCenter Server Appliance (VCVA), this problem can manifest itself as high CPU consumption of the ESX Agent Manager (EAM) and other Java-based processes.