However, if you want to study the “official way” here’s a TASTE of what you’ll need to know:

Deploying a new VMware installation:

• Identify minimum hardware requirements
• ESX Hardware Reqs – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=13
• ESXi Hardware Reqs – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esxi_i_vc_setup_guide.pdf#page=13
• Download, prepare and validate installation media
• Download media – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=25
• Determine appropriate ESX/ESXi configuration in a given situation
• Obtain required information for environment: IP info, LUN info, boot information, service console memory, user accounts, ntp server IP, etc.
• Verify hardware against the VMware Hardware Compatibility Guide: Server, hard drives, san, HBAs, nics, procs, etc. all on HCL
• Perform a custom installation
• Booting ESX installer – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=27
• Graphical Install – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=39
• Text Install – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=42
• Scripted Install – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=45
• Customize storage layout for given situations
• Required Partitions – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=61
• Optional Partitions – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=62
• Configure ESXi from the direct console
• Install ESXi – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esxi_i_vc_setup_guide.pdf#page=22
• Direct Console User Interface – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esxi_i_vc_setup_guide.pdf#page=26
• Configure ESX/ESXi NTP
• ESX NTP During Install – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=24
• Configuration tab, Time Configuration, Properties
• Manage ESX/ESXi licensing
• Compare/Contrast VMware vSphere editions
• Edition Comparison Chart – http://kb.vmware.com/kb/1010579
• Manage license keys – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf#page=107

Upgrading an existing VMware installation:

• Plan a VMware vSphere upgrade
• Backup/Restore ESX/ESXi host configuration
• Backup host configuration – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=71
• Restore host configuration – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=83
• Understand Virtual Machine backup options
• VMotion, storage VMotion, vcb, converter, vdr, third party
• Determine if existing hardware meets upgrade requirements
• Hardware Requirements – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=27
• Understand VMware ESX/ESXi upgrade scenarios
• Host Upgrades – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=67
• Release Upgrade Support – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=72
• Perform upgrade to ESX 4.0
• Upgrade VMware ESX/ESXi
• About Host Updates – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=101
• Update Manager Upgrade Baseline – http://www.vmware.com/pdf/vsp_vum_40_admin_guide.pdf#page=53
• esxupdate/vihostupdate – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=104
• ESX Upgrade – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=75
• ESXi Upgrade – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=77
• Upgrade virtual machine hardware
• Virtual Hardware Upgrade – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=97
• Upgrade VMware Tools
• Tools Upgrade – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=86
• Verify success of upgrade
• Upgrade Logs – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=79
• Understand upgrade roll back options
• Roll Back an ESX Upgrade – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=82
• Roll Back an ESXi Upgrade – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf#page=83

Understand VMware security:

• Identify default security principles
• Default Roles – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_admin_guide.pdf#page=214
• General Security – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf#page=179
• ESXi Lockdown Mode – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esxi_server_config.pdf#page=168
• Understand Service Console firewall operation
• Service Console Security Level
• COS Security – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf#page=142
• Firewall Security Level – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf#page=180
• Opening/Closing ports in the firewall using the vSphere Client
• Configuration, Security Profile, Properties
• Set up user/group accounts
• Host Users/Groups – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_admin_guide.pdf#page=212
• Understanding Users/Groups – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf#page=167
• Working With Users & Groups – http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf#page=170
• Determine applications needed for accessing the service console in a given scenario: vSphere client, ssh client, vCenter, VCB/VDR, Update Manager, Converter, etc.

Know these tools:

• VMware Hardware Compatibility Guide
• VMware ESX/ESXi and vCenter Server Installation Guide
• Configuration Maximums Guide
• Product Documentation
• VMware Virtualization Toolkit
• vSphere Host Update Utility
• vCenter Update Manager
• vSphere Upgrade Guide
• ESX 4 Patch Management Guide
• Product Documentation
• esxupdate
• vSphere Client
• ESX/ESXi Configuration Guides
• Product Documentation

As you can see from this sampling, you need to know a ton of stuff to pass the VCP 4. And, here’s a word of warning: not all of the test questions are answered the way that it’s done in the real world. Some of the answers are just plain wrong. The test prep materials will let you spot those questions which you’d otherwise get wrong because you know better

But, there’s still one question in your mind – what kinds of ID do they mean when they say “bring two forms of ID”?

Here’s what I found from taking both the VCP 3 and VCP 4:

1. Bring a state driver’s license. This is a no-brainer.
2. Bring a credit card or something else with your “signature” on it.

Beyond that, don’t bring anything else. The test center will provide you with an erasable/laminated paper and marker should you want to take notes. Nothing else is allowed to enter the computer area with you.

When I went to take my VCP 4 in December 2009, I brought my company badge with me since it has my name AND photo on it. The guy at the testing center would not accept the photo-badge as the second form of ID. He then asked for a credit card “because it has a signature on it”. How that proves my identity is beyond me, but whatever.

Oh, and the new process (at least since I took the VCP 3 in 2008) involves taking a photo of you to put on the print-outs/etc. so be prepared to smile and dress reasonably well if that’s of concern.

Basically, VMware is looking to increase the difficulty by a VERY large margin. Previously, the VCP 3 was taken in about an hour by most people. The beta testers in the VCP 4 program report that it’s going to be a FOUR HOUR test! The guide given to the beta testers which just outlines the areas to study is a whopping 16 pages long. Yikes!

So, what does this mean to you?

If you’re wanting to get “VCP certified” (or have a boss who’s demanding it) and you want to take the easier test, I would strongly advise that you make it a high priority goal to take the VCP while it’s still in version 3. If you delay too long, you’ll be stuck taking the four hour long VCP 4 exam instead and who knows how many times you’ll have to attempt it before passing. Grab the VCP study kit today and get started before it’s too late!

First, I had to schedule an appointment with your local Pearson Vue test center. I did this via their website and there’s not really much to say about that.

When I arrived, I had to sign-in and provide identification. At my testing center, they wanted two forms of ID, but the confirmation e-mail from Pearson Vue will confirm the requirements for your test, so be sure to read it closely. Bring multiple IDs regardless.

Next, I had to place everything in my pockets such as car keys and wallet into a backpack. The attendant placed a padlock on the backpack so that I could not get into the bag. She kept the key at the front desk while the backpack traveled with me so I could know that nobody was stealing my wallet.

I was lead into a small room with four or five computers each divided by a wall. Think of the study carols you used to have in school. The attendant started the particular testing program on the computer and told me to sit down and follow the on screen prompts. There were TV cameras watching the room to ensure that you don’t talk with other people or try to pull a cheat sheet out of your pocket.

On the computer system, I entered my name/etc. and the test began. Using the mouse, each question is answered one at a time. As you proceed, you have no indication of how well you’re doing. You may go back to previous questions and at the end of the test before you submit it, you have another chance to re-visit any questions. I think the time limit was 90 minutes and I took my time, being extra careful, and finished in about 60 minutes.

Once done, I took the backpack up to the front counter where the attendant was waiting with my print-out showing my score and certification number on a temporary form. I grabbed my keys and wallet and left. The print-out is your temporary proof that you passed or failed and it has a confirmation number and some other information on it.

A couple weeks later, I received the official certificate of completion from VMware in the mail along with a free serial number for a copy of VMware Workstation. The certificate is the usual “congratulations you’ve completed such and such” type, but I am proud of it. Even with my day-to-day use of VMware and relatively deep knowledge, I only passed with a 77 out of a required 70, so I’m very glad I prepared for the VCP exam in advance or I’d probably have failed.

Taking the official VMware Certified Professional test is much harder than most of the hundreds of tests I took in college for one simple reason: there can be multiple answers for each question.

You see, after many years in college, I have become very adept at taking multiple choice tests and when there is only one answer allowed per question, I can usually rule-out at least half of the questions and then reason the actual answer from what remains. You probably can too.

However, the VCP destroys that multiple-choice test taking skill by requiring multiple answers on most of the questions! For example, some questions may have a list of seven possible choices and you will select four of those to arrive at the correct answer. You can’t use deductive reasoning on these questions – you must know the answer and know it well.

The difficulty is also increased because a very large number of the VCP exam questions are derived from the introductory/early chapters in the official VMware manuals. Yeah, you know, those books/sections that you never read? If you’re like me and use the manuals as a reference and don’t actually read them from cover-to-cover, you’ll be in for a shock when you see that many VCP questions are pulled from those early beginner-level chapters in the manuals!

The hours I spent studying and memorizing the study guide and sample exam were invaluable. Having many possible answers per question really makes the test tough, especially when the questions may be about trivial information or even (gasp) things I know to be wrong or untrue from my experience using VMware on a daily basis! Do yourself a favor and grab the study kit. If you have to re-take the VCP test, it will cost you more than the kit, so it’s really stupid not to prepare fully with the kit.

The HA process can determine that a VM is unreachable in a number of ways such as by network connectivity, heartbeat, or even by failure of an application. These conditions can trigger failover and thus the starting of another instance of the VM in question so that visible downtime to users is minimized.

VMware High Availability requires Virtual Center to setup and configure, but once it is configured, the VC machine can be removed (for example if it crashes) and the ESX hosts will continue to operate the HA environment.

DRS takes advantage of VMotion so that it can move a VM between two servers without incurring downtime. In the automatic mode, an algorithm will determine the optimal deployment of virtual machines based upon the min/max settings you dictate, while the manual and semi-automatic modes allow you to have a finer grained level of control over VM movement.

In configuring DRS, you will create various logical structures in the Virtual Center interface such as “datacenters”, “clusters” and “resource pools”. Each of these logical constructs operates with DRS to control which hosts are allowed to run which VMs and which VMs can consume what resources. I’ll get more into these ideas in the detailed information pages.

VMotion requires shared storage that can be accessed by all of the ESX hosts which will be expected to run a VM. When you do a hot migration between hosts using Virtual Center, the VM is placed into snapshot mode, the memory of the VM transferred to the new location, and then snapshot mode is removed thus allowing the new host to write to the virtual machine’s files.

This ability to move VMs which are executing is the basis for the DRS (Distributed Resource Scheduler) as VMs can be rearranged on different ESX hosts to meet various CPU and memory requirements.

In addition to truly shared storage, VMotion requires a gigabit network and VMware Virtual Center.

The VMware Certified Professional exam doesn’t focus extensively on VCB, at least as of the 3.5 update. It is good to have an idea of how it works and some of the requirements (such as the shared SAN) but an in-depth knowledge is not usually necessary.

Imagine if you have a set of three ESX hosts, each running a few virtual machines. If one of the ESX hosts needs to be brought-down to add some RAM, you would open the Virtual Center interface and migrate the running VMs off of the host that needs work. Assuming you have shared storage such as iSCSI or a SAN, this can be done seamlessly without any interruption in access to the VM! Your users would never see the server drop offline. Imagine not having to schedule downtime for a virtual server with users — that’s what VMotion allows thanks to Virtual Center — and that’s just part of the story.

Virtual Center is run as a separate machine in addition to the ESX hosts. VC can be run in a virtual machine if desired, or you can run it on a standalone box. VC runs inside of Windows 2003 and will use a built-in version of MS SQL server or you can point it to a MS SQL server installation which is preferrable. Once VC is installed, you connect using the VI Client just as you would to an ESX host except that by connecting to the Virtual Center server, you can manage multiple hosts, VMotion, HA, and DRS.

If ESX is the engine of the Virtual Infrastructure “car”, Virtual Center is the driver’s seat with the controls and displays.