Exchange Services

• Event. The MSExchangeES service is hosted by its own process,

Events.exe. This service provides an interface for event monitoring and
logging.
• Information Store. The MSExchangeIS service, hosted by Store.exe, hosts
the Exchange databases.
• MTA Stacks. Emsmta.exe. This service translates messages between
different transport protocols. For example, messages sent from an
Exchange 2003 server to an Exchange 5.5 server require conversion from
SMTP to RPC.
• Routing Engine. The RESvc service, hosted by Inetinfo.exe, enhances the
standard SMTP routing performed by Windows Server 2003. The enhanced
routing engine knows how to query Active Directory for recipient
information and can interact directly with the Exchange Store.
• Active Directory Connector (ADC). The ADC service isn't a core part of
Exchange, per se. The ADC maintains synchronization between the
contents of the legacy directory service in Exchange 5.5 and Active
Directory.
• Site Replication Service. Srsmain.exe.
This service maintains a functional copy of the legacy Exchange directory
service so that an Exchange 2003 server can pretend to be an Exchange
5.5 server. This simplifies the transition to Exchange 2003.
 Mixed Mode & Native mode
• Exchange Server 2003 and Exchange 2000 Server both take
advantage of Active Directory, and therefore coexist in what is
called a native mode organization
• Mixed mode is required for coexistence with Exchange 5.5
• Exchange 5.5 servers cannot be added to a native mode
topology.
• How to switch from mixed mode to native :
Features available after converting
to native mode
• Move mailboxes between Administrative Groups
• Create Query-Based Distribution Groups
• Administrative Groups and routing groups cannot be
managed independently
• 8BITMIME on Exchange 2003 Bridgehead Servers. If
two bridgehead servers in a Native mode organization
run Exchange 2003, then they use 8BITMIME for data
transfers. This improves bandwidth utilization by nearly
15 percent|
Front server

• A front-end server accepts requests from

clients and proxies them to the appropriate
back-end server for processing.
• Front-end servers cannot host any mail
boxes or public folders|
A simple Front End Back End
topology
A secure Exchange 2000 front-end and back-end topology
 Advantages of a Front-End and Back-End Topology

• The front-end and back-end server topology is

recommended for multiple-server organizations to provide
access over the internet.
• The primary advantage of a front-end and back-end server
architecture is the ability to expose a single, consistent
namespace.
• Without a front-end server, each user must know the name
of the server that stores their mailbox. (eg, OWA)
• The front-end server is the single point of access on or
behind an Internet firewall that is configured to allow only
traffic to the front-end from the Internet.|
 Advantages of a Front-End and Back-End
Topology (Contd.)
• Secure Sockets Layer (SSL) is used to encrypt traffic between
the client and the server
• When SSL encryption is in use, front-end and back-end server
architecture provides an advantage because the front-end
servers can handle all encryption and decryption processing.
• SSL accelerator card mitigates the impact encryption and
decryption has on the server
• Because the front-end server has no user information stored on
it, it provides an additional layer of security for the organization.
• Network load balancing can be used to balance the load among
multiple front-end servers.|
Configure Front-end servers
• To designate a front-end server

• 1. Install the server running Exchange in the organization.

• 2. Use Exchange System Manager to go to the server object, right-
click the server object, and then click Properties.
• 3. Select This is a front-end server, and then close the page.
• 4. To begin using the front-end server do one of the following:

– Restart the computer.

– Stop and restart the HTTP, POP, and IMAP services. |
 Front –End servers configuration
considerations
• MTA stacks service must run on front-end servers if
there are Exchange 5.5 servers in the site
• Do not delete the First Storage Group in ESM,
Information Store and related services depend on it.
• If installing in an existing EXCH 2000 environment first
upgrade front-end servers and then back-end servers.|
Additional configuration for Front-End Servers

• Delete the recipient update service

• Move the recipient update service (Ent) to the
back-end server
• Delete the default offline address list
• Select this is a front end server
• Restart all exchange server services as well
as World Wide Web Publishing services |
Recipient types
• User recipients
Mail-box enabled user
Mail-enabled user
Contact recipient
• Group recipients
security groups
distribution groups
Practicals
Managing mailboxes
• Deleting a mailbox
Through Ad , while deleting user, exch system manager,
user properties
• Deleted mailbox retention
set at mailbox store level default 30 days
• Purge a mailbox
• Reconnecting a deleted mailbox|
Managing mailboxes

• Hiding a mailbox
• Modifying e-mail address|
 Storage limits

• Configure storage limits for individual

users
• Configure storage limits with mailbox store
policies|
Configuring mailbox permissions

• Mailbox permissions classified into two

categories
a) Send email on behalf of someone
b) Access mail-box in order to view, edit or
create items

(to be done later)

Delivery Restrictions (why to
configure)
• Customer feedback mailbox , want to receive only text
messages (eg restrict to 50kb)
• Mailbox configured to send automatic responses,
prevent misuse|
Moving mailboxes to other servers
Moving mailbox using exmerge
wizard

• To be done later
Mail-enabled groups

• Creating mail enabled groups

• Creating query based distribution groups|
 Understanding Storage group
architecture
• Files common to the entire storage group
E00.CHK : Checkpoint file , used to mark which transactions in the
transaction have been committed to database.
E00.LOG: First writes data to transaction log and then to the
database
MAILBOX.EDB : Rich text file
MAILBOX.STM : Streaming file
RES1.LOG : Reserved log file , to reserve disk space in case drive
gets full, each transaction log is 5 mb.
Temp.edb : temporary transaction log used by Exch
E00TMP.LOG : Used to bridge gap when renaming occurs
Need for Storage groups
• Backup scheduling applies at storage group level
• Configure circular logging settings independent of each
other.
(process that saves disk space by reusing the same set
of log files, overwritting older ones)
with circular logging only full backups can be taken and
not incremental or differential.
When enabled applies to all databases in the storage
group
Practical

• How to create storage groups.

 Moving Exch storage groups and
Databases
• When the path of the transaction logs are changed ,
databases will be dismounted temporarily.
• When moving to another partition the following default
permissions have to been configured
Administrator: Full Control
AU : Read & Execute , List folder contents,Read
Creator owner : none
Server Operators : Modify, Read and Execute ,List
folder contents , Read, Write
System : Full control |
Practical

• Move Storage group

• Move database