Main menu
Fabrizio de Luca

Fabrizio de Luca

Italian freelance VMware Certified Instructor (VCI) and VMware Certified Mentor (VCM) based in Milano, teaching official VMware courses for the major VMware Authorized Training Centers (VATC) in EMEA. Website URL:

Recertification Policy: VMware Certified Professional

Effective March 10 2014, VMware is implementing a recertification policy for VCP certification. To recertify, VMware Certified Professional (VCP) holders must pass any VCP or higher-level exam within two years of earning their most recent VCP certification.

 

Why is VMware announcing this policy change?
Currently, VCP certification holders are not required to recertify their skills, which is uncommon in the IT industry, Maintaining currency in the expertise gained and proven by VMware certifications is just as important as earning the certification initially. If your skills are not current, your certification loses value. The technical and business communities expect that VMware certified professionals are current on the latest technologies and capable of implementing VMware products with the highest level of skill. To ensure that all certification holders meet these expectations, VMware is instituting a recertification policy.

 

The new policy gives you three options to recertify:

  1. Take the current exam for your existing VCP certification solution track. For example, if you are a VCP3, you could take the current VCP5-Data Center Virtualization (VCP5-DCV) exam.
  2. Earn a new VCP certification in a different solution track. For example, if you are a VCP-Cloud, you could recertify by earning VCP5-Desktop (VCP5-DT) certification.
  3. Advance to the next level by earning a VMware Certified Advanced Professional (VCAP) certification. For example, if you are a VCP5-DCV you could earn VCAP5-DCA certification.

 

Recertification Process

  • You will be notified that your certification is due to expire via the email associated with your MyLearn account. Your transcript will also show the dates your certification is valid.
  • To recertify, you must pass any VCP or higher-level exam within two years of earning your most recent VCP certification.
  • Failure to recertify by the required date will result in revocation of your certification.
    • If your certification is revoked, you will lose access to the VCP portal and your right to market yourself as certified for that certification, which includes the use of VMware certification logos. Also, your transcript will reflect that your certification is no longer valid.
    • If you would like to re-earn a certification for which you have been decertified, you must satisfy the same prerequisites as any candidate attempting to earn that certification for the first time.

 

Further details about the recertification policy announcement can be found in the VMware Certification announcements pages.

Read more...

VSICM55 - Slide 13-24 - vCenter Server Installation Wizard



1. Wrong:

In the slide notes, the unordered list item "SYSTEM account or user-specified account", which states the vCenter Server service account requirements, is incomplete. Hence, the statement is to be considered wrong as, without the additional requirements, the user-specified account will not have all the required permissions to run the vCenter Server service.

Even if you do not use Windows authentication for SQL Server, you might want to set up a local user-specified account for vCenter Server. The only requirement is that the user-specified account must be an administrator on the local machine.
1. Correct:

Actually, the domain user account permissions pre-requisites are three:

  • Member of the Administrators group.
  • Act as part of the operating system.
  • Log on as a service.
1. Source:

vSphere 5.5 Documentation Center.



2. Wrong:

In the slide notes, the unordered list item "vCenter ports", which lists the network ports required by vCenter Server, is incomplete.

2. Correct:

The most up-to-date list of the required ports for vCenter Server can be found in the online documentation following the link provided below (the page also provides a link for the documentation page listing ports required by the vCenter Server Virtual Appliance).

2. Source:

vSphere 5.5 Documentation Center.



3. Wrong:

In the slide notes, the unordered list item "JVM memory", which lists the JVM Heap Settings for vCenter Server, states:

If you have a large inventory (more than 400 hosts), select a JVM memory size of 4,096MB.
3. Correct:

According to the "vSphere Installation and Setup" guide - "System Requirements" chapter - "Hardware Requirements for vCenter Server, the vSphere Web Client, vCenter Inventory Service, and vCenter Single Sign-On" paragraph, the heap size for large inventories with more than 400 hosts, in case of a vCenter Server running on Windows, is 3GB and in case of the vCenter Server Appliance is 1GB.

Source:

VMware vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 13-20 - vCenter Database Requirements



Wrong:

The slide graphic is a mess of wrong database versions being listed: the majority of what is shown there is outdated and refers to previous vCenter Server versions. Additionally, the second paragraph of the slide notes contains an incomplete statement about the version of the embedded database supported by vCenter Server running on Windows systems.

Correct:

According to the VMware Product Interoperability Matrix for the Solution/Database Interoperability, the following is the list of the currently supported database versions:


Microsoft SQL Server 2005
  • Microsoft SQL Server 2005 Standard/Enterprise Edition (SP4) - 32-bit/64-bit

Microsoft SQL Server 2008 Express (for the embedded DB)
  • Microsoft SQL Server 2008 Express (R2 SP1) - 64-bit
  • Microsoft SQL Server 2008 Express (R2 SP2) - 32-bit/64-bit

Microsoft SQL Server 2008
  • Microsoft SQL Server 2008 Standard/Enterprise/Datacenter (R2 SP1) - 32-bit/64-bit
  • Microsoft SQL Server 2008 Standard/Enterprise/Data Center (R2 SP2) - 32-bit/64-bit

Microsoft SQL Server 2012
  • Microsoft SQL Server 2012 Standard/Enterprise - 32-bit/64-bit
  • Microsoft SQL Server 2012 Standard/Enterprise (SP1) - 32-bit/64 bit

Oracle 11g
  • Oracle 11g Standard ONE/Standard/Enterprise Edition, Release 2 - 32-bit/64-bit
  • Oracle 11g Enterprise Edition, Release 2 [11.2.0.3] - 32-bit/64-bit
Source:

VMware Product Interoperability Matrixes.


Read more...

VSICM55 - Slide 13-08 - Information for Installing ESXi



Wrong:

The third sentence in the first paragraph in the slide notes states:

If you have not installed ESXi on the target disk before, all data located on the drive is overwritten, including hardware vendor partitions, operating system partitions, and associated data.
Correct:

This is not true in vSphere ESXi 5.x. According to the "vSphere Installation and Setup" guide, "Setting Up ESXi" chapter, "Storage Behavior" paragraph:

On the hard drive or USB device that the ESXi host is booting from, the disk-formatting software retains existing diagnostic partitions that the hardware vendor creates.
Source:

vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 13-07 - ESXi Hardware Prerequisites



Wrong:

The second sentence in the first paragraph in the slide notes states:

The server can have up to 160 logical CPUs (cores or hyperthreads) and can support up to 2048 virtual CPUs per host.
Correct:

The actual configuration maximums in vSphere 5.5 are different. Hence, the above sentence must be corrected as follows:

The server can have up to 320 logical CPUs (cores or hyperthreads) and can support up to 4096 virtual CPUs per host.
Source:

Configuration Maximums for VMware vSphere 5.5.


Read more...

VSICM55 - Slide 12-08 - Installing vSphere Update Manager



Wrong:

There is a small typo in the slide notes when describing the information you need to gather to install vSphere Update Manager:

The system DNS name plus the user name and password for the database that vSphere Update Manager will work with.
Correct:

The author was clearly referring to the system DSN (data source name), used to describe the connection to the data source.

Source:

VMware vSphere 5.5 Documentation Center.


Read more...

VSICM55 - Slide 12-07 - Update Manager Components



Wrong:

The fourth bullet in the slide notes states:

Guest agents – Guest agents are installed into virtual machines from the Update Manager server and are used in the scanning and remediation operations.
Background Info:

The "VMware Update Manager 4.1 Administration Guide", on Chapter 5 "Installing the Guest Agent", page 39, explains that:

The VMware vCenter Update Manager Guest Agent facilitates Update Manager processes. For Linux and Windows operating systems, the Guest Agent is automatically installed the first time a patch remediation is scheduled or when a patch scan is initiated on a powered on virtual machine.
Source:

VMware vCenter Update Manager 4.1 Installation and Administration Guide.

Correct:

According to the VMware vCenter Update Manager 4.1 Release Notes:

Update Manager 4.1 and its subsequent update releases were the last releases of the product to support scanning and remediation of patches for Windows and Linux guest operating systems and applications running inside a virtual machine.

Hence it can be easily understood that, in Update Manager 5.x, the whole bullet mentioned above is simply not applicable.

Source:

VMware vCenter Update Manager 4.1 Release Notes.


Read more...

VSICM55 - Slide 11-22 - Removing a Host from the DRS Cluster



Wrong:

When describing the side effects of removing a host from a cluster, the second item if the bulleted list in the slide notes states:

Virtual machines with disks on local storage must be powered off, suspended, or migrated to another host and datastore by using EVC.
Correct:

EVC - Enhanced vMotion Compatibility - is something completely different from what you need here to migrate virtual machines either to a different host or to another datastore.

This is a typo, likely caused by a "search & replace" task with the text editor. The author, here, very likely wanted to say Enhanced vMotion (hence the typo while shortening the term), which has been now renamed into Cross-Host vMotion in vSphere 5.5.


Read more...

VSICM55 - Slide 11-19 - Viewing DRS Recommendations



Wrong:

When describing the vSphere DRS tab, the first paragraph in the slide notes states:

The DRS tab displays information about the DRS recommendations made for the cluster, the faults that have occurred in applying such recommendations, and the history of DRS actions. You can access three views from the DRS tab: Recommendations, Faults, and History.
Correct:

If you look at the vSphere Web Client, which is show in the slide graphic, elements names in the GUI are different than those mentioned above. Hence, the paragraph should be amended as follows:

The vSphere DRS link under the Monitor tab for the cluster displays information about the DRS recommendations made for the cluster, the faults that have occurred in applying such recommendations, and the history of DRS actions. You can access three views from the vSphere DRS tab: Recommendations, Faults, and History.

Read more...
Subscribe to this RSS feed