There’s a glitch some customers are encountering whereby a Linked Clone desktop is created on vCenter Ok, but is deleted soon after vCenter complains about either “disposable” or “internal” .vmdk files this desktop. Creating and recomposing linked clone desktops fails on VMware Horizon View 6.1.x and all older releases after you have applied an upgrade patch.
On View Administrator, recomposing of pool fails with the error:
View Composer DiskFault: Disk customization failed due to an internal error
This issue occurs when older versions of Horizon View Composer prior to VMware Horizon 6.2 attempt to communicate with VMware ESXi hosts, but SSL v3 is disabled beginning in VMware ESXi 5.5 Update 3b and 6.0 Update 1 hosts.
For the next few weeks, we are focusing our efforts on helping our vSphere 5.5 customers find answers to questions as quickly as possible. We tend so see a surge in March of customers installing, upgrading, and configuring their new vSphere 5.5 environments so we present you this list of the top 20 vCenter Server KB articles. Please share if you find this list useful :^)
Ever since vSphere 5.1 launched we’ve been getting a fair number of support calls about Single Sign On, or SSO for short. It is a requirement now, and many of you are getting caught on some aspect of the upgrade/implementation.
We don’t like our customers having to call into support. Not that we don’t love to hear from you, but we’d rather document how to deal with different issues and push the information out to you before you run into them. Then, you don’t have to waste time calling us!
Let’s start with two particularly important KB articles. These are classified as ‘Resolution Paths’. They walk you through an ordered set of steps in resolving a problem. You can read more about resolution path articles here.