Microsoft Exchange Server 2003 Deployment Guide- P54 pot

For information about managing and configuring Outlook Web Access, see the following topics in the Exchange Server 2003 Client Access Guide:  Configuring Outlook Web Access  Managing

For information about managing and configuring Outlook Web Access, see the following topics in the Exchange Server 2003 Client Access

Guide:

 Configuring Outlook Web Access

 Managing Outlook Web Access

How to Start, Pause, or Stop a Virtual Server

If you set services to start automatically and then must start, pause, or stop the services, use Exchange System Manager

Procedure

To start, pause, or stop the virtual server

 In Exchange System Manager, right-click the IMAP4, POP3, or NNTP virtual server you want to manage, and do one of the following:

 To start the service, click Start

 To change the server status to paused or to restart a server that

has previously been paused, click Pause

Note:

When a server is paused, an icon indicating that the server is

paused appears next to the server name in the console tree

 To change the server status to stopped, click Stop

Note:

When a server is stopped, an icon indicating that the server is

stopped appears next to the server name in the console tree

For More Information

For more information, see the following topics in the Exchange Server

2003 Client Access Guide:

servers, see How to Enable a POP3, IMAP4, or NNTP Virtual Server

 For information about configuring and managing client protocols, see

Managing Protocols

Synchronizing Multiple Exchange 2003 Forests

This topic provides information about synchronizing multiple Microsoft® Exchange Server forests Before you perform the procedures listed in this

topic, it is strongly recommended that first you read the guide Planning an Exchange Server 2003 Messaging System

(http://go.microsoft.com/fwlink/?linkid=21766) The planning guide

introduces you to the concepts behind running your Exchange

organization in multiple forests After familiarizing yourself with those concepts, read this section to learn how to synchronize your multiple Exchange organizations

Specifically, this topic will:

 Provide you with the requirements necessary to use the GAL

Synchronization feature in Microsoft Identity Integration Server

(MIIS) 2003

 Show you how to configure mail flow between your forests

 Show you how to configure extended mail features (such as a shared SMTP domain namespace)

 Show you how to use the Inter-Organization Replication Tool to

synchronize free and busy data and replicate public folders

 Show you how to administer the messaging system across forests (for example, how to use Migration Wizard to move mailboxes between

forests)

The first two bullets listed are required for basic messaging functionality The remaining bullets are extended mail features specific to a multiple forest scenario Essentially, your goal is to make features that were

initially designed to function only in a single forest span multiple forests

Overview: Multiple Forests Running Exchange

Although a single forest topology is recommended because it provides the richest set of messaging features, there are various reasons for

implementing multiple forests Some of these reasons include:

isolation

 You have multiple business units that have separate schema

requirements

 You are confronted with a merger, acquisition, or divestiture

In the multiple forest scenario (Figure 1), a company has multiple

Microsoft Active Directory® directory service forests, each containing an Exchange organization In this scenario, user accounts are not separated from their mailboxes Instead, a user account and its associated mailbox are in the same forest However, because a GAL is specific to a single forest, users cannot see users, groups, or contacts in other forests

Figure 1 Exchange deployed in multiple forests with

synchronization between forests (classic multiple forest

configuration)

Available Features in a Multiple Forest Environment

Most mail features were initially designed to function only in a single

forest Therefore, to ensure that these features are available across

forests, you must overcome many design constraints Some of the more advanced features, such as delegating mailbox access and viewing

calendars, are not available if users are in different forests Table 1 lists the available mail features in a multiple forest environment

Feature Available across forests?

required

Common global address list (GAL) Yes, with Microsoft Identity

Integration Server (MIIS) 2003

Free and busy data synchronization Yes, with the Inter-Organization

Replication Tool In Microsoft Office Outlook®, a meeting organizer can add an attendee from another forest

to a meeting request, and the organizer can check the attendee's

availability on the Scheduling tab

Public folder synchronization Yes, with the Inter-Organization

Replication Tool

Feature Available across forests?

Synchronization and set up SMTP authentication

another forest is represented as a contact You can send mail to a distribution group in another forest (however, you cannot query the membership of the group)

Secure/Multipurpose Internet Mail

Extensions (S/MIME)

Yes, with manual configuration By default, user certificates are not synchronized between forests You

must configure userCertificate to

enable S/MIME Key Management Service in Exchange 2000 and Exchange 5.5 are not supported in

a multi-forest environment

Feature Available across forests?

configured correctly (There are a few options for doing this; see

"Configuring Mail Flow Between Forests" later in this topic.)

Shared SMTP namespace across

forests

Yes, if each organization has a unique SMTP domain namespace

in addition to the shared namespace Add a recipient policy that specifies the unique SMTP proxy address to each forest (If Exchange 5.5 is running in the forest, Active Directory Connector (ADC) replicates the second proxy address to the Exchange 5.5

directory as long as two-way connection agreements are set up.)

Feature Available across forests?

Inter-Organization Replication Tool to replicate a public folder, the administrator for each forest must set the permissions on the folders

cross-forest mailbox move and need to be re-created after the move

another forest is represented as a contact, you cannot delegate mailbox access to someone in another forest Contacts cannot be designated in a mailbox's access rights Also, mailbox delegate permissions are not preserved when you move mailboxes from one forest to another