Exchange 2000 Server Administration: A Beginner's Guide

by Bill English (Conducted by)

Overview

The Exchange 2000 Server is a system which provides a backbone for communication, collaboration and information sharing. Exchange 2000 Server has features such as instant messaging, chat and conferencing, which are useful in business. This book is an implementation guide for administrators, either moving from Exchange 5.5 or those who are new to Exchange. The book contains eight pages of blueprints to illustrate how Exchange 2000 Server differs from the 5.5 version, and also show how it is tightly integrated with Windows 2000 Server's Active Directory.

Product Details

ISBN-13:	9780072131192
Publisher:	McGraw-Hill/Osborne Media
Publication date:	02/21/2001
Series:	Beginner's Guides (Osborne)
Pages:	473
Product dimensions:	7.50(w) x 9.25(h) x 1.02(d)

Read an Excerpt

Chapter 1: Upgrading to Exhange 200 Server

Migrating to Exchange 2000 Server and ensuring coexistence with Exchange 5.5 Server is going to be one of your most prominent challenges. This chapter details how to make the transition smooth and ensure that messaging traffic flows uninterrupted, and it also gives you a road map to follow when performing the migration and points out problems to avoid. Even though this is a beginner's book on Exchange 2000, we'd like to help you avoid beginner mistakes.

Before doing an upgrade to Exchange 2000, you must first perform an upgrade to Windows 2000 Server on at least one server that will be hosting Exchange 2000 Server. Before installing Exchange 2000 Server, you must have active Directory (aD) up and running. We will not discuss in depth in this book how to plan for and perform a migration to Windows 2000 Server from Windows NT 4.0 Server. If you need to learn more about that, please consult the following books:

• Microsoft Windows 2000 Server Resource Kit, Microsoft Press.
• Windows 2000 administration, by George Spalding, Osborne /McGraw-Hill.

Even though we're not going to outline how to perform a migration from Windows NT 4.0 Server to Windows 2000 Server, there are a few principles that need to be mentioned here about a Windows 2000 upgrade in order to paint the backdrop for our Exchange migration discussions.

First, you will upgrade your Primary Domain Controller (PDC) that holds at least one of your main user account databases to Windows 2000 Server. During this installation process, the contents of the Windows NT security accounts database are copied into active Directory (aD). as part of this upgrade process,dcpromo.exe is automatically run so that the PDC can still perform its functions with the downstream Backup Domain Controllers (BDCs). Because of this, aD will be created running in mixed mode. If at all possible, plan out your domain structure and migrate all of your PDCs to Windows 2000. This will help minimize the possibility of having duplicate accounts later on. also, try to get to a single domain model in NT 4.0 Server before migrating to Windows 2000 active Directory. While there are tools available to help conduct a smooth migration from a multiple-domain model to aD, it is easiest and best to migrate from a single domain.

Upgrading the PDC has several considerations. The first is the partition size on your current PDC. If you were like most administrators, you probably created a 2GB partition for the operating system. In Windows 2000, the basic installation often consumes at least 1GB of disk space; this leaves little room for other necessities, such as the pagefile.sys or programs that must he installed in the system root directory. Hence, the best practice in this scenario is to create a new NT 4.0 Server with a 4GB partition and install it as a BDC. Then promote it to PDC, and run the upgrade to Windows 2000 on this new server. This is preferable to using a third-party partition program to rearrange current partition sizes on your current PDC. Of course, if you don't want to migrate your existing Windows NT security accounts database to aD, you can use the active Directory Migration Tool (aDMT) to copy user accounts from the Windows NT PDC to aD.

You will want to take a good, hard look at your current hardware and make sure that it will provide enough resources to run Windows 2000, Exchange 2000, and any other BackOffice products or .NET server platforms that you plan to run in the next three to five years. In most companies today, except for the smallest of environments, the minimum hardware being purchased are dual PIII/800 with a minimum of 512MB RaM. In many cases, 1GB of RaM is being ordered to ensure that there are enough server-side resources to meet the increasing demand from the users.

The first PDC that is upgraded to a Windows 2000 domain controller (DC) will hold all five operation master roles, including the PDC Emulator role. This role allows the Windows 2000 domain controller to look and feel like a PDC to existing BDCs on the network. You can still use the former PDC to create new security principles, such as user, group, and workstation accounts, in aD and have these new accounts replicated to the BDCs. at the BDC, these new objects will look like NT 4.0 security principles, not aD objects. Cool, eh?

NOTE: If, at this point, the Windows 2000 domain controller that is operating as the PDC Emulator goes offline, you can promote a Windows NT 4.0 BDC to PDC. This will neither interrupt network operations nor adversely affect your security accounts database.

Once you've upgraded your PDC to Windows 2000 aD, you can go ahead and migrate the BDCs, though this really isn't necessary. However, it is always a best practice to take one BDC offline during this process, in case you need to failback to your Windows NT 4.0 domain. Once your domain controllers and members servers that are going to host Exchange 2000 Servers have been migrated to Windows 2000, it's time to begin looking at migrating to Exchange 2000 Server.

What we are going to discuss now is how to plan for your Exchange 2000 migration. Do not skip reading this section and do not perform your migration without first making sure you have done due diligence in this planning area. Failure to fully plan out your Exchange 2000 migration will lead to problems in administering and operating your new Exchange 2000 organization.

In addition, this chapter will illustrate how to migrate from a single domain model to aD. We realize that there are other, more complicated scenarios, but space limitations prohibit us from detailing additional scenarios. Keep in mind that the majority of Exchange 5.5 installations are in a single domain environment with only a few Exchange 5.5 Servers.

Reliance on Windows 2000

Exchange 2000 Server relies heavily on Windows 2000 in three main areas: the directory, transport, and name resolution. Previous versions of Exchange included a separate directory of objects that was distinct from the security accounts database managed by the PDC. In Windows 2000, we use a single database that performs both functions with the same set of objects. Windows 2000 manages this database and Exchange 2000 Server leverages its features. One example of this is the Global address List (GaL), which is really a listing of all the mail-enabled objects in aD.

after Windows 2000 is installed, the transport stacks, such as Simple Mail Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP), are placed inside the inetinfo.exe process (Internet Information Services or ITS) and run as separate transport stacks. Windows 2000 and Exchange 2000 will use these stacks for both messaging and overhead functions, such as directory replication. When Exchange 2000 Server is installed, it extends these stacks with additional command verbs and an advanced routing component, the link state protocol, to ensure that you enjoy an enterprise-class messaging and collaboration system.

The Exchange 2000 development team wrote both versions of the messaging protocol stacks. By decoupling these protocols from the information store services and placing them inside ITS, it allows both Windows 2000 and Exchange 2000 to use common protocol architecture.

Collaborative applications and messaging functionality both require name resolution. The Domain Name System (DNS) is now the preferred method of name resolution for Exchange 2000, and this function is offered by Windows 2000 Dynamic DNS. any service resolution that was performed by the Windows Internet Naming Service (WINS) in Windows NT 4.0 has been moved over to DNS as the primary service to the IP resolution process. If you are running any specialized applications that run inside an Exchange public folder and that rely on WINS resolution, you should plan to have that application updated to work with Windows 2000 DNS. Until then, be sure to run WINS on your network.

DSaccess and Global Catalog (GC) Usage

DSaccess is a new shared application Programming Interface (aPI) between Exchange 2000 and aD that performs several functions. It is used by the store.exe process, ITS protocols, and Outlook Web access (OWa)...

Table of Contents

	Acknowledgments	xvii
	Introduction	xix
Part I	Migration and Coexistence
1	Upgrading to Exchange 2000 Server	3
	Planning Your Exchange 2000 Migration	5
	Reliance on Windows 2000	6
	Extending the Schema	7
	Deployment Options	8
	Exchange 5.x Sites Versus Administrative and Routing Groups	8
	Mixed Mode Versus Native Mode	9
	Planning for Groups in Exchange 2000 Server	9
	Deployment Components	10
	Merging Legacy Directories with Exchange 2000	12
	Migrating to Exchange 2000 Server	14
	Installing the ADC Service	15
	Running/ForestPrep	21
	Upgrading an Exchange 5.5 Server on a Windows 2000 Member Server	38
	Upgrading the Remaining Exchange 5.5 Servers	39
	Migration and Deployment Considerations	40
	Upgrading in Other Scenarios	40
	Summary	43
2	Coexistence with Exchange 5.5 Server	45
	Directory Coexistence with Exchange 5.5 Server	46
	Site Replication Service (SRS)	47
	Active Directory Connector Service	57
	Public Folder Coexistence	78
	Summary	79
3	Exchange 2000 Server Integration with Windows 2000 Server	81
	Directory Integration with Windows 2000 Server	82
	Active Directory Naming Contexts and Exchange 2000	87
	Integration with DNS	94
	GC Services and Exchange 2000 Server	100
	Windows 2000 Security and Exchange 2000 Server	101
	Windows 2000 Administration and Exchange 2000	101
	Active Directory Connector (ADC) and Exchange 2000 Server	102
	Summary	103
Part II	Administration Deployment
4	Installing Exchange 2000 Server	107
	Requirements to Install Exchange 2000 Server	108
	Installing Exchange 2000 Server	110
	Performing a New Installation of Exchange 2000 Server	110
	Performing a Silent Installation	116
	Summary	121
5	Creating and Managing Recipients	123
	Creating and Managing Recipients	124
	Creating a New User Account	124
	Configuring Mail-Enabled User Accounts	128
	Creating and Configuring Contacts	139
	Creating and Configuring Distribution Groups	141
	Creating and Configuring Mail-Enabled Public Folders	144
	Managing Address Lists	144
	Offline Address Lists	147
	Summary	147
6	Creating and Managing Public Folders	149
	Public Folder Introduction	150
	Public Folder Referrals	151
	Internet Publishing	151
	Full-Text Indexing	152
	Public Folder Hierarchy	152
	Public Folder Strategies	152
	Creating Public Folders and Public Folder Trees	153
	Deleting Public Folder and Public Folder Trees	157
	Administering Public Folders	157
	Public Folder Replication	157
	Propagating Public Folder Settings	162
	Moving Public Folders	162
	Managing the Organizational Forms Library	162
	Setting Public Folder Limits	162
	Recovering Deleted Items from a Public Folder	164
	Accessing Public Folders	164
	Moving a Public Folder Tree	173
	Troubleshooting Public Folders	173
	No Replication Between Organizations	173
	Cannot Publish Forms in Organizational Forms Library	173
	Mixed Mode AD Users Denied Access to Public Folders	173
	Profile Error When Accessing a Public Folder's Properties	174
	Summary	174
7	Administering Storage Groups	175
	Benefits of Using Storage Groups	176
	Hosting More Users	177
	Quickening Recovery Time	177
	Minimizing Effected Users	177
	Planning for Multiple Storage Groups	178
	Required Restore Time	178
	Defragmentation Considerations	179
	Amount of Information to Be Managed	180
	Creating and Administering Storage Groups	180
	Moving File Locations for a Storage Group	182
	Enabling and Disabling Circular Logging	182
	Renaming Storage Groups	182
	Deleting Storage Groups	183
	Creating and Administering Stores	183
	Administering Mailbox Stores	184
	Recovering Deleted Items	187
	Recovering Deleted Mailboxes	188
	Deleting a User's Mailbox Permanently	190
	Reading Mailbox Summaries	190
	Creating Public Folder Stores	191
	Summary	191
8	Managing Administration and Routing Groups	193
	A Brief Look Back: Exchange 5.x Sites	194
	Administration Within Exchange 5.x Sites	194
	Routing Using Exchange 5.x Sites	194
	Exchange 5.x Sites: The Problem	195
	Administrative Groups	195
	Routing Groups	195
	Administrative Models	196
	Creating and Managing a Single Administrative Group	201
	Creating and Managing Multiple Administrative Groups	203
	Delegating Control Within Administrative Groups	205
	Creating and Managing Exchange 2000 Policies	206
	System Policies	207
	Summary	215
9	Administering Routing Group Connectors	217
	RGCs	218
	Creating and Configuring an RGC	218
	SMTP Connectors	225
	Creating and Configuring an SMTP Connector	226
	X.400 Connectors	233
	X.400 Addressing Basics	233
	Service Transport Stacks	234
	Creating and Configuring X.400 Connectors	235
	Summary	240
Part III	Exchange 2000 Server Architecture
10	Exchange 2000 Storage Architecture	243
	Exchange 2000 Architecture	244
	The Store Process	245
	The inetinfo.exe Process	245
	Storage Technologies in Exchange 2000 Server	246
	Multiple-Database Support	247
	Moving Stores and Transaction Logs	247
	Planning for Multiple Stores	248
	Storage Groups	248
	ESE Databases and Transaction Logs	250
	ESE Databases	250
	Transaction Logs	254
	ESE and Memory Management	258
	Circular Logging	258
	Data Reliability: -1018 errors	259
	ExIFS	261
	Indexing Services	270
	FE/BE Architecture	274
	HTTP and OWA	275
	POP3 and IMAP4 Protocols	276
	Deployment Considerations	276
	Setting Up Different Scenarios	277
	Summary	279
11	Exchange 2000 Server Routing Architecture	281
	Routing Groups: A Primer	282
	Message Routing in a Pure Exchange 2000 Environment	282
	Messages Sent Within the Same Server	283
	Messages Sent Within the Same Routing Group	284
	Messages Sent to Another Routing Group	285
	Messages Sent to a Foreign E-mail System	288
	Message Routing in a Mixed Exchange 2000/5.x Environment	288
	Sites Versus Routing Groups	290
	How Does Exchange 2000 Interact with Exchange 5.x?	290
	Messages Routed from Exchange 2000 to Exchange 5.x	290
	Messages Routed from Exchange 5.x to Exchange 2000	290
	Link State Information	291
	Exchange 5.x and the GWART	292
	Exchange 2000 and Link State Information	292
	Summary	294
Part IV	Advanced Administration
12	Configuring Security for Exchange 2000 Server	297
	Message Security Basics	298
	Message Encryption	298
	Digital Signatures	299
	Windows 2000 Certificate Services and the Key Management Server	300
	Certificate Services	300
	Key Management Server	301
	Installing Windows 2000 Certificate Services	301
	Postinstallation Tasks	306
	Installing Key Management Services	306
	Managing KMS	311
	Managing KMS Administrators	311
	Changing a KMS Administrator's Password	312
	Requiring Multiple KMS Administrators	312
	Changing the KMS Startup Password	314
	KMS User Enrollment	314
	Enrolling Users	315
	Finishing the Enrollment	317
	Recovering Keys	319
	Summary	320
13	Monitoring Exchange 2000 Server	321
	Using Exchange 2000 Monitors	322
	Monitoring States	322
	Server Monitors	322
	Connection Status	329
	Notifications	330
	Using the Message Tracking Center	337
	Summary	345
14	Backup and Recovery	347
	Transaction Logs in Backup and Recovery	348
	Backup of Exchange 2000 Server	350
	Performing Exchange Backups with NTBackup	353
	Performing Exchange Restores with NTBackup	356
	Advanced Backup Techniques and Considerations	362
	Restoring to an Alternate Server	362
	Mailbox Reconnect and Restoring a Single Mailbox	363
	Planning a Backup Strategy	364
	Physical Corruption of the Database	366
	Resolving Physical Corruption Errors	368
	Troubleshooting Database Recovery	368
	Preventing Restore Errors	371
	Database Restart Errors	372
	Eseutil	373
	Summary	377
15	Performance Tuning Exchange 2000 Server	379
	Performance Monitoring Basics	380
	Monitoring Resources	381
	Performance Monitoring Concepts	381
	Using System Monitor	383
	Monitoring the Four Main Resources in Windows 2000	386
	Setting the Foundation: Create a Baseline	386
	Monitoring Memory	387
	Monitoring the Disk Subsystem	391
	Monitoring the Network Subsystem	392
	Monitoring Exchange 2000 with System Monitor	394
	Mailbox Store Counters	395
	Public Folder Store Counters	397
	Simple Mail Transport Protocol (SMTP) Counters	399
	OWA Counters	400
	Summary	400
Part V	Client Administration
16	Installing and Administering Outlook 2000	403
	Microsoft Outlook 2000	404
	Microsoft Outlook Express	406
	Outlook Web Access	407
	Exchange Client	408
	Schedule+	408
	Other Clients	408
	UNIX Clients	408
	Macintosh Clients	409
	Configuring Outlook 2000	409
	Recovering Deleted Items	418
	Rules Wizard	419
	Summary	425
17	Supporting Instant Messaging	427
	Introduction to IM	428
	IM Architecture	429
	Installing IM	431
	Configuring IM	433
	Creating New IM Virtual Servers	433
	Enabling IM for User Accounts	436
	Configuring DNS for the RVP	437
	Working with Firewalls	439
	Working with the IM Client	439
	Managing IM Services from the Server	444
	Disabling IM for an Individual Account	444
	Finding an IM User on Your Network	445
	Ensuring a User's Privacy	446
	Managing IM Servers	448
	Removing an IM Server	448
	Taking an IM Server Offline Temporarily	449
	Moving IM Databases	449
	Troubleshooting IM	450
	Summary	451
	Index	453

Editorial Reviews

The Barnes & Noble Review
Exchange 2000 Server offers a remarkably powerful backbone for communication, collaboration, and information sharing in enterprises from the Fortune 100 down to folks who've bought Exchange as part of Microsoft's 50-user Small Business Server 2000 bundle. As Exchange 2000 catches on, many people are managing it for the first time -- often, without training. Now, there's a guide just for them.

Exchange 2000 Server Administration: A Beginner's Guide starts by reviewing the key issues associated with installing Exchange Server 2000, and upgrading from Exchange 5.5. You'll walk through creating and managing recipients via Active Directory; working with public folders and storage groups; creating effective Exchange system policies; and using routing group connectors to provide connectivity among far-flung Exchange 2000 Servers.

Next, you'll take a closer look at Exchange 2000's architecture, focusing on the elements you need to understand to maximize performance, reliability, and interoperability -- including techniques for routing mail to non-Microsoft email systems. There are thorough introductions to administering Exchange security, monitoring services and performance, and -- especially -- backup and recovery. You'll learn the basics of administering Outlook 2000 clients in Exchange environments, and even walk through implementing Exchange's cool in-house instant messaging. (Bill Camarda)

Bill Camarda is a consultant and writer with nearly 20 years' experience in helping technology companies deploy and market advanced software, computing, and networking products and services. His 15 books include Special Edition Using Word 2000 and Upgrading & Fixing Networks For Dummies®, Second Edition.

bn.com