Skip to main content

Major Update to VMware Certification Naming



Major Update to VMware Certification Naming and Schedule

VMware have announced a major shift in the naming and versioning for all certifications - alignment to the year in which a certification is earned, and a new annual release/update schedule for all VCP, VCAP, and VCDX certifications!

Naming Convention
Using the Data Center Virtualization (DCV) track, here's an example of the the next generation of certification names:

  • VCP-DCV 2019
  • VCAP-DCV Design 2019
  • VCAP-DCV Deploy 2019
  • VCDX-DCV 2019

Certifications launched from this month will use this new convention, starting with the release of:

  • VMware Certified Professional – Desktop and Mobility 2018 (VCP-DTM 2018)
  • VMware Certified Advanced Professional – Data Center Virtualization Deploy 2018 (VCAP-DCV Deploy 2018)
  • VMware Certified Advanced Professional – Cloud Management and Automation Deploy 2018 (VCAP- CMA Deploy 2018)

Release Schedule
As you might expect from such a naming convention, there's also a switch to an annual release schedule:

  • January 1st: Release and update all VCP certifications
  • March 1st: Release and update all VCAP Design certifications
  • May 1st: Release and update all VCAP Deploy certifications
  • VCDX certification updates will follow VCAP releases

Benefits
These changes give you:

  • Better predictability in certification releases
  • Stronger relevancy in the market - you can easily communicate your current status
  • Clarity of paths and requirements for upgrading and recertification

For further information and an FAQ document please see this blog announcement

Comments

Post a Comment

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x
You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out.
Now the option left is from the command line of VCSA appliance.
Below steps will make it possible to change the FQDN of the VCSA from the command line.
Access the VCSA from console or from Putty session.Login with root permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot the VCSA appliance.After reboot you will be successfully manage to change the FQDN of the VCSA .

Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client.

If you are using self-signed certificate, you can regenerate the certificate with the help of below KB 2112283 article.



Happy Sharin…

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …