You may have experienced issues with VMware portals when trying to download products, get license keys, register for VMworld or other tasks. We apologize for this inconvenience. Please know we are treating this matter as a Severity 1 issue and are working non-stop with our partners to resolve the issue and to prevent future issues.
Should you have any questions, please contact our Global Support & Services team at my.vmware.com.
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.
We've just put the finishing touches on a new video which discusses how to confirm ESX and ESXi host hardware compatibility using the VMware Hardware Compatibility Guides, which are available here.
You can use the VMware Hardware Compatibility Guides to confirm whether or not your particular server, system, HBA, network card, or other peripheral devices are certified and compatible for use with specific vSphere ESX and ESXi versions.
This is the second video for today which was produced in conjunction with Mike Foley who is a Senior Technical Marketing Manager at VMware. These videos should be of some help to those of you that are faced with SSL certificate creation tasks relating to vSphere 6. This video discusses and demonstrates Issuing a 3rd party SSL certificate to vCenter while using vSphere VMCA to issue certificates to ESXi which should be of special interest to anyone who has ever asked the question "How do I replace the “external” SSL certificate of vCenter but still use VMCA in default mode?"
Mike has provided additional information and context around this exact topic over on his blog here.
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.
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.