Here’s our latest top list of KB articles you should know about when encountering issues with PCoIP with Horizon View. It can be a tricky thing to configure and troubleshoot even for the best of us, so here’s some golden nuggets to help you on your way.
There are various reasons a user might experience a blank (black) screen when using the PCoIP protocol with Horizon View and our Support Engineers get calls on this every day. These include, but are not limited to:
Misconfiguration of connection server settings.
vRAM shortage on the View virtual machine.
Incorrect video driver version installed on the View virtual machine.
Note: Troubleshoot your PCoIP issues in the proper order
It is important that the steps outlined in KB article: Troubleshooting a black screen when logging into a Horizon View virtual desktop using PCoIP (1028332) be followed in the order provided in order to quickly isolate and identify the proper resolution. They are also ordered in the most appropriate sequence to minimize data loss. The KB walks you through a serious of checks, verifying that various requirements are met and that your systems are configured properly. You will see many articles referenced as you work through each step. Do not skip steps. A slow, methodical approach works best here.
If you still see a problem after reading through the body of the KB article, there are also a number of related articles listed in the ‘See Also’ section. If you want to be notified when this article is updated there is an rss link you can subscribe to.
Next up in our series of VMware View topics, we’re going to talk about security. I spoke with a couple of our top support engineers about View security and they identified three Knowledgebase articles that solve more support requests than any others in the area of security, namely SSL certificates. They recommend customers use:
In View 5.1 and later, you configure certificates for View by importing the certificates into the Windows local computer certificate store on the View server host. By default, clients are presented with this certificate when they visit a secure page such as View Administrator. You can use the default certificate for lab environments, and one could even make the argument that it is OK for fire-walled environments, but otherwise you should replace it with your own certificate from a trusted CA (Verisign, GoDaddy, others) as soon as possible. They also told me you should use an SSL certificate from a trusted CA when setting up a Security Server for your environment when the Security Server can be used from outside your firewall (Internet) to access View desktops inside your firewall.
My engineers stressed to me the importance of following each step in these KBs one at a time when you are filling out the forms on those sites to obtain your certificate. It is easy to make a mistake and you might not receive something that will work for you.
Note: The default certificate is not signed by a commercial Certificate Authority (CA). Use of noncertified certificates can allow untrusted parties to intercept traffic by masquerading as your server.
One of the biggest call drivers within our VMware View support centers revolves around linked clone pools. Some of your users may be calling you to report that their desktop is not available. You begin to check your vCenter and View Administrator portal and discover some of the following symptoms:
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
When a linked clone pool is created or modified, several backend databases are updated with configuration data. First there is the SQL database supporting vCenter Server, next there is the View Composer database, and thirdly the ADAM database. Let’s also throw in Active Directory for good measure. With all of these pieces each playing a vital role in the environment, it becomes apparent that should things go wrong, there may be an inconsistency created between these databases. These inconsistencies can present themselves with the above symptoms.
Recently a new Fling was created to address these inconsistencies. If you’re not acquainted with Flings, they’re tools our engineers build to help you explore and manipulate your systems. However, it’s important to remember they come with a disclaimer:
“I have read and agree to the Technical Preview Agreement. I also understand that Flings are experimental and should not be run on production systems.”
If you’re just in your lab environment though, they are an excellent way to learn and understand the workings of your systems at a deeper level. Here is the Fling: ViewDbChk. For production systems we recommend following the tried and true procedures documented in KB 2015112. The KB includes embedded videos to help walk you through the steps.
Hey there VMware View implementers, here’s a top 20 VMware View specific KBs list to help you avoid issues that many of you have reported. This list is hand picked by our View Support Engineers. Keep this list handy.
Remember the immensely popular Network port diagram for vSphere 5.x we released back in July? Many of you got your hands on a physical copy at VMworld that we were handing out at the Social Support booth in the Hang Space.
Today we make good on a promise to release one for Horizon View 5.2 Click the image to be taken to the KB article which contains the pdf file.
Network port diagram for Horizon View (2061913)
Let us know what you think in the comment area below; we’re interested!
As we spoke about in this announcement, here are our currently trending KB articles related to ESXi and vCenter Server. These are the issues the majority of users are encountering. See anything familiar?
To start off with the new week we have a new video which will demonstrate our View Composer API for Array Integration in VMware View 5.1 which is currently in a "Tech Preview" state. "Tech Preview" means that the feature is experimental and should only be used in a test and development environment. For more details read about VMware Experimental Feature Support.
Essentially what the feature allows you to do is to offload the creation of the linked clones which back your View desktops to the storage array, and let the storage array handle this task. The main advantage of VCAI is an improvement in performance and a reduction in the time taken to provision desktops based on linked clone pools. This task can now be offloaded to the array, which can then provision these linked clones natively rather than have the ESXi host do it.