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.
Normally, View Administrators can recover from errors that occur during provisioning or other operations by removing or resetting a desktop virtual machine using View Administrator. On rare occasions, the information in the different databases about a machine that is in an error state might become inconsistent and it is not possible to recover from the error using View Administrator. In situations where database inconsistencies cause a desktop machine to be in an unrecoverable error state or prevent a View Administrator task from completing successfully, you can use the ViewDbChk command to resolve the inconsistencies.
In a View environment, information about desktop virtual machines is stored in three places:
- The LDAP database
- The View Composer database
- The vCenter Server database
We’ve created a new Knowledgebase article specifically for this tool: Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions (2118050).
Note: For Horizon View 6.1 and later, the ViewDbChk tool is included with your View Connection Server installation. For Horizon View 5.3 and 6.0, you must download the tool from the VMware Labs ViewDbChk fling page.
In case you missed it, on January 27th, 2015 a buffer overflow vulnerability in the glibc gethostbyname() function was disclosed. The issue is identified by CVE-2015-0235 and was given the name “Ghost.”
The VMware Security Engineering, Communications, and Response group (vSECR) began investigating this issue immediately.
The security blog at VMware released a blog post concerning this vulnerability, and a KB article was published:
VMware Response to CVE-2015-0235 – glibc gethostbyname buffer overflow, aka “Ghost” (2105862).
VMware has an established software security engineering group that integrates these techniques into the software development cycle, provides security expertise, guidance on the latest security threats and defensive techniques, and training within the development organization. This group is also responsible for driving VMware products through external security accreditations and certifications.
Many VMware products, including vSphere™, VMware vCenter™ Server, and vCloud Networking and Security (vCNS) have achieved Common Criteria certification under the Common Criteria Evaluation and Certification Scheme (CCS).Common Criteria is an international set of guidelines (ISO 15408) that provides a common framework for evaluating security features and capabilities of Information Technology (IT) security products.
For more information, visit VMware’s Common Criteria and FIPS-140 Certifications.
Over the past few weeks we have been working on constructing a brand new network diagram, depicting ports in use for vSphere 5.x
These diagrams have been very popular in the past and we hope you like this one too! We created Knowledgebase article: Network port diagram for vSphere 5.x (2054806) as a container for the pdf diagram. The pdf also lists all of the ports used in tabular format.
If you’d like to see more of these, tell us in the comments section below!
Alternate download location.
Note: This information provided is on a best effort basis. VMware will endeavor to update the diagram as new releases come out.
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?
Something you’re going to see starting today are a new breed of KB articles, titled “Trending Issues: <topic of interest>“. Our plan is to run reports on incoming support traffic and determine which KB articles are used most often. As well, we are interviewing our front-line support engineers and asking what issues they are experiencing the most. The plan is once they are established to update them periodically, depending on the trends we see.
Our first set of articles will be of interest to our users of VMware Fusion.
For those of you administering multiple vSphere environments, getting a SSO multisite deployment up and running in a correct configuration is very important. Multisite deployments are where a local replica is maintained at remote sites of the primary vCenter Single Sign-On instance. The process of setting this up is not complicated, but it is possible to take a wrong turn and end up wasting a whole lot of time correcting it. That is why we have created a best-practice Knowledgebase article titled: Multisite Single Sign-On deployment best practices. (2042849). We highly recommend you look at the examples in that article.
We’ve written extensively in this blog about SSO in the past. You can see all the other posts on the topic here: http://blogs.vmware.com/kb/tag/sso
If you are still at the point where you are asking yourself- what is SSO? and why do I care? we recommend you start with this great introduction from Justin King: vCenter Single Sign-On Part 1: what is vCenter Single Sign-On?