Home > Articles > Software Development & Management

  • Print
  • + Share This
This chapter is from the book

Designing Remote Access to Exchange 2000

As the concept of the "office" changes, businesses are realizing the value of creating a more mobile workforce. In order for an organization to maintain pace with this evolution, remote access has become a requirement. For that reason, Exchange 2000 has developed and, more importantly, refined the remote access component of Exchange 2000, Outlook Web Access (OWA).

Planning and Designing Outlook Web Access (OWA)

Outlook Web Access allows mail access using the Internet. The interface is consistent with the client installed on the desktop. However, it is a pared down version. That is not to say that the important core features are not available via the Internet. Users will be able to access all mail stored on the Exchange server in addition to their address lists, calendars, and Public Folders. The ability to offer the option of accessing mail regardless of the user's location makes this one of the major features of Exchange 2000.

Outlook Web Access Architecture

The focus of this section is the different architecture options available when designing Outlook Web Access. The OWA component is installed on the Exchange Server by default. There are three design options for Outlook Web Access. They are the single-server model, the multiserver model, and the multiserver model with Secured Socket Layer (SSL) enabled.

  • Single-server model. In the single-server model the Internet Information Server (IIS) directly delivers client HTTP requests to the mailbox store using a high-speed internal channel.

  • Multiserver model. In the multiserver model, client HTTP requests are passed to the Exchange server by a proxy using the HTTP protocol. The advantage gained with this model is the ability to use a single front-end server to service multiple back-end servers. Also, with the use of Network Load Balancing (NLB), multiple front-end servers can be clustered to accept and service client requests.

  • Multiserver model with Secured Socket Layer (SSL) enabled. This configuration is the same as the preceding configuration. However, the difference is that Secured Socket Layer (SSL) is enabled. Again, this adds an additional layer of security by encrypting the communications between the client and the front-end servers.

Now that the three architectural models have been described, the next step is to determine which model will work best based on needs of the organization. As you select the model best suited for your organization's requirements, there are important rules to consider that should be followed for both the single and the multiserver model.

  • Single-server rule. In a single server rule, the server setup to run Exchange 2000 can also be the system that'll host the Outlook Web Access server services. This minimizes the number of systems the organization needs to have, and provides full access for an organization that may have fewer than 50–100 total users.

  • Multiserver rule. In a multiple server rule, OWA servers should be dedicated to perform Web-based message access. For example, front-end servers are used only as the OWA server(s) and the back-end server(s) are the actual Exchange mail store servers. Servers should not serve mixed roles.

  • NOTE

    Exchange 2000 Server Enterprise Edition must be installed in order to take advantage of the front-end server feature. To configure this feature, use the Exchange System Manager.

  • Multiserver rule. By default, front-end servers are configured to automatically service all back-end servers within the Exchange organization. In practice, this is not recommended. Instead, target the front-end server for specific back-end servers. This is important when SSL is enabled due to the amount of overhead required to process SSL connections.

Outlook Web Access Security

There are security considerations when planning for the deployment of Outlook Web Access to the enterprise. The current security implementation will impact the design of Outlook Web Access. In a multiserver configuration, the primary consideration is server placement. There are three available options: internal, perimeter, or demilitarized zone (DMZ). These three design options will be discussed in detail.

Internal Network

An internal network configuration is recommended only under certain circumstances; specifically, in scenarios where Outlook Web Access is deployed for users roaming or roving between locations within the organization. For example, these users will be accessing the Outlook Web Access server exclusively through the corporate intranet.

Perimeter Network

Users will access the front-end server from the Internet using a Web browser over HTTP or HTTPS (HTTP over SSL). It is important to remember that the front-end server should reside only on the perimeter network as shown in Figure 3.4 if there is a firewall and/or proxy server between the front-end and back-end servers.

The front-end server is a dedicated Exchange 2000 Enterprise installation with the front-end feature enabled. It communicates with the back-end server within the private network via Lightweight Directory Access Protocol (LDAP) on port 389. Port 3268 needs to be opened on the firewall. This allows the front-end server to have access to the internal Global Catalog.

Port 80 for HTTP traffic also needs to be enabled to allow communication to the back-end server. The back-end server is a standard Exchange 2000 server that hosts mail or public folder stores. If security is an issue, the front-end and back-end servers should be configured to communicate using IP secure protocol to encrypt all communications.

Figure 3.4 Perimeter configuration.

Demilitarized Zone (DMZ)

The DMZ shown in Figure 3.5 is similar to the perimeter network scenario, with one exception. The front-end server is isolated from the public Internet. It provides an additional level of protection for the front-end because all communication with this machine is protected and controlled by the firewall. It is strongly suggested that this design configuration be used in all circumstances where external access is required.

Figure 3.5 DMZ configuration.

Authenticating OWA Clients

Microsoft recommends that authentication should occur only on the back-end servers. The reason for this recommendation is security. It is more important that the back-end servers are secured than the front-end servers. By designating the back-end server as the authentication server, possible conflicts between the front-end and the back-end are minimized.

There are several authentication options available with Outlook Web Access. The option used by an organization is based on both the existing security policies and the installed Internet browser software used to access Outlook Web Access.

  • Basic—Challenge/response using clear text. Basic authentication where clear text is used for transmitting the password is not a secure method of authentication and is usually not advised as the method of logon authentication when security is of concern.

  • Integrated Windows. Integrated Windows authentication uses the security attributes of the remote client to validate the user's identity and logon authentication information to access the messaging system.

  • Digest. The Digest option provides secure authentication using cryptology.

  • Anonymous. The Anonymous option allows for general access to specifically designated Public Folders without logon authentication. This is usually a good solution for remote users to access completely unsecured public information that requires no user validation.

  • Secured Socket Layer (SSL). SSL makes available a secure communication channel that can be used with the Basic, Integrated Windows, Digest, and Anonymous methods of authentication.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020