Did you know VMware now offers a series of troubleshooting KBs on NSX for vSphere 6.x? The series covers topics ranging from NSX Controllers, Distributed Firewall (DFW), VXLAN, Guest Introspection, and NSX Manager to Edge Services Gateway and its services, including IPSec VPN, SSL VPN, and High Availability.
We’ve created a master KB of sorts to serve as a starting point: Understanding and troubleshooting VMware NSX for vSphere 6.x (2122691) This article provides a master understanding and troubleshooting information regarding VMware NSX for vSphere 6.x and all functional services. This article is targeted towards VMware Technical Support, VMware Network Administrators, Virtualization and Network Architects providing additional troubleshooting assistance when dealing with issues encountered with VMware NSX for vSphere 6.x. Bookmark this one for sure.
Additionally, the following KBs are designed to assist VMware customers and partners with fast resolution to NSX for vSphere 6.x technical support issues by describing critical diagnostic information to collect and key known issues. Come check it out.
As you have probably heard by now, VMware yesterday released shiny new versions for it’s desktop virtualization products: VMware Fusion 8 and VMware Fusion 8 Pro, and VMware Workstation 12 Pro & VMware Workstation 12 Player. To go along with these new versions, the Knowledge Experience Team has created some new Knowledgebase articles and/or updated existing articles. Here is a list of what you need to know.
Today we will highlight one of our KB articles that is getting some traction with our Horizon View customers. The issue can occur if the ADAM database contains an invalid entry for a persistent disk.
- Attempting to import the disk from vCenter Server fails with the error:
This disk is already managed by View
- Cannot detach a Persistent User Data Disk in View Manager.
- Cannot import a Persistent Disk from vCenter Server for a virtual machine that was deleted in View Administrator.
- The Persistent disk is visible when the option to show incompatible files is selected.
If you are encountering any of these symptoms in your environment, please refer to KB article: Cannot detach a Persistent Disk in View Manager 4.5 and later (2007076). This article has a 5 star customer rating.
Note: This KB contains two Warnings. Be sure you completely understand the article, and as always check that your backups are working and are valid.
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:
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)
We’ve noticed a number of you who are encountering an error when attempting to access the VMware Knowledgebase, whether it be the main landing page, or a specific article in the KB. You see something like:
Access Denied – You don’t have permission to access “http://kb.vmware.com/” on this server.
We are aware of the problem and are investigating the issue on our servers, but in the meantime we want everyone to know the work-around. Go into the menu of the browser you are using and clear both the cookies and the cache. Then reload the KB URL – it should then work.
We apologize for this inconvenience.