Home > Articles

Installing Exchange Server 2003

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

In This Chapter

  • Preparing for Implementation of Exchange 2003

  • Preparing to Install Exchange 2003

  • Conducting Preinstallation Checks on Exchange 2003

  • Performing an Interactive Installation of Exchange Server 2003

  • Performing a Scripted Installation of Exchange Server 2003

  • Completing the Installation of Exchange 2003

  • Performing Postinstallation Configurations

  • Configuring Additional Server Services

  • Testing the Exchange 2003 Installation

This chapter explains the basic installation of a new Exchange 2003 server. In this latest version of Exchange, Microsoft has taken a big step in improving the installation process to make it a lot more intuitive than previous versions of Exchange. The tools included on the installation CD walk you through the preinstallation tasks to verify the environment prior to installing the server.

When you execute setup.exe, you are not launched immediately into the installation program. You are taken through a step-by-step checklist of tasks prior to launching the setup executable.

This chapter does not present upgrading or migrating from previous versions of Exchange and other messaging platforms. You read about migrations in Chapters 14, "Migrating from NT4 to Windows Server 2003"; 15, "Migrating from Exchange 5.5 to Exchange Server 2003"; 16, "Migrating from Exchange 2000 to Exchange Server 2003; 34, "Migrating from Novell GroupWise to Exchange 2003"; and 35, "Migrating from Lotus Notes to Exchange 2003."

Preparing for Implementation of Exchange 2003

Several tasks should be done prior to installing Exchange 2003. The choice of running Exchange 2003 on Windows 2000 or Windows 2003 affects the preinstallation steps that need to take place and the functionality of Exchange. Some tasks are optional, such as forest prep and domain prep (automatically done when setup is run), but most tasks are requirements that would stop the install process, such as having a Global Catalog available on the network or not having the NNTP service installed on the server where you are installing Exchange.

Implementing Active Directory

Before you install Exchange Server 2003 on your network you need to make sure that Active Directory is properly deployed. The Active Directory infrastructure and DNS need to be healthy and without replication errors prior to installing your first Exchange 2003 server. It is so important to perform health checks and verification steps in your environment prior to installation that the Exchange development team has designed the installation program to include these steps. Exdeploy walks you through all the preinstallation health checks before running the setup program for Exchange 2003.

Realizing the Impact of Windows on Exchange

Because Windows is the base infrastructure for Exchange 2003, take into account key factors prior to implementing Exchange:

  • Global Catalog placement

  • Windows Mixed versus Native Mode

  • Group type used

  • Extension of the forest schema

  • Preparation of the Active Directory domain

Global Catalog Placement

One item to review is the placement of Global Catalogs within the Active Directory site configuration. The importance of the Global Catalog server cannot be overstated. The Global Catalog is used for the address list that users see when they are addressing a message. If the Global Catalog server is not available, the recipient’s address will not resolve when users address a message, and the message will immediately be returned to the sender.

One well-equipped Global Catalog server can support several Exchange 2003 servers on the same LAN segment. There should be at least one Global Catalog server in every Active Directory site that contains an Exchange 2003 server. For large sites, two Global Catalogs are much better and provide redundancy in the event the first Global Catalog server is unavailable.

For optimization, plan on having a Global Catalog server close to the clients to provide efficient address list access. Making all domain controller servers Global Catalog servers is recommended for an organization that has a single Active Directory domain model and a single site, and it’s also not a bad idea for Active Directory designs that use a placeholder domain as the forest root with one or two first-level domains. A good Active Directory site design helps make efficient use of bandwidth in this design. This design helps reduce some of the overhead with multiple Global Catalogs in every Active Directory site.

The Active Directory Replication Monitor (ReplMon) can be used to help determine the number of Global Catalogs in the Active Directory forest. To start the Active Directory Replication Monitor, click Start, All Programs, Windows Support Tools, Command Prompt, and then run replmon.exe. Use the Edit menu to add a monitored server. When the server is displayed, right-click the server and select Show Global Catalog Servers in Enterprise.

Choosing Between Active Directory Mixed and Native Mode in Exchange 2003

If the domain that will host Exchange 2003 is or was in mixed mode, a message may be displayed during domain prep saying that the domain might possibly be insecure because of the Pre-Windows 2000 Compatible Access group. This is just a warning, and the installation of Exchange can proceed with just the understanding that Exchange may be insecure due to the current configuration of the domain.

Members of the Pre-Windows 2000 Compatible Access group will be able to see the members of groups that have their membership marked as hidden. In order to secure group membership, users and groups must be removed from this group before installing Exchange 2003. It is not necessary to resolve this security issue prior to installing Exchange 2003, because the removal of objects from this group can be done soon after Exchange 2003 has completed installation.

Selecting a Windows 2000/Windows 2003 Group Model

Groups can be a big issue in Exchange 2003, especially in multidomain Windows 2000 or Windows 2003 Active Directory environments. Exchange 2003 uses Windows 2000 groups in place of the distribution lists that were used in Exchange 5.5. Distribution lists in Exchange 5.5 have been replaced by distribution groups in Active Directory. A Windows 2000 or Windows 2003 distribution group is the same as an Exchange 5.5 distribution list except it cannot be assigned permissions on an access control list. This means the strategy to secure calendars, public folders, and resources in Exchange 5.5 has to be redesigned for Exchange 2003. There are two major issues with groups that architects and administrators need to be concerned about:

  • Visibility

  • Permissions

Viewing Group Membership with Visibility

Visibility enables users to view the membership of the group. This is obviously an important requirement when sending an email to a group of users, because the users would like to see the list of recipients to whom they are sending the message.

Here is the way the group types affect visibility:

  • Domain Local—Domain membership is not in the Global Catalog. Users in a domain can see the membership of domain local groups only from their own domain. They can see the group entry for domain local groups from other domains in the Global Address List (GAL), but they cannot see the members.

  • Global—Domain membership is not in the Global Catalog. Users in a domain can see the membership of global groups only from their own domain. They can see the group entry for global groups from other domains in the Global Address List but they cannot see the members.

  • Universal—Domain membership is in the Global Catalog. Users can see the membership of the group no matter where the group resides.

In a single domain model or a domain model that uses a placeholder for the forest root and just one first-level domain, this issue is fairly simple to solve. Any group model will work in this design as long as all mailbox-enabled users reside in the same domain. If the plan is to add more domains later, universal groups should be used because of their flexibility. Another option would be to use domain local groups and then convert them to universal groups after the additional domains are installed.

Permissions

Security groups are required for assigning permissions to calendars, public folders, and resources. A security group type of domain local, global, or universal must be selected to control permissions on objects. Because controlling access to collaboration objects is essential, it’s best to avoid distribution groups to reduce confusion for end-users and administrators. If the organization is supporting multiple mail platforms, it might be forced to support the distribution group as a representation of the foreign mail system’s mailing list, but try to avoid using them for collections of Exchange 2003 users.

For full functionality, the best solution is to use universal security groups. This provides the ability to see group membership across all domains and to assign permissions to calendars, file shares, public folders, and other resources—all with the same group. In larger environments, there are some obvious challenges with using universal groups that are mostly political because of the segmentation of which group controls email, directory, and file resources.

The second challenge with universal security groups is that the Active Directory domain must be in native mode to support universal security groups. This means all DCs in the domain must be running Windows 2000 or Windows 2003 Active Directory and not Windows NT 4.0.

The last challenge with using universal security groups is that they incur a replication penalty. If the group membership changes for one user, the entire group is replicated to all DCs in the local domain and to all Global Catalogs in the forest. This usually does not make or break a design decision to use universal security groups, but architects need to keep it in mind if they have remote Global Catalogs across bandwidth-choked links. The way Active Directory handles group membership changes might change in future revisions of the product.

Extending the Active Directory Schema

The first step to the actual implementation of Exchange 2003 is to extend the Active Directory schema. The schema comprises the rules that apply to the directory and controls what type of information can be stored in the directory. It also describes how that information is stored in the directory—such as string, string length, integer, and so on. Exchange 2003 almost doubles the amount of attributes in the Active Directory schema.

Extending the schema is the easiest part of the installation, but it is also the place where many organizations make mistakes. To extend the Active Directory schema, use the /forestprep switch on setup.exe for Exchange 2003 or follow the steps outlined in the deployment tool. A few tips to note before extending the Active Directory schema:

  • The schema must be extended on the server that holds the Schema Master FSMO role. By default, the first server installed in the forest contains the Schema Master; however, this role could have been moved to another server. To locate which server contains the Schema Master FSMO role, use the Active Directory Schema MMC snap-in, right-click the Active Directory Schema icon under the console root, and select Operations Master.

  • The account used to extend the schema must be a member of the schema admins group and domain admins or enterprise admins groups. The schema admins and enterprise admins groups are available only in the first domain in the forest. If the messaging group does not control the forest root domain, this process must be delegated to the group that does.

  • A schema change forces a full replication of domain databases and Global catalog information in Active Directory. Many administrators are scared of full replications and have heard stories of bandwidth-saturated WAN links due to schema extensions. However, when a full replication occurs, the directory information is compressed before it is sent across the network. The actual amount of data sent across the wire will be approximately 15%–20% of the actual Active Directory database size.

Preparing the Windows 2000 or Windows 2003 Domain

The second step in preparing to install Exchange 2003 is to prepare the Windows 2000 or Windows 2003 domain that will host the Exchange servers or mailbox-enabled users. To prepare the Windows 2000 or Windows 2003 domains, use the /domainprep switch on setup.exe for Exchange 2003 or follow the steps outlined in the deployment tool.

The account used to prepare the Windows 2000 or Windows 2003 domains must be a member of the domain admins group in the domain where the /domainprep command is being run. Running domainprep performs the following operations on the domain:

  • Creates the global security group Exchange Domain Servers

  • Creates the domain local security group Enterprise Exchange Servers

  • Adds the Exchange Domain Servers group to Enterprise Exchange Servers group

  • Grants appropriate rights to the domain controller used for the Recipient Update Service

For domains that will host mailbox-enabled users and not host Exchange servers, administrators have the choice of running domainprep or manually creating a Recipient Update Service for the domain in Exchange System Manager. If the domain will never host Exchange servers, the Recipient Update Service should be manually created. If the domain will eventually host Exchange servers, domainprep should be used.

  • + 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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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