One of Windows 64-bit x86-64 editions is needed to apply Exchange Server 2007 (v8 or v8.1 supposing SP1 available). Anyway just 32 bits are required for the trial edition of this software. Still some companies will have to replace the hardware they are using for they keep on working in Exchange Server with thirty two-bit hardware. Still hardware is not the single point. Due to the fact that Exchange Server 2007 doesn't allow in-place upgrading some firms using software of 2000 and 2003 will need to upgrade to the edition of 2007.
"Exchange 12", the 1st beta edition of Exchange Server 2007, was available in December 2005 first for a small number of people. Later in early spring 2006 the appearance of one more developed beta version was realized. Developer team of the software made it accessible via TechNet Plus and MSDN subscriptions. And then in April 2005 the company confidently appointed the coming version of the program to be called Exchange Server 2007.
In fact Exchange 2007 is included into those Innovative Communications Alliance developments. The hosting exchange server roles in Microsoft Exchange 2007 are to be like this:
1. Mailbox Role
It serves as hosting for some information available to people. MAPI service for those who use Outlook is also provided by the role. The role has its modification. To use high-availability MSCS clustering of information kept on the computer Clustered Mailbox role is applied. This role cannot ever be applied in combination with any different role on the exchange hosting.
2. Client Access or CA
Client Access is meant to cater for the mail storage service protocol access with no links to MAPI. Like that it’s possible for the one who uses it to access his mailbox with an Internet browser, mobile device and 3rd party mail client. Absolutely like in Exchange 2003 FrontEnd server.
3. UM – Unified Message
Applying this role the users may read their mail, manage address books or something with only a telephone. But a VoIP gateway has to be surely catered for the people who wish to use the server role well.
4. Hub Transport or HT
Managing messages and sorting them according to the route of each is the aim of HT. Exchange 2007 classifies the message amounts using AD site data, which differs from the strategy of 2003 when admin fixed routing groups were used.
5. The Role of Edge Transport
That is the 1st step for inbox and the last one for outbox. In Windows SharePoint Services ET is supposed to be a very handy role. It’s applied to provide mail quarantine. Edge Transport can also function even if it is not connected with any Active Directory. It caters for safety even with only corporative network.
UI and Server Role Features
Server role concept actually sets the server configuration for Graphic User Interface and CMD. In Exchange 2007 every role that supposes its own functions is designed to perform them. Get/Set-MailboxServer is the function for Mailbox. You can see whether you have it installed with a command IsMailboxServer. Client Access role will then possess the function like Get/Set-ClientAccessServer and IsClientAccessServer. Hub Transport role with functions Get/Set-TransportServer will be simply checked with IsHubTransportServer. And commands like IsUnifiedMessagingServer and Get/Set-UmServer are referred to UM role.