Some of Windows 64-bit x86-64 versions is needed to try Exchange Server 2007 (v8 or v8.1 with SP1 accessible). But it features only full versions and a 32-bit trial version is open to anyone. If there are any firms applying Exchange Server with 32-bit equipment, they’ll be informed of the time to change their hardware in a certain period. Still that is not the single thing. According to the fact that Exchange Server 2007 doesn’t provide in-place upgrading a number of firms using programs of 2000 or 2003 will need to upgrade to the edition of 2007.

In winter 2005 there came the first beta version of Exchange Server 2007, that was called E12 or Exchange 12. Not too many users could try it then. As fixed in Microsoft Exchange team archives a developed beta version appeared in early spring 2006. It turned accessible with TechNet Plus and MSDN subscriptions. In some time, on April 25, everybody knew that the coming version to be let out by Microsoft will be known as Exchange Server 2007.

Exchange Server 2007 belongs to the Innovative Communications Alliance products. Below are the exchange host server roles to be components of the program release of 2007.

1. The Role of Mailbox
It keeps pand sorts mail. MAPI access for those who use Outlook is also provided by the role. Clustered Mailbox role is a modification of common Mailbox. It is greatly useful to cluster incoming data with MSCS. This role can be never used in combination with any other role on the hosted exchange.

2. Client Access Role
Client Access doesn’t apply MAPI, it is meant for another mailbox server protocol admission. Like that it’s affordable for the user to access his mail with a network browser, mobile gadget and 3rd party mail client. Absolutely like in Exchange 2003 FrontEnd hosting.

3. Unified Message or UM
Applying this role the users can read their mail, enter address books or anything with just a telephone. But an IP-PBX gateway has to be definitely provided for those who want to apply the server role fully.

4. Hub Transport or HT
Resending mails to their next destinations is the task of this role. Worked over, they are delivered to either some different Hub Transport, mailbox or Edge hosting. Well, if Exchange 2003 Bridgehead manages mailbox flow with admin fixed groups, this 2007 edition applies AD site data to arrange it.

5. ET (Edge Transport)
Edge Transport is used to work over both incoming and outbox. It’s quite a great thing for some BES so it is often used in perimeter networks as it provides mail quarantine. Edge Transport may also function even if it is not linked to any Active Directory. It caters for security even with only company network.

Tasks for Server Roles. User Interface

Server settings for Graphic User Interface and Cmdlet are connected with the server role idea. Each server role is designed just for its functions in Exchange 2007. As for Mailbox, its function is Get/Set-MailboxServer and the operator to check if it is installed is IsMailboxServer. And so that will be Get/Set-ClientAccessServer and IsClientAccessServer for Client Access role. Hub Transport role with features Get/Set-TransportServer will be simply proved with IsHubTransportServer. And finally Unified Message works with commands like Get/Set-UmServer and IsUnifiedMessagingServer.