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.
For today’s post, we’d like to focus on issues surrounding DB validation during upgrade. Many of you are running into one of the issues when moving to vSphere 6.0
Does anything here look familiar?
Back in July we had a post about using the ViewDbChk command to remove invalid linked clone entries, which applied to Horizon View 5.3 and later. Apparently a similar situation can arise in earlier versions of the product as well, but the steps to fix it are different.
For users of View 5.2 or earlier, we have created KB article: Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View.
- You cannot provision or recompose a linked clone desktop pool
- You see the error:
Desktop Composer Fault: Virtual Machine with Input Specification already exists
- Provisioning a linked clone desktop pool fails with the error:
Virtual machine with Input Specification already exists
- The Connection Server shows that linked clone virtual machines are stuck in a deleting state
- You cannot delete a pool from the View Administrator page
- You are unable to delete linked clone virtual machines
- When viewing a pools Inventory tab, the status of one or more virtual machines may be shown as missing
So remember, if you have 6.1 or later, you want to use KB article: Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions (2118050)
If you have 5.2 or earlier, use: Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View (2015112)
Update – VMware portals issues (download products, get license keys, or other tasks) are resolved. We apologize for the inconvenience and appreciate your patience with this Severity 1 issue.
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.
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.