Access your Pro+ Content below.
Do this before virtualizing Exchange Server 2010
This article is part of the Exchange Insider issue of November 2010, Vol. 7
Microsoft Exchange Server is one of the most mission-critical IT services for many enterprises. When mail servers are down, so is the entire business communication infrastructure. Virtualizing Exchange combines the server’s high-availability features with all of the benefits that virtualization brings to Windows servers. The steps involved in creating a virtual Exchange 2010 server aren’t all that different from those used to create a physical one. The primary difference lies with the creation of a virtual machine (VM). The real planning takes place in these five steps you need to do before you even click New -> Virtual Machine. Step 1: Select and verify a hypervisor Microsoft doesn’t support every configuration of Exchange Server running on a hypervisor. The company recognizes that Exchange is a high-priority workload that consumes a lot of resources, so it places limits on what it allows you to virtualize. Microsoft supports Exchange 2010 on hypervisors that have been validated by the Windows Server Virtualization Validation ...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
Virtualizing Exchange 2010 servers is a smart move, and the steps involved are fairly simple. The actual virtualization process begins long before you create a VM.
When Outlook Web App’s default settings just won’t do, it’s time to tweak. Certain configuration changes will help OWA run more efficiently and securely.
After you've installed Exchange Server for a client, it's time to write the installation documentation. Providing consistent and easy-to-understand documentation is vital for both Exchange administrators and users. These three principles of good documentation writing can help.