Exchange servers can be configured individually with server specific settings. This is accomplished by configuring the properties of the specific server container, and configuring the objects within that server container. The server configuration objects are:

1. Private Information Store – Used to configure deleted item recovery, set storage limits for mailboxes, view resources such as NT accounts accessing mailboxes, and configure diagnostic logging for the IS.
2. Protocols – such as IMAP4, LDAP, NNTP and POP3
3. Public Information Store – Used to configure deleted item recovery, set storage limits for public folders, age limits for items in public folders, replica locations, replication schedules, and diagnostic logging.
4. Server Recipients – Contains the recipients homed on this particular server.
5. Directory Service – Used to manually initiate DS functions such as directory replication. Diagnostic logging can be configured.
6. Message Transfer Agent – Contains MTA message size limits. Can be used to manually recalculate the routing table. Used to view and change priorities of Queued messages. Diagnostic Logging.
7. System Attendant – Used to configure automatic deletion of message tracking log files (in days).
8. Directory Synchronization – ONLY PRESENT IF MS MAIL CONNECTOR IS INSTALLED.
9. MTA Transport Stack - ONLY PRESENT IF MS MAIL CONNECTOR IS INSTALLED.

Each server object itself has property pages (tabs) which can be used to configure Services, Database Paths, IS Maintenance, Diagnostic Logging, General and Advanced features, Permissions, and Locales (International and Global locales).

There are 2 Upgrade Options:

1. Standard Upgrade – Upgrades your current Exchange databases in their current locations. Failure requires restore from backup.
2. Fault-Tolerant Upgrade – Backs up each database to a different, temporary location before performing the upgrade. If the upgrade fails, the original databases will still be in their original locations. Requires at least twice the disk space as your IS and cannot be a network drive. NOT POSSIBLE WHEN UPGRADING FROM EXCHANGE 4.0.

Upgrade from 4.0 – Requires installation of Exchange 4.0 SP2 in a multi server environment. Single server environment is straightforward.

1. Administrator modifies EXCHNG.STF using a text editor or Setup Editor to modify the installation options for SETUP.EXE (installed services, protocols, etc...The file contains MS determined defaults by default).
2. Administrator modifies DEFAULT.PRF to modify the default profile information. This file is created when Setup Editor is run and configurations to ‘User Options’ are modified. By this process, Administrator can customize a default messaging profile for users.

1. Administrator modifies OUTLOOF.STF (32bit equivalent of EXCHANGE.STF) using Network Installation Wizard (NIW), available only on the Office 97 Resource Kit.
2. Administrator modifies OUTLOOK.PRF using a text editor (there is no other way).

1. MS Mail Connector
2. Directory Synchronization between Exchange and MS Mail
3. Schedule+ Free/Busy Connector

1. Manage a mixed environment
2. Configure Outlook to use the Schedule+ option (dummy it down) for group scheduling
3. Migrate all clients to Outlook

1. How frequently will backups be performed?
2. What type of backup will be performed? (Full, Differential, Incremental)
3. What time of day should backups be performed?
4. What device(s) will be used to backup?
5. How will backup data be stored?

1. Defragments the Private and Public Information Stores
2. Removes expired messages based on configured age limits
3. Deletes indices created to cache folder views

Exchange comes in two editions: Standard and Enterprise. The main difference between the two is the connectors that are bundled with each:

Standard Edition: Ships with connectors for IMS, MS Mail, Lotus cc:Mail, and Lotus Notes

Enterprise Edition: adds connectors for IBM OfficeVision/VM, SNADS, and X.400

In addition the Enterprise Edition can work with MS Cluster Server, and increases the storage limit to 16T for each of the Exchange databases (DS, Private IS, and PublicIS).

1. User Cannot Change Password
2. Password Never Expires
3. "User Must Change Password at Next Login" is NOT enabled

Exchange Server will grant the Site Service Account the following rights:

1. Act as part of the Operating System
2. Log on as a Service
3. Restore Files and Directories

1. Display Name – This is the name that will be displayed in the GAL and the Administrator window. By default, it is the first and last name values (ie Joe Smith)
2. Alias – The name used to generate foreign email addresses for the mailbox. By default, it is the Primary NT Account name. Exchange automatically generates foreign addresses for:

1. Primary Windows NT Account – This is the NT Account associated with this mailbox
2. Home Server – The Exchange Server on which this mailbox will reside

1. Admin Role (Modify User Attributes, Modify Admin Attributes)
2. Permissions Admin (Modify User Attributes, Modify Admin Attributes, Modify Permissions)
3. Send As
4. User (Modify User Attributes, Send As, Mailbox Owner)

The Standard Options for the types of foreign address are:

1. cc:Mail address
2. MS Mail address
3. MacMail address (MS Mail for AppleTalk)
4. Internet address
5. X.400 address
6. Other address

1. Permissions
2. Forms – can be associated with a public folder to provide a format for entering information.
3. Views – Public folders can be organized by various views, such as by sender, recipient, subject, and time frame.
4. Rules – Pertain to the automatic processing of information sent to the public folder.

1. Display Name
2. Alias Name
3. Members
4. Owner
5. Expansion Server – Designates the Server that will expand the DL
6. Notes

1. Address Space
2. Connector Cost
3. Option to Override the Account used to make the connection

1. Low to Medium Bandwidth requirement
2. Can utilize Dial-up connections
3. ALL DATA IS TRANSFERRED THROUGH MESSAGES
4. Different Transport Stacks Used – Supports TCP/IP, TP0/X.25, and TP4/CLNP. Each must be installed and configured through Control Panel/Network, and defined as an MTA Transport Stack in Exchange. Stacks are created in Exchange Administrator, File, New Other, MTA Transport Stack. After a stack is created, the X.400 Connector can be installed and configured
5. Remote Site Configuration is NOT AUTOMATIC
6. MUST use Messaging Bridgehead Server
7. Allows Connections to the Remote Site to be Scheduled (options are Remote Initiated, Never, Always, Selected Times)
8. Allows Delivery Restrictions (which users can use the connector, maximum message size)

Installed from Exchange Setup - Add/Remove Programs

Configuration can be organized into four main procedures:

1. LAN – Requires entering the postoffice path, and connection attempts
2. Asynchronous Connection – Requires Network Name, Postoffice Name, Sign-on ID, Password, Connection Attempts, Phone Number, Optional Settings
3. X.25 – the X.25 protocol must be installed and configured on the Exchange server. Properties are the same as Async, however X.25 requires X.121 address of the postoffice (a 16-digit number that identifies the computer on the X.25 network that contains the external postoffice)

1. Define and Configure Message Transfer – To create a new Connector MTA Instance, click the New button on the Connector MTA’s property page, and configure the following attributes:

1. Service Name – the name that represents a particular instance of the MTA
2. Polling Frequency – Set to indicate how long this instance of the MTA will wait before checking the postoffice for new mail. The default is 5 minutes
3. Connection Parameters – Default is LAN

1. Configure Destination Address – Four address templates are available:

1. X.400
2. MS Mail
3. Internet
4. General (can be used to create any type of address).

1. Configure Other Settings – Contains the following pages:

1. General Property Page – Used to set a maximum message size, and include an administrative note
2. Interchange Property Page – Used to select the Admin mailbox to receive information messages and alert notifications from the connector. Other properties include primary language and Message Tracking. If Tracking is enabled, information will be written to the tracking logs
3. Local Postoffice Property Page – The MS Mail Connector allows an Exchange server to function as an MS Mail postoffice. By default, the Exchange Organization name is used as the network name and the Exchange Site name is used as the postoffice name. This page is also where you would enter and change any passwords associated with the connector.

1. Create and Configure a Dirsync Object – In Exchange Administrator, File, New Other, Dirsync Server. Some of this object’s properties are:

1. Name – the directory name of this object
2. Dirsync Administrator
3. Server – The name of the Exchange Server that will function as the dirsync server
4. Schedule – A schedule can be defined to execute the T2 event

1. Remote Dirsync Requestors MUST be Created and Configured – the Administrator configures this information by creating a remote dirsync requestor object for each MS Mail postoffice. One of the most important properties of this type of object is the list of recipient containers that are to be exported to the remote requestor. This information is entered on the Export Containers Property Page. Attributes on this page include:

1. Recipient Containers
2. Trust Level
3. Configure the MS Mail Postoffices that are Dirsync Requestors – The requestors must be configured with information about the server

1. A Dirsync Requestor Object must be Created and Configured – The Dirsync Requestor Object is created and configured in the same manner as the Dirsync Server Object.
2. Configure the Mail Dirsync Server – The server must be configured with information about the requestors

1. Use the Replication Schedule Property Page of the IS to set a "global" replication schedule
2. Use the Replication Schedule Property Page on the folder itself. This Overrides the IS setting

1. Configure the messaging connector to be used for intersite directory replication

All Connectors except he Site Connector (which is used to connect to Exchange sites) need to be "informed" that the remote site is an Exchange Server site. This is specified on the Connected Sites Property Page of the messaging connector.

2. Install a Directory Replication Connector for BOTH sites

1. Local Bridgehead Server
2. Remote Site Name
3. Remote Bridgehead Server
4. E-Mail Address of the Remote Bridgehead Server

1. Identify the directory replication BRIDGHEAD at each site

Only one server in a site can be assigned the duty to replicate to a given remote site. One server can, however, replicate to more than one remote site. In Intersite Directory Replication, Bridgehead Servers Must Request Replication Information. Directory information is never pushed to a remote site. This is in contrast to intrasite replication, where servers send a notification of new information to the other servers of the site.

2. Configure a replication schedule

There are 2 strategies to Migration, the SINGLE-PHASE, and the MULTI-PHASE.

Three Main Tools are used to perform a migration:

1. Source Extractors – Extracts information and places it in a format that can be imported into Exchange. Requires Administrative privileges on the foreign mail system. Creates three file types: (The 3 together are commonly referred to as "The Migration Files"

1. Primary files (*.PRI) – Contain mailbox names, custom recipients, personal address book, message headers of messages being extracted. Is in CSV format.

2. Secondary Files (*.SEC) – Contain the message bodies, message attachments, and scheduling data

3. Packing List File (*.PKL) – Contains Filenames and other information pertaining to the information in the primary and secondary files.

2. Migration Wizard – Executed from the Exchange Program Group. Can automatically extract information from: MS Mail, cc:Mail, Novell GroupWise, and Collabra Share forums.

1. Select Mailboxes to Import
2. Create Mailboxes – Existing mailboxes can be used, but the default is to create new Exchange mailboxes. Additional properties pertaining to new mailboxes are:

1. Recipient Container
2. Templates
3. Passwords (Random or Use Alias Name)

1. Messages and Folders
2. Shared Folders
3. Personal Address Books (PABs)
4. Calendar Files

1. Directory Import and Export - used when bulk changes need to be made. Copies the properties of a large number of recipients to an editable text file.

Mail sent to a migrated user can be handled by:

1. Forwarding Feature – If the foreign mail system supports it
2. Directory Synchronization – enables users in the foreign system to see and use the addresses of the migrated users. This is probably the best option.
3. Use Both Mailboxes – Lame
4. Former Email address maintained through a Proxy Address
5. Edit an alias file on the SMTP relay host to point to the new address
6. Delete Postoffices once all users are migrated
7. Migrate ALL Users

In addition to the information in Article 1.06, Messaging Profiles need to be addressed. It is important to remember that they can be automatically setup using the edited DEFAULT.PRF and OUTLOOK.PRF files.

1. Information Services – Specifies the Information Services (MAPI providers that permit access to back-end messaging systems) to be used. Can include MS Exchange, Personal Folders, MS Mail, MSN, MS Fax, Internet Mail, and CompuServe Mail.
2. Information Storage – Where to deliver incoming mail, Offline folders, Message handling settings (sounds,etc.), Options for deleting (prompt or not), and Options after moving or deleting open messages (open next, open prev, etc...)
3. Delegate Access – Send on Behalf of, Send As, etc...
4. Remote Mail

Roaming Messaging Profiles are setup much the same as Roaming User profiles. The key is that the profile must be on a server, and the local machine must be configured to find the profile on that server. For DOS and Win3.x Clients, this involves editing configuration files (Win.ini) , for win9x and NT clients, the procedure is accomplished by pointing to the profile in the User Environment Tab in Control Panel/Users

The role of the MTA is to manage the transfer of data. MTA properties are accessed through the MTA Site Configuration Object in the Configuration container. IS handles message transfer within a server, MTA handles all transfers BETWEEN servers.

Message Tracking - An important feature that is enabled from the Tools menu in Exchange Administrator. If enabled, the SA will keep a log of routing information for every message in the MTA process. The Log is stored in ASCII format in the EXCHSRVR\TRACKING.LOG directory. Filenames are formatted as YYYYMMDD.LOG, example 19970201.LOG .

1. RTS Values – Indicate:

1. How often you want to verify information being sent

2. How long to wait after an error before re-sending

3. How often you want verification from another server that it has received a message.

RTS Values Attributes:

a. Checkpoint Size – The amount of data to be sent before a checkpoint is inserted

b. Recovery Timeout – The length of time the MTA waits for a reconnection after an error

c. Window Size – Indicates the number of checkpoints that can be sent before an acknowledgement must be received from the destination.

2. Connection Retry Values – Indicate:

1. How many times you want to try to open a connection
2. How many times to try to send a message
3. How long to wait after an error to re-open a connection
4. How long to wait to re-send after an error

1. Association Parameters – Indicate:

1. How long to keep an association (an open pathway to another system) open
2. How long to wait for a response before closing the association
3. The number of queued messages that will trigger an additional association

1. Transfer Timeouts – Indicate how long to wait after a transfer failure before sending a Non-Delivery Report (NDR) to the sender

If there are several connectors the MTA will go through a selection process to choose a connector through which to send messages. The basic steps are:

1. A LOCAL MTA component receives a message destined for another site. The MTA temporarily store the message in a queue until it determines a route for the message
2. The MTA reads the destination address of the message and queries the GWART (Gateway Address Routing Table) for an entry to that destination. If there is only 1 connection, the MTA passes the message to the MTA on that connector’s server. If there are more than one connection, the MTA goes through a selection process, with COST being a key factor.
3. After passing he message to the relevant connector, the MTA deletes the message from the queue and notifies the SA of successful delivery. The SA writes that information in the tracking log file.
4. If the Message cannot be delivered, the local MTA sends the message back to the sending object with an NDR.

1. General – Enabled and Disabled here.
2. Authentication
3. Message Format
4. Idle Time-Out

1. POP3 Server Name
2. SMTP Server Name
3. POP3 Account Name
4. POP3 Account Password – The password of the NT User account
5. POP3 Client E-Mail Address – The SMTP address of the POP3 client

1. General
2. Authentication
3. Anonymous
4. Message Format
5. Idle Time-Out

1. Collaboration Data Objects (CDO) – The libraries of functions providing basic messaging functions to Active Server Pages
2. Active Server Pages – Programs, written in ActiveX and running on an Active Server, that provide access to a specific MS BO application.

1. Authentication – Basic or MSCHAP. Set through IIS Internet Service Manager
2. Encryption – Enabled through IIS Internet Service Manager. Active Server uses SSL encryption protocol. Normally Web Browsers use Port 80 to communicate with a Web server. But when a Web browser and Web server communicate using SSL, Port 995 is used.
3. Rejecting IP Addresses – Can be used to reject designated IP addresses or Ranges of IP addresses. Can be used to reject clients using POP3, IMAP4, NNTP, and LDAP. Configured through the Exchange Administrator Program

1. General
2. Folder Shortcuts – Contains the list of public folders that will be available to anonymous Web users
3. Advanced – Enables the setting of the maximum number of Address Book entries that will be returned to an authorized Web client. The default is 50.

1. Installed Server – The name of the Exchange Server that will receive the newsfeed
2. Type of Newsfeed – Inbound, Outbound, or Both
3. Connection Type – LAN or DUN
4. Schedule –
5. Host Computer – The computer that SENDS the newsfeeds
6. Security
7. Administrator
8. Active File – This file contains the list of all available newsgroups on the USENET host. Allows importing or downloading of the Active File

1. General
2. Messages – Controls Inbound and Outbound message size
3. Hosts
4. Connection
5. Security
6. Schedule
7. Advanced
8. Outbound
9. Inbound

The primary advanced security feature in Exchange is the Key Management Server. To deploy KM, ONE server in the organization must be configured as follows:

1. It must be in the domain used for centralized administration
2. It must be backed up regularly and physically secure
3. It must use NTFS

During client setup, Exchange copies ETEXCH.DLL to Win3.x clients, and ETEXCH32.DLL to Win9x and NT clients. Each user’s mailbox must be configured for advanced security and create certificates (form the Security Page of the mailbox) before security can be enabled. Also, before a client can use advanced security, they must request and receive their keys and certificates from the KM Server.

Managing Users is accomplished through responsible and efficient creation of mailboxes in Exchange Administrator, and User Accounts in User Manager for Domains. Tools such as templates can be used to facilitate creation of multiple, similar mailboxes. The Find Recipients feature in the Tools menu of Exchange Administrator as well as the ability to move mailboxes between Servers can be of great benefit in managing Users. Moving Mailboxes (and organizing mailbox storage from the start) can be EXTREMELY beneficial in regard to:

1. Balancing the Load between Servers
2. Keeping "Common" Users on the same Network Segment
3. Allowing Users to access their mailboxes while servers are taken down for maintenance

Periodic Cleaning of mailboxes based on age, size, read/unread status, can also aid an administrator in managing Users and resources.

Using Batch Processes to modify multiple recipients can also reduce the amount of time an Administrator must spend on User maintenance and management. Other issues such as address space entries, Trust, Cost, and Affinity levels, and automated, customized installations can further facilitate User Management.

A related setting is the Garbage Collection Interval, which is the time interval at which tombstones are permanently deleted.

The DS/IS Consistency Adjustment ensures that the DS and IS databases are synchronized. It is initiated on the Advanced Property Page of an individual server.

EDBUTIL.EXE (Exchange Database Utility) can only be run when the DS and IS are stopped. It performs the following:

1. Defragments a database
2. Consistency Check – Compares related information in a database to make sure it agrees.
3. Recover a database

The ISINTEG Utility discussed in article 1.07(b) can also be a very useful directory maintenance tool.

This has been covered in articles 2.03, 2.04, and 2.05.

Be aware of the implications and requirements of RAS and the RAS Connector. See Page 500

Used to test the message link between two Exchange servers. Sending a message to a designated remote server or recipient on a remote server tests a link. Created in Exchange Administrator by choosing File, New Other, Link Monitor.

Used to monitor the services running on an Exchange server, send notifications, and perform specified actions. Created in Exchange Administrator by choosing File, New Other, Server Monitor. This brings up thew property pages of the Server Monitor:

1. General – Directory name, Display Name, LOG FILE, Polling Interval
2. Servers – Monitored Servers, Services to Monitor
3. Notification – When, How, Who
4. Actions – Actions to take when a service has stopped. (None, Restart Service, Restart Computer)
5. Clock – Synchronization of system clocks on both computers, and actions to take if not within a specified range

These Properties also apply to the Link Monitor

Microsoft Exchange Server 5.5 supports the MADMAN MIB (RFC 1566). This enables third-party SNMP management programs to access the various management statistics of an Exchange Server (version 5.5). MIB stands for Management Information Base, and defines a database structure for management statistics. SNMP stands for Simple Network Management Protocol, and defines a set of management objects and procedures for managing enterprise-wide environments.

To Troubleshoot a Migration Problem, the primary tools to use are Event Log (Event Viewer) and the Migration Wizard Error Summary.

If problems occur during a migration, some probable causes are:

1. Account used to perform migration does not have Administrator privileges in the existing system.
2. Account used to perform migration does not have Administrator privileges in the Exchange system.
3. The .PKL, .PRI, or .SEC files were edited improperly
4. The .PKL or .PRI files are missing
5. The .PKL or .PRI files are renamed
6. Network Problems occurred during the migration
7. The Private Information Store ran out of space during the migration
8. When migrating GroupWise accounts, be sure to have "PROXY ACCESS" granted to the account performing the migration

See Page 342

 Content created and copyright Ó 1998-1999, by David L. Woodall, all Rights Reserved