Archive for June, 2008

Hyper-V RTM: Now Available

It’s a little earlier than expected, but the final, release to manufacturing (RTM) version of Microsoft’s long-awaited Hyper-V is now available.  There are several available download packages, listed below.  Links for the main download package (for the server side) is listed below.  For most of us, this should be a "clean" update (no special considerations) except for one: You will need to commit or discard saved state files for any VMs that are currently defined on existing Hyper-V servers.  On to the details and links (courtesy of Microsoft)….

Hyper-V RTM Packages: Windows Server 2008 x64 Hyper-V Parent Partition

This is the complete Hyper-V RTM package for Windows Server 2008 x64. This package must be installed on the Hyper-V Parent Partition. It includes the Hyper-V Server components for Full and Core installations. In addition, is contains the Windows Server 2008 Hyper-V Management components for Full installations. Note This package is permanent.  Once installed, it cannot be uninstalled.

http://www.microsoft.com/downloads/details.aspx?FamilyId=F3AB3D4B-63C8-4424-A738-BADED34D24ED

Hyper-V Management

This is the Windows Vista SP1 x64 Management package. This package provides the management tools for Windows Vista SP1 x64.

http://www.microsoft.com/downloads/details.aspx?FamilyId=88208468-0AD6-47DE-8580-085CBA42C0C2

This is the Windows Vista SP1 x86 Management package. This package provides the management tools for Windows Vista SP1 x86.

http://www.microsoft.com/downloads/details.aspx?FamilyId=BF909242-2125-4D06-A968-C8A3D75FF2AA

This is the Windows Server 2008 x86 Management package. This package provides the management tools for Windows Server 2008 x86Note This package is permanent.  Once installed, it cannot be uninstalled. 

http://www.microsoft.com/downloads/details.aspx?FamilyId=6F69D661-5B91-4E5E-A6C0-210E629E1C42

UPGRADE CONSIDERATIONS

If upgrading from Hyper-V RC0, RC1 Escrow, RC1 or RTM Escrow, you will not need to recreate your virtual machines or network settings.  All virtual machine information will simply persist once the upgrade is complete. However, the following upgrade considerations need to be followed to ensure a successful upgrade to Hyper-V RTM.

· Saved-state files are not supported during the upgrade.  All virtual machine saved-states should be discarded before upgrading to Hyper-V RTM (or prior to resuming virtual machines after upgrading to Hyper-V RTM).

· Online snapshots contain virtual machine save-states and thus online snapshots are not supported when upgrading to Hyper-V RTM. Either apply any online snapshots and shut down the VM or discard the virtual machine save-state associated with the snapshot before or after the update to Hyper-V RTM.

· New Integration Components (ICs) must be installed for your supported guest operating systems. Integration Components are specific to the build of Hyper-V. Hyper-V RTM Integration Components for all supported Windows Operating Systems are provided using the ‘Action’ à ‘Insert Integration Services Setup Disk’ action.

o Hyper-V RTM Integration Components for ALL supported Windows Operating Systems are now part of the IC Setup Disk. This includes all of the new guest support being added at RTM such as Windows XP (x86), XP (x64), Vista (x64), Windows 2000 Server and Windows 2000 Advanced Server. Simply install the Hyper-V RTM Integration Components and you’re set. (‘Action’ à ‘Insert Integration Services Setup Disk’).
Note You need to close the found new hardware wizard before setup will begin on all Windows Operating Systems.

Hyper-V Fail-Over Clustering Options

Clustering is a real requirement for many mission-critical applications.  Fortunately, most virtualization platforms (including Microsoft’s Hyper-V) support several options.  The main approaches involve either clustering within Guest OS’s (i.e., within a VM if the guest OS supports it), or by using shared storage at the host level.  But, clever systems administrators can often come up with some more creative options.

Jose Barreto has recently posted a very well-written and comprehensive article called Windows Server 2008 Hyper-V Failover Custering Options.  The article outlines (and illustrates) several different approaches.  From the introduction:

There are many ways to implement Windows Server Failover Clustering with Hyper-V. I could actually find five unique methods to do it. Some of them will actually not give you a fully fault-tolerant solution, but most of them actually make sense in specific scenarios (even if only for demonstrations). In any case, just trying to understand and differentiate them will probably be a good exercise.

And here are the titles for your clustering options:

  • Parent-based Failover Clustering with two physical servers
  • Child-based Failover Clustering with two physical servers
  • Mixed Physical/Virtual Failover Clustering
  • Failover Clustering with two child partitions on one physical server
  • Standalone demo laptop with Virtual iSCSI SAN

Jose has done a great job documenting them, and I think this post will serve as a good reference.

The Case Against Desktop Virtualization

Virtual Strategy Magazine has recently published my article, The Case Against Desktop Virtualization.  From the introduction to the article:

Ladies and gentlemen of the jury: You are being called upon to partake in one of the most important duties of an IT professional.  You will be asked to objectively evaluate claims and determine whether a relatively new development in virtualization technology – desktop virtualization – is a valid and useful solution for your environment.  You have already heard many strong arguments for desktop virtualization from much of the industry.  You will now hear from the other side: A discussion of how you can gain many of the benefits of virtualization without moving desktop computing to the confines of the data center.

OK, all drama aside, I should be clear about the point of this article.  My goal is not to convince you that desktop virtualization is not a good idea.  Rather, I’d like to provide some counter-point to a lot of the hype that we have been hearing lately.  Specifically, I’ll point out how many of the problems that desktop virtualization is designed to solve can be addressed in other ways.  The goal for you, the reader, is to determine which of these is the best way to solve these problems.  Order in the court!

Perhaps it’s a bit too dramatic, but I think it presents a good case, overall.  Feel free to leave your pleas and judgments here.

From the Trenches: The Great Office War

In the eternal struggle for workplace dominance, two factions – formerly coworkers – must struggle to keep their departments alive. Welcome to: The Great Office War.  Trouble had been brewing between IT and Sales for years.  Key issues centered around disputed territory located near the West side of the Water Cooler region.  Computer usage rights were also an issue.  Seeing no other options, the sides resort to war.  This is their story…

Microsoft Server Quest

While it seems that the powers of marketing are often used for evil rather than good, every once in a while, we see an entertaining site or application.  Microsoft has given us its share of humorous clips and commercials.  This time around, it’s Microsoft Server Quest – a Flash-based, animated game that allows you to try to save the entire office with your superior intellect.  You’ll also get some valuable discount codes (which are not-so-cleverly disguised in the standard dialog).  It’s not exactly World of Warcraft, but you can earn up to 4,800 GeekPoints.  You can use those… well, nowhere.  But it’s still fun.