After VMware vSphere and View, VMware vCloud Director is the next big thing to setup and customers start asking for it. But the problem is that the knowledge and available resources are limited. So for real life implementations of vCloud Director we have to rely on VMware employees to show us the ropes.
First of all, what is VMware vCloud Director. In short, VMware vCloud Director gives enterprise organizations the ability to build secure private clouds as a base for a infrastructure-as-a-service (IaaS) solution. Coupled with VMware vSphere, vCloud Director delivers cloud computing for existing datacenters by pooling virtual infrastructure resources and delivering them to users as catalog-based services.

The vCloud Director architecture is shown below.

(more…)

On July 12th, VMware announced the release of vSphere 5.

With the release comes the challenge to upgrade your existing installation.

However, there are a few caveats:

• vSphere 5 is the first version which comes in a ESXi version ONLY! ESXi 5 is available in an embedded or installable version. If you’re running ESX 3.x or 4.x you should do a clean installation. You can find more information here.;
• VMware changed their licensing method. Familiarize yourself with this and check if you need to upgrade/extend your licenses. You can find more information here.

Because I run a VMware vSphere 4.1 environment, this is a upgrade from vSphere 4.1 to 5.

The upgrade is a straight forward five step process.

(more…)

I often get questions about how to license Microsoft Windows 7 in a VMware View VDI deployment, I will try to elaborate what is needed in general and for specific scenarios. By understanding how they apply to common VMware View scenarios you can calculate and try to get the most out of existing and new licenses needed.

Every device you want to use to access the VMware View environment, with Windows 7 Desktops, needs to be licensed. It does not matter if it is a PC, a Thin or Zero client, an iPad or similar devices, every device accessing Windows 7 via VDI needs to be licensed.

You have two ways to license the environment, you can utilize the Software Assurance Windows Virtual Desktop Access Use Rights benefit at no additional cost; or you purchase Windows VDA subscription. Windows VDA is licensed per access device. There is currently no option to license Windows VDA per user.

VDA through SA or VDA subscription?

Certain devices, such as thin or zero clients, do not qualify for Software Assurance coverage for Windows. To license these devices for use with VDI you will need Windows VDA subscription. The rule of thumb is that if it isn’t a full blown Windows Desktop Operating System with Software Assurance (SA) you will need VDA subscription licenses to access the VMware View vDesktops.

(more…)

Last week I decided to buy a new lab server and I doubted between a HP or Dell mini server or an ESXi whitebox. Because most mini servers only have 8GB memory, I decided to collect specific parts to build my own VMware ESXi whitebox.

To find parts which are compatible with VMware ESXi 4.1, I used the following resources:

• Ultimate VMware ESX Whitebox;
• VM-help.com.

I chose a AMD Phenom II X6 processor, socket AM3 six core processor because it’s a lot cheaper than the Intel Core i-processors. As the basis I needed a AM3 socket motherboard and my selection criteria where simple, 16GB memory and onboard video.

As an ASUS fan I had to choose between the ASUS M4A88T and M4A88TD. Both can house 16GB of memory and have onboard video but the TD version has SATA 6Gbps. Because storage will most likely be the bottleneck, I decided to go for the M4A88TD-M but on the above sites there was no entry for this motherboard.

But Google is my friend so I searched for ‘M4A88TD’ in combination with ‘ESXi’. I found a few sites which mention an almost identical combination of motherboard, processor and ESXi 4.1. Eventually I took a gamble and ordered the ASUS M4A88TD-M/USB3.

The last two items where the simple ones, two sets of 8GB dual channel memory and a 6Gbps SATA disk.

(more…)

Yesterday Anne Jan linked me to an article on the VMware website which contained information on a free online training course. The title is Transition to ESXi Essentials. The course is dedicated to ESXi and depending on your learning style it takes about 3 hours to complete. It’s broken up in several chapters so you don’t have to do all at once.

Since VMware is moving towards ESXi, abandoning ESX with its Service Console, it’s a great time to release a course all about ESXi and how to manage it.

(more…)

Last week we got a question concerning the licensing options around vSphere and how to choose the correct edition and options from all the flavors and options offered by VMware. So while answering the questions concerning the licensing I thought back to a nice overview picture we had available a few years back from VMware. So that’s why I compiled two overview pictures where there is one for the SMB market and one for the Enterprise market. In the overview the current situation and options are summarized per edition.

(more…)

Yesterday a colleague asked me to add four blades from our old test environment to our new VMware vSphere 4.1 test environment. Of course this was no problem (yet), I had an hour or two to spare, so I started immediately.

Download the ESXi 4.1 installable ISO, connecting this to the four blades, installing and preconfiguring ESXi and adding them to them VMware HA/DRS test cluster. Adjust the zoning for the SAN and configure the correct VLANs and where done. WRONG!

The two running ESX hosts are equipped with Intel Xenon X5660 CPUs, the four extra ESX hosts have Intel Xenon X5430 CPUs. When I tried to do a vMotion the following error message appeared.

Surprise, the CPUs are not compatible. So I needed to setup EVC in this cluster to mask the advanced features from the Intel Xenon X5660 and bring it to the same feature level as the Intel Xenon 5430′s.

But this creates the first ‘chicken or egg dilemma’ of the day.

(more…)

[This is the 2nd part in the sequel. You can find part 1 here.]

We talked about licensing Windows Server on a VMware environment but that’s only one part of the licensing nightmare. You will also need client access licenses also called CALs.

Client Access Licensing

In addition of the Windows Server 2008 License you also need a Windows Server 2008 Client Access License also called CAL. This is required for each user or device (or combination of both) that accesses or uses the Windows 2008 software.

Requirements

Every user or device accessing the Windows Server 2008 needs a CAL. You don’t need a CAL when:

• You access the instance of server software only through the internet without being authenticated or individually identified by the server software;
• You access Windows Web Server 2008;
• If external users are accessing the instances of server software and you have acquired a Windows Server 2008 External Connector License for each server being accessed;
• You only administer the server software with two devices or users;
• You use the Windows Server 2008 solely as a virtualization host.

The last point doesn’t impact us much because we use VMware ESXi solely as our virtualization platform.

(more…)

We’ ve been doing quite a few VMware View POC’s and the question that colleagues keep asking me is:
‘How do I optimize my Windows guest OS for use with VMware View?’.

First of all, I primarily use x86 versions of Windows XP and 7. The disk usage is much less, I seldom need more than 4 GB of RAM and application compatibility is still an issue on x64 systems.

After installation of the guest operating system in the template virtual machine I do the following to optimize the operating system for use with VMware View.

(more…)

With yesterdays release of vSphere 4.1 comes the challenge to upgrade your existing installation to this new version. Because I have been testing the beta for a while now, I couldn´t wait to try it in our new testing environment.

However, there are a few caveats:

• VMware released a KB article with the supported upgrade methods for ESX(i) 3.0.x, 3.5 and 4 full, embedded or installable;
• Do NOT upgrade vCenter server to version 4.1 if you are using VMware View Composer 2.0.x. Check out this VMware KB article for more information.

Before you start the upgrade process, back-up the vCenter- and Update Manager databases.

After downloading the needed ISO´s, I started with the upgrade of the vCenter server.

But first of all, I had to uninstall all incompatible vCenter components, in this case Guided Consolidation 4.0.

When this is done, it´s time to update the vCenter server.

(more…)