VMware Certified Advanced Professional 6 – Data Center Virtualization Deployment Beta Exam


VMW-LGO-CERT-ADV-PRO-6-DATA-CTR-VIRT-DEPLOY-KI recently stumbled upon the VMware Certified Advanced Professional 6 Data Center Virtualization Deployment Beta exam, probably the successor of the famous VCAP5-Data Center Administration exam. Passing this exam is the final step on your road to the VCAP6-DCV Deploy Certification. For more information about the requirements, have a look at this page.

In the past, I have written two Study guides to help you pass the VCAP5-DCA exam, being the VDCA510 (vSphere 5.1) and VDCA550 (vSphere 5.5) exam. So with this new VCAP6 exam, let’s have a look at the changes.

So let us compare the objectives of this new VCAP6 with latest VDCA550 (vSphere 5.5) exam.

First, the name of the exam and the certification has been changed; in VCAP6 it’s “Datacenter Virtualization Deployment” instead of “Data Center Administration

Second, I have always wondered why the objectives started with Storage- and Network Infrastructure, instead of the Infrastructure components (vCenter Server, ESXi etc.). This Exam Blueprint starts with “Create and Deploy vSphere 6.x Infrastructure Components”, which makes more sense to me.

It will be no surprise that the objectives have not been completely changed and contain many objectives found in previous editions. A brief overview of the objectives, where applicable a reference to the VDCA550 (vSphere 5.5) exam has been made ( ==> <VDCA550 Objective>).

Read the rest of this entry »

Deploying replica fails with .vmdk access errors


A quick post about an annoyance I encountered while recomposing a View Horizon Linked-Clone desktop pool to multiple local datastores. In this situation multiple replicas will be created from the Parent VM.

These replicas are created simultaneously; however during this process the task pane in the vCenter Server shows many .vmdk access errors on the parent VM and as a result replicas are created one after the other.

VMware KB “Deploying multiple virtual machines in VMware vCenter Server 5.x and 6.0.x from the same template fails with the error: vmdk access error (2114026)” explains that this issue occurs because of locked –ctk.vmdk files. These files are part of the Change Block Tracking (CBT) mechanism. The KB provides instructions how to modify the settings of the Parent VM by disabling CBT.

However after editing the .vmx file and deleting the –ctk.vmdk files from the datastore, the files reappeared immediately. To resolve this behavior, SSH to an ESXi host and browse to the datastore where the Parent VM is located.
Then, edit ALL .vmdk files and remove or comment out the line starting with; changeTrackPath=.

2016-04-24-01Figure 1

Now, the –ctk.vmdk files will be gone for good.
To prevent third-party applications from enabling CBT, you can add the following line to the .vmx file of the Parent VM: ctkDisallowed=”true”.
As always, I thank you for reading and welcome your comments.

VMware wants You!


we-want-youThe folks at VMware are very excited to announce the upcoming VMware vSphere Beta Program. This program enables participants to help define the direction of the most widely adopted industry-leading virtualization platform. Folks who want to participate in the program can now indicate their interest by filling out this simple form. The vSphere team will grant access to the program to selected candidates in stages. This vSphere Beta Program leverages a private Beta community to download software and share information. We will provide discussion forums, webinars, and service requests to enable you to share your feedback with us.

You can expect to download, install, and test vSphere Beta software in your environment or get invited to try new features in a VMware hosted environment. All testing is free-form and we encourage you to use our software in ways that interest you. This will provide us with valuable insight into how you use vSphere in real-world conditions and with real-world test cases, enabling us to better align our product with your business needs.

Some of the many reasons to participate in this beta opportunity:

  • Receive early access to the vSphere Beta products
  • Interact with the vSphere Beta team consisting of Product Managers, Engineers, Technical Support, and Technical Writers
  • Provide direct input on product functionality, configurability, usability, and performance
  • Provide feedback influencing future products, training, documentation, and services
  • Collaborate with other participants, learn about their use cases, and share advice and learnings

To make the most of it, you have already deployed vSphere 5.5 and 6.0 in a portion of your environment. As a good participant, you are expected to:

  • Online acceptance of the Master Software Beta Test Agreement will be required prior to visiting the Private Beta Community
  • Install beta software within 3 days of receiving access to the beta product
  • Provide feedback within the first 4 weeks of the beta program
  • Submit Support Requests for bugs, issues and feature requests
  • Complete surveys and beta test assignments
  • Participate in the private beta discussion forum and conference calls

VCP6-DTM exam – Section 2


In the attachment, you will find the complete VCP6-DTM exam Section 1 and 2.

I have also updated the following Objectives:

  • Objective 1.3
  • Objective 1.5, Verify Trust Relationships
  • Objective 2.1, Identify default Viw Composer port settings
  • Objective 2.2, Configure and Modify Horizon View Global settings

I hope you like this guide, and welcome your comments.

Download new VCP6-DTM exam – Section 2 (Complete)

VCP6-DTM exam – Section 2.2


In the attachment, you will find VCP6-DTM exam Objective 2.1 and 2.2 besides the complete Section 1.

Section 2 contains a lot of material, for that reason I’ve decided to split up this section.

I hope you like this guide, and welcome your comments.

Download new VCP6-DTM exam – Section 2.2

View 6.2.1. Upgrade, two caveats


Recently, I was performing an upgrade from View version 6.0.1 to 6.2.1. On other occasions upgrades from version 6.0.1 to 6.2.0 did not cause serious issues. View 6.2.1 is said to be a “maintenance” release, so I did not expect much problems.

The update of the standalone View Composer, the Connection Server and the Security Server went smoothly. After this stage it is a good practice to test the functionality of the View Composer and the Connection Server and Security Server. Setting up a connection from a Windows Horizon Client, went well, but after selecting a desktop pool, the following error was received “Unable to connect to desktop: There is no available gateway for the display protocol. Try again etc…”

20160109-01Figure 1

The Connection Server log files showed the following error message: “ERROR (0894-1510) <ajp-nio-8009-exec-1> [DesktopsHandler] (SESSION:3580_***_7533) No co-management availability for protocol PCOIP””.

Read the rest of this entry »

Wots … Uh the Driver?


A modern server is besides our favorite ESXi hypervisor loaded with all kinds of additional software, like BIOS, and firmware and drivers for items like; Baseboard management , Remote support interfaces, Storage controllers, NICs, Power Supplies, to name a few.
If trouble arises and you must contact your hardware vendor or VMware support, in many situations you are kindly requested to install the latest updates, firmware versions and drivers.

Some vendors provide ISO images or repositories containing the actual updates, you may run the update process and voilà, ready and done.
If you want to stay in control and want some more insight in this subject, please read on.

It comes down to these four questions:

  • What hardware is in the server?
  • How to determine the current firmware and or driver?
  • Which driver and or firmware do I need?
  • How do I upgrade drivers and firmware?

Read the rest of this entry »


Get every new post delivered to your Inbox.

Join 436 other followers