This document lists critical issues that can potentially impede you from successfully installing or deploying Exchange 2000 Service Pack 1 (SP1) in your environment.
Information in this document, including URL and other Internet Web site references, 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. Unless otherwise noted, the example companies, organizations, products, people and events depicted herein are fictitious and no association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or 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.
Copyright 2001 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, and Outlook are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
This document contains the following sections:
About this Document
Upgrading to SP1
Migrating to SP1
Outlook Web Access
Routing and Connectors
Clustering
Instant Messaging
Security
Web Storage System
This document lists critical issues that can potentially impede you from successfully installing or deploying Exchange 2000 in your environment. The issues listed in this document do not include Exchange 2000 Conferencing Server release notes.
The account running Update.exe must have a minimum permission role of Administrative Group Administrator (the Administrator doesn't have to be a "full" administrator), and also be a Local Administrator.
An administrator with any one of the following permission levels can upgrade an Exchange deployment to SP1: Organization Administrator (Full or Regular), Administrative Group Administrator (Full or Regular), or Enterprise Administrator.
An administrator with only the following permission levels cannot upgrade an Exchange deployment to SP1: Organization Administrator (View), Administrative Group Administrator (View), Domain User, Domain Administrator.
Note If you are an Administrative Group Administrator (Regular) and a Local Machine Administrator, there are a few exceptions to the minimum required permissions:
An unattended update .ini file created on one Exchange 2000 server will successfully update any Exchange 2000 server as long as the components installed on the server match the components specified in the .ini file.
To create an unattended update file:
update /createunattend <drive>:\filename.ini
Note For example, type "update /createunattend d:\update.ini". Setup will detect the components installed on the Exchange 2000 server and select them to be updated.
To use the unattended update file:
update /unattendfile <drive>:\filename.ini
Note For example, type "update /unattendfile d:\update.ini". Setup will update the components specified in the .ini file.
Any errors are logged to the Exchange Server Setup Progress Log. Microsoft recommends that you check your logs to confirm a successful update of your server after setup has completed.
The update .ini file does not reference domain name, administrative group, routing group, Exchange 5.5 site name, server language, installation drive, or path. A mismatch of installed components to components selected for update in the .ini file will lead to a failed update. Microsoft recommends that you make sure the components installed on the Exchange 2000 server you are updating match the components selected to be updated in the .ini file.
If you uninstall Active Directory Connector (ADC) using the ADC setup Remove ALL option (from the Exchange 2000 RTM CD or from Control Panel - Add/Remove Programs), the Active Directory Connections container is removed from Active Directory. If you want to install a new Exchange 2000 server, the Installation Wizard will not find the ADC container in Active Directory and the installation will fail.
Therefore, to uninstall a previous version of ADC, or to upgrade ADC to Exchange 2000 SP1 ADC, you must use the ADC setup.exe located on the Exchange 2000 Server SP1 CD in the <CDROM drive>/ADC/i386/setup.exe directory.
If you have already removed ADC using Exchange 2000 RTM, you must run Forest Prep again to recreate the ADC container with the right Access Control Lists (ACLs). Refer to Knowledge Base article Q287172 for more details.
Outlook Web Access clients download script files from the front-end server they connect to. Exchange Server 2000 Outlook Web Client script files are not compatible with an Exchange 2000 SP1 back-end server. When you upgrade an Exchange 2000 server to Exchange 2000 SP1, you must upgrade all front-end servers to Exchange 2000 SP1 before installing Exchange 2000 SP1 on any back-end servers. The Exchange 2000 SP1 script files on a front-end server are compatible with any back-end server running Exchange 2000 or Exchange 2000 SP1.
Note If there are multiple front-end servers, you do not have to upgrade all front-end servers simultaneously. However, all front-end servers must be upgraded to Exchange 2000 SP1 before any back-end servers are upgraded.
If you have any pre-release or beta versions of Microsoft Web Storage System Forms installed on your Exchange 2000 server, use Add/Remove Programs to remove them before installing Exchange 2000 SP1. Installing Exchange 2000 SP1 will install the latest version of Web Storage System Forms.
Exchange Event Service is provided in Exchange 2000 for backward-compatibility with Exchange 5.5 event scripts. New applications written specifically for Exchange 2000 should use native Web Storage System Events instead of Exchange Event Service, as described in the Exchange 2000 Software Development Kit (SDK). To use Event Service on an Exchange 2000 server, complete the following steps regardless of whether you are upgrading an existing Exchange 5.5 server or installing a new Exchange 2000 server.
To use Exchange Event Service:
Note The local Administrators group is part of the Local Users and Groups section of the Computer Management tool and should not be confused with the Administrators group in Active Directory Users and Computers.
If you are using Active Directory Connector to replicate mailboxes between an Exchange 5.5 organization and a separate Exchange 2000 organization, you have the option to set an X.500 proxy address.
However, if you are using Migration Wizard to migrate mailboxes between an Exchange 5.5 organization and a separate Exchange 2000 organization, you should only create an X.500 address on the connection agreement to Active Directory. The connection agreement to the Exchange 5.5 organization should not be configured to create X.500 addresses. If you configure the Active Directory Connector Connection Agreement to create X.500 addresses in the Exchange 5.5 organization, after migration, creation of the Custom Recipients will fail.
Please refer to the Exchange System Manager online documentation for instructions on how to edit a Connection Agreement and to ensure that X.500 addresses are not created in your Exchange 5.5 organization.
Note Refer to the "Upgrading to SP1" section for important notes regarding upgrading Outlook Web Access to SP1 when using front-end servers.
The following new features have been added to Outlook Web Access:
It is possible to encode e-mail using a set of alternate charsets. If the following registry key is set to 0x1:
DWORD HKLM\System\CurrentControlSet\Services\MSExchangeWEB\OWA\UseAltRegionalCharset
e-mail composed with both Internet Explorer 5.01 and greater browsers and downlevel browsers will be composed using the following charsets:
If this registry key is not set, e-mail composed with Internet Explorer 5.01 and greater browsers will use UTF8, and downlevel browsers will use the following charsets:
Note If both the UseRegionalCharset registry key (specified in Knowledge Base article Q273615) and this UseAltRegionalCharset registry key are set, the UseAltRegionalCharset registry key will take precedence.
If you configure your server to retain items emptied from your deleted items folder, you can now view and recover these items and folders using Outlook Web Access.
To use this feature:
When a meeting request is downloaded from a POP3 or IMAP4 client, a URL to the meeting request is included in the message. The POP3 or IMAP4 user can click the URL to go to the Outlook Web Access meeting request and accept the appointment to have it automatically added to his or her calendar.
Note If you use this feature with POP3 clients, you must configure the POP3 client to keep a copy of the message on the server. If the POP3 client is configured to delete mail from the server after it has been downloaded to the client, clicking the URL within the meeting request will result in an HTTP 404 error indicating that the Outlook Web Access meeting request is not available.
The online documentation tells you that for each SMTP and X.400 connector, you can have only a single local bridgehead server and a single remote bridgehead server. Instead, it should say that, for each SMTP connector, you can have multiple local bridgehead servers and multiple smart hosts. But, for each X.400 connector, you can have only a single local bridgehead server and a single remote bridgehead server. This means that load balancing within the routing group can be achieved two ways with SMTP connectors: using multiple connectors, and using multiple local bridgehead servers and smart hosts (separated by commas or semicolons). For X.400 connectors, however, load balancing can be achieved only with multiple connectors. You may also want to configure multiple X.400 connectors to support different transport types, such as TCP/IP or X.25.
The Exchange online documentation does not mention that you can have multiple smart hosts configured in an SMTP connector, separated by commas or semicolons. This is useful when performing load balancing across smart hosts. In addition, it is useful for fault tolerance, so the Exchange server can fall back to the next available smart host when one does not respond.
Calendar Connector is not supported in the Japanese version of Exchange 2000 SP1.
Calendar Connector is now available in Exchange 2000 SP1, but it must be installed from a separate setup.
The Calendar Connector documentation, previously published in the Readme.rtf file, has been removed. The content has been added to the Exchange 2000 SP1 online documentation.
Calendar Connector in Exchange 2000 SP1 cannot respond to calendar queries if the foreign user's Free/Busy information is replicated on an Exchange server running version 5.5 or earlier. To support that configuration, you must use Calendar Connector for Exchange version 5.5 or earlier.
See http://www.microsoft.com/exchange for updated information on cluster configuration recommendations.
In Exchange 2000 SP1, Instant Messaging added a new client connection method. This connection method, called Polling, allows clients to connect to Exchange 2000 Instant Messaging servers even if the server cannot connect to the client or if the server is outside of a firewall. Polling ensures that a client can connect to and communicate with an Instant Messaging server. If you have an instant message or status update that you need to send to the client, you can now use this open connection to send the message.
For more information on polling and how to configure Exchange 2000 Instant Messaging for polling, please see Microsoft Knowledge Base article Q285781.
When Certificate Server issues a new Exchange Certificate on Windows 2000, the following descriptions may be incorrect depending on the language of Windows 2000 that you are using.
When creating a front-end server in a hosting environment, do not delete the First Storage Group object in Exchange System Manager. It is standard to delete the Public Folder Stores and Private Stores, but the MSExchangeIS service is dependent on the First Storage Group object existing in the directory.