Expert analysis and advice on server virtualization technologies, deployments and management.
Our bloggers: Kevin Fogarty is a veteran technology journalist and analyst who has previously worked for Computerworld, Baseline, eWeek, and Illuminata. Virtualization expert Edward L. Haletky is the author of "VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers", Pearson Education (2008) and runs his own firm, AstroArch Consulting. Laurianne McLaughlin serves as technology editor for CIO, focusing on virtualization as a primary area of coverage.
Virtualization with Microsoft Essential Business Server 2008: Old Apps Cause Trouble
Keywords: Virtualization, Microsoft, Windows Essential Business Server 2008, Hyper-V, VMware
Ninety minutes into a complex product demo and briefing, I generally pity only myself.
Yesterday, though, I found myself having to feel for the Microsofties who were pitching me on Windows Small Business Server 2008 and Windows Essential Business Server 2008—preconfigured sets of databases and applications aimed at small- and mid-sized businesses. Microsoft announced pricing details and a testing program Tuesday.
It's not that the virtualization flaw that became obvious isn't significant; it's just not their fault.
The two spokeswonks from the Essential Server Solutions group, Dean Paron and Eric Watson, demonstrated the integration among the various products in painstaking detail. They focused on the install-and-setup routines designed to manage all the small configuration details customers generally don't read through 300 pages of documentation in order to learn. (See more info and demos on the packages from Microsoft here.)
They made a point of saying both the small-business edition (SBS) and the version for mid-sized businesses (EBS) would run in virtualized environments from the day they ship.
In the case of EBS, though, they had to qualify that. EBS will run on a single physical server, with each of its applications running in VMs. But Microsoft won't guarantee it will run well unless it's running on hardware specifically tested and recommended by Microsoft. The list of recommendations isn't available yet, but will be by the time EBS ships, Watson promised.
Any new server running VMs has to be configured carefully; run more than one server instance and you're going to suck up more compute cycles, need more input/output, more storage, more of everything.
And the Microsoft suites were carefully configured to run in one-, two-, three- and four-server configurations, depending on the size and requirements of the customer. They were designed for convenience, not flexibility. (It may be only me that thinks it's funny that one of the key "integration" factors was that Microsoft figured out for you which of the various applications, editions, service packs and other version data were compatible -- a problem that only exists because Microsoft ships and supports a million versions of each of its products and doesn't differentiate clearly between them.)
But the reason EBS especially won't run under generic virtualized setups is that some of the applications in it—Exchange Server 2007, SQL Server 2008, SharePoint, two versions of Forefront Security and Systems Management Server—are such resource hogs that they'll overwhelm the I/O and resources of even many servers set up to support VMs.
Find out what vendors offer the products you need.
View the Vendor Matrix »



