After the release on July 12th, you can now download VMware vSphere 5 and enjoy the 150 new features.

You can find the downloads here.

For more information visit:

• VMware ESXi and VMware ESX Info Center
• VMware vSphere 5 release notes.

If you want to upgrade your existing VMware vSphere installation, check out my previous article on how to upgrade to vSphere 5.

Want to know more regarding VMware’s new licensing model? Check out the latest changes here.
Hint: Read carefully and calculate the impact on your environment before forming your opinion!

Now, don’t let me keep you, GO and try out vSphere 5!

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…)

Last Friday VMware released the Orchestrator plugin for Active Directory v1.0. With the plugin it is possible to manage Active Directory objects straight from within Orchestrator.

For those of you that don’t know what VMware Orchestrator is:

VMware vCenter Orchestrator provides out of the box workflows that can help administrators automate existing manual tasks. Administrators can utilize sample workflows from VMware vCenter Orchestrator’s workflow library and provide a blueprint for creating additional workflows.

VMware vCenter Orchestrator exposes the building blocks to enable more detailed workflows to be created for VMware vSphere.

(more…)

A few minutes ago VMware released their long awaited vSphere client for the iPad and it is available at the AppStore for FREE.

VMware’s goal is to provide a tool which can be accessed anywhere to perform essential tasks and view performance metrics in a simplified interface. It is not intended to be the functional equivalent of the Windows vSphere client but it should enable you to perform 80% of the most common Admin tasks.

The functionality for now includes:

• Search for vSphere hosts and virtual machines;
• Monitor the performance of vSphere hosts and virtual machines;
• Manage virtual machines with the ability to start, stop and suspend;
• View and restore virtual machine snapshots;
• Reboot vSphere hosts or put them in maintenance mode;
• Diagnose vSphere hosts and virtual machines using build in ping and trace-route tools.

(more…)

Tonight VMware released Update 1 for vSphere 4.1 and vCenter server 4.1.

Update 1 for ESX/ESXi contains a few new/improved features:

• Enablement of Trusted Execution Technology (TXT) — ESXi 4.1 Update 1 can be configured to boot with Intel Trusted Execution Technology (TXT). This boot option can protect ESXi in some cases where system binaries are corrupted or have been tampered with. TXT is currently available on Intel Xeon processor 5600 series servers.
• Improvement in scalability — ESX 4.1 Update 1 supports up to 160 logical processors.
• Support for additional guest operating systems — Added support for RHEL 6, RHEL 5.6, SLES 11 SP1 for VMware, Ubuntu 10.10, and Solaris 10 Update 9 guest operating systems.
• Inclusion of additional drivers — ESX 4.1 Update 1 includes the 3ware SCSI 2.26.08.036vm40 and Neterion vxge 2.0.28.21239-p3.0.1.2 drivers.

Furthermore ESX/ESXi 4.1 Update 1 contains a lot of patches and fixes a list of issues.

(more…)

Luc Dekens and Alan Renouf did a great presentation on PowerCLI.

PowerCLI is based on PowerShell. PowerShell is designed by Microsoft with the SysAdmin in mind. It’s the universal language for Windows data centers.

Most of the time GUI interfaces are single purpose and rigid. PowerShell is the glue between your infrastructure. Microsoft makes it as a requirement for new application releases that it will work with PowerShell like SQL Server, Exchange, IIS7, SCOM and more. Commands (called cmdlets) are pretty easy to remember because they are in the verb-noun format (for example get-host)

(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…)

As with most products you want to keep them up to date for several reasons, which can include security, availability, reliability or even new features in the product. Keeping products up to date is a process that keeps repeating itself and needs a good plan to keep up with the most recent updates.

A lot of times though you will see that an organization isn’t on top of the update process, either because they aren’t aware of it or just forget to execute the tasks for updating their products.

The following BBC News article shows what might happen when you’re not keeping your system up to date. Several companies have become victims of the the Sasser virus which interrupted their normal operations.

Recently I have been doing a quick look at an VMware ESX infrastructure in which I noticed they did install the VMware update manager. They also had a baseline configured and attached to several ESX hosts and every evening there was a scheduled task to check for new updates available.

(more…)

In order to reach everyone possible, VMware put out an alert via the VMware toolbar yesterday, repeating the message with regards to the issue users of VMware vCenter Server may experience with performance charts after the time change over the past weekend.

So, again:

Users of VMware vCenter Server may notice the following since the time change:

• Performance charts do not display data
• Past week, month, and year performance overview charts are not displayed
• Datastore performance/space data charts are not displayed
• You receive the error: The chart could not be loaded

With the release of vSphere 4.1, VMware has released a new licensing model.

The management products below change from a CPU-based pricing model to one that is VM-based.

• VMware vCenter CapacityIQ;
• VMware vCenter AppSpeed;
• VMware vCenter Site Recovery Manager;
• VMware vCenter Chargeback.

Until December 15th these product can be offered both ways, CPU-, or VM-based.

As of today VMware vCenter Lifecycle Manager is end-of-sale.

This new licensing model has no impact on VMware vSphere licensing!

If you haven’t upgraded to VMware vSphere 4 by now, you should consider it and rethink your strategy. VMware has removed all but the most recent versions of their Virtual Infrastructure product binaries from their download page on June 17th. As of May 2010, the following Virtual infrastructure products have all reached end of general support according to the published support policy:

• ESX 3.5 versions 3.5 GA, Update 1, Update 2, Update 3, Update 4
• ESX 3.0 versions 3.0 GA, 3.01, 3.02, 3.03
• ESX 2.x versions 2.5.0 GA, 2.5.1, 2.5.2, 2.1.3, 2.5.3, 2.1.2, 2.5.4
• Virtual Center 2.5 GA, Update 1, Update 2, Update 3, Update 4, Update 5
• Virtual Center 2.0

(more…)

Up until a week ago, I hadn’t had the pleasure to work a lot with vSphere. Now with a test environment at the customer site I was able to freely play a bit with vSphere. One of the features I was curious on trying was Fault Tolerance (FT). I just created a random VM and enabled FT on it which all went fine.

After FT was enabled on the VM we wanted to see how we could upgrade the ESX hosts in that cluster as the documentation states that FT only works on hosts with the same build number.

(more…)

While I was updating the Determining VMware vCenter and ESX Build Numbers post I thought I would semi-automate the updating of the post with new build numbers for new releases, while working on it I started too fill an excel sheet and ended up with an excel sheet with the following products and build numbers for easy reference:

VMware vSphere 4 Suite (combines several products)
VMware Infrastructure 3 Suite (combines several products)
Cisco Nexus v1000 (1.0)
VMware ESXi (4.0, 3.5, 3.0)
VMware ESX  (4.0, 3.5, 3.0, 2.5, 2.0, 1.5, 1.0)
VMware Server (2.0, 1.0)
VMware vCenter Server (4.0, 2.5, 2.0)
VMware vCenter Converter Standalone (4.0, 3.0)
VMware vCenter Lab Manager (4.0, 3.0, 2.5, 2.4)
VMware vCenter Site Recovery Manager (4.0, 1.0)
VMware vCenter Server Heartbeat (5.5)
VMware vCenter Lifecycle Manager (1.0)
VMware vCenter CapacityIQ (1.0)
VMware vCenter AppSpeed (1.0)
VMware vCenter Chargeback (1.0)
(more…)

The last breakout session we attended the XTG vCenter Server Heartbeat workshop, a quick way to get familiar with a new VMware product.

The instructor first introduced us to the product and discussed some installation and configuration hints and tips.

After that we quickly started with preparing and cloning the vCenter Server and installing and configuring the vCenter Server Heartbeat product.

The workshop certainly was useful but in a different way you would probably expect.

After the workshop Anne Jan and I discussed our experiences with the product and we quickly agreed that VMware could have spent more time OEM-ing the former Neverfail product to give it a VMware-like interface instead of the 1980′s Windows 3.11 interface it has now. Besides that the configuration of the product has a very high tweaker-level. In our opinion this is a 0.9 version and in the 1.0 versionVMware should definitely address the interface and configuration look and feel.

Nevertheless VMware vCenter Server Heartbeat does what it is supposed to as we saw during the lab exercises where we did a clean failover and finally caused a BSOD which vCenter Server Heartbeat handled perfectly.

I wonder if customers are willing to pay so much money for a product which isn’t worthy the VMware name based on its ancient interface. I know I will be having a very hard time to convince customers to use this to achieve a very high vCenter protection level even when it’s clear that the use case is definitively there.

I have just updated the list after receiving word the new version is out and the build numbers are known for vSphere 4 and vCenter Server. So I compiled a list of build numbers and updates from the patch notes for VMware ESX and VMware vCenter Server.

vCenter Server 4.0 Update 1 | 19 Nov 2009 | Build 208156

vCenter Server 4.0 | 05 May 2009 | Build 162902

VirtualCenter 2.5 Server Update 5 | 10 Jul 2009 | Build 174791 (English version)

VirtualCenter 2.5 Server Update 4 | 23 Feb 2009 | Build 147633 (English version)

VirtualCenter 2.5 Server Update 3 | 03 Oct 2008 | Build 119598 (English version)

VirtualCenter 2.5 Server Update 2 | 25 July 2008 | Build 104217 (English version)

VirtualCenter 2.5 Server Update 1 | 10 Apr 2008 | Build 84767 (English version)

VirtualCenter 2.5 Server | 10 Dec 2007 | Build 64201

(more…)

Last night VMware has released Update 1 for ESXi 4, ESX 4, and vCenter server 4.

According to the release notes Update 1 includes the following improvements:

• Support for Windows 7 and Windows Server 2008 R2;
• Support for View 4;
• Support for 160 VMs per host in a HA cluster with 8 hosts or less;
• Increased vCPUs per core limit from 20 to 25;
• Paravirtualized SCSI support has been extended to Windows 2003 and 2008 boot drives;
• vDS performance improvements;
• Support for DB2 database;
• Improved support for Microsoft Clustering.

Besides this vCenter server now includes a pre-upgrade checker tool which enables you to proactively check ESX hosts for any potential issues that you might encounter while upgrading vCenter agents on these hosts as part of the vCenter Server upgrade process. You can run this tool independently prior to upgrading an existing vCenter Server instance. The tool can help identify any configuration, networking, disk space or other ESX host-related issues that could prevent ESX hosts from being managed by vCenter Server after a successful vCenter Server upgrade.

The release note can be found here.

vSphere 4 Update 1 can be downloaded here.

Back in April we we’re the first to report the limited management and automation support in vSphere, but now VMware has released version 4.0 of vCenter Site Recovery Manager.

Besides that vCenter Site Recovery Manager can now be used with VMware’s vSphere 4 it has some additional new features and improvements, like:

• Support for NFS storage arrays;
• Support for Shared Recovery Sites;
• Support for VMware Fault Tolerance;
• Support for Distributed vSwitches;
• Maximum number of protected VMs increased to 1000;
• Graphical interface to advanced settings;
• Support for DB2 as an SRM database server;
• Fully compatible with Distributed Power Management.

Licensing remains to be socket based as it was the case with SRM 1.0

For more information visit VMware’s website or see the release notes.

Filtering through my e-mail after a short, one week, holiday I ran into an e-mail from one of my colleagues pointing me to VMware KB Article 1013013. This KB article describes one of the first patches for vCenter Server 4.

The problem is that High Availability in a vSphere 4 virtual environment may not work when a host failure occurs and the node failure detection algorithm fails when using certain IP addresses. VMware found out that this is due to the fact that all of the Service Console Port(s) or Management Network IP address(s) on an ESX host fall within the following range:

3.x.x.x – 9.x.x.x
26.x.x.x – 99.x.x.x

Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.

The problem can obviously be solved by changing (one of the) Service Console Port(s) or Management Network IP address(s) or install vCenter Server 4.0 Patch 1.

More information can be found here.

To get a new project funded is often hard work. You have to calculate how much it costs to build your virtual infrastructure and how fast you can save money so you can justify the investment. Even after you started the project and you are building the infrastructure you still have to keep an eye on your wallet.  The same goes for virtualizing desktops. We calculate what it costs to create the virtual infrastructure for the virtual desktops.

But what do we do when the infrastructure is in place? We simply put the total cost for maintaining the infrastructure on the IT budget. Wouldn’t it be more sensible to let the ‘user’ pay for the resources he is using, like in the old days with shared computers/mainframes?

(more…)

Usually everybody is on holiday during this period and because of that we lack new projects and great news. ‘Komkommertijd‘, as we call it in the Netherlands. Fortunately (for us) Duncan Epping, known from Yellow-Bricks, isn’t  on holiday (yet) and he pointed me to some great new VMware whitepapers.

So,do you want to get educated on VMware now?

Then you should definitely visit Duncan’s blog or directly download and read the following whitepapers:

• VMware vSphere 4: The CPU scheduler in VMware ESX 4;
• Virtual Machine execution modes in VMware vSphere 4;
• VMware vSphere 4 Fault Tolerance: Architecture and Performance.

And to top it of, yesterday Duncan posted an addition to his ‘HA deepdive‘ discussing HA and slot sizes.

So that’s four documents which will help you through your day.

Across the room Anne Jan is working on an article discussing his first vCenter Chargeback implementation. So after you have read the four documents get back here as soon as possible.