The Exchange 5.5 Administrators Guide To Exchange 2000

1
The Exchange 5.5 Administrators Guide To
Exchange 2000 Tony RedmondTechnical
DirectorApplied Microsoft Technologies
GroupCompaq Services
2
Agenda

• List the major areas of change in Exchange 2000
• Understand where all the familiar pieces have
  gone
• Understand how to prepare to evolve

3
Exchange So Far

• Exchange 5.5 (1999) is very similar
• to Exchange 4.0 (1996)

Information Store (STORE.EXE)
MTA (EMSMTA.EXE)
System Attendant (MAD.EXE)
Connectors
Clients
Directory (DSAMAIN.EXE)
ADMIN (ADMIN.EXE)
4
Exchange 5.5 and 2000A generation apart
Exchange 2000
Exchange 5.5

• Designed in 1993-95
• Lots of different email systems
• X.400 and X.500
• Single CPU, small memory, tiny disks
• Single MAPI Capone client
• Roll your own management

• Designed in 1997-99
• Messaging is down
• to the Big 3
• Internet Protocols
• Four-way clusters and
• high-speed CPUs
• and disks
• Wide range of clients
• Management framework

5
Exchange 2000 Changes

• Dont look for ADMIN.EXE
• The DS is superseded by the Active Directory
• SMTP is now the primary focus for message routing
• The Information Store can be split
• The Web Store has arrived
• Events are pervasive
• The System Attendant is evolving

6
Management

• Exchange 2000 leverages the Microsoft Management
  Console framework
• Exchange System Manager console is used for
  server-centric activities
• Active Directory Users and Computers snap-in is
  used for user-centric activities

7
Management

• Exchange provides MMC snap-ins to allow granular
  management
• Address Lists
• Folders
• Message Tracking
• Conferencing and Chat Services
• More

8
Managing Exchange 2000
9
Comparing Administration
Exchange 2000
Exchange 5.5
Exchange System Manager Active Directory Users
and Computers AD Connectors AD Sites and
Services AD Domains Computer Management Performanc
e
ADMIN.EXE User Manager
ADMIN.EXE ADMIN.EXE (DRCs) Server Manager Server
Manager Control Panel Performance Monitor
Windows 2000 sites Exchange sites
10
More Management Changes

• EMO CDO for Exchange Management
• System and recipient policies
• Queue Viewer and API for MTAs (X.400 and SMTP)
  Connectors
• Monitoring data based on WMI (Windows Management
  Instrumentation)
• Core providers used to access event logs etc
• Exchange providers for items like connector
  status
• Far more granular scope of management activities
  to consider

11
Command Line Tools

• ESEUTIL is still there, but back to \BIN
• ADSIEDIT/LDP replaces raw mode administration
  (Window 2000 RK)
• NTDSUTIL is used for low level AD management
• Improved Backup utility included in Windows 2000
• MTACHECK is still around
• ISINTEG is in the Store

12
The DS And The AD

• The Active Directory replaces the DS
• AD Global Catalog is now the GAL
• Writeable objects from local domain plus
  read-only partial objects from the forest
• Some changes in terminology
• Windows 2000 Sites Exchange 5.5 Sites
• Exchange 5.5 Site Administrative Group
  Routing Group (per site)
• User Objects, Contacts, and Groups

13
The DS And The AD

• The good news is that the AD looks
• and feels like the DS

ADSI
LDAP
MAPI
Other
Directory System Agent (DSA)
DB Layer
Extensible Storage Engine (ESE)
NTDS .DIT
Log Files
EDB .CHK
TEMP .EDB
14
The Active Directory

• Exchange 2000 extends the AD schema to add new
  properties to user objects
• The store that holds the mailbox, quotas,
  delivery restrictions, etc.
• Configuration data is placed in a special
  Exchange container
• Replicated along with other AD data
• Permissions on everything are now based on
  Windows 2000 ACLs
• Common UI used to set ACLs

15
Forests, GCs, And Exchange

• An Exchange 2000 organization cannot span
  multiple AD forests
• Exchange depends on the GC and configuration data
  thats replicated across all servers within a
  forest
• Stay tuned on the subject of cross-forest
  replication

16
Users, Contacts, And Groups

• Changes are made to all objects through AD Users
  and Computers
• Exchange is just another property sheet to
  complete
• MAILDSMX.DLL specifies Exchange UI to reveal
  properties
• Objects have DNs like Exchange 5.5, but GUIDs are
  the unique key in the AD
• Easy to move users around containers

17
Managing Users

• Exchange extends Active Directory Users
• and Computers

18
ADSIEDIT

• Used to examine AD properties
• Be careful its easy to make mistakes!

19
Exchange 5.5 Sites

• Exchange sites control namespace, administration,
  routing, replication
• Windows 2000 sites are based on IP subnets, so
  they just define locality
• Administrative Groups define who can manage
  different servers, Routing Groups, and other
  objects
• Exchange 2000 uses Routing Groups to define
  servers that can connect point to point

20
Mixed Mode Sites

• During the migration, its likely that you will
  run mixed mode organizations
• Exchange 2000, and older Exchange servers
• SRS (Site Replication Services) makes Exchange
  2000 servers appear to have a DS
• DIR.EDB used to hold data

21
Administrative And Routing Groups
Each RG has a RG master
Multiple RGs can be in an AG
22
Enterprise Flexibility

• Initially, Exchange 2000 will be deployed in
  mixed mode
• Native mode Pure Exchange 2000 environment
  (one-way switch like Windows 2000)
• Mixed mode makes administrative and routing
  groups work like Exchange 5.5 sites
• Native mode allows much greater flexibility
• But its difficult to go back to 5.5

23
Client Impact Statement

• You dont have to upgrade clients
• Web browsers should upgrade!
• IE5 is best for new OWA
• Outlook 2000 is functionally the best client
• Filtered off-line synchronization
• Local copy of calendar
• Better integration with AD
• But you have to consider cost of deployment

24
Client Access To The AD

• MAPI clients use proxies or referrals
• DSProxy service on Windows 2000 server passes RPC
  packets sent to DS from old MAPI clients to the
  nearest GC
• Outlook 2000 contacts the DSProxy once and then
  logs details of the GC in the MAPI profile
• Registry settings available to control preferred
  GC
• Users arent aware of this magic

25
Address Lists

• ABVs are now Address Lists
• ABVs not migrated
• An Address List is a predefined LDAP query
  executed against the AD
• System Attendant refreshes Address Lists every
  10 minutes (configurable)

26
Offline Address Lists (OAB)

• The OAB is still generated and available for
  download
• Different OAB can be allocated per EBD
• Nothing changes from a user perspective
• Exchange 5.5 users in mixed mode get the OAB from
  5.5
• Exchange 2000 users get the OAB from their
  Exchange 2000 server
• Exchange 5.5 OAB works after user is migrated to
  Exchange 2000

27
Active Directory Connector

• Bi-directional connector between Exchange 5.5 and
  the Active Directory
• LDAP used to exchange data
• Connection agreement required for each site for
  bidirectional replication
• One agreement can handle one-way for all sites
• Bi-directional replication may require multiple
  agreements
• Exchange 5.5 objects are mapped to AD objects

28
ADC
29
Exchange 5.5 Objects After Replication
30
SMTP Routing And The MTA

• The MTA is still in Exchange, but it now is
  focused on pure X.400 connections
• The path to Exchange 5.5 sites (SMTP can be used
  too)
• Does not perform routing
• The default routing between Exchange 2000 servers
  is performed by the new SMTP Routing Engine
• Link State Routing is a major advantage

31
Exchange 2000 Storage

• Major area to master during Exchange 2000
  deployments
• Concepts
• Storage Groups
• Split databases
• EBDs and STM (Streaming Media)
• Multiple Public Folder hierarchies
• MAPI clients will only ever be able to see one PF
  hierarchy

32
Storage Groups

• Each SG runs as an instance within STORE.EXE
• Each SG has its own set of transaction logs
• Each SG can have up to six databases
• Each server supports up to 15 SGs
• Number may change before RTM
• Special SG reserved for recovery
• Not part of the 15 SGs for normal operation

33
Storage Groups
STORE
Storage Group 1
Storage Group 2
ESE Instance
ESE Instance
LOG
LOG
LOG
LOG
LOG
LOG
EDB1
EDB2
EDB3
EDB4
EDB5
STM
STM
STM
STM
STM
34
Splitting The Store

• One large private store is a block on scalability
• The database is too large
• It takes too long to back up
• Its an I/O hotspot
• Exchange 5.5 IS Storage Group with Private and
  Public Stores

35
Points To Ponder On SGs

• Mailboxes can be distributed across SGs
• SGs can be backed up and restored separately
• I/O load can be split across volumes
• Single Instance Storage is impacted
• Disaster Recovery Plans must be updated
• System balance must be maintained

36
Streaming Databases

• New STM file introduced to hold native Internet
  content
• Inserted by Internet clients
• Suitable for voice, video, etc.
• Header information held in EBD
• Automatic format conversion when accessed by MAPI
  clients

37
Events

• Asynchronous folder-based events are supported in
  Exchange 5.5
• Synchronous and asynchronous events are now
  supported through the core services of Exchange
  2000
• Transport
• Protocol
• Routing
• Store
• Events are used to build core Exchange 2000
  services

38
New Stuff

• Instant Messaging and Presence Information
• Better VoiceMail support
• NetMeeting to your hearts desire

39
Web Store

• Everything in the Store can be addressed by a URL
• No GUIDs just normal stuff
• Brand new Outlook Web Access
• Best on IE 5 or above
• HTTP-DAV is very important for the future
• SMB support and NSE for Windows Explorer

40
Management Challenges

• Planning a graceful migration
• Minimizing downtime when migrating users
• Moving users from Exchange 5.5 to Exchange 2000
  in mixed mode
• Running two administrative environments
• Servers need to be managed through their own
  admin tools
• Users can be managed from either (with caveats)
• Qualifying third party products

41
Preparing For Migration

• Consolidate sites and servers, if possible
• Upgrade servers to Exchange 5.5 SP3
• Understand then design the AD for your company
• Establish the AD infrastructure on Windows 2000
  (PDC upgrade time)
• Connect Exchange 5.5 to the AD via the ADC
• Plan, design, then implement!

42
Other Sessions To AttendOr buy the tape

• Three Part Overview Series (Hall C)
• 2-301 (Tuesday 115)
• 2-302 (Tuesday 300)
• 2-303 (Tuesday 445)
• Monitoring and Reporting (3-313)
• Store (1, 401, 1-402, 1-302)
• Transport (1, 305, 1-310)
• Active Directory (3-305, 3-403)

Session already over!
43
Exchange 5.5 and 2000A generation apart
Exchange 2000
Exchange 5.5

• Designed in 1993-95
• Lots of different email systems
• X.400 and X.500
• Single CPU, small memory, tiny disks
• Single MAPI Capone client
• Roll your own management

• Designed in 1997-99
• Messaging is down
• to the Big 3
• Internet Protocols
• Four-way clusters and
• high-speed CPUs
• and disks
• Wide range of clients
• Management framework

44
Summary

• Exchange 2000 is a major technology refresh
• Windows 2000 knowledge is key
• Plan for a migration rather than rushing to
  embrace change

45
(No Transcript)
46
(No Transcript)