a
With multiprocessor support for 8-way Pentium and XEON processors, memory-tuning options via the /3GB switch and /USERVA switch, and IPSec server communication between Exchange 2003 front-end and back-end servers, Windows Server 2003 is the operating system of choice. Although Exchange Server 2003 can be run on Windows 2000 Server SP3 and later, Windows Server 2003 should be run to take advantage of enterprise class features, such as enhanced reliability, remote access, and server clustering.
With multiprocessor support for 8-way Pentium and XEON processors, memory-tuning options via the /3GB switch and /USERVA switch, and IPSec server communication between Exchange 2003 front-end and back-end servers, Windows Server 2003 is the operating system of choice. Although Exchange Server 2003 can be run on Windows 2000 Server SP3 and later, Windows Server 2003 should be run to take advantage of enterprise class features, such as enhanced reliability, remote access, and server clustering.
a
Server Reliability
a
Windows Server 2003 improves on the server platform reliability delivered in Windows 2000 Server. With improvements in the underlying server architecture, Active Directory performance, management, and maintenance tools, as well as support for new technologies such as the Volume Shadow Copy Service (VSS) and server clustering, Windows Server 2003 represents major enhancements to the reliability and scalability of Exchange 2003. Cluster Fail Over and Fail Back technology and snapshot backup technology with VSS will dramatically reduce server downtime and provide creative options for disaster recovery. Because the reliability of the server platform has been significantly improved, organizations can look at reducing costs by reducing the amount of money spent on purchasing and supporting multiple servers and network infrastructure.
a
Remote Access
Remote Access
a
Windows Server 2003 also significantly improves remote access capability for Exchange users. One of the most noted improvements is the capability for Outlook 2003 users to communicate securely with Exchange servers via RPC over an HTTP connection. This connection over the Internet eliminates the need for tunneling technologies such as Virtual Private Networks (VPNs), smart cards, and other secure access technologies. Coupled with the new Outlook 2003 Cached mode, which allows users to have a full copy of their mailboxes available at all times and eliminates the need for a continuous connection to the email server or network, RPC over HTTP provides a secure and reliable method for remote access across slow or problematic network connections. This option is available only with Windows 2003 Server.
a
Server Clustering
a
Clustering services in Windows Server 2003 provide dramatic improvements by enhancing existing features found in previous versions and also offering new key options. Unlike Windows 2000 Server cluster support for only two nodes, Windows Server 2003 Enterprise Edition and Datacenter Edition provide support for up to 8-node clustering. Clusters can be created in various active/passive node configurations, such as seven active/one passive or four active/four passive or in an Active/Passive with as little as one Passive node.
a
With preconfigurations, remote administration, and default settings, installation and setup are easier and more robust; basic server clusters can be up and running quickly, and with fewer server reboots.
With preconfigurations, remote administration, and default settings, installation and setup are easier and more robust; basic server clusters can be up and running quickly, and with fewer server reboots.
a
Clustering services are also closely integrated with Active Directory. This tight integration includes features such as Kerberos authentication, delegation, and security, and Active Directory-aware service integration with other services that publish information to Active Directory.
a
Enhanced network features such as improved failover logic, media sense detection, and multicast heartbeats provide greater failover capabilities and high system uptime. In addition, all internal cluster communications are signed and secure. With the addition of real-time monitoring tools, such as ClusDiag and ClusterRecovery, support personnel can locate failures and possible future cluster problems.
a
Understanding Front-End Servers
a
a
Front-end servers are deployed in an Exchange Server architecture that distributes server tasks among front-end and back-end servers. In this architecture, a front-end server accepts requests from clients and proxies them to the appropriate back-end server for processing and management of the information store. Exchange Server 2003 enhances the front-end and back-end server architecture of Exchange 2000 and adds new features and capabilities, such as RPC over HTTP communication, that enables users with Outlook 2003 clients to access their Exchange information from the Internet. In addition, the HTTP communication between front-end and back-end servers is enabled with Kerberos authentication by default; no longer is it necessary to configure and enable IPSec server-to-server communication unless the server is in a public network. Moreover, the scalability of the exchange organization is now enhanced because the topology can grow as the organization grows; back-end servers can easily be added to handle additional users, connections, or processing requests. Finally, the standard version of Exchange Server 2003 can also be configured as a front-end server, reducing initial software costs.
a
a
Using front-end and back-end server technology also provides the following advantages both for remote users accessing email over the Internet and users who are located on the internal network:
a
a
● Single Namespace A single, consistent namespace such as https://Outlook Web Access Server/ exchange for mailbox access allows administrative flexibility when adding or removing back-end servers, without affecting users who are accessing the front-end server. A single namespace also remains scalable for HTTP, POP, or IMAP access as the organization grows and reduces the number of server SSL certificates, because client computers are using SSL to the same servers and namespace.
● Offloading of SSL encryption and decryption SSL traffic presents a large overhead for Exchange servers. In a front-end and back-end setup, the front-end server assumes the load of the SSL encryption, freeing up the back-end server to handle email requests and processing only, improving overall email performance for the users.
● Improved Public Folder access Because a front-end server knows the state of a back-end server, the front-end server can provide multiple requests to public folder data and system data, such as calendar free/busy information. Exchange 2003 enhances the usability of OWA when using a front-end server by allowing OWA users to read, reply, and forward public folder postings. Public folder posts can be read only in a nonfront-end server topology.
● Security The front-end server can be positioned as the single point of access in front of or behind a firewall. It contains no user data stored in the server and acts as an additional layer of security for the exchange organization against Denial of Service attacks, authenticating requests before proxying them to the back-end servers. Any services that are not needed can be disabled on these servers for further security hardening.
● Offloading of SSL encryption and decryption SSL traffic presents a large overhead for Exchange servers. In a front-end and back-end setup, the front-end server assumes the load of the SSL encryption, freeing up the back-end server to handle email requests and processing only, improving overall email performance for the users.
● Improved Public Folder access Because a front-end server knows the state of a back-end server, the front-end server can provide multiple requests to public folder data and system data, such as calendar free/busy information. Exchange 2003 enhances the usability of OWA when using a front-end server by allowing OWA users to read, reply, and forward public folder postings. Public folder posts can be read only in a nonfront-end server topology.
● Security The front-end server can be positioned as the single point of access in front of or behind a firewall. It contains no user data stored in the server and acts as an additional layer of security for the exchange organization against Denial of Service attacks, authenticating requests before proxying them to the back-end servers. Any services that are not needed can be disabled on these servers for further security hardening.
Save to del.icio.us
