Exchange Server 2007was released in late 2006 to firm customers as part of Microsoft's roll-out wave of new products. It includes new clustering options, 64-bit preserve for greater scalability, voice mail integration, great hunt and preserve for Web services, great filtering options, and a new Outlook Web entrance interface. Exchange 2007 also dropped preserve for Exchange 5.50 migrations, routing groups, admin groups, Outlook movable Access, X.400, and some Api interfaces, surrounded by other features.
Exchange Server 2007 (v8 or with Sp1 v8.1) runs on 64-bit x86-64 versions of Windows Server only. This requirement applies to supported yield environments only; a 32-bit trial version is ready for download and testing. However, fellowships currently running Exchange Server on 32-bit hardware will be required to replace or migrate hardware if they wish to upgrade to the new version. fellowships that are currently running Exchange Server on 64-bit capable hardware are still required to migrate from their existing Exchange 2000/2003 servers to a new Server 2007since in-place upgrades are not supported in 2007.
Server
The first beta of Exchange Server 2007 (then named "Exchange 12" or E12) was released in December 2005 to a very miniature estimate of beta testers. A wider beta was made ready via TechNet Plus and Msdn subscriptions in March 2006 according to the Microsoft Exchange team blog On April 25, 2006, Microsoft announced that the next version of Exchange Server would be called Exchange Server 2007.
Exchange Server 2007 is an integrated part of the Innovative Communications Alliance products. At Exchange 2007 release, the server roles will be:
- Mailbox (Mb): The Mailbox server role is responsible for hosting mailbox and group briefcase data. This role also provides Mapi entrance for Outlook clients. Note that there is also a incompatibility of this role called Clustered Mailbox role, for use with high-availability Mscs clustering of mailbox data. When Clustered Mailbox role is selected, other server roles cannot be combined on the same corporeal server.
- Client entrance (Ca): The Client entrance server role provides the other mailbox server protocol entrance apart from Mapi. Similar to Exchange 2003 FrontEnd server, it enables user to use an Internet browser (Owa), 3rd party mail client (Pop3/Imap4) and movable device (ActiveSync) to entrance their mailbox.
- Unified Message (Um): This role enables end users to entrance their mailbox, address book, and calendar using telephone and voice. Ip-Pbx or VoIp gateway needs to be installed and configured to facilitate much of the functionality of this server role.
- Hub converyance (Ht): The Hub converyance role handles mails by routing them to next hop: another Hub converyance server, Edge server or mailbox server. Unlike Exchange 2003 Bridgehead that needs Exchange admin defined routing groups, Exchange 2007 Hub converyance role uses Ad site info to conclude the mail flow.
- Edge converyance (Et): The last hop of outgoing mail and first hop of incoming mail, acting as a "smart host" and regularly deployed in a perimeter network, Edge converyance provides mail quarantine and Smtp service to improve security. One advantage of this role is that is does not require Active Directory access, so it can function with miniature entrance to the corporate network for increased security.
Server Role Tasks and Ui
Server configuration for both Cmdlet and Gui is organized around the server role concept. To check what roles are installed on the server, you can use task: Get-ExchangeServer and check properties: IsMailboxServer, IsClientAccessServer, IsHubTransportServer and IsUnifiedMessagingServer. For each role, Exchange 2007 provides dedicate tasks to carry on properties exact to each server role:
- Get/Set-MailboxServer
- Get/Set-ClientAccessServer
- Get/Set-TransportServer
- Get/Set-UmServer
Note that Get/Set-TransportServer is used by both converyance server roles (Hub converyance and Edge Transport). Please refer to help for more detailed info regarding these tasks. In Exchange 2007 administration console under Server Configuration, each server role has a dedicated node with the role name. Servers with the prime role installed will be listed in the results pane for each server role node. A singular server will appear in many results panes if many server roles are installed on that server. This build gives user a clear view on what servers are ready for each exact server role.
What is Microsoft change Server 2007?
No comments:
Post a Comment