Planning a Microsoft

Exchange Server 2003

Infrastructure
Installation Considerations
 Supported Combinations of Exchange
and Windows Server
 Exchange Server 5.5
 Windows NT 4 Server, Windows 2000
Server (any service pack)
 Not Active Directory-aware but can
replicate data to and from Active Directory
with the Active Directory Connector (ADC).
 Exchange 2000 Server
 Windows 2000 Server (SP1 or later)
 Can be installed on a member server or
domain controller but requires Active
Directory.
 Exchange Server 2003
 Windows 2000 Server (SP3 or later)
 Windows Server 2003
 Can be installed on a member server or
domain controller but requires Active
Directory
 It is worth noting that when deploying
Exchange Server 2003, Windows 2000 Server
with SP3 or later and Windows Server 2003
are not equal.
 To take full advantage of the functionality of
Exchange Server 2003, you must run it on a
Windows Server 2003 server.
 In fact, complete functionality requires
Windows Server 2003, Enterprise Edition.
 The following list identifies features of
Exchange Server 2003 that are
supported when installed on a server
running Windows Server 2003 but that
are not supported on Windows 2000
Server
 Mount points overcome the 24-drive
letter limitation of previous versions of
Windows.
 Volume Shadow Copy service for
database backup (requires Windows
Volume Shadow Copy service backup
application vendor).
 Internet Protocol Security (IPSec)
support for front-end and back-end
clusters.
 Cross-forest Kerberos authentication
with Microsoft Outlook 2003 (requires
Microsoft Metadirectory Services 2003
and Outlook 2003).
 Internet Information Server (IIS) 6
enhanced security and dedicated
application mode.
 Hypertext Transfer Protocol (HTTP)
access from Outlook 2003.
 Real-time collaboration (requires Real-
Time Collaboration service).
 Microsoft SharePoint Portal Server Web
Parts (requires SharePoint Portal Server,
Microsoft Windows SharePoint Services,
or both).
 The following list identifies functions
that are available only when running
Exchange Server 2003 on Windows
Server 2003, Enterprise Edition:
 Supports 8-way PIII Xeon Processors
 Supports 8-way P4 XeonMP Processors
(hyper-threaded)
 Up to 8-node clustering
 Mount point support
Hardware Requirements
 There are several factors that affect the hardware
requirements for Exchange Server 2003:
 the number of users that will be accessing the server;
 the size and number of messages transferred on a daily
basis (not to mention during peak usage periods);
 availability requirements; and so on.
 These factors will have a significant influence on the
type of hardware you use for your deployment
Component Minimum
requirements
 Processor : Pentium 133
 Operating system : Windows 2000 Server +
SP3
 Memory : 256 megabyte (MB)
 Disk space : 200 MB on system drive, 500 MB
on partition where Exchange Server 2003 is
installed
 Drive :CD-ROM drive
 Display : VGA or better
 File system All partitions involving Exchange
Server 2003 must be NTFS file system
(NTFS), including
 ¦ System partition
 ¦ Partition storing Exchange binaries
 ¦ Partition containing Exchange database files
 ¦ Partition containing Exchange transaction logs
 ¦ Partitions containing other Exchange files
Recommended Hardware
Requirements for Exchange
Server 2003
 Processor Pentium III 500 (Exchange Server 2003,
Standard Edition)
 Pentium III 733 (Exchange Server 2003, Enterprise
Edition)
 Operating system Windows Server 2003
 Memory 512 MB
 Disk space 200 MB on system drive, 500 MB on
partition where Exchange Server 2003 is installed.
Separate physical disks for the Exchange binaries,
database files, and transaction logs.
 Drive CD-ROM drive
 Display SVGA or better
 File system All partitions involving
Exchange must be NTFS, including
 System partition
 Partition storing Exchange binaries
 Partition containing Exchange database
files
 Partition containing Exchange transaction
logs
 Partitions containing other Exchange files
Creating a Service Account
 Another consideration when installing
Exchange Server 2003 is the creation of
a dedicated service account.
 One reason for using a dedicated
service account is related to security
auditing
Permissions and Roles Required to
Perform Exchange Installation Tasks
 Run ForestPrep for the first time in a
forest (this updates the schema)
 Member of the Schema Admins and
Enterprise Admins groups
 Run ForestPrep (other than the first
time)
 Exchange Full Administrator permissions at
the Exchange organization level
 Run DomainPrep
 Member of the Domain Admins group in
the target domain
 Install the first server in a domain
Exchange
 Full Administrator permissions at the
Exchange organization level
 Install additional servers in a domain
 Exchange Full Administrator permissions at
the administrative group level Machine
account added to the Exchange Domain
Servers group
 Install a server with the Site Replication
Service (SRS) enabled
 Exchange Full Administrator permissions at
the Exchange organization level
 When creating a service account, you
will want to select the User Cannot
Change Password option
Installing Windows Services
Required by Exchange Server 2003
 Prior to installing Exchange Server 2003,
there are certain Windows Server 2003 com-
-ponents that must be enabled on the server
because of the level of integration Exchange
has with Active Directory and the Windows
operating systems.
 For Setup to complete successfully, you must
have the following services installed and
enabled on your server
 Microsoft .NET Framework
 Microsoft ASP.NET
 World Wide Web service
 Simple Mail Transfer Protocol (SMTP)
service
 Network News Transfer Protocol (NNTP)
service
 The configuration will vary depending on
whether your server platform is Windows
2000 Server or Windows Server 2003.
 If you are installing Exchange Server 2003
onto a server running Windows 2000 Server,
Setup automatically installs and enables the
.NET Framework and ASP.NET services.
 This is because these services were not avail
able when Windows 2000 Server was
released
 Since Windows Server 2003 has the .NET
Framework built into the operating system
and has ASP.NET available through the
Add/Remove Windows Components Wizard,
the Microsoft Exchange Installation Wizard
will not install these components on that
platform.
 Instead, you must manually enable these
components on Windows Server 2003
 With Windows 2000 Server, the World Wide Web
service and SMTP service were automatically installed
and enabled as part of a default installation of the
operating system.
 By default in Windows Server 2003, these services
are not installed. So, if you are installing Exchange
Server 2003 onto a system running Windows 2000
Server, it is likely that the only service you will need
to add is the NNTP service.
 With Windows Server 2003, none of the above-
mentioned services are installed and enabled, so you
must add all of them.
Preparing Forests and
Domains
 To prepare Active Directory for the
Exchange installation, Preparing Active
Directory involves running ForestPrep
and DomainPrep, two utilities that
prepare the forest and domains,
respectively.
 Active Directory consists of three
partitions that store data: the schema
partition, the configuration partition,
and the domain partition. Prior to
installing Exchange Server 2003, you
need to use ForestPrep and
DomainPrep to prepare these Active
Directory partitions
ForestPrep
 ForestPrep updates the schema and
configuration partitions in Active
Directory. There fore, the account used
to run ForestPrep must be a member of
the Schema Admins and Enterprise
Admins security groups.
 Specifically, ForestPrep is a setup switch
for Exchange that, when run, extends
the Active Directory schema to include
Exchange Server 2003–specific classes
and attributes .
 With Exchange 2000 Server, ForestPrep
also created the Exchange organization
container, but this has changed with
Exchange Server 2003. As a result, you
no longer have to specify an
organization name until you actually
install Exchange Server 2003.
DomainPrep
 DomainPrep prepares the domain
partition.
 Another key difference is that while
ForestPrep is run once (in the forest
root domain) for the entire forest,
DomainPrep must be run in each of the
following domains
 The forest root domain
 All domains that will contain Exchange
Server 2003
 All domains that will contain Exchange
mailbox-enabled objects (users and
groups), even if the domain does not
have its own Exchange Server 2003
server
 The DomainPrep switch creates the
groups and permissions required by
Exchange Server 2003. Two security
groups are created by DomainPrep:
 Exchange Enterprise Servers A domain
local group that contains all Exchange
servers running in the forest
 ¦ Exchange Domain Servers A global group
that contains all Exchange servers running
in the domain you have selected
 To run DomainPrep, you must use a
user account that is a member of the
Domain Admins group in the local
domain.
Performing an Exchange
Server 2003 Installation
 Installation Types
 There are two primary types of installations
available when the Microsoft Exchange
Installation Wizard starts. They are:
 Create a New Exchange Organization
 Join Or Upgrade An Existing Exchange
Server 5.5 Organization
 The following list identifies the available
switches that can be used with the
Microsoft Exchange Installation Wizard
(Setup.exe), and their function:
 /ChooseDC dcname Specifies a domain
controller to be used during Setup for the
reading and writing of Active Directory
information.
 /DisasterRecovery Recovers an Exchange
installation after the server’s configuration
has been restored from backup.
 /ForestPrep Prepares the Active Directory
forest for the Exchange Server 2003
installation. You only need to run this once
in a forest
 /DomainPrep Prepares each Active
Directory domain that will have an
Exchange Server 2003 installation, or
mailbox-enabled objects such as user
accounts. DomainPrep is run in each
domain that fits the criteria.
 /? Displays a list of all of the command-line
switches with a brief explanation of their
function.
 /CreateUnattend filename.ini – Creates an
.ini file where filename.ini is the name of
the file that will contain all the information
necessary to perform an unattended
installation of Exchange Server 2003.
 /EncryptedMode – Encrypts the .ini file to
protect it from being read by unauthorized
personnel.
 /UnattendFile filename.ini – Performs an
unattended installation using the .ini file
specified. This switch can be further
modified by other Setup switches related
to unattended installation.
 /Password password – Specifies the
password of the currently logged on user
as a Setup switch, which will auto-logon
rather than prompting you during Setup.
 /ShowUI – Displays the wizard user
interface even though Setup is running in
unattended mode; this switch is used in
conjunction with the /UnattendFile switch
 /NoEventLog Prevents Setup from writing
any event information to the Windows
event logs
 /NoErrorLogging – Disables any error
logging during Setup.
 /All – Enables all Exchange components for
an install, upgrade, or reinstall
Removing an Exchange Server 2003
Server
from an Organization
 Removing an Exchange Server 2003 Server
Using the Microsoft Exchange Installation
Wizard
 This is the preferred removal method
because Setup is able to read and write
information to Active Directory and to
remove all references to the server.
However, to use the Microsoft Exchange
Installation Wizard, there are some
prerequisites that must be met.
 You must move all mailboxes to another Exchange
server in the organization or remove them from
each user account.
 The server must not be a bridgehead server or
routing group master. If it is, the role must first be
transferred to another Exchange server in the
routing group The server must not be a part of
any connection agreements.
 The server must not have any connectors installed
and in use.
Forcibly Removing Exchange
Server 2003 from an Organization
 forcibly remove an Exchange Server
2003 server from an organization by
using the Exchange System Manager
console.
 Before proceeding, stop all of the
Exchange Server services.
 Right-click on the server you want to
remove in the console, point to All Tasks,
and then click Remove Server.
 The installation wizard will warn you that proceeding
will result in a loss of mailbox, public folder, and
configuration data, and that you should uninstall
using Add Or Remove Programs instead.
 If you click Yes, Exchange Server 2003 will ignore its
built-in checks for protecting data and will remove
itself from the server and from Active Directory, with
the accompanying loss of data that entails. This is a
last-resort tool—one you would use if you were
unable to perform a removal with the Microsoft
Exchange Installation Wizard.
 To finish removing the Exchange Server 2003
server, there are a number of steps to be
completed. First, you will have to disable all
of the Microsoft Exchange Server services on
the server (rather than just stopping them).
Then there are several registry keys that
need to be deleted. If you are not using the
IIS components required by Exchange Server
2003 for anything else, remove those as well.
 Once you have completed these tasks,
reboot the server and delete the folder
structure and contents for the Exchange
Server installation. Finish cleaning up by
reapplying service packs and patches,
and if the Exchange Server 2003 server
was installed in an Exchange Server 5.5
site, delete the object in Exchange 5.5
Administrator.
Procedure
 . Disable all Microsoft Exchange
services on the server, and then delete
the follow-ing registry keys
(HKEY_LOCAL_MACHINE has been
shortened to HKLM for formatting
purposes):
Remove the following registry
keys
 HKLM \SOFTWARE\Microsoft\ESE98
 HKLM \SOFTWARE\Microsoft\Exchange
 HKLM \SYSTEM\CurrentControlSet\Services\DAVEX
 HKLM \SYSTEM\CurrentControlSet\Services\EXIFS
 HKLM \SYSTEM\CurrentControlSet\Services\ExIPC
 HKLM \SYSTEM\CurrentControlSet\Services\EXOLEDB
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeMU
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeES
 HKLM \SYSTEM\CurrentControlSet\Services\IMAP4Svc
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeAL
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeIS
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeMGMT
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeMTA
 HKLM \SYSTEM\CurrentControlSet\Services\POP3Svc
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeFBPublish
 HKLM \SYSTEM\CurrentControlSet\Services\RESvc
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeSRS
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeS
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeTransport
 HKLM \SYSTEM\CurrentControlSet\Services\MSExchangeWEB
 Remove the IIS components SMTP,
NNTP, and World Wide Web service
(if not needed by other components on
the server), and remove the
Metabase.bin file from the
Systemroot\System32\Inetsrv folder.
Systemroot refers to the folder that
Windows is installed into, such as
C:\WINNT
 Restart the server.
 Rename the \Exchsrvr folder
structures on all drives. For
example, rename C:\Exchsrvr to
C:\Exchsrvrold. This is necessary if you
have anything you want to save, such
as log files. Alternatively, you could
delete the directory structure
 Reapply any service packs and security patches
previously installed on the server.
 Open the Exchange System Manager (the console
is not in the Exchsrvr folder structure, so you
didn’t delete it in step 4) and navigate to your
server
 Right-click the server, point to All Tasks, and click
Remove Server.
 Confirm the removal of the Exchange Server 2003
data from Active Directory.
 Close Exchange System Manager