VCP 6.5 Study Notes – Exam Number 2V0-622

Like most performing certification renewals it can be difficult to find time to study. I’ve put together a condensed set of notes I used for the VCP6.5-DCV exam.

There are some fairly comprehensive resources out there, and if you are new to the VMware VCP I would highly recommend building a lab and running through each of the sections identified in the official exam guide.

If you don’t have a lab, have a look at VMware Hands On Lab – a fantastic resource, one which I use regularly when I need to refresh my knowledge given the large remit of technologies I need to cover.

Hope this guide is useful to anyone taking their VCP6.5-DCV exam. My condensed set of notes can be downloaded via PDF – here: vcp6.5-dcv – study notes v1.0

Official VMware VCP6.5 DCV Exam Guide :

VCDX Defence Dates

The 2017 defence dates have now been released. Here is the official statement from Karl Childs.

VMware Certified Design Expert (VCDX) application deadlines and defense dates for 2017! The calendar will have the most current information soon. Be sure to always confirm the deadline dates as you prepare to submit your application.

The dates listed below apply for every region. Locations include the Palo Alto, US office, the Staines, UK office, and the Sydney, Australia office. Depending on panelist availability, some tracks may not be available on all dates. That detail will be listed in the official calendar, so always be sure to confirm the information there.

We will also be releasing v6 of all tracks, starting with VCDX6-DCV – look for that information to be live soon.

The schedule is:

Dec 2, 2016 – applications due
Feb 13-17, 2017 – defenses

Mar 10, 2017 – applications due
May 22-26, 2017 – defenses

June 9, 2017 – applications due
Aug 21-25, 2017 – defenses

Sep 22, 2017 – applications due
Dec 4-8, 2017 – defenses

Note:  Dates may be subject to change based on physical location availability or other unforeseen issues. Candidates should never book travel until they have received an invitation to defend for the confirmed defense week. Actual physical locations and dates will be updated in the calendar and on the invitations to defend.

vRealize 7 Orchestrator Deployment

This is part of a series of posts that will look at the deployment VMware vRealize product suite, commencing with vRealize Orchestrator.

VMware vRealize Orchestrator

VMware vRealize Orchestrator is a development and process-automation platform that provides a library of extensible workflows to allow you to create and run automated, configurable processes to manage VMware products as well as other third-party technologies. vRealize Orchestrator automates management and operational tasks of both VMware and third-party applications such as service desks, change management systems, and IT asset management systems.

Platform Architecture

Orchestrator is composed of three distinct layers:

  • An orchestration platform that provides the common features required for an orchestration tool
  • A plug-in architecture to integrate control of subsystems
  • A library of workflows

Orchestrator is an open platform that can be extended with new plug-ins and libraries, and can be integrated into larger architectures through a REST API.

vRO Architecture

A standard set of plugins are provided, however 3rd party extensible plug-ins can also be used.

The Orchestrator database comes preconfigued with a PostrgreSQL database and is suitable for small to medium scale environments. External databases are also supported (Review the VMware Product Interoperability Matrix for list of externally supported DBs).

vRO Appliance Components:

  • SUSE Linux Enterprise Server 11 Update 3 for VMware 64-bit edition
  • Embedded PostgreSQL
  • In-Process ApacheDS LDAP (only recommended for Dev/Test purposes)
  • Orchestrator/Process automation engine

After the appliance has been deployed we can setup the authentication provider to use directory services or vSphere authentication. However, according to the documentation LDAP authentication is deprecated. The default authentication mechanism uses ApacheDS LDAP, which is fine for testing purposes. For production you could change this to vCenter SSO authentication. VMware recommend using localised authentication providers to avoid long LDAP response times. Similarly narrowing the LDAP search path to a specific OU – should also help.

PostgreSQL Database

PortgreSQL comes baked into to the deployment, this is suitable for small and medium scaled production purposes. An external database is recommended for large scale deployments. Orchestrator supports external database deployments of Oracle, Microsoft SQL server and PostgreSQL. For this implementation I will just be using the embedded db, but should you want to use an external db you will need to setup this up as a separate workflow.


Once vRealize Orchestrator has been deployed connectivity is established via the vRO control centre a web-UI (https://ipOfvROappliance:8283). From the control centre we will perform some basic configuration and then connect using the vRealize Orchestrator Workflow Designer tool. This will allow us to connect the vRO instance to vCenter. Once connected to vCenter as an extension we can create and manage workflows from the vSphere Web Client.

Deploying the vRealise Orchestrator Appliance


  • VMware vCenter Server deployed and running
  • Enough compute and storage resources to support the vRO appliance.
  • If using the vSphere Web-UI – Install the Client Integration plug-in as this is required to deploy the appliance.

Deployment: Follow the deployment procedure found on page 26 of the install and configuration guide (note this references v6 documentation but is essentially the same for v7.x).

The password for the root account of the Orchestrator Appliance expires after 365 days. You can increase the expiry time for an account by logging in to the Orchestrator Appliance as root, and running passwd -x number_of_days name_of_account. If you want to increase the Orchestrator Appliance root password to infinity, run passwd -x 99999 root.

Initial Configuration

Here we want to set the authentication mode to vSphere (as we are adopting the simple deployment). Configure the database to use PostgreSQL (embedded).

1a. Open your browser to https://ipOfvROapplaince:8281/vco

1b. Under Configure the Orchestrator Server select ‘Orchestrator Control Center’.



2. Login to the vRO Control Center.

3. Welcome to the vRO Control Center.

4. Select Configure Authentication Provider, for this deployment we will use vSphere (PSC SSO domain).

4a. Set the host address to your vCenter server and accept the certification warnings.


4b. Restart the services when prompted.

5. Configure the Database. I will be using the embedded PostgreSQL db in this deployment.


6. Restart the services


7. Next we want to navigate back to the vCO start page https://ipofvROapplaince:8281/vco

7a. Download and install the Orchestrator Client.

8. Open the Client and login with your vCenter Admin SSO user (administrator@vsphere.local)


9. First up we want to connect this instance of vRO to an endpoint such as vCenter. To do this we need to create our first workflow.

10. Select ‘Workflows’ icon (blueprint) and expand Library -> vCenter -> Configuration.


10a. Select ‘Add a vCenter Server instance’.

10b. Select ‘Start workflow’ (green play button).

10c. Enter your vCenter server hostname/IP address as well as the HTTPS port (443). The location should be set to /sdk. As I am not using any CA signed certificates I will select ‘yes’ to ignore any warnings.


10d. Enter the vCenter admin user/password and select submit.


11. Once the workflow has processed you should be able to view the vCenter server endpoint and resources from the inventory object.


12. The next task (optional) is to register the vRO instance with vCenter as an extension. This will allow us to the vSphere web client to manage and create workflows.

12a. Select ‘Workflows’ -> ‘vCenter’ -> ‘Register vCenter Orchestrator as a vCenter server extension’.

12b. Start the workflow to register vRO with the vCenter server instance.

12c. Set the vCenter instance as: https://FQDNofVC:443/sdk. Select submit to complete the task.


13. To confirm that task has completed login the vSphere web client then select vRealize Orchestrator.


14. There you have it, vRealize Orchestrator deployed. In future blog posts we will cover some basics around creating workflows before moving onto the deployment of vRealize Automation.


Documentation References

WSFC/MSCS vSphere 6.x Enhancements

For those that aren’t aware, VMware released an updated Microsoft WSFC Setup and Deployment Guide for vSphere 6.x.
In a previous blog post I covered Microsoft Clustering Design Implications in vSphere 5.x. Fundamentally the deployment of WSFC has not changed significantly. However, there are a couple of new features that I wanted to cover here.
New Features and Requirements:
  • vMotion supported for cluster of virtual machines across physical hosts (CAB deployment) with passthrough RDMs. Note, you must use VM-hardware version 11.
    • VMware recommends updating the heart-beat timeout ‘SameSubnetThreshold’ registry value to 10. Additional info can be found on MS Failover Clustering and NLB Team Blog and in VMware’s updated WSFC Setup and Deployment Guide.
    • The vMotion network must be a 10Gbps.
      • 1Gbps Ethernet link for vMotion of MSCS virtual machines is not supported.
        • Fair enough, but most customer deployments using 10GbE also share that with other workloads. In addition using NIOC to prioritise traffic to prod workloads. So its not clear if the minimum requirement is 10GbE or higher bandwidth that can be provided by 1GbE.
    • vMotion is supported for Windows Server 2008 SP2 and above. Windows Server 2003 is not supported.
    • SCSI bus sharing mode set to Physical.
  • ESXi 6.0 supports PSP_RR for Windows Server 2008 SP2 and above releases (same as ESXi 5.5 but with restrictions)
    • Shared disk quorum or data must be provisioned to guest in PassThrough RDM mode only
  • All hosts must be running ESXi 6.x
    • Mixed mode operating with older ESXi revisions not supported.
    • Rolling upgrades of cluster hosts from previous versions of ESXi to ESXi 6.x is not supported.
  • MSCS (Windows Server Failover Clustering (WSFC)) is supported with VMware Virtual SAN (VSAN) version 6.1 and later. See VSAN 6.1 Whats New!.
  • In vSphere 6.0, VMware introduced support for using Windows Server Failover Clustering or Microsoft Server Failover Clustering to protect a Windows-based vCenter Server.
  • Modifying the MSCS heartbeat time-out: An MSCS virtual machine can stall for a few seconds during vMotion. If the stall time exceeds the heartbeat time-out interval, then the guest cluster considers the node down and this can lead to unnecessary failover.
    • VMware recommends changing the DWORD ‘SameSubnetThreshold’ registry value in each WSFC node to 10.
  • VMware also warns of deploying WSFC in vSphere environments with memory overcommitment. Memory overcommitment (worse active memory reclamation like compression, swapping) can cause virtual machine I/O latency to increase, potentially causing failover. Set memory reservations if you are concerned this may affect your WSFC/MSCS nodes.

Not Supported / Limitations:

  • No Storage vMotion for VMs that are configured with shared disks.
  • No support for WSFC on NFS.
  • Running WSFC nodes on different ESXi versions (Pity as this would have been ideal for ESXi 5.x to ESXi 6.x upgrades).
  • Cant use WSFC in conjunction with VMware FT.
  • NPIV not supported.
  • Server 2012 storage spaces not supported.

VCP6-DCV Study Resources

Quick note: The exam blueprint is no longer available in a PDF form. For those interested I’ve collated all the information which can be found in my VCP6-DCV study checklist.

Official Resources:


Practice Exam:

Study Tips:

  • Use a Proficiency Matrix. Rene Van Den Bedem (aka. VCDX133) has a great post on this. In this blog post Rene looks at breaking the learning objective down into its logical components, and measuring one’s knowledge against a skills matrix.

Additional Resources:

Blueprint Documentation Set: