Deploying Exchange 2000 1

1
Deploying Microsoft Exchange 2000 (Part 1)
FundamentalsKen EwertProgram ManagerExchange
Product UnitMicrosoft Corporation
2
Objective

• Part 1 of a 3 part series covering Exchange 2000
  deployment
• Introduce key concepts and components that will
  help you plan your Exchange 2000 deployment
• Some of the mechanics of having Exchange 2000
  co-exist with your current topologies

3
Agenda

• Windows 2000
• The concepts
• The components
• The actions
• Advanced deployment configurations

4
Reliance On Windows 2000

• Active Directory
• Stores configuration information
• Forms the basis of the Exchange 2000 GAL and
  other address lists
• Internet Information Server 5.0
• SMTP, NNTP, and HTTP are core to the operating
  system
• Common protocol architecture
• DNS
• Provides name resolution for transports and
  routing

5
Extending The Windows 2000 Schema

• Will occur when first Exchange 2000 server is
  installed
• /schemaonly command line switch
• Installing Exchange 2000 into other domains
  depends on it
• Schema master dependency
• Full schema available on the CD for manual
  inspection

6
Deployment Options

• Wizard-based setup
• Local server-based installations
• Terminal Server-based installations
• Silent / batch install
• Remote installations (no terminal server)
• Able to generate INI file from the UI
• System Management Server 2.0

7
The Deployment Concepts

• Exchange 4.0/5.x Sites vs. Administrative /
  Routing Groups
• Exchange Organization Modes

8
Exchange 4.0/5.x Sites Versus AGs And RGs

• Why Exchange 4.0/5.x sites today?
• Admin Group
• Logical grouping of Exchange objects that are
  managed by a common group of administrators
• Routing Group
• Collection of well-connected Exchange servers
  with guaranteed full time / full mesh
  connectivity
• Relationship to Window 2000 sites

9
Mixed Versus Native Mode

• Mixed Mode
• Maintains 5.5 interoperability
• Maintains 5.5 limitations / concepts
• All servers in a Routing Group must also be
  contained in the Admin Group Servers container
• Cant move a mailbox or server across Admin Groups

10
Mixed Versus Native Mode

• Native Mode
• No 5.5 servers in topology
• No dependency between Admin Groups and Routing
  Groups
• Can move mailboxes and servers across Admin Groups

11
Directory With Exchange 2000 Added
Organization
Site 2
Site 1
Site 3
Site 1
Servers
A1 A2
B1 B2
C1 C2
A1
A2
Site 2
Servers
B1
B2
Site 3
Servers
C1
C2
12
5.5 Active Directory
Organization
Organization
Site 1
AG Site 1
Servers
Servers
A1
A1
A2
A2
RG Site 1
Site 2
Servers
AG Site 2
B1

B2
AG Site 3
Site 3
Servers
Servers
C1
C1
C2
C2
PT
RG Site 3
13
Native Mode Diagram
Organization
AG Site 1
Servers
A1
A2
A3
C1
C2
C3
AG Site 3
Routing Groups
RG Site 1
RG Site 3
14
The Deployment Components

• Active Directory Connector (ADC)
• Connection Agreements (CA)
• Site Replication Service (SRS)

15
Active Directory Connector

• Replication engine
• Leverages standard replication mechanism of
  querying for deltas based on the last known
  Update Sequence Number (USN)
• Run on a scheduled or continual basis
• Done via LDAP
• Exchange DS must be 5.5 (writeable LDAP paged
  results)

16
Unification Of Objects

• Objects with similar semantics are merged
• Mailboxes ? Users
• Custom recipients ? Contacts
• Distribution lists ? Groups
• Security Groups - like NT4 groups
• Distribution Groups - may not be used in ACLs
• Either type of group may be used as a DL

17
Connection Agreements

• Defines replication characteristics
• Schedule, authentication, containers to
  replicate, schema map, one way vs. two way
  replication
• Types of Connection Agreements
• User CAs
• Configuration CAs
• Multiple CAs to the same site
• Provides granular control of container
  replication

18
Site Replication Services

• Need a solution to supporting upgrading /
  retiring Directory bridgehead servers
• Prevents continually re-homing ADC connection
  agreements
• Used to hook up similarly named Exchange
  Organizations (5.5 and Exchange 2000)

19
SRS Components

• Directory Database
• ESE98 database engine
• Incorporates 5.5 replication engine
• Mail-based for inter-site
• RPC-based for intra-site
• Supports both LDAP and XDS as access protocols
• MAPI interface is disabled

20
SRS Components

• Knowledge Consistency Checker
• Supports multiple writeable naming contexts
  (useful for backbone)
• Site Consistency Checker
• Modifies Connection Agreements
• Makes decisions after analyzing the topology

21
Client-Side Implications

• No need to upgrade your clients when you upgrade
  the server to Exchange 2000
• Clients running against an Exchange 2000 server
  requires access to a Global Catalog
• Existing Offline Address Books still work

22
Merging Multiple Legacy Directories

• How can you upgrade accounts from different
  legacy directories into a single account in
  Active Directory?
• Accounts created by upgrading Exchange 5.5
• Accounts created by upgrading Windows NT 4.0
• Accounts created by upgrading other systems
  (Novell, Notes, etc.)

23
Merging Multiple Legacy Directories
ActiveDirectory
Exchange 5.5
Third Party Directory
NT 4
24
Active Directory Account Cleanup Wizard (ADCLEAN)

• Provides merging of Twin objects in the Active
  Directory
• Searches Active Directory for possible Matching
  Twin objects
• Administrator manually selects Twin objects
• Look before you leap ! (Feature)

25
Upgrading Exchange And Windows NT 4.0 With The AD

• Option 1. Completely upgrade Windows NT 4.0 to AD
  first
• Avoids twins
• Option 2. Upgrade Exchange 5.5 to AD first
• Use ADCLEAN.EXE to clean up twins after later
  Windows NT 4.0 upgrades

26
The ADC And Upgrading Exchange 5.5 Directory

• The Active Directory Connector (ADC) will ensure
  that the AD has an account for EACH AND EVERY
  object in Exchange 5.5
• Match with existing AD Accounts OR
• Create new accounts
• Default - Disabled User Accounts
• Stamp - ID of actual associated Windows NT user
  (most likely Windows NT 4.0 user)

27
Using The ADC To Upgrade Exchange 5.5 Directory
ADDomain(B)
28
Later Windows NT 4.0 Upgrades To AD

• The Windows NT 4.0 Upgrade will create twin
  objects
• Use ADCLEAN for these objects
• ADCLEAN will search for Twins based on ID
  stamped by ADC
• Merge Disabled account created by Exchange into
  Active account created by Windows NT 4.0 upgrade

29
Later Windows NT 4.0 Upgrades To AD
ADDomain(B)
NT4 Domain(A)
30
Later Windows NT 4.0 Upgrades To AD
ADDomain(B)
31
Merge Twin Objects
ADDomain(B)
32
Merge Twin Objects
ADDomain(B)
ADDomain(A)
ADC
33
ADClean Demo
34
The Deployment Actions
35
Installing Exchange 2000 Into An Existing Site

• Similar to joining a 4.0/5.x site today
• After replication Exchange 2000 Server looks like
  a 5.5 server to other 4.0/5.x servers
• Messaging connectors available to all users

36
Upgrade Existing 5.5 Server

• Must be running SP3
• Change LDAP port if running on DC
• Upgrade occurs in-place
• Upgrades mailboxes / public folders / connectors
• Will not upgrade third party connectors

37
Upgrade Existing 5.5 Server

• Connectors
• Site Connector ? RG connector
• X.400 Connector and Stacks remain intact
• TP4 no longer supported in Windows 2000
• IMC ? SMTP virtual Server SMTP connector
• Other installed MS messaging connectors upgrade
  (MSMail / ccMail / Notes)

38
Typical Upgrade Scenarios

• In Place
• Swing Server
• Install Exchange 2000 on additional piece of
  hardware and join 5.5 site to be upgraded
• MoveUser mailboxes from a 5.5 server to an
  Exchange 2000 server
• Either replace the old hardware, or (if
  sufficient to run Windows 2000 and Exchange 2000)
  recycle it as the next Exchange 2000 server to
  move users to

39
Front End / Back End

• Allows separation and abstraction of client
  namespace and physical implementation
• Supports POP / IMAP / HTTP / SMTP
• MAPI has its own referrals
• Can use either round-robin DNS or Windows NT
  Load Balancing Service to abstract IP address
  dependency
• Allows customer to scale the system up or down
  by addition / removal of resources

40
HTTP Front End / Back End
ServerA
ServerC
ServerB
/exchange/ericl
/exchange/kene
/disc/XML
/disc/foo
/exchange/gordm
/disc/dogfood
/exchange/brianv
Front End Servers
/exchange/gordm
/disc/foo
Directory
/exchange/ericl
41
Clustering Support

• Exchange implements active/active clustering
• Does not fail over services but instead
  responsibility for a given configuration and its
  data
• Configuration IP / network name / shared disk /
  Exchange server config
• Abstracted from an administrative perspective

42
Active / Active Clustering
Router /DNS service resolver
SMTP
POP
IMAP
NNTP
HTTP
Windows 2000 Directory
Store
Store
Store
Store
Cluster A
Cluster B
43
Sessions To Follow Up With

• Deployment Part 2, Part 3
• Exchange 5.5 Administrators Guide to Exchange
  2000
• Clustering
• Deploying RTC

44
(No Transcript)
45
(No Transcript)