Exchange Server 2007 and Virtualization

Only 64-bit versions of Exchange 2007 are sold (a 32-bit exists but is not sold by Microsoft and was created only for test environments). For their part, the two virtualization software currently marketed by Microsoft (Virtual PC 2007 and Virtual Server 2005 R2) are only able to manage virtual machines in 32-bit (even if the host is 64-bit). It is possible to install a 32-bit test version of Exchange 2007 in a virtual machine but not this version can not be dismissed (because Microsoft only sells licenses for 64-bit product). This is unfortunate because virtualization can reduce hardware costs (eg in the case of a cluster, it might be interesting to create a passive node as a virtual machine while maintaining an active node dedicated).

The arrival of Longhorn Server will change the in virtualization! Indeed the architecture of the next Microsoft server OS has been designed to generalize the creation and production of virtual machines (the system itself is also regarded as a virtual machine). The sub-component used by Longhorn Hypervisor is called and it will bring, among other things, support for 64-bit virtual machines. Therefore, it is possible to production Exchange 2007 as a virtual machine from the time Longhorn will be installed!

Like previous versions, Exchange Server 2007 is available in Standard Edition and Enterprise Edition. The Standard Edition is limited in the number of databases (5 bases in length.) However the size of these bases is not capped (with Exchange 2003 standard edition the maximum file size is 16GB, and RTM 75Go if SP2 is deployed). This means that databases can "grow" indefinitely from the time when there is enough disk space. The databases can be placed in the same storage group or storage in five separate groups (indeed The standard edition of Exchange 2007 supports the creation of five storage groups maximum). The enterprise edition of Exchange 2007 supports in turn, up to 50 storage groups for a maximum of 50 databases. Furthermore, only the Enterprise Edition supports the establishment of a failover cluster (cluster SCC or CCR cluster).

It is possible to switch from one version to another without reinstalling. In fact just change the product key via the management console (this is possible because the same sources are used for both editions). For upgrades only cons are taken into account (id is: it is impossible to "downgrade" except by uninstalling the product). Here is a list of changes supported License:

• Skip a license to a standard license TRIAL
• Skip a license to an enterprise license TRIAL
• Moving from a standard license to a business license

:whistling

I would like to continue the discussion about this topic. The role server mailboxes (Mailbox Server) is the equivalent of back-end server in an Exchange 2003 topology. This machine hosts the user mailboxes and public folders in the form of databases (or banks). It is also she who manages access MAPI clients (although the message routing is not provided by this server). This role is the only one that can be clustered (implied with Microsoft clustering services or MSCS). The Client Access server role (Client Access Server) is the equivalent of front-end server in Exchange 2003 topology. This includes management of all non-MAPI Access (OWA ActiveSync, POP3, IMAP4, Outlook Anywhere ...) but also support improvements like the function sharing access OWA / ActiveSync (also known as Direct File Access), the automatic detection service (function autoconnect Outlook 2007), the system of planning meetings.

The Hub Transport server roles (Hub Transport) is responsible for routing messages to its Active Directory site (equivalent bridgehead server in routing group Exchange 2003). This server is designed to redirect mail to an external server or Edge Transport to an SMTP gateway (it can optionally be configured to send mail outside itself). It is recommended to put an antivirus on the server "hub" because it is through the gateways for e-mails (anti-spam features can be turned on for this role).