Exchange Server 2003

Exchange Server 2003

Ports Used in Exchange Server 2003 The following table lists Exchange Server 2003 services and their corresponding ports. For more information about how to configure Exchange front-end servers, including the ports that are associated with various scenarios, see the technical article, Using Microsoft Exchange 2000 FrontEnd Servers. Although that article relates to Exchange 2000 Server, the information applies to Exchange Server 2003 as well. Ports used in Exchange 2003 Services (dependencies)

Ports inbound

Ports outbound (initiate connections to)

Notes

Microsoft Exchange System Attendant

135 & other RPC Other ports required for RPC over HTTP

Microsoft Exchange Information Store (Microsoft Exchange System Attendant)

135 & other RPC User Datagram Protocol (UDP)Runs the Exchange databases. Other ports packets to random ports for For more information about RPC over HTTP port required for RPC new mail notification configuration, see the guide Exchange Server 2003 over HTTP RPC over HTTP Deployment Scenarios.

Microsoft Exchange MTA Stacks (Microsoft Exchange System Attendant)

135 & other RPC 135 & other RPC 102 for X.400 102 for X.400 over TCP over TCP

Microsoft Exchange MTA Stacks are required for legacy connections to Exchange Server 5.5 servers. Port 102 opened only for active X.400 connections.

Simple Mail Transfer Protocol (SMTP) (IIS Admin Service)

25

25

Exchange store requires SMTP

Microsoft Exchange Routing Engine (IIS Admin Service)

691

691

Routing Engine service

World Wide Web Publishing Service (IIS Admin Service)

80 & 443

80 on the front-end server

Required for Outlook Web Access and public folder administration

UDP 2883 on the front-end server

Required for SP2 Exchange ActiveSync Direct Push

Exchange ActiveSync (IIS Admin Service)

All core Exchange services require the Microsoft Exchange System Attendant. For more information about RPC over HTTP port configuration, see the guide Exchange Server 2003 RPC over HTTP Deployment Scenarios.

Microsoft Exchange POP3 (IIS Admin Service)

110 & 995 (SSL) 110 on the front-end server

Required for POP3 access

Microsoft Exchange IMAP4 (IIS Admin Service)

143 & 993 (SSL) 143 on the front-end server

Required for IMAP4 access

Network News Transfer Protocol (NNTP) (IIS Admin Service)

119 & (563 SSL)

N/A

Microsoft Exchange Site Replication Service

379, 135 & other 135 & other RPC RPC

Depends whether Exchange Server 5.5 servers are in the organization.

Active Directory

NA

Depends whether Exchange Server 5.5 servers are in

379, 389, can be configured

Connector

the organization

Microsoft Exchange Event (Microsoft Exchange Information Store)

Not automatic by default

Exchange Management (Windows Management Instrumentation)

This is not a required service; however, Microsoft Operations Manager and other programs do not function without this service. Note: Port 445 is required for Message Tracking

Exchange Server 2003

Technical Details of Using RPC over HTTP to Access Exchange from an Outlook Client RPC over HTTP allows Microsoft® Office Outlook® 2003 clients to access Microsoft Exchange servers by using the MAPI protocol to tunnel Outlook RPC requests inside an HTTP session, or tunnel. Typically, an Outlook 2003 client contacts an Exchange server over a TCP session. If you use RPC over HTTP, you can use Outlook 2003 to access Exchange Server over the Internet, because HTTP is a common Internet protocol. The HTTP session terminates at a server running Internet Information Services (IIS) that has the Microsoft Windows Server™ 2003 RPC over HTTP Proxy networking component installed. This server is called an RPC proxy server. It is recommended that your RPC proxy server is an Exchange front-end server. The RPC over HTTP Proxy networking component extracts the RPC requests from the HTTP request and forwards the RPC requests to the appropriate server. The advantage of this approach is that only the RPC proxy server has to allow access from the Internet. Back-end Exchange servers do not have to allow access from the Internet. You should use the Secure Sockets Layer (SSL) to establish the HTTP session that you use to access Exchange Server over the Internet from an Outlook 2003 client. A common misconception is that the use of RPC over HTTP turns a Web request into an RPC request. Outlook 2003 sends the RPC request inside an HTTP tunnel. The actual RPC request does not change between the Outlook client and the Exchange server. The following figure shows an RPC request inside an HTTP tunnel. RPC request inside HTTP tunnel

Protocol: LDAP • •

Port (TCP/UDP): 389 (TCP) Description: Lightweight Directory Access Protocol (LDAP), used by Active Directory, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory.

Protocol: LDAP/SSL • • •

Port (TCP/UDP): 636 (TCP) Description: LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted. To enable SSL, you must install a Computer certificate on the domain controller or Exchange Server 5.5 computer.

Protocol: LDAP • •

Port (TCP/UDP): 379 (TCP) Description: The Site Replication Service (SRS) uses TCP port 379.

Protocol: LDAP •

Port (TCP/UDP): 390 (TCP)

•

Description: While not a standard LDAP port, TCP port 390 is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on a Microsoft Windows 2000 Active Directory domain controller.

Protocol: LDAP • •

Port (TCP/UDP): 3268 (TCP) Description: Global catalog. The Windows 2000 Active Directory global catalog (which is really a domain controller "role") listens on TCP port 3268. When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP.

Protocol: LDAP/SSL • •

Port (TCP/UDP): 3269 (TCP) Description: Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data. To configure a global catalog to support SSL, you must install a Computer certificate on the global catalog.

Protocol: IMAP4 • •

Port (TCP/UDP): 143 (TCP) Description: Internet Message Access Protocol version 4, may be used by "standards-based" clients such as Microsoft Outlook Express or Netscape Communicator to access the e-mail server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service (Inetinfo.exe), and enables client access to the Exchange 2000 information store.

Protocol: IMAP4/SSL • •

Port (TCP/UDP): 993 (TCP) Description: IMAP4 over SSL uses TCP port 993. Before an Exchange 2000 server supports IMAP4 (or any other protocol) over SSL, you must install a Computer certificate on the Exchange 2000 server.

Protocol: POP3 • •

Port (TCP/UDP): 110 (TCP) Description: Post Office Protocol version 3, enables "standards-based" clients such as Outlook Express or Netscape Communicator to access the e-mail server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange 2000 information store.

Protocol: POP3/SSL • •

Port (TCP/UDP): 995 (TCP) Description: POP3 over SSL. To enable POP3 over SSL, you must install a Computer certificate on the Exchange 2000 server.

Protocol: NNTP • •

Port (TCP/UDP): 119 (TCP) Description: Network News Transport Protocol, sometimes called Usenet protocol, enables "standards-based" client access to public folders in the information store. As with IMAP4 and POP3, NNTP is dependent on the IIS Admin Service.

Protocol: NNTP/SSL Port (TCP/UDP): 563 (TCP) Description: NNTP over SSL. To enable NNTP over SSL, you must install a Computer certificate on the Exchange 2000 Server. Protocol: HTTP • •

Port (TCP/UDP): 80 (TCP) Description: Hyper-Text Transfer Protocol is the protocol used primarily by Microsoft Outlook Web Access (OWA), but also enables some administrative actions in Exchange System Manager. HTTP is implemented through the World Wide Web Publishing Service (W3Svc), and runs on top of the IIS Admin Service.

Protocol: HTTP/SSL • •

Port (TCP/UDP): 443 (TCP) Description: HTTP over SSL. To enable HTTP over SSL, you must install a Computer certificate on the Exchange 2000 server.

Protocol: SMTP • •

Port (TCP/UDP): 25 (TCP) Description: Simple Mail Transfer Protocol, is the foundation for all e-mail transport in Exchange 2000. The SMTP Service (SMTPSvc) runs on top of the IIS Admin Service. Unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS).

Protocol: SMTP/SSL • •

Port (TCP/UDP): 465 (TCP) Description: SMTP over SSL. TCP port 465 is reserved by common industry practice for secure SMTP communication using the SSL protocol. However, unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange 2000 does not use a separate port for secure communication (SSL), but rather, employs an "in-band security sub-system" called Transport Layer Security (TLS). To enable TLS to work on Exchange 2000, you must install a Computer certificate on the Exchange 2000 server.

Protocol: SMTP/LSA

• •

Port (TCP/UDP): 691 (TCP) Description: The Microsoft Exchange Routing Engine (also known as RESvc) listens for routing link state information on TCP port 691. Exchange 2000 uses routing link state information to route messages and the routing table is constantly updated. The Link State Algorithm (LSA) propagates outing status information between Exchange 2000 servers. This algorithm is based on the Open Shortest Path First (OSPF) protocol from networking technology, and transfers link state information between routing groups by using the X-LSA-2 command verb over SMTP and by using a Transmission Control Protocol (TCP) connection to port 691 in a routing group.

Protocol: RVP • •

Port (TCP/UDP): 80 (TCP) Description: RVP is the foundation for Instant Messaging in Exchange 2000. While RVP communication begins with TCP port 80, the server quickly sets up a new connection to the client on an ephemeral TCP port above 1024. Because this port is not known in advance, issues exist when you enable Instant Messaging through a firewall.

Protocol: IRC/IRCX • •

Port (TCP/UDP): 6667 (TCP) Description: Internet Relay Chat (IRC) is the chat protocol. IRCX is the extended version offered by Microsoft. While TCP port 6667 is the most common port for IRC, TCP port 7000 is also very frequently used.

Protocol: IRC/SSL • •

Port (TCP/UDP): 994 (TCP) Description: IRC (or Chat) over SSL. IRC or IRCX over SSL is not supported in Exchange 2000.

Protocol: X.400 • •

Port (TCP/UDP): 102 (TCP) Description: ITU-T Recommendation X.400 is really a series of recommendations for what an electronic message handling system (MHS) should look like. TCP port 102 is defined in IETF RFC-1006, which describes OSI communications over a TCP/IP network. In brief, TCP port 102 is the port that the Exchange message transfer agent (MTA) uses to communicate with other X.400-capable MTAs.

Protocol: MS-RPC • •

Port (TCP/UDP): 135 (TCP) Description: Microsoft Remote Procedure Call is a Microsoft implementation of remote procedure calls (RPCs). TCP port 135 is actually only the RPC Locator Service, which is like the registrar for all RPC-enabled services that run on a particular server. In Exchange 2000, the Routing Group Connector

uses RPC instead of SMTP when the target bridgehead server is running Exchange 5.5. Also, some administrative operations require RPC. To configure a firewall to enable RPC traffic, many more ports than just 135 must be enabled. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base: 148732 XADM: Setting TCP/IP Port Numbers for Internet Firewalls 161931 XCON: Configuring MTA TCP/IP Port # for X.400 and RPC Listens Protocol: T.120 • •

Port (TCP/UDP): 1503 (TCP) Description: ITU-T Recommendation T.120 is a series of recommendations that define data conferencing. Data conferencing is implemented on the server side as a Conferencing Technology Provider (CTP) in the Multipoint Control Unit (MCU), which is one component of the Exchange Conferencing Services (ECS). Data conferencing is implemented on the client side as Chat, Application Sharing, Whiteboard, and File Transferring in Microsoft NetMeeting.

Protocol: ULS • •

Port (TCP/UDP): 522 (TCP) Description: User Locator Service is a type of Internet directory service for conferencing clients, such as NetMeeting. Exchange 2000 Server and Exchange 2000 Conferencing Server do not implement a ULS, but rather take advantage of Active Directory for directory services (by TCP port 389).

Protocol: H.323 (Video) • •

Port (TCP/UDP): 1720 (TCP) Description: ITU-T Recommendation H.323 defines multimedia conferencing. TCP port 1720 is the H.323 (video) call setup port. After a client connects, the H.323 server negotiates a new, dynamic UDP port to be used for streaming data.

Protocol: Audio • •

Port (TCP/UDP): 1731 (TCP) Description: Audio conferencing is enabled in much the same way as H.323 video conferencing is enabled in Exchange 2000 Server. After clients connect to TCP port 1731, a new dynamic port is negotiated for further streaming data.

Protocol: DNS •

Port (TCP/UDP): 53 (TCP)

•

Description: Domain Name System (DNS) is at the heart of all of the services and functions of Windows 2000 Active Directory and Exchange 2000 Server. You cannot underestimate the impact that a DNS issue can have on the system. Therefore, when service issues arise, it is always good to verify proper name resolution.

Related articles You might also want to read the following related articles: • • • • • • • • • • • • • •

Block Incoming Internet Mail to Specific Users or Groups Change the IMAP4 Banner Change the POP3 Banner Change the SMTP Banner Configure IIS to be a Smart Host for Exchange Configure MX Records for Incoming SMTP E-Mail Traffic Message Protocols Used by Exchange 2000/2003 Preventing Exchange 2000/2003 from Relaying Quickly Send Email Messages Remote Version Checking through SMTP/POP3/IMAP4 Send Mail from Script Send Mail (from the Tools and Scripts section) SMTP, POP3 and Telnet in Exchange 2000/2003 Test SMTP Service in IIS and Exchange

Links

Planning the migration from Microsoft's own "legacy XENIX-based messaging system" to Exchange Server environment began in April 1993 [1], and by January 1995 some 500 users were running on Exchange Server Beta 1. By April 1996 32,000 users were migrated to the environment. Exchange Server 4.0, released on June 11, 1996, was the original version of Exchange Server sold to the public, positioned as an upgrade to Microsoft Mail 3.5. The original version of Microsoft Mail (written by Microsoft) had been replaced several weeks after Lotus acquired cc:Mail by a package called Network Courier, acquired during the purchase of Consumer Software Inc. in April of 1991.[2] Exchange Server was however an entirely new X.400-based client-server mail system with a single database store that also supported X.500 directory services. The directory used by Exchange Server eventually became Microsoft's Active Directory service, an LDAP-compliant directory server. Active Directory was integrated into Windows 2000 as the foundation of Windows Server domains. On May 23, 1997, Exchange Server 5.0 was released, which introduced the new Exchange Administrator console, as well as opening up "integrated" access to SMTP-

based networks for the first time. Unlike Microsoft Mail (which required a standalone SMTP relay), Exchange Server 5.0 could, with the help of an add-in called the Internet Mail Connector, communicate directly with servers using the new mail standard. Version 5.0 also introduced a new Web-based e-mail interface Exchange Web Access, this was rebranded as Outlook Web Access in a later Service pack. Along with Exchange Server version 5.0, Microsoft released version 8.01 of Microsoft Outlook, version 5.0 of the Microsoft Exchange Client and version 7.5 of Microsoft Schedule+ to support the new features in the new version of Exchange Server. Exchange Server 5.5, introduced November, 1997, was sold in two editions, Standard and Enterprise. They differ in database store size, mail transport connectors and clustering capabilities. The Standard Edition had the same 16 GB database size limitation as earlier versions of Exchange Server, while the Enterprise Edition had an increased limit of 8 TB (although Microsoft's best practices documentation recommends that the message store not exceed 100 GB). The Standard Edition includes the Site Connector, MS Mail Connector, Internet Mail Service (previously "Internet Mail Connector"), and Internet News Service (previously "Internet News Connector"), as well as software to interoperate with cc:Mail, Lotus Notes and Novell GroupWise. The Enterprise Edition adds an X.400 connector, and interoperability software with SNADS and PROFS. The Enterprise Edition also introduced two node clustering capability. Exchange Server 5.5 introduced a number of other new features including a new version of Outlook Web Access with Calendar support, support for IMAP4 and LDAP v3 clients and the Deleted Item Recovery feature. Exchange Server 5.5 was the last version of Exchange Server to have separate directory, SMTP and NNTP services. There was no new version of Exchange Client and Schedule+ for version 5.5, instead version 8.03 of Microsoft Outlook was released to support the new features of Exchange Server 5.5. Exchange Server 2000, released on November 29, 2000, overcame many of the limitations of its predecessors. For example, it raised the maximum sizes of databases and increased the number of servers in a cluster from two to four. However, many customers were deterred from upgrading by the requirement for a full Microsoft Active Directory infrastructure to be in place, as unlike Exchange Server 5.5, Exchange Server 2000 had no inbuilt Directory Service, and had a dependency upon Active Directory. The migration process from Exchange Server 5.5 did not have any in-place upgrade path, and necessitated having the two systems online at the same time, with user-to-mailbox mapping and a temporary translation process between the two directories. Exchange Server 2000 also added support for Instant Messaging, but that capability was later spun off to Microsoft Office Live Communications Server. This migration was made significantly easier by Exchange Server 2003 (although still involved the same basic steps); many users of Exchange Server 5.5 waited for the release of Exchange Server 2003 to upgrade. The upgrade process also required upgrading a company's servers to Windows 2000. Some customers opted to stay on a combination of Exchange Server 5.5 and Windows NT 4.0, both of which are no longer supported by Microsoft.

[edit] Exchange Server 2003 Exchange Server 2003 debuted on September 28, 2003. Exchange Server 2003 (currently at Service Pack 2) can be run on Windows 2000 Server (only if Service Pack 4 is first

installed) and 32-bit Windows Server 2003, although some new features only work with the latter. Like Windows Server 2003, Exchange Server 2003 has many compatibility modes to allow users to slowly migrate to the new system. This is useful in large companies with distributed Exchange Server environments who cannot afford the downtime and expense that comes with a complete migration. One of the new features in Exchange Server 2003 is enhanced disaster recovery which allows administrators to bring the server online quicker. This is done by allowing the server to send and receive mail while the message stores are being recovered from backup. Some features previously available in the Microsoft Mobile Information Server 2001/2002 products have been added to the core Exchange Server product, like Outlook Mobile Access and server-side ActiveSync, while the Mobile Information Server product itself has been dropped. Better anti-virus and anti-spam protection have also been added, both by providing built-in APIs that facilitate filtering software and built-in support for the basic methods of originating IP address, SPF ("Sender ID"), and DNSBL filtering which were standard on other open source and *nix-based mail servers. Also new is the ability to drop inbound e-mail before being fully processed, thus preventing delays in the message routing system. There are also improved message and mailbox management tools, which allow administrators to execute common chores more quickly. Others, such as Instant Messaging and Exchange Conferencing Server have been extracted completely in order to form separate products. Microsoft now appears to be positioning a combination of Microsoft Office, Microsoft Office Live Communications Server, Live Meeting and Sharepoint as its collaboration software of choice. Exchange Server is now to be simply e-mail and calendaring. Exchange Server 2003 is available in two versions, Standard Edition and Enterprise Edition. Standard Edition supports one message database per server, and supports databases up to 16 GB in size. Beginning with the release of Service Pack 2, Standard Edition allows a maximum database size of 75 GB, but only supports 18 GB by default; larger sizes databases have to be opted-in with a registry change.[3] Enterprise Edition allows a 16 TB maximum database size, and supports up to 4 storage groups with 5 databases per storage group for a total of 20 databases per server.[4] Exchange Server 2003 is included with both Microsoft Small Business Server 2003 Standard and Premium editions and is 32-bit only, and will not install on the various 64bit versions of Windows Server 2003. Microsoft Exchange Server uses a proprietary RPC protocol, of which only the API is documented (see MAPI). It was designed to be used by the Microsoft Outlook client. Email hosted on an Exchange Server can be accessed using POP3 and IMAP4, with clients such as Mozilla Thunderbird and Lotus Notes. Both Microsoft Outlook and Novell Evolution are clients capable of using the advanced features of Exchange Server; Microsoft Entourage for Mac also has most of the advanced features implemented in the latest version. Exchange Server mailboxes can also be accessed through a web browser, known as Outlook Web Access (OWA). Exchange Server 2003 also featured a version of OWA for mobile devices, called Outlook Mobile Access (OMA). Coupled with Windows Mobile 5.0 AKU2 or higher, Exchange Server 2003 SP2 supports "pushing" e-mail to mobile devices - similar to the operation of BlackBerry devices.[5][6]

Unlike Exchange Server 2000, Exchange Server 2003 no longer ships instant messaging for internal corporate systems. Microsoft released Live Communication Server to provide those services as a standalone program. Exchange 2003 Anti-Spam Filtering: Exchange Server 2003 added several basic filtering methods to Exchange Server. They are not sophisticated enough to eliminate spam, but they can protect against DoS and mailbox flooding attacks. Exchange Server 2000 supported the ability to block a sender's address, or e-mail domain by adding '*@domain.com', which is still supported in Exchange Server 2003. Added filtering methods in Exchange Server 2003 are: • •

• •

Connection filtering - messages are blocked from DNS RBL lists[7] or from manually specified IP addresses/ranges Recipient filtering - messages blocked when sent to manually specified recipients on the server (for intranet-only addresses) or to any recipients not on the server (stopping spammers from guessing addresses) Sender ID filtering - Sender ID, a form of SPF Intelligent Message Filter - A free Microsoft add-on that uses heuristic message analysis to block messages or direct them to the "Junk E-Mail" folder in Microsoft Outlook clients.[8]

[edit] Exchange Server 2007 For some time after the release of Exchange Server 2003, Microsoft's future plans for the product were not known. Edge Services, an add-on for the main product, was to have been released sometime in 2005 but was dropped. The new version, Exchange Server 2007, was released in late 2006 to business customers as part of Microsoft's rollout wave of new products. It includes voice mail integration, better search and support for Web services, better filtering options, and a new Outlook Web Access interface. Exchange Server 2007 runs on 64-bit x64 versions of Windows Server only, pointing out the substantial performance benefits that 64-bit computing brings to the product. This limitation applies to supported production environments only; a 32-bit trial version is available for download and testing. However, companies currently running Exchange Server on 32-bit hardware will be forced to replace or migrate hardware if they wish to upgrade to the new version. Companies that are currently running Exchange Server on 64-bit capable hardware are still required to simultaneously upgrade their server operating system to a 64-bit version in order to use Exchange Server 2007. The first beta of Exchange Server 2007 (then named "Exchange 12") was released in December 2005 to a very limited number of beta testers. A wider beta was made available 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.

[edit] Key improvements The principal enhancements, as outlined by Microsoft, are:[9]

• • • •

•

• •

Protection: anti-spam, antivirus, compliance, clustering with data replication, improved security and encryption Improved Information Worker Access: improved calendaring, unified messaging, improved mobility, improved web access Improved IT Experience: 64-bit performance & scalability, command-line shell & simplified GUI, improved deployment, role separation, simplified routing "Exchange Management Shell": a new command-line shell and scripting language for system administration (based on Windows PowerShell). Shell users can perform every task that can be performed in the Exchange Server graphical user interface plus additional tasks, and can program often-used or complex tasks into scripts that can be saved, shared, and re-used. "Unified Messaging" that lets users receive voice mail, e-mail, and faxes in their mailboxes, and lets them access their mailboxes from cell phones and other wireless devices. Voice commands can be given to control and listen to e-mail over the phone (and also send some basic messages, like "I'll be late") Removed the database maximum size limit. Database size is now limited by hardware capability and the window for backups and maintenance. Increased the maximum number of storage groups and mail databases per server, to 5 each for Standard Edition (from 1 each in Exchange Server 2003 Standard), and to 50 each for Enterprise Edition (from 4 groups and 20 databases in Exchange Server 2003 Enterprise).

[edit] Clustering and High Availability Exchange Server Enterprise Edition supports clustering of up to 4 nodes when using Windows 2000 Server, and up to 8 nodes with Windows Server 2003. Exchange Server 2003 also introduced Active/Active clustering, but for two node clusters only. In this setup, both servers in the cluster are allowed to be active simultaneously. This is opposed to Exchange's more common Active/Passive mode in which the failover servers in any cluster node cannot be used at all while their corresponding home servers are active. They must wait, inactive, for the home servers in the node to fail. Subsequent performance issues with Active/Active mode have led Microsoft to recommend that it should no longer be used.[10] In fact, support for Active/Active mode clustering has been discontinued with Exchange Server 2007. Exchange's clustering (Active/Active or Active/Passive mode) has been criticised because of its requirement for servers in the cluster nodes to share the same physical data. The clustering in Exchange Server provides redundancy for Exchange Server as an application, but not for Exchange data.[11] In this scenario, the data can be regarded as a single point of failure, despite Microsoft's description of this set up as a "Shared Nothing" model.[12] This void has however been filed by ISV's and storage manufacturers, through "site resilience" solutions, such as geo-clustering and asynchronous data replication.[13] Exchange Server 2007 introduces new cluster terminology and configurations that address the shortcomings of the previous "shared data model".[14] Exchange Server 2007 now provides built-in support for asynchronous replication modeled on SQL Server's "Log Shipping"[15] in CCR (Cluster Continuous Replication)[16] clusters, which are built on MSCS MNS (Microsoft Cluster Service - Majority Node Set)

clusters which do not require shared storage. This type of cluster can be inexpensive and deployed in one, or "stretched" across two datacenters for protection against site wide failures such as natural disasters. The limitation of CCR clusters is ability to have only two nodes and the third node known as "voter node" of file share witness[17] that prevents "split brain"[17] scenarios, generally hosted as a file share on a Hub Transport Server.[18] Second type of clusters is the traditional clustering that was available in previous versions, and is now being referred to as SCC (Single Copy Cluster). In Exchange Server 2007 deployment of both CCR and SCC clusters has been simplified and improved where the entire cluster install process takes place during Exchange Server install. LCR or Local Continuous Replication[18] has been referred to as the "poor man's cluster". It is designed to allow for data replication to an alternate drive attached to the same system and is intended to provide protection against local storage failures. It does not protect against the case where the server itself fails. In February, the Microsoft Exchange team announced they are wrapping up the beta release of SP1 for Exchange Server 2007. It was announced that SP1 will include an additional high avabilibity feature called SCR (Standby Continuous Replication). Unlike CCR which requires that both servers belong to a Windows cluster, typically residing in the same datacenter, SCR can replicate data to a non-clustered server, located in a separate datacenter.

[edit] Licensing Like Windows Server products, Exchange Server requires Client Access Licenses, which are different from Windows CALs. Most corporate license agreements include Exchange Server CALs. For Service Providers looking to host Microsoft Exchange, there is a SPLA (Service Provider License Agreement) available whereby Microsoft receives a monthly service fee in the place of the traditional Client Access Licenses.

[edit] Exchange hosting Microsoft Exchange Server can also be purchased as a hosted service from a number of providers.[19]

[edit] See also • • • •

Extensible Storage Engine List of collaborative software Microsoft Exchange Client Microsoft Servers

[edit] References 1. ^ Microsoft's Migration to Microsoft Exchange Server - The Evolution of Messaging within Microsoft Corporation. Retrieved on May 2, 2007. 2. ^ Paul Korzeniowski. E-mail becoming foundation for networked applications electronic mail; local area network. Software Magazine. Retrieved on 2007-07-02.

3. ^ Registry tweak to set a 75gb store limit on Exchange 2003 Standard Sp2. Retrieved on 2007-07-02.

4. ^ Exchange 2003 editions. Retrieved on 2007-07-02. 5. ^ New Mobility Features in Exchange Server 2003 SP2. TechNet. Retrieved on 2007-0702.

6. ^ Microsoft Looks to Mobilize With Exchange SP2. Retrieved on 2007-07-02. 7. ^ Implementing and Configuring Blacklist Support in Exchange Server 2003. Retrieved on 2007-07-02.

8. ^ Exchange Intelligent Message Filter. Retrieved on 2007-07-02. 9. ^ Microsoft Exchange Server Website 10. ^ Considerations when deploying Exchange on an Active/Active cluster. Retrieved on 2007-07-02. (Logging in required)

Exchange public folders FAQs 31 Oct 2005 | SearchExchange.com RSS FEEDS:

Exchange Server tips, tutorials and expert advice

Creating and managing Exchange Server public folders can be a tricky business. In the list of frequently asked questions below, you'll discover a wealth of information from configuring and troubleshooting permissions to recovering and exporting data. Frequently Asked Questions:

EXCHANGE SERVER PUBLIC FOLDERS 1. 2. 3. 4. 5. 6. 7. 8.

Configuring public folders in Exchange 2003 Recovering public folder data Recovering a deleted public folder subfolder Creating top-level public folder permissions Propagating permissions to all public folder subfolders Using a public folder as a distribution list Expanding Exchange public folders Copying large amounts of contact information to a public folder 9. Exporting from a user's Outlook calendar to a public folder calendar 10. Public folder messages converting from ipm.note to ipm.post 11. How storage limits work in a public folder hierarchy 12. How to view public folders in Outlook 2003 public folders in Exchange 2003

Configuring

How do I configure public folders in Exchange 2003, and what are the advantages of public folders? Good question. Public folders provide a way of sharing Exchange data across your Exchange organization inside of Exchange. You configure public folders from within Exchange System Manager. Navigate to the appropriate Administrative Group and expand the public folders container. You can create and configure public folders from here. Once top-level public folders are created, users with adequate permissions will be able to create subfolders and store content. I strongly recommend that you keep public folder usage under tight control. Microsoft has suggested that public folders will be phased out of Exchange gradually, with the logical replacement being SharePoint Portal Server. Return to Exchange public folders FAQs Recovering public folder data