Dec 06

You will have to get 64-bit x86-64 editions of Windows to use v8 or even v8.1 of Exchange Server 2007. Anyway just 32 bits are demanded for the trial edition of this program. Anyway some firms will have to change the equipment they are using as they keep on operating in Exchange Server with 32-bit equipment. But that is not the only thing. According to the fact that Exchange Server 2007 doesn't allow in-place upgrades a number of companies using software of 2000 and 2003 will need to move 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 people could try it then. Later in early spring 2006 the release of one more developed beta edition was fixed. Developer team of the program made it accessible with TechNet Plus and MSDN subscriptions. And finally in April 2005 the enterprise officially appointed the new edition of the program to have the name of Exchange Server 2007.

Exchange Server 2007 belongs to the Innovative Communications Alliance products. The exchange server roles in Exchange Server 2007 are to be the following:

1. Mailbox Role
It keeps open data and sMAPI service for those who apply Outlook is also provided by Mailbox. Mailbox has its variation. To apply high-availability MSCS clustering of data kept on the computer Clustered Mailbox role is used. Clustered Mailbox cannot ever be applied together with any different role on the hosted exchange.

2. Client Access or CA
The role doesn't use MAPI, it is supposed for a different mailbox server protocol access. It as well lets use any handy services of Exchange 2003 FrontEnd hosting like ActiveSync (mobile device), POP3/IMAP4 e-mail clients or an OWA (Internet browser).

3. UM – Unified Message
With this role the users may list their messages, enter address books or something with just a telephone. Still an IP-PBX gateway needs to be surely provided for those who wish to apply the server role fully.

4. Hub Transport or HT
Routing mails to their next steps is the task of HT. Processed, they are sent to some different Hub Transport, mailbox or Edge hosting. And if Exchange 2003 Bridgehead manages mailbox flow with admin set groups, this 2007 edition uses AD site info to arrange it.

5. ET (Edge Transport)
ET is used to process both incoming and outgoing mail. Specially to apply mail quarantine ET is quite often applied in some blackberry enterprise server. It appears also smart that ET doesn’t demand Active Directory access. Working with cut admission to some firm’s network is quite enough for it to cater for safety.

Aims for Server Roles. User Interface

Server settings for Graphic User Interface and Cmdlet are connected with the server role concept. For each destination there is its own role in Exchange Server 2007. Get/Set-MailboxServer is the function for Mailbox. You may see whether you have it working with a command IsMailboxServer. Client Access role will then possess the function like Get/Set-ClientAccessServer and IsClientAccessServer. HT role with features Get/Set-TransportServer will be simply checked with IsHubTransportServer. And finally UM functions with operators like Get/Set-UmServer and IsUnifiedMessagingServer.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

You must be logged in to post a comment.