Microsoft Exchange Server 5.5 Service Pack 1
Information in this document is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. 
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1998 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, MS, Outlook, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Before You Begin
Service Pack 1 for Microsoft® Exchange Server version 5.5 is part of Microsoft’s commitment to provide important product refinements on a regular basis. This service pack includes significant new enhancements, including Microsoft Outlook 98, Microsoft’s premier messaging and collaboration client. In addition, Service Pack 1 includes many important new server features, which are described in the following sections.
Service Pack 1 includes fixes to server issues that were previously available as Microsoft Quick-Fix Engineering (QFE) patches. For a complete list of QFE patches included in this service pack, see Microsoft Knowledge Base article Q171593. Knowledge Base articles are available from the Microsoft support Web site at http://www.microsoft.com/support.

Note  To print a single page of this document, use the Print command in your Web browser. To print the entire document, print the file Readme.rtf using Microsoft Word. Readme.rtf is located in the root directory of the Service Pack 1 compact disc, or in the main directory of the files you downloaded.

This document has three main sections: “Installing Service Pack 1,” “What’s New in Service Pack 1,” and “Known Issues.” It contains information about this service pack release that is not available in the Microsoft Exchange Server 5.5 documentation.
Installing Service Pack 1
Microsoft recommends that you apply Service Pack 1 to all servers running Microsoft Exchange Server 5.5 as soon as possible. The Update program installs all QFE patches and basic new functions. Additional new functions are installed separately, as described in the documentation for those functions.

Important  Be sure to make and verify a complete backup of your Microsoft Exchange Server computer before installing this service pack. The service pack cannot be uninstalled.

The system requirements for installing Service Pack 1 are the same as the requirements for installing Microsoft Exchange Server 5.5.
	To install Service Pack 1 from the compact disc	
1.	Make and verify a complete backup of your Microsoft Exchange Server computer.
2.	Insert the Service Pack 1 compact disc into the CD-ROM drive.
3.	At the Windows NT command prompt, switch to that CD-ROM drive, and then switch to the \<language>\Server\Setup directory (see the root directory for server languages included on this compact disc).
4.	Switch to the I386 or Alpha directory (depending on whether you have an Intel or Alpha AXP processor).
5.	Type Update, and then follow the instructions displayed on the screen.
What's New in Service Pack 1
Microsoft Exchange Server 5.5 Service Pack 1 includes the following new features:
•	Microsoft Outlook Web Access
•	Microsoft Outlook 98
•	Microsoft Outlook for Macintosh
•	Microsoft Exchange Chat Service
•	Microsoft Outlook HTML Form Converter
•	Move Server Wizard
•	Key Management Server
•	Migrating from Lotus Notes
•	Message Journaling
•	Preventing Unsolicited Commercial E-mail
•	Clean Mailbox
•	Free Space Message
•	Microsoft Exchange Server Routing Objects
•	Using the Cirel X.25 Card with Microsoft Exchange Server
•	Collaboration Data Objects (CDO) 1.21
•	Using Connectors on Computers with Alpha AXP Processors
•	Message Transfer Agent Enhancements
•	Replicating Large Distribution Lists
Microsoft Outlook Web Access
This service pack includes the following enhancements to Outlook Web Access.
Contacts Module
The Contacts module has been added to Microsoft Outlook Web Access. Users can now create new contacts to store information such as phone numbers, addresses, e-mail addresses, job titles, Web pages, and notes. Contacts can be sorted by first name or last name for quick access to important information. Users can also move or copy a contact to a different folder, or attach a file, such as a Microsoft Word document, to a contact to keep related information together. In addition, e-mail messages and meeting requests can be created directly from a contact. Outlook Web Access users can also view a map of a contact's business or home address.
Change Password Feature
The Change Password feature is part of Outlook Web Access Options. This feature enables users on Microsoft Internet Information Server (IIS) version 4.0 with Secure Sockets Layer (SSL) enabled to change the password for their domain server account.
Check Names Feature
The Check Names feature enables users to verify the names of mail message and meeting request recipients. When users choose the Check Names button on the Compose New Meeting Request or Compose New Mail Message screen, Outlook Web Access identifies any names that cannot be resolved. Users can accept a suggested match, or if no matches are available, they can ignore the recipient.
For more information about these new features, see Outlook Web Access Help.
Microsoft Outlook 98
This service pack includes Microsoft Outlook 98, which combines the leading support for Internet standards-based messaging systems—including Microsoft Exchange Server—with integrated calendar, contact, and task-management features. Outlook makes it easy to:
•	Get connected, and communicate and share information.
•	Work seamlessly with Microsoft Office 97, Microsoft Exchange Server, and Microsoft Internet Explorer version 4.0.
•	Organize and view information.
Microsoft Outlook for Macintosh
Microsoft Outlook Exchange Server Edition for Power Macintosh adds support for Apple Power Macintosh computers running Apple's MacOS 8 system software, including version 8.1. Outlook functionality, that was disabled when the previous version of Outlook was used with MacOS 8, has been restored.
This release also supports Macintosh computers with Motorola M680x0 processors.
Microsoft Exchange Chat Service
This service pack includes the newest release of Microsoft Exchange Chat Service, a Microsoft Windows NT service that allows real-time conversation and collaboration among users in the Internet community or on a private network. Chat Service is based on the Internet Relay Chat (IRC) protocol, an Internet standard that currently forms the basis of several worldwide chat networks. Chat Service also supports IRCX, a set of functional extensions to the IRC protocol. IRCX offers many features, including Unicode support, multilayer security, and several new commands for managing users and channels.
This release of Chat Service also includes the following server extensions:
•	Channel Transcription. Allows you to transcribe conversations in persistent or dynamic channels on a chat server.
•	Profanity Filter. Allows you to detect and control the use of inappropriate language in persistent and dynamic channels.
These extensions are based on the Chat Server Extensibility Model, which provides the means for monitoring and controlling Chat Service properties. You can write custom extensions using the Chat Server Extensibility Software Development Kit (SDK) included with Chat Service. Developing your own server extensions allows you to extend your administrative control over your chat network and its users.
For more information, see the Chat Service online documentation and Chat readme file relnotes_chat.htm.The online documentation is installed by the Chat Service Setup program located in the Eng\Chat\Setup directory on the SP1 compact disc. Be sure to select the Online Documentation and Server SDK option when installing the Chat Service. To view the documentation after installing the Chat Service, from the Start menu, choose Programs, choose Microsoft Exchange Chat Service, and then choose Books Online.
Microsoft Outlook HTML Form Converter 
To create forms that Web users inside and outside your organization can use, start with the built-in form creation capability of Outlook version 8.03 or Outlook 98 and finish with the Outlook HTML Form Converter tool. This tool can convert a form designed and created in Outlook into a form that can be used on the Web (a form created from HTML and Active Server Pages [ASP] code).
After conversion, these HTML/ASP forms can be used by anyone running Microsoft Outlook Web Access. To obtain Outlook Web Access, install it from the Microsoft Exchange Server 5.5 compact disc.
The Outlook HTML Form Converter runs only on English versions of Windows 95, Windows 98, and Windows NT.  
For more information Outlook HTML Form Converter, see the Cdo.hlp file. It is located in the Eng\Server\Setup\I386\Bin directory. Choose the Index tab and choose “Microsoft Outlook HTML Forms Converter.”
Move Server Wizard
The Microsoft Exchange Move Server Wizard allows administrators in organizations that use Microsoft Exchange Server to change the structure of, or information about, their site or organization.
The Move Server Wizard allows administrators to:
•	Move a Microsoft Exchange server between existing sites and organizations.
•	Move a Microsoft Exchange server to create a new site or organization.
•	Move a Microsoft Exchange server to a new site in an existing organization.
•	Merge existing Microsoft Exchange server sites and organizations.
The Move Server Wizard for SP1, including documentation, is available for download from the Microsoft Web site at  http://backoffice.microsoft.com/downtrial/moreinfo/Ex55sp1wizard.asp. The Move Server Wizard is not included on the SP1 compact disc.
Key Management Server
You can use Microsoft Exchange Server 5.5 Service Pack 1 to perform the following new security-related functions:
•	Use Microsoft Certificate Server to generate user certificates. Service Pack 1 is the first release in which Certificate Server can act as the certification authority (CA) for the organization. If you use only Version 3 (V3) certificates in your organization, Key Management server (KM server) no longer acts as the CA. KM server is now the key recovery agent for Certificate Server. For more information, see "Configuring Microsoft Certificate Server for Use with KM Server" later in this document.
•	Use industry standard X.509 V3 certificates issued by the Certificate Server for use with Secure/Multipurpose Internet Mail Extension (S/MIME) clients. Any S/MIME client (for example, Outlook Express, Outlook 98, or any third-party S/MIME client) can use X.509 V3 certificates. KM server generates the X.509 V1 certificates for backward compatibility with Outlook 97 and earlier Microsoft Exchange clients. For more information, see "Configuring KM Server to Use V1 and V3 Certificates" later in this document.
•	Establish trust with other certification authorities. You can use KM server to establish trust relationships by importing or removing root certificates and Certificate Revocation Lists (CRLs) from outside organizations. Root certificates must be X.509 V3, but are not required to be issued by a Certificate Server. When a certificate is imported, it is added to a certificate trust list that is published to the directory. Outlook 98 clients running in corporate mode can read the certificate trust list and authenticate and trust the S/MIME digital signatures on e-mail received from users in other organizations. In addition to importing certificates from other organizations, you should export your root certificates so KM server administrators in other organizations can import them. This establishes a network of trust. For more information, see Microsoft Exchange Server Operations, which is included in the version 5.5 documentation.

Note  To enable clients to use S/MIME security, you must install the Outlook 98 QFE version from the Support\Olcsp<security type> directory on the Microsoft Outlook 98 compact disc included with Microsoft Exchange Server 5.5 Service Pack 1.

Configuring Microsoft Certificate Server for Use with KM Server
You can use Certificate Server to issue, revoke, and renew certificates that can be used for client authentication. Certificate Server can be deployed in the following ways depending on how you use security in your organization:
•	As a Web client that KM server can use to communicate with a CA. 
•	As a stand-alone CA.
•	As a subordinate CA that is dependent on a CA to sign the certificates it issues.
Installing the Certificate Server Web Client
Typically, KM server and Certificate Server are installed on different computers, although they can be installed on the same computer. If KM server is installed on a computer that does not have Certificate Server installed, you must install the Certificate Server Web client so KM server can communicate with a CA installed on a different computer. This communication between the certification client and CA is called a chain of trust.
On the computer where the Certificate Server Web client will be installed, before installing the Certificate Server Web client, you must:
•	Install Internet Explorer version 4.01 or later.
•	Map a network drive to the shared certificate directory on the CA computer, and then select the Reconnect at logon option.

Important  The drive you map to the shared certificate directory on the CA computer can never be changed. If the drive is mapped to a particular drive letter, that drive letter must never change. This is called a persistent mapping. You can use the following Windows NT command to create a persistent mapping, where Certs is the name of the directory where the certificates are contained:
net use z: \\<servername>\<Certs> /persistent:yes

	To install the Certificate Server Web client 	
1.	Run the Windows NT Option Pack 4 Setup program and choose Custom.
2.	On the Components page, select Certificate Server, and then choose Show Subcomponents.
3.	Select Certificate Server Web Client, and then choose Next.
4.	On the Microsoft Certificate Server page, in the Shared Folder box, enter the drive letter you mapped to the shared certificate directory on the CA computer, and then choose Next.
Installing the Certificate Server CA
A Certificate Server CA can function as the top level (root) of a chain of trust or can run stand-alone. Computers running the Certificate Server Web client and computers running Certificate Server as a subordinate CA require a Certificate Server CA to sign certificates, issue certificates, and issue Certificate Revocation Lists (CRLs) for clients to use.
Before installing the Certificate Server CA, you must install Internet Explorer 4.01 or later on the server computer. You must also create a shared directory where Certificate Server will store certificates. The Windows NT Everyone account should have Read permission on the shared directory.
After installing the Certificate Server, you must install the Exchange policy module and Certificate Server hot fix before the Certificate Server can use KM server. 
	To install the root CA 	
1.	Run the Windows NT Option Pack 4 Setup program and choose Custom.
2.	On the Components page, select Certificate Server, and then choose Show Subcomponents.
3.	Select Certificate Server Certifying Authority, and then choose Next.
4.	On the Microsoft Certificate Server page, in the Shared Folder box, enter the path to the shared certificate directory on the CA computer, and then choose Next.
5.	Select Show Advanced Configuration, and then choose Next.
6.	In the Hash Algorithm box, choose SHA-1.
7.	Verify that Root CA is selected, and then choose Next.
8.	Type the information describing your CA, and then choose Next.
9.	After the computer reboots, install the Microsoft Exchange Server policy module and the Certificate Server hot fix. 
	To install the Microsoft Exchange Server policy module and the Certificate Server hot fix 	
1.	In Control Panel, double-click Services, and then stop the Certificate Authority service.
2.	Download the Certificate Server hot fix from FTP://ftp.microsoft.com/bussys/iis/iis-public/fixes/usa/certserv and install it. This fix is also included in Microsoft Windows NT Server version 4.0 Service Pack 4.
3.	Copy the Expolicy.dll file from the Eng\Support\KMS\Expolicy\<operating system> directory on the Microsoft Exchange Server 5.5 Service Pack 1 compact disc to the Winnt\System32 directory on your Certificate Server computer. 
4.	At the command prompt, type regsvr32 c:\winnt\system32\expolicy.dll to register the policy module.
5.	In Control Panel, double-click Services, and then restart the Certificate Authority service.
Installing a Certificate Server Subordinate CA
A Certificate Server subordinate CA is a certifying authority that issues certificates and CRLs, but does not sign certificates. The subordinate CA must submit certificates to a root CA to be signed. 
Before installing the Certificate Server subordinate CA, you must install Internet Explorer 4.01 or later on the server computer. You must also create a shared directory where Certificate Server will store certificates. The Windows NT Everyone account should have Read permission on the shared directory.
After installing the Certificate Server, you must install the Exchange policy module and Certificate Server hot fix before the Certificate Server can use KM server.
	To install a subordinate CA 	
1.	Run the Windows NT Option Pack 4 Setup program and choose Custom.
2.	On the Components page, select Certificate Server, and then choose Show Subcomponents.
3.	Select Certificate Server Certifying Authority, and then choose Next.
4.	On the Microsoft Certificate Server page, in the Shared Folder box, enter the path to the shared certificate directory on the CA computer, and then choose Next.
5.	Select Show Advanced Configuration, and then choose Next.
6.	In the Hash Algorithm box, choose SHA-1.
7.	Select Non-Root CA, and then choose Next.
8.	Type the information describing your CA, and then choose Next. 
9.	After the computer reboots, install the Microsoft Exchange Server policy module and the Certificate Server hot fix. 
	To install the Microsoft Exchange Server policy module and the Certificate 
Server hot fix 	
1.	In Control Panel, double-click Services, and then stop the Certificate Authority service.
2.	Download the Certificate Server hot fix from FTP://ftp.microsoft.com/bussys/iis/iis-public/fixes/usa/certserv and install it. This fix is also included in Microsoft Windows NT Server version 4.0 Service Pack 4.
3.	Copy the Expolicy.dll file from the Eng\Support\KMS\Expolicy\<operating system> directory on the Microsoft Exchange Server 5.5 Service Pack 1 compact disc to the Winnt\system32 directory on your Certificate Server computer. 
4.	At the command prompt, type regsvr32 c:\winnt\system32\expolicy.dll to register the policy module.
Creating Trust Between a Subordinate CA and a Root CA
The Certificate Authority service will not start automatically until you obtain a certificate from another CA using the request file in the Certs directory. You must copy the certificate from the CA directory to the Certs directory, and then run the Certificate Server Hierarchy Configuration tool (Certhier.exe) to establish a trust relationship between the root CA and the subordinate CA. 
	To create a trust relationship between a subordinate CA and a root CA 	
1.	From the Certs directory on the subordinate CA computer, copy the .req file to a floppy disk.
2.	At the root CA computer, log on as an Administrator. 
3.	From the command prompt, type the following command:
certreq a:\<filename>.req a:\ <filename>.crt
4.	From the shared certificate directory, copy the signature file of the root CA to the floppy disk. The following files are now on the floppy disk:
•	SubMachineName_SubCAName.crt
•	SubMachineName_SubCAName.req
•	RootMachineName_RootCAName.crt
5.	From the subordinate CA computer, copy the root CA signature file to the Winnt\System32 directory, and name it RootCa.crt. 

Note  This file must be copied as RootCa.crt not RootMachineName_RootCAName.crt, where RootMachineName is the name of your computer, and RootCAName is the name of your CA.

6.	Copy the new signed .crt file and the original .req file from the floppy disk to the shared directory.

Note  The subordinate CA certificate is SubMachineName_SubCAName.crt where SubMachineName is the name of the computer where the subordinate CA is installed, and SubCAName is the name of the subordinate CA.

7.	Verify that the following registry key value exists. If not, add a new string value.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\
Configuration\<SubCAName>\HierFileName
where <SubCAName> is the name of the subordinate CA. Set the value of the registry key to <path><SubCAName>, where <path> is the complete path to the shared certificate and <SubCAName> is the name of the .req file without the .req extension. For example:
c:\certs\SubMachineName_SubCAName
8.	From the command prompt, run Certhier.exe.
9.	In Control Panel, double-click Services, and then start the Certificate Authority service.
Configuring KM Server to Use V1 and V3 Certificates
You can configure KM server to use any combination of V1 and V3 certificates. 

Note  You must have Windows NT 4.0, Windows NT 4.0 Service Pack 3 or later, and Internet Explorer 4.01 or later installed.

	To use existing client security 	
1.	Run the Setup program for Microsoft Exchange Server 5.5 and choose Custom\Complete.
2.	Select KM Server.
3.	Install Microsoft Exchange Server 5.5 Service Pack 1. 
	To enable the server to issue V3 certificates for S/MIME clients 	
1.	Run the Setup program for Microsoft Exchange Server 5.5 and choose Custom\Complete.
2.	Select KM Server.
3.	Install Microsoft Exchange Server 5.5 Service Pack 1.
4.	Install the Certificate Server Web client.
5.	In Control Panel, double-click Services, and then restart the Key Management service.
6.	In the Administrator window, double-click the CA object.
7.	Select the Enrollment tab.
8.	Select V1 and V3 or V3 only. 
9.	Select your Certificate Server configuration string, and then choose OK.

Migrating from Lotus Notes
The Microsoft Exchange Migration Wizard now supports migration of mailboxes and calendars from Lotus Notes and Lotus Domino servers. You can migrate from Lotus Notes server releases 3.x, 4.0, and 4.1, and Lotus Domino server releases 4.5 and 4.6 running on Microsoft Windows NT Server, OS/2, UNIX, and Novell NetWare operating systems.
Preparing for Migration
You should plan your migration strategy using the information in Microsoft Exchange Server Migration. You can choose a one-step migration, which is shown in the following illustration. A one-step migration extracts information from the Notes server and imports it directly to the Microsoft Exchange Server computer.

You can also choose a two-step migration. To complete a two-step migration, you first extract migration files from the Notes server, optionally review or edit the migration files, and then later import the migration files to a Microsoft Exchange Server computer. When you run the Migration Wizard a second time, choose the Import from Migration Files option. The two-step migration process is shown in the following illustration.

You must install Microsoft Exchange Server 5.5 Service Pack 1 on the computer running the Migration Wizard. The Migration Wizard is supported on both Intel 386 and Alpha platforms.
You must install the Lotus Notes release 4.5.2 or later client program on the computer you are using for migration. Add the Notes client directory to the system path of the computer. The default directory is C:\Notes. The source extractor uses some of the Notes client files to connect to the Notes server.
You must provide the ID file for a Notes user that has at least Editor permissions for all of the mailboxes being migrated. The source extractor uses this ID file when it connects to the Notes server. You must specify the path of the Notes.ini file that was created by the Notes client program. The default path is C:\Winnt\Notes.ini.
If you want to maintain coexistence between a Notes domain and a Microsoft Exchange Server organization during a phased migration, you must install the Microsoft Exchange Connector for Lotus Notes on a Microsoft Exchange Server computer in the organization. In addition, you must install the Notes E-mail Addressing Component on one server in each Microsoft Exchange site that does not contain the Connector for Lotus Notes. You can install the Notes E-mail Addressing Component using the Connector for Lotus Notes Setup program, which is on the Microsoft Exchange Server 5.5 compact disc.
Notes and Domino users should accept or decline all meeting requests in their mail databases before migration. When accepted meeting requests are processed, the information is moved to the calendar and migrated as a calendar entry. Unaccepted meeting requests are converted to text messages during migration, and users then have to enter the appointments in their calendars manually.
Japanese users should avoid double-byte character set (DBCS) characters for the account alias, and Windows NT user name and password. If you use DBCS names, you should change them to single-byte names before migrating to Exchange.
If you are migrating to a Microsoft Exchange Server running on a DEC Alpha computer and you plan to convert Notes Document Links to OLE attachments, you must change the .dll name in the following registry entry.
HKEY_CLASSES_ROOT\CLSID\{4BF8C361-AA44-11CE-861A-02608CDC7325}\InProcServer32] @="<c>:\notes\nolemon.dll"
The correct .dll name is Aolemon.dll as shown in the following example.
[HKEY_CLASSES_ROOT\CLSID\{4BF8C361-AA44-11CE-861A-02608CDC7325}\InProcServer32] @="<c>:\notes\aolemon.dll"
Run the Migration Wizard on a different computer from the one running the Notes server being migrated.
What is Migrated
The source extractor in the Migration Wizard can migrate Notes and Domino mail databases, messages in all folders in mail databases, and calendar entries. For each account you select on the Notes server, the Migration Wizard can create a new mailbox on the Microsoft Exchange Server computer.

Note  Documents in a Notes mail database are called memos and messages. The terms mean the same thing. The term messages is used in this documentation.

The Migration Wizard supports messages based on the standard templates that are included with Notes and Domino. If you have customized templates with additional properties, the additional properties are not migrated.
For each account selected to be migrated, you can choose to migrate all of the messages stored in the Notes mail database, or only messages within a selected date range.
Messages containing Lotus rich text formatting, such as bold, font size, and color, are converted to Microsoft rich text format (RTF) messages in Microsoft Exchange Server. The conversion is done using the Lotus RTF converter that ships with the Notes client. Not all attributes can be converted correctly. The following table shows which attributes are correctly mapped in migrated messages.
Lotus Rich Text Attribute	Microsoft Rich Text Attribute	
		
Size	Mapped correctly	
Color	Mapped correctly	
Bold	Mapped correctly	
Underline	Mapped correctly	
Italic	Mapped correctly	
Strikethrough	Mapped correctly	
Tables	Mapped correctly in WordMail, not displayed correctly in Outlook	
Embedded OLE objects, including graphics	Mapped correctly, can be edited	
Font name 	Always Times Roman	
Double strikethrough	Ignored	
Superscript	Ignored	
Subscript	Ignored	
Shadow	Ignored	
Outline	Converted to italic	
Emboss	Ignored	
Engrave	Ignored	
Small caps	Ignored	
All caps	Ignored	
Drop caps	Ignored	
Hidden	Ignored, text is visible	
Underline other than single	Ignored	
Bitmaps not embedded as OLE objects	Not migrated	
You can choose one of the following options for converting Document Links within the messages being migrated:
•	Select URL to convert Document Links to URL shortcuts within the message. The referenced document remains on the Domino server. When a Microsoft Exchange Server user selects the URL shortcut, the referenced document is displayed in the user’s default browser. The URL option only works for servers that have the Domino Web server configured and running; Document Links on Notes servers are handled as if you selected the RTF option.
•	Select OLE to convert Document Links to OLE attachments within the message. The OLE object contains a pointer to the referenced document that remains on the Notes server. When a Microsoft Exchange Server user selects the OLE attachment, the referenced document is displayed in the user’s Notes client.
•	Select RTF to convert Document Links to rich text format message attachments. The referenced document is converted to RTF format and stored on the Microsoft Exchange Server computer. When a Microsoft Exchange Server user selects the RTF attachment, the converted document is displayed in the user's default application configured for .rtf files.
You can choose to convert calendar entries on the Notes server to appointments on the Microsoft Exchange Server computer. When you choose to migrate calendar entries, all calendar entries for the selected accounts are migrated; you cannot specify a date range.
Because the source extractor cannot obtain access to users' private keys, encrypted messages cannot be migrated.
User folders that do not contain messages are not migrated.
Running the Migration Wizard
Before running the Migration Wizard, read Microsoft Exchange Server Migration. If you plan to maintain coexistence between a Notes domain and a Microsoft Exchange Server organization, verify that you have installed the Connector for Lotus Notes before beginning migration.

Note  The Migration Wizard migrates only mail and calendar information from Notes and Domino servers.

	To start the Migration Wizard 	
1.	From the Start menu, choose Programs, choose Microsoft Exchange, and then choose Microsoft Exchange Migration Wizard.
2.	Select Migrate from Lotus Notes, and then choose Next.
Follow the Migration Wizard instructions. If you need more information about an option in the Migration Wizard, choose Help.

Note
•	Do not allow client sessions with a Notes server running on UNIX during the migration. Connected users will not be migrated.
•	Passwords are case-sensitive.
•	You can migrate all accounts or select the accounts you want to migrate.
•	The Migration Wizard does not make changes to the mail databases on the Notes server.

Using Command-Line Options
You can run the Migration Wizard using a combination of command-line options and a control file. For general information on command-line options, see Microsoft Exchange Server Migration, which is included in the version 5.5 documentation.
The specific control file option for migrating from a Lotus Notes server is Mode and the value is NOTES. 
The accounts file, specified by the Accounts option in the control file, lists the specific accounts to migrate. The format for names in the optional accounts file is different than the format that appears in the Migration Wizard. To list specific accounts, use the following format:
<First name> <Last name>/<Notes Organization Name>
For example: Maria Black/FergBard.
If the Lotus Notes address book uses the Middle Initial field, use the following format:
<First name> <Initial> <Last name>/<Notes Organization Name>
For example: Maria R Black/FergBard.

Note  Any option that applies when Mode is CCMAIL also applies when Mode is NOTES.

Maintaining Coexistence
If you have a small Notes server to migrate, you can choose to stop using Notes and start using Microsoft Exchange Server at migration time. For larger domains, you may need to plan a phased migration where both Notes and Microsoft Exchange Server are coexisting.
During a phased migration, you use the Microsoft Exchange Connector for Lotus Notes for message transfer and directory synchronization between a Microsoft Exchange Server organization and a Lotus Notes domain. For more information about using the Microsoft Exchange Connector for Lotus Notes, see Microsoft Exchange Server Operations and Microsoft Exchange Server Concepts and Planning in the Microsoft Exchange Server 5.5 documentation.
Message Journaling
Message journaling enables you to save a copy of all messages sent or received by users of your Microsoft Exchange Server, site, or organization. You may need to save copies of all messages to comply with laws or regulations that apply to your business.
You can choose to send the collected messages to a mailbox, a public folder, or to a custom recipient. Then you need to permanently store or otherwise process the message copies.
Saving Messages
Message journaling saves copies of the following types of messages when the Microsoft Exchange Server is configured correctly:
•	Any message sent or received by a Microsoft Exchange Server user
•	Any message relayed through the Microsoft Exchange Internet Mail Service
•	Read receipts for messages
•	Messages sent to public folders
•	Delivery reports for messages sent through the Internet Mail Service
Copies of the following types of messages are not saved:
•	Messages posted to public folders
•	Delivery reports and non-delivery reports (NDRs) (except delivery reports for messages sent through the Internet Mail Service, which are saved)
•	Directory replication
•	Public folder replication
•	Link monitor
•	X.400 probe
•	Message copies being sent to the message journal
Messages are captured when they first enter a Microsoft Exchange Server that is configured for message journaling. If a message is sent within a Microsoft Exchange Server organization, the message is copied when it is sent. Another copy is not made when the message is received.
If message journaling is configured at the server level, a message is copied when it is first sent from or received by the server. If message journaling is configured at the site level, a message is copied when it is first sent or received within the site. If message journaling is configured at the organization level, the message is copied when it is first sent or received within the organization.
Enabling Message Journaling
To enable message journaling throughout a Microsoft Exchange Server site or organization, each server must be running Microsoft Exchange Server 5.5 Service Pack 1 and each server must be configured for message journaling.
You can configure message journaling at the server level, site level, or organization level. If you configure it at the site level, a message that is sent between two sites in the organization is saved twice: once at the sending site and once at the receiving site.
You enable and configure message journaling using Windows NT Server registry settings. Complete the following steps on each server. Each step is described in detail later in this document.
1.	Specify where messages are saved.
2.	Specify message journaling at the server, site, or organization level.
3.	Route all Internet Mail Service messages through the private information store.
4.	Route local messages through the message transfer agent (MTA).
Specifying Where Messages are Saved
Specify where messages are saved by adding a registry key with the distinguished name of a mailbox, public folder, or custom recipient.
	To view the distinguished name of a recipient 	
1.	Run the Microsoft Exchange Administrator program in raw mode by typing C:\Exchsrvr\Bin\Admin /r at a command prompt.
2.	Select the recipient object in the appropriate Recipients container.
3.	From the File menu, choose Raw Properties.
4.	In the Objects attributes box, select Obj-Dist-Name. The distinguished name of the object is displayed in the Edit value box.
	To specify the recipient 	
1.	Open the following registry key:
	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeMTA\Parameters
2.	Add a new string value named Journal Recipient Name.
3.	Set the value of Journal Recipient Name to the distinguished name of the mailbox, public folder, or custom recipient.
Specifying Message Journaling at the Server, Site, or Organization Level
You can specify if message journaling is done at the server level, site level, or organization level. By default, message journaling is done at the organization level.
1.	Open the following registry key:
	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeMTA\Parameters
2.	Add a new DWORD value named Per-Site Journal Required.
3.	For journaling at the server level, set the value of Per-Site Journal Required to 2. For journaling at the site level, set the value of Per-Site Journal Required to 1.
To return to organization level message journaling, set the value of Per-Site Journal Required to 0.
Routing Internet Mail Service Messages Through the Private Information Store
To be copied correctly, all Internet Mail Service messages must be routed through the private information store.
1.	Open the following registry key:
	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeIMC\Parameters
2.	Add a new DWORD value named RerouteViaStore.
3.	Set the value of RerouteViaStore to 1.
Routing Local Messages Through the MTA
To be copied correctly, local messages must be routed through the message transfer agent (MTA) instead of being delivered directly by the private information store.
1.	Open the following registry key:
	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\MSExchangeIS\ParametersSystem
2.	Add a new DWORD value named No Local Delivery.
3.	Set the value of No Local Delivery to 1.
Security
There are two primary security issues with message journaling: 
•	Unauthorized disabling of message journaling when it should be used
•	Unauthorized use of message journaling to intercept messages
In both cases, it is important to limit who can change the registry entries that control message journaling. By default, all users with Windows NT Server administrator permissions can change these registry entries.
The mailbox, public folder, or custom recipient that receives the message copies must be secured. This recipient should be hidden from the directory. If the recipient is a public folder, on the Permissions tab for the public folder, set the Roles for the default user to Contributor, and then clear all permissions except Create items.
Copies of encrypted messages are saved similar to other messages, but they are not decrypted.
Performance
Message journaling adds processing overhead to the Microsoft Exchange Server and increases network traffic. Use Windows NT Performance Monitor after enabling message journaling to ensure that your system can handle the additional load. You may need to upgrade your hardware or balance system resources.

Note  The performance enhancements in the message transfer agent (MTA) in this service pack should help balance the processing overhead of message journaling.

The mailbox, public folder, or custom recipient that receives the message copies must always be available, or message journaling will fail. Depending on message volume, you might need to set up the mailbox or public folder on a dedicated Microsoft Exchange Server computer within the site.
Additional Considerations
•	If you need to archive message tracking data with the message copies, select Enable message tracking on the General property page of the MTA Site Configuration object. Then copy the daily log files from the Exchsrvr\Tracking.log directory to your archive location.
•	Do not disable per-domain-bilateral-info if you are using message journaling. Per-domain-bilateral-info is disabled when the following registry key it set to 1.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\MSExchangeMTA\Parameters\Do not generate Bilateral Info
For more information, see Microsoft Knowledge Base article Q157358. Knowledge Base articles are available from the Microsoft support Web site at http://www.microsoft.com/support.
•	Message journaling can only capture messages that pass through the Microsoft Exchange Server MTA. If a user connects to an external mail server using a client that submits e-mail through SMTP (POP3 and IMAP4 clients) without passing through Microsoft Exchange Server, the messages will not be captured. Likewise, messages sent using other mail systems such as PC Mail that do not pass through a Microsoft Exchange Server cannot be captured, even if the other mail system has a connector to a Microsoft Exchange Server computer.
Preventing Unsolicited Commercial E-mail
Unsolicited commercial e-mail (UCE) sent to recipients across the Internet is a growing problem for Internet mail server administrators. UCE can consist of special offers, commentaries, or any message a sender wants to convey to as many recipients as possible over the Internet. Often, senders relay messages through large, well-known Internet servers to avoid burdening their server with performing the majority of the delivery work. 
For example, your server receives one UCE message addressed to 10,000 recipients on 5,000 different Internet mail servers. Without configuring any UCE prevention, your server will host the message, and attempt to deliver it to each of those 5,000 servers. This increased load can significantly hinder your server's performance and prevent it from efficiently delivering messages to recipients on your server. 
You can prevent your Microsoft Exchange Server computer from relaying messages to recipients outside your organization by configuring the Internet Mail Service not to accept messages addressed to outside recipients. Use this for messages sent through Simple Mail Transfer Protocol (SMTP) hosts. Specified messages received by the Internet Mail Service that are addressed to recipients outside the organization are returned to the sender as non-deliverable.
To configure message relaying, run the Internet Mail Wizard and install the Internet Mail Service. After the Internet Mail Service is installed, you can configure relay restrictions and custom message filtering.
	To install the Internet Mail Service 	
1.	From the Connections container in the Administrator window, choose File, choose New Other, and then choose Internet Mail Service. 
2.	Restart the Internet Mail Service.
You can now customize the Internet Mail Service using various property pages. 
	To access the Internet Mail Service property pages 	
1.	In the Administrator window, choose a site, and then choose Connections.
2.	Double-click the Internet Mail Service object you want to customize.
Configuring Relay Restrictions
You can prevent users from using your site to host and relay messages to recipients that are not in your organization. Messages that were intended to be relayed are instead returned to the sender as non-deliverable. 
For example, if you want to only allow messages sent from the domain xxx.com to be relayed through your site, you can add that domain name to the Specify the hosts and clients that can route mail when the following conditions are met list. The Internet Mail Service will allow mail sent from the xxx.com domain to be relayed through your site, but will not allow mail sent from any other domain to be relayed.
	To restrict message relaying 	
1.	Select the Routing tab.
2.	Choose Reroute incoming SMTP mail (required for POP3/IMAP4 support), and then choose Routing Restrictions.
3.	In Specify the hosts and clients that can route mail when the following conditions are met, choose your hosting option, and then choose Add to specify restricted IP addresses. 

Option	Description	
	
Hosts and clients that successfully authenticate	Messages sent from hosts and clients with valid logon information are relayed.	
Hosts and clients with these IP addresses	Messages sent from the specified IP addresses are relayed.	
Hosts and clients with these internal addresses	Messages sent by hosts and clients that connect to the specified IP address on the Microsoft Exchange Server computer are relayed.
Allows multi-homed servers to restrict relaying based on the IP address to which the client connects. If you choose this option, you must disable IP forwarding on the Networking property pages in Control Panel.	

	To disable message relaying 	
1.	Select the Routing tab.
2.	Choose Reroute incoming SMTP mail (required for POP3/IMAP4 support), and then choose Routing Restrictions.
3.	Under Specify the hosts and clients that can never relay mail, choose Add to specify IP addresses. 

Configuring Custom Message Filtering
You can prevent messages that contain certain domains and users in the From field from being delivered to recipients in your site. Messages from the specified domains and users can be deleted or stored in the Turf directory. Users who send these messages will not receive non-delivery notifications.
For example, if you don't want to accept messages from the domain xxx.com, you can add that domain name to the Prevent these domains and users list. The Internet Mail Service will filter mail that contains the xxx.com domain name in the From field as specified. 
	To configure custom message filtering 	
1.	Select the Connections tab.
2.	In Accept Connections, choose Message Filtering.
3.	In Prevent these domains and users, choose Add.
4.	Type the name of the domain and user you want to prevent from delivering messages to your site. 
5.	To save and automatically move messages from the selected sender to the Turf directory, clear the Delete messages instead of moving to the Turf directory check box. 
Clean Mailbox
You can use the Microsoft Exchange Server clean mailbox feature to delete messages from user mailboxes. Cleaning mailboxes increases available disk space in the private information store. 
The clean mailbox feature has been enhanced in this service pack. You can now delete specific types of messages. You can also choose to delete messages based on either the last modified date or the received date.
	To use clean mailbox 	
1.	In the Microsoft Exchange Administrator window, select a mailbox.
2.	From the Tools menu, choose Clean Mailbox.
Free Space Message
Microsoft Exchange Server now writes event messages that provide an estimate of the free space in the public and private information stores. The free space is the amount of disk storage that would be returned to the file system if you ran an offline defragmentation of the information store.
The free space reported is the amount of storage in completely empty pages in the information store. Because there may also be partially empty pages, the reported value is a conservative estimate. Free space in the information store is not usually a problem and is managed automatically by the online defragmentation process. The free space message is generated during this online defragmentation.
The free space message is written to the application event log with the Event ID 1221. The Source value in the message indicates if the message is for the public information store or the private information store.
Microsoft Exchange Server Routing Objects
This service pack includes a set of components that build on the Microsoft Exchange Server 5.5 event and scripting architecture to simplify the creation of routing and approval applications. The components include a Routing Engine, Routing Objects, documentation, and sample applications.
For more information, see the Agents.hlp file located in the Eng\Server\Support\Collab\Sampler\Scripts directory of the SP1 compact disc.
Using the Cirel X.25 Card with Microsoft Exchange Server
In Microsoft Exchange Server 5.5 Service Pack 1, you can use the Cirel X.25 card with Winsock for connectivity between sites.
To install the Cirel X.25 card and configure it for use with Microsoft Exchange Server, you must complete the following steps:
•	Install the Cirel FPX X.25 card in your computer using the installation instructions provided by Cirel.
•	Use the Cirel configuration application provided with the card to configure the card for use with Microsoft Exchange Server.
•	Use the Microsoft Exchange Administrator program to install and configure the X.25 message transfer agent (MTA) transport stack.

Configuring the Cirel X.25 Card for Use with Microsoft Exchange Server
Use the software on the Cirel FPX installation compact disc to install the Cirel FPX Communication Manager. Use the FPX Communication Manager to configure and use your Cirel X.25 card. For more information, see the documentation located on the Cirel FPX installation compact disc. 
To optimize the configuration of the Cirel X.25 card for use with Microsoft Exchange Server, you can complete the following steps.

Important  Before you begin configuring the Cirel X.25 card, you must install Microsoft Windows NT version 4.0 Service Pack 3 or later and Microsoft Exchange Server 5.5 Service Pack 1.

To configure the card, you must complete steps in both the FPX Communication Manager and the Microsoft Exchange Administrator program as described in the following sections.
FPX Communication Manager
1.	The FPX Communication Manager will automatically detect a new PCI card. If you are using an ISA card, add the card to the Adapters container. Select the Adapters container in the left pane of the Communication Manager window. From the Edit menu, choose New Object. 
2.	In the left pane of the Communication Manager window, choose the FPX01 adapter.
3.	In the Plugs section of the right pane, select the junction type for A plug (V11/V28/V35). 
4.	Choose the appropriate parameters for MAC, LAP, and PLP. Select each layer in the left pane, and choose the parameters in the right pane.
5.	Select the FPX01 adapter container. 
6.	From the Commands menu, choose Immediate Loading. 
7.	When you are prompted to save the current configuration, choose Yes. The adapter state in the right pane should be green.
8.	Choose the junction type in the right pane (V11/V28/V35).
9.	Check the connection states to verify that all the links are green. If so, the adapter is ready. Red connection states indicate a link problem. Press F5 to refresh the connection states.
10.	Close the FPX Communication Manager.
11.	Insert the FPX Connector Exchange diskette into your computer and run Setup (Fpxsock.exe) with the -d command line option. 
12.	In the FPX Connector Exchange Manager, choose the Edit Link property page, and then choose New Link ID.
13.	In the FPX Name box, type the local FPX name (FPX01). 
14.	In the LinkId box, type the local LinkId, for example, 1.
15.	If you are using a multi-link adapter (Cirel FPX/S), type the switching prefix in the Prefix box; a single-link adapter (Cirel FPX/B) has no prefix. Choose OK.
16.	Close the FPX Connector Exchange Manager.

Microsoft Exchange Administrator Program
1.	Start the Microsoft Exchange Administrator program.
2.	From the File menu, choose New Other, and then choose MTA Transport Stack.
3.	In the Server box, select the name of the Microsoft Exchange Server that has the Cirel X.25 card installed. In the Type box, select X.25 MTA Transport Stack, and then choose OK.
4.	Select the Servers container, and then choose the Microsoft Exchange Server that has the Cirel X.25 card installed.
5.	Double-click the X.25 MTA transport stack. Select Winsock X.25, and then set the appropriate remote and local addressing information.
Collaboration Data Objects (CDO) 1.21
The CDO libraries now support both server and client-based applications, providing developers with a common set of programming interfaces. In addition, CDO now provides a stand-alone setup, allowing developers to install CDO on servers running Microsoft Internet Information Server that do not have Microsoft Exchange Server installed.
For more information, see the Cdo.hlp file located in the Eng\Server\Setup\I386\Bin directory on the SP1 compact disc. The document is available only in English for all language versions of SP1.
Using Connectors on Computers with Alpha AXP Processors
All of the connectors in Microsoft Exchange Server 5.5 Service Pack 1 have been updated to run on computers with Intel or Alpha AXP processors running Windows NT. To install the connectors on an Alpha AXP system, run Setup.exe in the \Eng\Exchconn\Setup\Alpha directory located on the Service Pack 1 compact disc.
Message Transfer Agent Enhancements
This service pack includes enhancements to the message transfer agent (MTA) that give you more control over message priority, limits, and timeouts. It also includes functionality that allows you to filter incoming X.400 mail by originator name.
MTA Queue Priority Timeouts
You can specify different timeouts for messages in the MTA queue based on the message priority. If the MTA cannot deliver the message within the specified time period, it returns a non-delivery report (NDR) to the sender. You can specify different timeout values for urgent (high importance), normal, and non-urgent (low importance) messages.
You specify timeouts by setting registry keys on each Microsoft Exchange Server computer you want to use timeouts on. Create the following DWORD registry keys, and then modify them to set the value of the key to the timeout in minutes.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeMTA\Parameters\Message timeout (urgent), minutes
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeMTA\Parameters\Message timeout (normal), minutes
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeMTA\Parameters\Message timeout (non-urgent), minutes
MTA Queue Threshold Limits
You can specify the minimum queue size required to open a link to another system. The MTA queues messages until the threshold is reached, and then sends all messages in the queue. You may want to use this feature if establishing a connection is costly compared to sending data over the link.
You can specify the threshold by the number of messages in the queue, total queue size in kilobytes, or both. If you specify both thresholds, all messages in the queue are sent when either threshold is reached. You can also specify to send urgent (high importance) messages immediately.

Note  This does not override the schedule specified on the Schedule property page of a connector.

You specify thresholds by setting a registry key for each link on each Microsoft Exchange Server computer you want to use thresholds on. Create the following DWORD registry keys and then modify them. Substitute the display name of the connector in upper case letters for <CONNECTOR NAME>.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA\Parameters\<CONNECTOR NAME >\Content Length Threshold (KBytes)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA\Parameters\<CONNECTOR NAME >\Queue Length Threshold
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA\Parameters\<CONNECTOR NAME >\Urgent Overrides Thresholds
To allow urgent messages to be sent immediately, set the value of the Urgent Overrides Thresholds key to 1.
Per-Connector Message Type and Priority Limiting
You can specify which messages can use a particular connector based on message type or priority. For each connector, you can prohibit system, non-system, urgent (high importance), normal, or non-urgent (low importance) messages. You can also specify that urgent messages override the schedule for a connector and are sent immediately; other messages remain in the queue until the next scheduled time.
The per-connector message limits are set on each connector object by editing the raw properties of the connector. The limits are set using the Heuristics attribute. The value of the Heuristics attribute is the decimal integer sum of the following values for each limit you want to set.
Limit	Decimal Value	
Prohibit system messages	4096	
Prohibit non-system messages	8192	
Prohibit urgent (high importance) messages	16384	
Prohibit normal messages	32768	
Prohibit non-urgent (low importance) messages	65536	
Override schedule for urgent messages	131072	

	To set the per-connector limits 	
1.	Run the Microsoft Exchange Administrator program in raw mode by typing C:\Exchsrvr\Bin\Admin /r at a command prompt.
2.	In the Administrator window, choose the site where the connector is installed, and then choose Connections.
3.	Select the connector.
4.	From the File menu, choose Raw Properties.
5.	In the List attributes of type box, select All.
6.	In the Objects attributes box, select Heuristics.
7.	Type the sum of the values for the limits you want to set in the Edit value box, and then choose Set.
Filtering Incoming X.400 Mail By Originator Name
You can reject incoming X.400 mail based on the contents of the originator name in the P1 message header. You can specify which message to reject by listing particular originator name components. You can return a non-delivery receipt (NDR) to the originator of the rejected message. An event is logged for each rejected message.
For example, you can reject all messages from specified countries by filtering on the country component of the originator name, or you can reject all messages from a particular company by filtering on the organization component.
Message filtering is defined for each connector using a registry key on the Microsoft Exchange Server computer where the connector is installed. A second registry key specifies if an NDR is returned for rejected messages. 
	To reject messages by originator name 	
1.	Create the following REG_MULTI_SZ registry key and substitute the display name of the connector in all upper case letters for <CONNECTOR NAME>.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services MSExchangeMTA\Parameters\<CONNECTOR NAME>\Bar P1 Originator
2.	Set the value of the key to the originator name components of messages you want to reject. You can use any of the X.400 name components except ou2, ou3, and ou4. To specify multiple originators, add separate values within the REG_MULTI_SZ key. For example, to reject all messages from an originator with an organization name of MSFT, set the registry key value to o=MSFT. To reject all messages from originators in the United States and Great Britain, set the registry key to two values, c=US and c=GB.
3.	To return an NDR to the originator of rejected messages, create the following DWORD registry key, substitute the display name of the connector in all upper case letters for <CONNECTOR NAME>, and set its value to 1.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services MSExchangeMTA\Parameters\<CONNECTOR NAME>\NDR to barred originator
Replicating Large Distribution Lists
You can replicate large distribution lists between Microsoft Exchange Server computers. If you have had problems replicating distribution lists, you can increase both the time available for the replication to run and the number of threads available to the replication process. Both of these settings apply to intrasite replication and will increase the resources available for intrasite replication.
For example, if you have a 17,000 member distribution list that takes more than the default of 35 minutes to replicate, change the available time to 480 minutes, and then change the number of threads from the default of 50 to 200.
To increase the time available for replication to run, create the following DWORD registry key.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ MSExchangeDS\Parameters\Replication async thread check (minutes)
Start by setting the value to 480 minutes. You may need to adjust this value for best results, depending on the size of the distribution lists, connection speed between computers, processor speed, available memory, and other factors.
To increase the number of threads available to the replication process, change the value of the following registry key.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ MSExchangeDS\Parameters\Max Threads (EXDS+NSP+DRA)
Start by setting the value to decimal 200. You may need to adjust this value for best results.
Known Issues
The following are known issues in Microsoft Exchange Server 5.5:
•	User Interface Changes
•	Microsoft Exchange Connector for Lotus Notes
•	Microsoft SNA Server
•	Clustering Services
•	Key Management Server
•	Connector for IBM OfficeVision/VM (PROFS) - Sending Attachments Larger Than 3KB
•	Microsoft Exchange Chat Service
•	Running Setup in Recovery Mode with Connectors Installed
•	Microsoft Outlook
•	Installing and Updating Connectors on Computers with Intel Processors
•	Updated Migration Wizard Available for cc:Mail DB8 Migration
•	Microsoft Exchange Server Routing Objects
•	Collaboration Data Objects (CDO) 1.21 Cannot Run with Microsoft Event Service Visual Studio Extensions
User Interface Changes
The Microsoft Exchange Server user interface has been updated for this service pack. The dialog boxes and other user interface elements illustrated in the Microsoft Exchange 5.5 documentation may not match what you see in the product. For the most current information on the user interface, choose Help.
Microsoft Exchange Connector for Lotus Notes
•	Scheduling Database Maintenance
•	Generating Proxy Addresses
•	Sending Messages Containing Rich Text Formatting
•	Specifying the Notes Letterhead
•	Installing the Connector for Lotus Notes on a DEC Alpha Computer
•	Versions of Lotus Notes That Can be Used with the Microsoft Exchange Connector for Lotus Notes
•	Japanese DBCS Characters Not Converted
•	Changing the Directory Synchronization Import Container is Not Detected by the Connector
•	Documentation Error
•	Migrating from the Japanese Version of Lotus Notes and OLE Document Link Conversion
•	Installing the Connector for Lotus Notes with the Japanese Version of Lotus Notes
Scheduling Database Maintenance
You can enter a time for daily database maintenance in the Run Notes database maintenance box of the Advanced property page of the Microsoft Exchange Connector for Lotus Notes. This feature does not work correctly. To schedule a time for daily database maintenance, edit the MAINTSCHED item in the [LME-NOTES] section of the Exchconn.ini file. Enter the time based on a 24-hour clock. For example, to set the daily maintenance to run at 9:00 P.M., use the syntax MAINTSCHED=21:00.
Generating Proxy Addresses
The Microsoft Exchange Server 5.5 documentation for the Microsoft Exchange Connector for Lotus Notes states that you can use numeric wildcards to generate custom e-mail addresses. This feature does not work as described. You cannot use numeric wildcards to generate proxy addresses for use with the Connector for Lotus Notes.
Sending Messages Containing Rich Text Formatting
When messages containing rich text formatting, such as bold, font size, and color, are sent between Lotus Notes and Microsoft Exchange Server using the Connector for Lotus Notes, the text is converted to the appropriate format for the recipient. Because of differences in the client programs, not all attributes are converted correctly. The following table shows how attributes are converted in messages.
Attribute	Outlook to Notes	Microsoft WordMail to Notes	Outlook HTML to Notes	Notes to Outlook or WordMail	
					
Size	Converted 	Converted 	Converted 	Converted 	
Color	Converted 	Converted 	Converted 	Converted 	
Bold	Converted 	Converted 	Converted 	Converted 	
Underline	Converted 	Converted 	Converted 	Converted 	
Italic	Converted 	Converted 	Converted 	Converted 	
Strikethrough	Converted 	Converted 	Converted 	Converted 	
Paragraph formatting	Converted 	Converted 	Ignored	Converted except justify, which is ignored by Outlook	
Line spacing	Not applicable	Not applicable	Not applicable	Converted	
Bullets	Converted 	Not applicable	Not applicable	Some are not converted	
Indents	Some complex formatting is lost 	Not applicable	Not applicable	Some are not converted	
Tables	Not applicable	Converted 	Converted 	Converted correctly in WordMail, not displayed correctly in Outlook	
Embedded OLE objects including graphics	Converted, can be edited	Converted, can be edited	Converted, can be edited	Converted, can be edited	
Font name 	Varies, may substitute Symbol font if recipient does not have original font	Does not map, usually Times Roman	Does not map, usually Times Roman	Converted 	
Double strikethrough	Not applicable	Ignored	Ignored	Ignored	
Superscript	Not applicable	Ignored	Ignored	Ignored	
Subscript	Not applicable	Ignored	Ignored	Ignored	
Shadow	Not applicable	Ignored	Ignored	Ignored	
Outline	Not applicable	Converted to italic	Converted to italic	Converted to italic	
Emboss	Not applicable	Ignored	Ignored	Ignored	
Engrave	Not applicable	Ignored	Ignored	Ignored	
Small caps	Not applicable	Ignored	Ignored	Ignored	
All caps	Not applicable	Ignored	Ignored	Ignored	
Drop caps	Not applicable	Ignored	Ignored	Ignored	
Hidden	Not applicable	Ignored, text is visible	Ignored, text is visible	Ignored, text is visible	
Underline other than single	Not applicable	Ignored	Ignored	Ignored	
Bitmaps not embedded as OLE objects	Not applicable	Not converted, may appear as garbled text	Displayed as unnamed, blank icons, may need to be renamed before viewing	Converted to monochrome	
Computed text	Not applicable	Not applicable	Not applicable	Not converted	
Text or formula pop-up	Not applicable	Not applicable	Not applicable	Pop-up is not converted, hotspot text is converted	
Action hotspot	Not applicable	Not applicable	Not applicable	Action information is not converted, hotspot text is converted	
Button	Not applicable	Not applicable	Not applicable	Not converted	
Hyperlinks embedded in text	Not applicable	Not applicable	Not converted	Not applicable	
HTML buttons, fields, check boxes, drop-down boxes 	Not applicable	Not applicable	Not converted	Not applicable	
HTML frames	Not applicable	Not applicable	Not converted	Not applicable	
VB Script, JavaScript, Java applets, ActiveX controls	Not applicable	Not applicable	Not converted	Not converted	

Specifying the Notes Letterhead
The Connector for Lotus Notes enables you to specify the Notes letterhead used for messages sent from Microsoft Exchange to Lotus Notes recipients; however, the connector only recognizes letterhead names in English. The following table shows the name you must enter to use the desired letterhead. For example, to use centered and bold, type StdNotesLtr3 in the Notes letterhead box on the connector’s Advanced property page.
Letterhead	Letterhead value	
		
Plain Text	StdNotesLtr0	
Bouncy Earth	StdNotesLtr1	
Buck Rogers Mail	StdNotesLtr2	
Centered and Bold	StdNotesLtr3	
Decco	StdNotesLtr4	
Falling Spheres	StdNotesLtr5	
First Initial	StdNotesLtr6	
Frank Lloyd	StdNotesLtr7	
From The Desk	StdNotesLtr8	
Geometry	StdNotesLtr9	
Gray Gradient with Lines	StdNotesLtr13	
Green and Yellow Diamond	StdNotesLtr14	
Metal Plate	StdNotesLtr15	
Pencil and Grid	StdNotesLtr16	
Pony Express	StdNotesLtr17	
Purple Geometry	StdNotesLtr18	
Reversed Teal	StdNotesLtr20	
Slashed Lines with Globe	StdNotesLtr21	
Squiggle with Backdrop	StdNotesLtr22	
Squiggly Line	StdNotesLtr23	
Tacks	StdNotesLtr24	
Tape	StdNotesLtr25	
Teal and Yellow Lines	StdNotesLtr26	
Three Dimensional Relief	StdNotesLtr27	
Torn Paper	StdNotesLtr28	
Triangle with Dots 1	StdNotesLtr29	
Triangle with Dots 2	StdNotesLtr30	
Wild Confetti	StdNotesLtr32	
Yellow Gradient	StdNotesLtr33	
Marquee	StdNotesLtr34	
Gateway	StdNotesLtrGateway	

Installing the Connector for Lotus Notes on a DEC Alpha Computer
If you have installed the Connector for Lotus Notes on a DEC Alpha computer and selected OLE Document Links from the Convert Notes DocLinks to option on the Advanced property page of the connector, you must change the following registry entry and then restart the connector. The .dll name must be changed or an error message will occur.
Current Registry Entry
HKEY_CLASSES_ROOT\CLSID\{4BF8C361-AA44-11CE-861A-02608CDC7325}\InProcServer32] @="<c>:\notes\nolemon.dll"
Change To
[HKEY_CLASSES_ROOT\CLSID\{4BF8C361-AA44-11CE-861A-02608CDC7325}\InProcServer32] @="<c>:\notes\aolemon.dll"
Versions of Lotus Notes That Can be Used with the Microsoft Exchange Connector for Lotus Notes
The Microsoft Exchange Connector for Lotus Notes can be used with the following versions of Lotus Notes:
•	Lotus Notes mail client releases 4.5.2 through 4.6.1 on both computers with Intel and Alpha AXP processors.
•	Lotus Notes server releases 4.6.1 and earlier.

The Microsoft Exchange Connector for Lotus Notes will also correctly process mail sent from Lotus Notes Web mail clients, Internet Message Access Protocol Version 4rev1 (IMAP4) mail clients, and Post Office Protocol version 3 (POP3) mail clients connecting to servers running Lotus Domino or Lotus Notes releases 4.6.1 and earlier.
Japanese DBCS Characters Not Converted
The DBCS characters are not converted correctly when sending a message with DBCS (Japanese) characters in the subject line from a Microsoft Exchange Server user to a Lotus Notes recipient using the Japanese version of the Outlook client (HTML mode) configured to encode the forward header in English.
The Lotus Notes RTF converter strips the tags from the message because the converter does not recognize the HTML tags in the message.
Changing the Directory Synchronization Import Container is Not Detected by the Connector
When you change the Import container after directory synchronization is completed, the Microsoft Exchange Connector for Lotus Notes does not detect the change and subsequent updates are processed in the old container.
	To change the Import container for the connector	
1.	Change the Import container to the new container name in the Microsoft Exchange Server Administrator program.
2.	Delete the custom recipients for Lotus Notes users from the old container.
3.	Run an immediate full reload from Lotus Notes to Microsoft Exchange Server.

When directory synchronization is complete, custom recipients for the Lotus Notes users are re-created in the new Import container.
Documentation Error
In the online documentation for the Microsoft Exchange Connector for Lotus Notes, the “Configuring Lotus Notes Manually” chapter contains a section called "Updating the Person Document." The following important information is not included in the online documentation:
•	You must have a minimum level of permissions on the Lotus Notes Server to manually edit the Person document. You must have at least Editor Access permissions to the Name and Address Book.  
•	In the procedure, users are incorrectly instructed to select No in the Foreign directory sync allowed box. Instead, select the field and type No in the box. 
Migrating from the Japanese Version of Lotus Notes and OLE Document Link Conversion
When activating an OLE Document Link using Outlook 98 after migrating messages from a server running the Japanese version of Lotus Notes, Lotus Notes produces a server exception error. This is a known issue with Lotus Notes. To avoid the error, choose either the RTF or the URL option for document link conversion in the Microsoft Exchange Migration Wizard.
When this problem is corrected in Lotus Notes, a release note will be included in the Fix History section of the Lotus Notes Japanese version Quarterly Maintenance Release (QMR).
Installing the Connector for Lotus Notes with the Japanese Version of Lotus Notes
Installing the Japanese version of the Lotus Notes client before installing the Microsoft Exchange Connector for Lotus Notes can cause Lotus Notes to stop responding.
	To install the Connector for Lotus Notes with the Japanese version of Lotus Notes	
1.	Install the Microsoft Exchange Connector for Lotus Notes.
2.	Install Lotus Notes and any Lotus Notes Quarterly Maintenance Releases.
3.	Run the Microsoft Exchange Connectivity Configuration program Setup.exe, which is located in the Exchsrvr\Connect\Exchconn\Setup directory.
Microsoft SNA Server
•	Using Microsoft SNA Server with Microsoft Exchange Server
•	Using Microsoft SNA Server 4.0 with the Connectors for SNADS and IBM OfficeVision/VM (PROFS)
•	Using Microsoft SNA Server 4.0 on Alpha AXP Computers with the Connector for SNADS
Using Microsoft SNA Server with Microsoft Exchange Server
When running Microsoft SNA Server version 3.0 or version 3.0 with Service Pack 1 or 2 applied on Intel-based computers, a problem can occur when using dependent LUs. If SNA Server attempts to find the remote LU corresponding to the PLU name and a network ID does not exist, a match is never made and the bind will fail. For more information, see the Microsoft Knowledge Base article Q177299 at the Microsoft Product Support Services Web site (http://www.microsoft.com/support).
Using Microsoft SNA Server 4.0 with the Connector for SNADS and IBM OfficeVision/VM (PROFS)
The Microsoft Exchange Connectors for SNADS and IBM OfficeVision/VM (PROFS) can be used with Microsoft SNA Server and SNA Client version 4.0, on both computers with Intel and Alpha AXP processors. Prior to this service pack update, these connectors only supported SNA Server and SNA Client 2.11, and 3.0 Service Pack 2.
Using Microsoft SNA Server 4.0 on Alpha AXP Computers with the Connector for SNADS
On Alpha AXP computers running Microsoft SNA Server 4.0 and Microsoft Exchange Server with the Microsoft Exchange Connector for SNADS installed, the SNADS-OUT process in Process Manager can always appear in busy mode. For more information, see the Microsoft Knowledge Base article Q182064 at the Microsoft Product Support Services Web site (http://www.microsoft.com/support).
Clustering Services
•	Updating Microsoft Exchange Server in Clustered Installations
•	Installing SP1 on a Computer Running Clustering Services
Updating Microsoft Exchange Server in Clustered Installations
When you update a previous version of Microsoft Exchange Server on clustered computers, the installation program will stop the Microsoft Exchange Server services. When the update installation is finished, the installation program will restart the services. This will cause an interruption for users because they will not be able to connect during this time.
Installing SP1 on a Computer Running Clustering Services
When installing SP1 on a computer running clustering services, unexpected failovers to the secondary node in the cluster can occur. To avoid this, complete the following procedure.
	To install SP1 on a computer running clustering services	
1.	Stop the cluster service on the secondary (inactive) node.
2.	Install SP1 on the primary (active) node.
3.	Restart the cluster service on the secondary node.
4.	Install SP1 on the secondary node.

If the SP1 installation is not completed, the new SP1 files can be installed on the shared disk without upgrading the required supporting files in the Windows NT directory.
Key Management Server
•	Multiple Password Policies
•	Issuing X.509 V3 Certificates on Mail Between Sites
•	KM Server Database Validation
•	Enrollment Welcome Message
•	Using Certificate Server Hierarchies
•	Exporting Certificate Revocation Lists
•	Configuring the Internet Mail Service for Use with Signed S/MIME Mail
•	KM Server Log Files
•	Problems Enrolling Users in Advanced Security Using KM Server
•	Configuring the Microsoft Certificate Server Certificate Directory for KM Server
•	Creating Trust Between Organizations
•	Renewing Security Keys After Changing Enrollment Settings
Multiple Password Policies
With the new multiple password policies in this service pack, you can require more than one administrator password when you are changing the enrollment settings from X.509 V1 certificates to X.509 V1 and V3 certificates, or to X.509 V3 certificates only. You can also require more than one administrator password to import or untrust a certificate from another Certificate Server. You must use the version of the Microsoft Exchange Administrator program included with Microsoft Exchange Server 5.5 Service Pack 1 to change the password policies to use these new features. Older versions of the Administrator program cannot access the Multiple Password Policies property page.
Issuing X.509 V3 Certificates on Mail Between Sites
If you have installed KM server in an organization with multiple sites and are issuing X.509 V3 certificates to clients, you must first install Microsoft Exchange Server 5.5 Service Pack 1 on at least one computer in each site within your organization. X.509 V3 certificates cannot replicate across sites without an updated installation in each site. 
To enable X.509 V3 mail between sites, you must also complete the following procedure in each site.
1.	In the Administrator window, choose Configuration.
2.	Double-click DS Site Configuration, and then select the Attributes tab.
3.	In the Configure box, select Inter-site replication.
4.	In the attributes list, select the Tagged-X509-Cert box, and then choose OK.
KM Server Database Validation
This service pack includes a validator for the KM server database, which runs automatically when you update the KM server using this service pack. 
You can also use this tool to validate the KM server databases on a regular basis. To use the validator, complete the following procedure.
1.	In Control Panel, double-click Services. 
2.	Select the Microsoft Exchange Key Management Server service, and then choose Stop.
3.	At a command prompt, change the working directory to the Exchsrvr\Bin directory and type Kmserver -R. 
4.	In the Services application, select the Microsoft Exchange Key Management Server service, and choose Start.
Enrollment Welcome Message
You can use the Enrollment Welcome Message to send temporary KM server keys to clients who choose advanced security. The default message provides the procedures for using Outlook 8.03 and earlier client versions. 
If you have some users who are using later versions of the client (such as Outlook 98) and you have previously customized the Enrollment Welcome Message, update it so it is relevant to all users. Complete the following procedure to update the Enrollment Welcome Message.
1.	In the Administrator window, view the properties of the CA object.
2.	Select the Enrollment tab.
3.	Choose Edit Welcome Message.
4.	Replace the Enrollment Welcome Message by typing a custom replacement message, or by selecting Default Settings, which will replace your message with the following message.
Your advanced security temporary key is %TOKEN%. To enroll in advanced security and start generating security credentials, please do the following:
From the Tools menu in Outlook 98, choose Options, and then choose Security. Select Get a Digital ID, and then choose Set up Security for me on the Exchange Server. Choose OK and enter your temporary key.
If you are using an earlier version of Outlook, from the Tools menu, choose Options, and then choose Security. Choose Set Up Advanced Security.
Using Certificate Server Hierarchies
If you design a Certificate Server hierarchy, the certificate of the root certification authority (CA) container will have a lifetime of five years. Subordinate CA certificates will have a lifetime of one year, which will cause problems with the use of X.509 V3 certificates. 
If you design a Certificate Server hierarchy, you must first change a registry key on the root CA computer to change subordinate certificate lifetimes to five years. You must change the registry entry on the root CA computer before you set up subordinate CA certificates. Failure to do so will result in serious problems with your subordinate CA certificates.
To make this change, add the following values to the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\
Configuration\CERT_SERVER_NAME
Value	Data Type	Description	
	
ValidityPeriod	Years	Specifies the validation period; can also be set to Hours or Days.	
ValidityPeriodUnits	dword:00000005	Specifies desired number of units of time for validation period in hexadecimal format.	

Note  Do not assign end users to the root CA certificate in a Certificate Server hierarchy. End users must be assigned to subordinate CA certificates. Certificate Server considers KM server to be another end user.

For more information on Certificate Server hierarchies, download the white paper Hier3.exe from the Microsoft Web site at http://support.microsoft.com/support/downloads/Lnp279.asp.
Exporting Certificate Revocation Lists
If you want to export a Certificate Revocation List (CRL) so another organization can import it, you must do it from the Certificate Server computer. This may be a different computer than your KM server computer. Your CRL is found in the Winnt\System32\Certsrv directory of your Certificate Server computer.
Configuring the Internet Mail Service for Use with Signed S/MIME Mail 
To send signed Secure/Multipurpose Internet Mail Extension (S/MIME) mail through the Microsoft Exchange Server Internet Mail Service, you must first configure the Internet Mail Service to support signatures. 
1.	In the Administrator window, choose Connections.
2.	Double-click Internet Mail Service.
3.	On the General property page, select Clients Support S/MIME Signatures.

KM Server Log Files
KM server log files are not configured for circular logging. Each KM server log file is approximately 1MB. When a log file reaches its size limit, a new log file is created. These log files are not automatically deleted. To manually delete KM server log files, periodically complete the following procedure.
1.	In Control Panel, double-click Services. 
2.	Select the Microsoft Exchange Key Management Server service, and then choose Stop.
3.	Run the Eseutil.exe utility with the command line switch /mh kmsmdb.edb to verify the consistency of your KM server database. 
4.	If Eseutil.exe indicates that the database is inconsistent, restart the Microsoft Exchange Key Management Server service and attempt to perform a clean shutdown again using the Services application in Control Panel.
5.	Perform a backup of your database using Windows NT Backup. From the Start menu, choose Programs, choose Administrative Tools, and then choose Backup. Select the Kmsmdb.edb database, which is located in the Exchsrvr\Kmsdata directory.
6.	Delete the .log and .chk files in the Exchsrvr\Kmsdata directory.
7.	Start the Microsoft Exchange Key Management Server service using the Services application in Control Panel.
Problems Enrolling Users in Advanced Security Using KM Server
If a user consistently has problems enrolling in advanced security, check the Key Management Server event log for the following entry:
mailbox o=yourOrg, ou=yourSite, cn=recipients, cn=yourAlias has failed being enabled
If this entry appears multiple times in the log, check the event log on the Certificate Server computer for the following entry or a similar entry.
The Certificate Server could not process request 1312 due to an error: 0x8007000d. The request was for CN=yourAlias, CN=recipients, OU=yourSite, O=yourOrg. The certificate would contain an encoded length that is potentially incompatible with older enrollment software. Submit a new request using different length input data for the following field: Extensions.Array.Extension.Value[2] ObjectId=2.5.29.17 
To avoid these messages and enroll a user in advanced security, change the length of the display name or the alias of the affected mailbox. This will change the length of the encoding so the Certificate Server can issue the certificate. Another way to avoid these messages is to edit the following registry key entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Certsvc\configuration\%caname%\CertEnrollCompatible
Change the value to zero, which will disable the Certificate Server check. This may cause errors if the certificate is to be used by Microsoft Internet Explorer 3.0 or later.
Configuring the Microsoft Certificate Server Certificate Directory for KM Server
If the directory where your Microsoft Certificate Server certificates are stored cannot be read by KM server when you enable V3 certificates, the following error can occur.
The Key Management Server was not able to complete a security operation because it was not able to contact the certificate server. Make sure the certificate server is operating and that the Key Management Server can gain access to it.
The service account that KM server runs under must be granted Read access to the directory where your Certificate Server certificates are stored. This directory should  be shared to the Windows NT Everyone account as readable. If KM server is installed in one domain and your Microsoft Certificate Server computer is in another domain, KM server must be able to read the shared directory. You must set up the domain's trust relationships appropriately to ensure the folder is readable.
Creating Trust Between Organizations
When exchanging CA certificates with another organization, you should verify the fingerprint of the certificate using a different communication method than the one used to transmit the certificate. For example, you could verify the certificate fingerprint with the sender by telephone to ensure the certificate was not intercepted and modified during transmission. CA certificates are imported on the Certificate Trust List property page of the CA object.
Renewing Security Keys After Changing Enrollment Settings
If you change the settings on the Enrollment property page of the CA object to allow X.509 V3 certificates to be issued to users of advanced security, Outlook 98 users cannot automatically renew their security keys.
To fix this problem, run the Olcsp40.exe or Olcsp128.exe program included in this service pack. Olcsp40.exe is for 40-bit clients and Olcsp128.exe is for 128-bit clients. You need to run the program on each client computer that is affected by the problem.
	To run the program	
1.	Copy Olcsp40.exe or Olcsp128.exe from the Eng\Support\Update\Advsec directory of the Outlook 98 compact disc included in SP1 to a temporary directory on the client computer.
2.	Stop Outlook 98.
3.	Run the program.
You can run the Olcsp40.exe or Olcsp128.exe program on clients throughout your organization using the Outlook Deployment Kit. For more information, insert the Outlook 98 compact disc included with SP1 into the CD-ROM drive, and then choose Browse Outlook 98 Deployment Kit.
Connector for IBM OfficeVision/VM (PROFS) - Sending Attachments Larger Than 3KB
If the RSCS buffer size in the Microsoft Exchange Connector for IBM OfficeVision/VM (PROFS) is set to anything larger than 3KB, problems can occur when sending mail that has attachments greater than 3KB through the connector. For more information, see the Microsoft Knowledge Base article Q183976 at the Microsoft Product Support Services Web site (http://www.microsoft.com/support).
To eliminate this problem, set the RSCS buffer in the connector to 3KB or install an updated version of the system file Dlc.sys. For more information about the updated system file, see the Microsoft Knowledge Base article Q175321 at the Microsoft Product Support Services Web site (http://www.microsoft.com/support).
Microsoft Exchange Chat Service
For information about Microsoft Exchange Chat Service known issues, see the Chat readme file relnotes_chat.htm located in the Chat directory on the Microsoft Exchange Server 5.5 Service Pack 1 compact disc.
Running Setup in Recovery Mode with Connectors Installed
If you run Microsoft Exchange Server Setup in recovery mode  (setup /R), the following connectors are not recovered:
•	Microsoft Exchange Connector for IBM OfficeVision/VM (PROFS)
•	Microsoft Exchange Connector for Lotus Notes
•	Microsoft Exchange Connector for SNADS
You must reinstall and reconfigure these connectors.
Microsoft Outlook
•	Using the Chinese Simplified Character Set
•	Using the Outlook 98 Deployment Kit Included in This Release
•	Enabling the Server Scripting Add-In
•	Cannot Decrypt S/MIME Secure Mail Sent to Multiple Recipients
Using the Chinese Simplified Character Set
Service Pack 1 provides support for the Chinese Simplified (HZ-GB-2312) seven-bit character set. To read mail sent using this character set, use Microsoft Outlook 98 or Outlook Express 4.01 connected to Microsoft Exchange Server using the POP3 or IMAP4 protocol. Outlook 98 running in corporate mode does not display these characters correctly.
Using the Outlook 98 Deployment Kit Included in This Release
The Outlook 98 Deployment Kit enables you to create a customized installation of Outlook 98. To install the Outlook 98 Deployment Kit for the first time, insert the Outlook 98 compact disc included in this service pack into the CD-ROM drive, and then choose Install the Outlook 98 Deployment Wizard.
If you used an earlier version of the Outlook 98 Deployment Kit, you may experience the following problems:
•	An Outlook 98 installation failure may occur on computers using Spanish (Traditional) or Spanish (Mexican).
•	Outlook 98 may fail to register as the default mail client.
•	An Outlook 98 installation failure may occur on computers with an existing version of Outlook 98 installed.
•	The Reinstall All option does not work on a customized installation of Outlook 98.
•	The Silent Install option fails to find a Setup.ini file that is configured correctly.
If any of these problems occur, complete the following steps to replace the earlier version with the Outlook 98 Deployment Kit included in this service pack.
	To replace an earlier version of the Outlook 98 Deployment Kit	
1.	Uninstall the earlier version of the Outlook 98 Deployment Kit. The Odkwiz.exe file in the earlier version has a version number of 8.5.5104.7.
2.	Install the Outlook Deployment Kit included in this service pack. Insert the Outlook 98 compact disc included in this service pack into the CD-ROM drive, and then choose Install the Outlook 98 Deployment Wizard. The Odkwiz.exe file in the new version has a version number of 8.5.5104.9.
3.	Run the Outlook Deployment Kit. On the Stage 1: Select Location for Your Customized Outlook 98 Setup screen, enter the path to your customized Outlook 98 build. Complete the wizard again to build a new custom Outlook 98 build. The customized settings from the original build are preserved. You must put the new customized Outlook 98 build in the same location as the old customized Outlook 98 build.
4.	Digitally sign the files that need signatures.
After creating the new customized Outlook 98 build, users who were not able to use the Reinstall All option with the old build can now run Reinstall All and the new build will be available.

Enabling the Server Scripting Add-In
To create and modify event service scripts using Outlook 98, you must enable the server scripting add-in.
	To enable the server scripting add-in for Outlook 98 	
1.	From the Tools menu, choose Options.
2.	Select the Other tab
3.	Choose Advanced Options, and then choose Add-In Manager.
4.	Select the Server Scripting check box, and then choose OK.
Cannot Decrypt S/MIME Secure Mail Sent to Multiple Recipients
Messages sent to multiple recipients using S/MIME encryption cannot be decrypted by recipients using Outlook 98 and Outlook Express 4.01. This problem usually occurs when there are more than 15 recipients.
To fix this problem, run the Ol98qfe.exe program included in this service pack. The program replaces the file Inetcomm.dll on the computer running Outlook 98 or Outlook Express 4.01. You need to run the program on each client computer that is affected by the problem.
	To run the program	
1.	Copy Ol98qfe.exe from the Eng\Support\Update\Smime directory of the Outlook 98 compact disc included in SP1 to a temporary directory on the client computer
2.	Stop Outlook 98 and Outlook Express 4.01 before running Ol98qfe.exe.
3.	Run the program. You can run Ol98qfe.exe in quiet mode by typing Ol98qfe /Q on the command line.
Installing and Updating Connectors on Computers with Intel Processors
This service pack includes updates to the Microsoft Exchange Connector for Lotus Notes, Microsoft Exchange Connector for SNADS, and the Microsoft Exchange Connector for IBM OfficeVision/VM (PROFS).
If any of these connectors are installed on your Microsoft Exchange Server computer, they are updated when you apply the service pack. If you install one of these connectors later by running the connector Setup program from the Microsoft Exchange Server 5.5 compact disc, make sure you apply Service Pack 1 again.  
If you do not have any of these connectors installed, you can install them from the SP1 compact disc. The versions of the connectors on the SP1 compact disc already contain the SP1 updates. The Setup program is located in the Eng\Exchconn\Setup\I386 directory on the SP1 compact disc.
Updated Migration Wizard Available for cc:Mail DB8 Migration
When migrating cc:Mail DB8 post offices to Microsoft Exchange Server using the Migration Wizard, you should update the Migration Wizard .dll from the version on the Microsoft Exchange Server compact disc to a newer version. The new version provides fidelity enhancements for migrating messages and attachments from existing cc:Mail DB8 post offices. The updated Migration Wizard is available from the Microsoft Exchange Server Migration Web site (http://www.microsoft.com/exchange/migrate).
Microsoft Exchange Server Routing Objects
•	Parallel and Sequential Route Restrictions
•	Routing Cannot Detect Circular Routes
•	Signed and Encrypted Messages Are Not Supported
•	Message Flags Are Not Copied to Routed Messages
•	One Routing Agent Per Public Folder Limit
•	Using Routing Slip Approval URLs
•	Multiple Roles as Recipients in a Sequential Route
•	No Report for Items Posted to Public Folders
•	Wait Time Activities Triggered Upon Folder’s Next Timer Event
•	Error Occurs When Modifying Existing Route
Parallel and Sequential Route Restrictions
Custom recipients and distribution lists should not be used as recipients for either sequential or parallel routes. Public folders and distribution lists should not be used as recipients in parallel routes, unless they have been configured to respond to the routed message.
Routing Cannot Detect Circular Routes
It is possible to create non-terminating circular routes. The routing engine will neither prevent these routes nor detect and terminate them if they occur.
Signed and Encrypted Messages Are Not Supported
Signed and encrypted messages are not supported with this version of the Microsoft Exchange Server routing engine.
Message Flags Are Not Copied to Routed Messages
The message flags added to mail messages by Microsoft Outlook, such as follow-up indicators, are not copied to routed messages.
One Routing Agent Per Public Folder Limit
It is possible to create two routing agents in the same public folder. This can cause unexpected results. If a problem occurs, remove the second routing agent manually using the Agents tab in Outlook.
Using Routing Slip Approval URLs
Participants in a route receive routing slip e-mail messages that contain Approve/Reject URLs they can use to respond to the message. This approval feature requires an e-mail client that supports the mailto: URL feature, including the ability to specify the subject line. The following e-mail clients have been tested and support the mailto: URL feature:
•	Microsoft Outlook 97
•	Microsoft Outlook 98
•	Microsoft Outlook for Windows 3.1
•	Microsoft Outlook for Macintosh
•	Microsoft Outlook Express 4.0
•	Microsoft Outlook Web Access
•	Netscape Messenger 4.0
•	Qualcomm Eudora Pro for Windows version 3.03 or later
Microsoft Outlook clients also display voting buttons in routing slip messages. Users can either use the voting buttons or the Approve/Reject URLs.
Multiple Roles as Recipients in a Sequential Route
You can use multiple roles as recipients in a sequential route, and set the routed item to be approved automatically (with AutoApprove) upon time-out for each role. In this case, responses received from the second (and subsequent) roles do not appear on the Tracking tab of Microsoft Outlook 98.
No Report for Items Posted to Public Folders
If you post to a public folder an item to be routed, you will not receive a report on the item's completion through the route.
Wait Time Activities Triggered Upon Folder’s Next Timer Event
You can create a route that contains a specified time to wait before continuing to the next activity. In this case, the next activity does not fire at the exact expiration of the wait time. Rather, it fires upon the first timer event (set for the monitored folder) following the expiration of the wait time.
Error Occurs When Modifying Existing Route
The Routing Wizard sample application or a custom application you have written can quit unexpectedly with a 0x8000ffff error when attempting to modify an existing route. This can occur if the user does not have full Event Scripting permission and the computer hosting the Event Service is part of a multi-site topology. To fix this problem, change the default permissions on the EventConfig_<server> folder, where <server> is the name of the server hosting the Event Service.
	To change the default permissions	
1.	In the Microsoft Exchange Administrator window, choose Folders, and then choose System Folders.
2.	Choose Events Root, and then choose EventConfig_<server>.
3.	From the File menu, choose Properties.
4.	Choose Client Permissions.
5.	In the Name box, select Default.
6.	Select the Folder Visible check box, and then choose OK.
Collaboration Data Objects (CDO) 1.21 Cannot Run with Microsoft Event Service Visual Studio Extensions
The Microsoft Visual Studio event service extensions cannot be used on a computer with CDO version 1.21 installed. These extensions are contained in the Exchange.dsm file, which is installed by the Outlook 98 and Outlook 97 Setup programs.
To create and modify event service scripts on a computer with CDO version 1.21 installed, use the server scripting add-in to Outlook 98, which is installed by the Outlook 98 and Outlook 97 Setup programs.

Index

0
0x8000ffff errors, 50
A
Advanced Security in KM server, 43
Alpha AXP processors, 27, 38
B
bug fixes. See known issues
C
CA certificates, 44
cc Mail DB8, 48
CDO (Collaboration Data Objects), 26
Certificate Revocation Lists (CRL), 42
Certificate Server, 7–11, 41–42, 44
Certificate Server CA, 8–9
Certificate Server Subordinate CA, 9–10
Certificate Server Web client, 7
chain of trust, 7
Change Password feature, 3
channel transcriptions, 4
Chat Service, 4–5, 45
Check Names feature, 3
Chinese Simplified character set in Outlook, 46
circular routes with routing objects, 49
Cirel FPX Communication Manager, 25–26
Cirel X.25 cards, 25–26
clean mailbox, 24
clustering services
known issues, 38–39
Microsoft Exchange Server, 38
SP1 installation, 39
Collaboration Data Objects (CDO), 26
command-line options in Migration Wizard, 16–17
connectors for MTA, 28–29
Contacts module, 3
CRL (Certificate Revocation Lists), 42
D
database validation for KM server, 40
DBCS (Japanese) characters in Lotus Notes, 36
DEC Alpha computers, Lotus Notes on, 35
distribution lists, replicating, 30
E
e-mail
message filtering, 23–24
relay restrictions, 22–23
unsolicited commercial, 21–24
wildcards in Lotus Notes addresses, 32
encrypted messages in routing objects, 49
enhancements. See new features
enrollment settings for KM server, 44
Enrollment Welcome Message for KM server, 41
Event Service Visual Studio, 50
Exchange Chat Service, 4–5, 45
Exchange Migration Wizard. See Microsoft Exchange Migration Wizard
Exchange Move Server Wizard, 5–6
Exchange Server, 38
existing routes with routing objects, 50
F
filtering X.400 mail for MTA, 29–30
FPX Communication Manager, 25–26
free space messages, 24
H
HTML Form Converter, 5
I
IBM OfficeVision/VM (PROFS), 38, 45
Import container in Lotus Notes, 36
installing, 2, 39
Intel processors, 27, 48
Internet Mail Service, 21, 42
introduction, 1
issues. See known issues
J
Japanese (DBCS) characters in Lotus Notes, 36
Japanese version of Lotus Notes, 37
K
Key Management (KM) server
Advanced Security, 43
Certificate Revocation Lists, 42
Certificate Server, 7–11, 41–42, 44
Certificate Server CA, 8–9
Certificate Server Subordinate CA, 9–10
Certificate Server Web client, 7
database validation, 40
enrollment settings, 44
Enrollment Welcome Message, 41
Internet Mail Service, 42
known issues, 39–44
log files, 42
password policies, 40
security features, 6
security keys, 44
signed S/MIME mail, 42
trust relationships, 6, 10–11, 44
V1 and V3 certificates, 6, 11
X.509 V3 certificates, 6, 40
known issues
attachments larger than 3KB, 45
cc Mail DB8, 48
clustering services, 38–39
IBM OfficeVision/VM (PROFS), 45
Intel processors, 48
Key Management server, 39–44
list of, 31
Lotus Notes, 31–37
Microsoft Event Service Visual Studio, 50
Microsoft Exchange Chat Service, 45
Microsoft Exchange Connector for Lotus Notes, 31–37
Microsoft Exchange Server Setup, 45
Microsoft Outlook, 45–47
Microsoft SNA Server, 37–38
routing objects, 48–50
user interface changes, 31
Visual Studio, 50
L
letterheads, Lotus Notes, 34–35
log files for KM server, 42
Lotus Notes
change to, 35
command-line options, 16–17
current registry entry, 35
DBCS (Japanese) characters, 36
DEC Alpha computers, 35
Import container, 36
Japanese (DBCS) characters, 36
Japanese version, 37
letterheads, 34–35
maintenance, 32
Person document, 37
phased migration, 17
preparing for migration, 12–13
rich text format messages, 32–34
running the wizard, 15–16
starting and stopping, 17
versions, 36
what is migrated, 14–15
wildcards in e-mail addresses, 32
M
Macintosh, Microsoft Outlook for, 4
maintenance, scheduling Lotus Notes, 32
message flags in routing objects, 49
message journaling
archiving messages, 20
enabling, 18–20
external mail servers, 21
message transfer agent (MTA), 19
organization level, 19
per-domain-bilateral-info, 21
performance, 20
private information stores, 19
saving messages, 17–21
security, 20
server level, 19
site level, 19
where messages are saved, 18
message transfer agent (MTA)
connectors, 28–29
filtering X.400 mail, 29–30
message journaling, 19
priorities, 28–29
threshold limits, 27–28
timeouts, 27
X.400 mail, filtering, 29–30
Microsoft Certificate Server, 7–11, 41–42, 44
Microsoft Event Service Visual Studio, 50
Microsoft Exchange Administrator, 26
Microsoft Exchange Chat Service, 4–5, 45
Microsoft Exchange Migration Wizard
command-line options, 16–17
phased migration, 17
preparing for migration, 12–13
running the wizard, 15–16
starting and stopping, 17
what is migrated, 14–15
Microsoft Exchange Move Server Wizard, 5–6
Microsoft Exchange Server, 38
Microsoft Exchange Server Setup, 45
Microsoft Outlook
Chinese Simplified character set, 46
deployment kits, 46
known issues, 45–47
Lotus Notes Japanese version, 37
S/MIME mail, 47
server scripting add-in, 47
Microsoft Outlook 98, 4
Microsoft Outlook for Macintosh, 4
Microsoft Outlook HTML Form Converter, 5
Microsoft Outlook Web Access, 3–4
Microsoft SNA Server
Alpha AXP processors, 38
IBM OfficeVision/VM (PROFS), 38
known issues, 37–38
Microsoft Exchange Server, 38
SNADS Connector, 38
Migration Wizard. See Microsoft Exchange Migration Wizard
Move Server Wizard, 5–6
MTA (message transfer agent)
connectors, 28–29
filtering X.400 mail, 29–30
message journaling, 19
priorities, 28–29
threshold limits, 27–28
timeouts, 27
X.400 mail, filtering, 29–30
multiple password policies for KM server, 40
multiple roles with routing objects, 50
N
new features
Alpha AXP processors, 27
CDO (Collaboration Data Objects), 26
Cirel X.25 cards, 25–26
clean mailbox, 24
Collaboration Data Objects (CDO), 26
distribution lists, replicating, 30
e-mail, preventing unsolicited commercial, 21–24
free space messages, 24
Intel processors, 27
Key Management server, 6–11
list of, 2
Lotus Notes, 12–17
message journaling, 17–21
message transfer agent (MTA), 27–30
Microsoft Exchange Chat Service, 4–5
Microsoft Exchange Migration Wizard, 12–17
Microsoft Exchange Move Server Wizard, 5–6
Microsoft Outlook 98, 4
Microsoft Outlook for Macintosh, 4
Microsoft Outlook HTML Form Converter, 5
Microsoft Outlook Web Access, 3–4
MTA (message transfer agent), 27–30
preventing unsolicited commercial e-mail, 21–24
replicating distribution lists, 30
routing objects, 24
O
OfficeVision/VM (PROFS), 38, 45
Outlook
Chinese Simplified character set, 46
deployment kits, 46
known issues, 45–47
Lotus Notes Japanese version, 37
S/MIME mail, 47
server scripting add-in, 47
Outlook 98, 4
Outlook for Macintosh, 4
Outlook HTML Form Converter, 5
Outlook Web Access, 3–4
P
password policies for KM server, 40
persistent mapping, 7
Person document in Lotus Notes, 37
printing this document, 2
priorities for MTA, 28–29
profanity filters, 4
public folders with routing objects, 49, 50
Q
Quick Fix Engineering (QFE) patches, 1
R
replicating distribution lists, 30
restrictions for routing objects, 48
rich text format messages in Lotus Notes, 32–34
routing objects
circular routes, 49
encrypted messages, 49
existing routes, 50
known issues, 48–50
message flags, 49
multiple roles, 50
new features, 24
public folders, 49, 50
route restrictions, 48
routing slips, 49
signed messages, 49
timer events, 50
S
S/MIME mail in Outlook, 47
security features of KM server, 6
security keys in KM server, 44
server moves, 5–6
server scripting add-in in Outlook, 47
signed messages in routing objects, 49
SNA Server
Alpha AXP processors, 38
Exchange Server, 38
IBM OfficeVision/VM (PROFS), 38
known issues, 37–38
SNADS Connector, 38
SNADS-OUT process, 38
T
threshold limits for MTA, 27–28
timeouts for message transfer agent (MTA), 27
timer events with routing objects, 50
trademarks, 1
trust relationships for KM server, 6, 10–11, 44
U
unsolicited commercial e-mail (UCE), 21–24
Update program, 2
user interface changes, 31
V
V1 certificates, 11
V3 certificates, 6, 11
versions of Lotus Notes, 36
Visual Studio, 50
W
web sites
Alpha AXP processors, 38
Certificate Server, 41–42
IBM OfficeVision/VM (PROFS), 45
migration, 48
Move Server Wizard, 5
Quick Fix Engineering (QFE) patches, 1
SNA Server, 38
what's new. See new features
wildcards in Lotus Notes e-mail addresses, 32
X
X.400 mail for MTA, 29–30
X.509 V3 certificates, 6, 40