Access your Pro+ Content below.
What to virtualize with Microsoft Exchange
This article is part of the May 2008, Vol 2 issue of Virtual Data Center
If you’re considering virtualizing Microsoft Exchange, it’s wise to be skeptical. But when properly designed and tested, the outcome is a smooth-running Exchange environment that offers all of virtualization’s benefits for some Exchange roles. First, consult Microsoft’s Virtual Machine Support Policy for Exchange Server 2003.Microsoft supports Exchange Server 2003 running on virtual machines (VMs) with the following: Virtual Server 2005 R2 or a later version; Microsoft Exchange Server 2003 Service Pack 2 (SP2) or a later SP version; Microsoft Virtual Server 2005 R2 Virtual Machine Additions installed on the guest OS; Exchange Server 2003 configured as a standalone server, not as part of a Windows cluster; Only the Microsoft Virtual Machine PCI SCSI Controller driver installed as a SCSI driver; The virtual hard disk with the Undo feature not enabled. Microsoft Exchange 2007 is not supported for virtualization, but with the upcoming release of Windows Server2008’s Hyper-V, full support from Microsoft is imminent. As far as VMware ...
Access this Pro+ Content for Free!
Features in this issue
Virtualization deployments often introduce I/O bottlenecks at various levels of your physical infrastructure and undercut the gains of virtual servers. But with today’s tools, you can identify and loosen I/O choke holds at their source.
Virtualizing mission-critical systems like email can aid with storage and disaster recovery. But without understanding system requirements and mandates like Sarbanes-Oxley, you’ll get derailed
Virtualizing only certain aspects of Microsoft Exchange helps you get the benefits without undermining performance, says an expert.