Tags


Release Notes for Exchange Server 2007 SP2

See the “Legal Notice” section later in this document for important information.
Welcome to Microsoft Exchange Server 2007 Service Pack 2 (SP2).
This document contains the following sections:
• Features that are available in Exchange 2007 SP2
• Installing Exchange 2007 SP2
• Known issues
• Legal notice
Features Available in Exchange 2007 SP2
For an overview of the new features that are available in Exchange 2007 SP2, see What’s New in Exchange Server 2007 SP2.
You can also read information about these features in the Help file that is included with Exchange 2007 SP2. To access the Exchange 2007 SP2 Help, use one of the following methods:
• Start the Setup program for Exchange 2007 SP2. In the Setup wizard, click Read about Microsoft Exchange Server 2007 SP2.
• If you have not installed Exchange 2007 SP2, access the Exchange 2007 Help file (Exchhelp.chm) from the following location on the SP2 media:

\Setup\ServerRoles\Common
Note:
The Exchange 2007 SP2-related features for Outlook Web Access are not documented in Exchange 2007 SP2 Help. Instead, the features are documented in the Outlook Web Access Help.
• Update Rollup 9 for Exchange 2007 SP1 and Exchange 2007 SP2 include a change to the “when the Subject field or the body of the message contains text patterns” condition that is used to create a transport rule. Previously, this condition matched any strings that contained the word that was specified. For example, if you defined “change” as the specific word, any strings that contained “change,” such as “Exchange” or “changes,” would be considered a match. Starting with Update Rollup 9 for Exchange 2007 SP1, this condition is matched only by the actual word, where “word” is defined as any group of letters or digits that are surrounded by non-word characters. Non-word characters are characters other than letters or digits.

Given this change, if you intend for an existing rule to match only the actual word, no action is required. Existing rules will be recompiled after Update Rollup 9 or Exchange 2007 SP2 is installed and the Microsoft Exchange Transport service is restarted. However, any rules that are based on the old behavior (pattern match) will not work after Update Rollup 9 or Exchange 2007 SP2 are installed. In this case, you must rebuild your transport rules to specify that a subject, body, from address, or header contains text patterns instead of specific words. For example, to obtain a pattern match rather than a word match, a transport rule that contains a “when the from address contains specific words” condition must be changed to “when the from address contains text patterns.”
Installing Exchange 2007 SP2
You can use the following methods to install Exchange 2007 SP2:
• Upgrade a computer that is running the original release version of Exchange 2007 to Exchange 2007 SP2.
• Upgrade a computer that is running Exchange 2007 SP1 to Exchange 2007 SP2.
• Perform a new installation of Exchange 2007 SP2.
For more information about the requirements that must be met and the procedures that you must follow to install Exchange 2007 SP2, see the following topics in the Exchange 2007 SP2 online Help:
• Exchange 2007 System Requirements
• How to Perform a Typical Installation Using Exchange Server 2007 Setup
• How to Perform a Custom Installation Using Exchange Server 2007 Setup
• How to Install Exchange 2007 in Unattended Mode
Installation Overview
Consider the following when you install Exchange 2007 SP2:
• You can install Exchange 2007 SP2 from the command line or by using the Exchange 2007 Setup wizard.
• You can use any of the following methods when you install Exchange 2007 SP2:
• Run the Setup program in upgrade mode to perform an in-place upgrade to Exchange 2007 SP2.
• If you want to run the Setup program in upgrade mode to perform an in-place upgrade from a beta version of Exchange 2007 SP2, you must first prepare Active Directory and the domains.
• You can perform a clean installation of Exchange 2007 SP2.
• You must prepare Active Directory and each domain before you perform the first installation of Exchange 2007 SP2 in an organization. This process includes updating the Active Directory schema for Exchange 2007 SP2. For information about the required permissions and steps that you must follow to complete this process, see How to Prepare Active Directory and Domains in the Exchange 2007 SP2 online Help. For a list of Active Directory schema changes that are made when you install Exchange 2007 SP2, see Active Directory Schema Changes (SP2).

After you have prepared Active Directory and each domain, you can install Exchange 2007 SP2 by using an account that has been delegated the Exchange Organization Administrator role.
• To install or upgrade the first instance of an Exchange 2007 server role in an organization, you must have been delegated the Exchange Organization Administrator role. After you install Exchange 2007 SP2 on an Exchange computer that is running the particular role, you can perform later installations or upgrades of Exchange 2007 SP2 servers. To do this, you must use an account that has the Exchange Server Administrator role.
Note:
This permissions requirement does not apply when you are installing the Edge Transport server role or the Exchange 2007 management tools. You can install and upgrade the Edge Transport server role or the management tools by using an account that has local administrator rights on the computer.
• We do not support upgrading the operating system to Windows Server 2008 and then upgrading Exchange 2007 to Exchange 2007 SP2. Also, we do not support upgrading Exchange 2007 to Exchange 2007 SP2, and then upgrading the operating system to Windows Server 2008. To deploy Exchange 2007 SP2 on a Windows Server 2008-based computer, first install Windows Server 2008 on a computer that does not have Exchange installed, and then install Exchange 2007 SP2.
• You cannot uninstall Exchange 2007 SP2. After you install Exchange 2007 SP2, the only way to remove it is to remove Exchange 2007 from the computer, and then reinstall an earlier version of Exchange 2007.
• The Exchange 2007 Setup program requires all installation source files to be stored on a local resource. This resource can be either a local hard drive or a DVD drive that is connected to the computer. During Setup, if the installation files are detected on a resource that is not local to the computer, the Setup program creates a local copy of the installation files in the temporary files folder and then removes them after Setup has completed.

A local file source is required because Exchange 2007 Setup is a Microsoft .NET Framework application. This requirement was put in place to help make sure that all installation files are from a secure and trusted resource. Sometimes, the Setup program may determine that there is insufficient disk space to continue. When determining disk space requirements, the Setup program includes a buffer space to meet data storage requirements. The amount of buffer space varies, depending on the server role or roles that are being installed. After Setup has completed, you may notice that the installation consumed less space than was requested.
• You must uninstall all Interim Updates prior to installing Exchange 2007 SP2.
• If you use any third-party programs on the computers on which you are going to install Exchange 2007 SP2, we recommend that you contact the program vendors to determine whether any updates are needed for the installation of Exchange 2007 SP2. You should also verify application and hardware compatibility with Windows Server 2008 if you are planning to install Exchange 2007 SP2 on a computer that is running Windows Server 2008.
Note:
Before you install Exchange 2007 SP2, you should stop any third-party applications that are integrated with Exchange.
• If you are using Microsoft System Center Operations Manager to monitor Exchange, we recommend that you stop the Health Service before you install Exchange 2007 SP2. If you stop this service, you won’t have to restart Exchange 2007 after installing SP2.
Note:
If Exchange 2007 SP2 is installed automatically by using Microsoft Update, a restart is required.
Upgrading to Exchange 2007 SP2
Consider the following when you upgrade to Exchange 2007 SP2:
• If you install Exchange 2007 SP2 on a computer that is running the RTM version of Exchange 2007, all server roles are upgraded to Exchange 2007 SP2. You cannot choose which server roles you want to upgrade to Exchange 2007 SP2.
• If you want to add a server role to a computer after you upgrade to Exchange 2007 SP2, you must run the Exchange 2007 SP2 Setup program. This differs from the process that you must follow with earlier versions of Microsoft Exchange. For example, when you add a component to a Microsoft Exchange Server 2003 installation, you must run the Exchange 2003 Setup program to change the installation and then reapply the service pack.
• We recommend that you upgrade your servers that are running the Mailbox server role after you upgrade your servers that are running the Client Access, Unified Messaging, Hub Transport, or Edge Transport server roles. Upgrade your computers in the following order:
1. Client Access servers
2. Unified Messaging servers
3. Hub Transport servers
4. Edge Transport servers
5. Mailbox servers
If you upgrade your servers in this order, you may avoid potential service interruptions.
• We recommend that you upgrade Client Access servers that reside in Internet-facing sites before you upgrade Client Access servers that reside in sites without Internet connectivity.
Consider the following when you upgrade servers that are running the RTM version of Exchange 2007 together with Microsoft Forefront Security for Exchange Server.
• The original release (RTM) version of Forefront Security for Exchange Server is incompatible with Exchange 2007 SP2.

You must either remove Forefront Security for Exchange Server or upgrade it to a later version before you can upgrade to Exchange 2007 SP2. The Exchange 2007 SP2 Setup program does not pass prerequisites if the computer is running the RTM version of Forefront Security for Exchange Server.
• If you are running the latest version of Forefront Security for Exchange Server, you must stop all Forefront services before you run the Exchange 2007 SP2 Setup program.
Consider the following when you install Exchange 2007 SP2 on clustered Mailbox servers:
• Use the same procedure to perform a new installation of Exchange 2007 SP2 as you do for the RTM version of Exchange 2007. For more information, see Planning for Cluster Continuous Replication and Planning for Single Copy Clusters in the Exchange 2007 online Help.
• To upgrade clustered Mailbox servers, see the information in Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or SP2 in Exchange 2007 online Help.
Consider the following when you install Exchange 2007 SP2 on a server that uses Outlook Web Access, and the regional language is set to Spanish:
• When a contact is created in Outlook Web Access, and the regional language is set to Spanish, the mapping of the name fields is as follows:
• “Nombre” in Spanish maps to “First Name” in English and to the underlying storage in Exchange.
• “Inicial” in Spanish maps to “Middle name” in English and to the underlying storage in Exchange.
• “Apellidos” in Spanish maps to “Last Name” in English and to the underlying storage in Exchange.
• This is a change from the behavior of Exchange 2007 RTM and Exchange 2007 SP1. In the earlier versions of Exchange 2007, the mapping of the name fields is as follows:
• “Nombre” in Spanish maps to “First Name” in English and to the underlying storage in Exchange.
• “Primer Apellido” in Spanish maps to “Middle name” in English and to the underlying storage in Exchange.
• “Segundo Apellido” in Spanish maps to “Last Name” in English and to the underlying storage in Exchange.
For more information about how to troubleshoot issues that may occur because of this change, see Name Mapping in Outlook Web Access Contacts is Reversed After Installing Exchange 2007 SP2 When Regional Language Is Spanish.
To upgrade a server to Exchange 2007 SP2 by using the graphical user interface
1. Run Setup.exe from the Exchange 2007 SP2 installation folder. This action starts the Exchange 2007 Setup wizard. The Setup program detects that you want to upgrade the Exchange 2007 installation to a later version of Exchange 2007.
2. Under Install, click Install Microsoft Exchange Server 2007. Follow the Setup wizard to complete the installation. Accept all default options when you follow the steps in the Setup wizard. You cannot specify which server roles you want to upgrade to Exchange 2007 SP2.
To upgrade a server to Exchange 2007 SP2 from the command line
At a command prompt, connect to the AMD64 or I386 directory of the Exchange 2007 SP2 media location, and then run Setup.com /mode:upgrade. Accept all default options when you perform the steps from the command line.
Performing a Clean Installation of Exchange 2007 SP2
You can perform a clean installation of Exchange 2007 SP2 in the same manner as you would with Exchange 2007 RTM or Exchange 2007 SP1. This is because the Exchange 2007 SP2 updates are rolled directly into the file set of the original release version of Exchange 2007. Both the high-level deployment procedures and the specific installation steps are the same. The steps that you must follow will depend on the complexity of the Exchange deployment that you want to create.
Installing Exchange 2007 SP2 on Windows Small Business Server 2008
You must update your Windows Small Business Server 2008 settings both before and after you install Exchange 2007 SP2. Before installing Exchange 2007 SP2, read the detailed information in Microsoft Knowledge Base article 973862.
Installing Exchange 2007 SP2 on Windows Essential Business Server 2008
You must update your Windows Essential Business Server 2008 settings both before and after you install Exchange 2007 SP2. Before installing Exchange 2007 SP2, read the detailed information in Microsoft Knowledge Base article 973461.
Known Issues
The following known issue exists for Exchange 2007 SP2:
• Windows Installer version 4.5 is required to install Exchange 2007 SP2. This is a requirement for upgrade scenarios as well as for new installations of Exchange 2007 SP2.

To address this issue, install the latest version of Windows Installer before you install Exchange 2007 SP2. When you install Windows Installer 4.5, you may have to restart the computer. To install this software, see Windows Installer 4.5.
Note:
You do not have to download and install Windows Installer 4.5 on a computer that is running Windows Server 2008 Service Pack 2 (SP2). Windows Server 2008 SP2 includes Windows Installer 4.5.
PowerShell Support
PowerShell Version 2 is supported on Exchange 2007 SP2 administrator workstation installations in order to allow Exchange Management Console and Exchange Management Shell “side-by-side” management of Exchange 2007 and Exchange 2010 from the same computer.
PowerShell Version 2 is supported on all Exchange 2007 SP2 server roles. PSv2 is the preferred solution for PowerShell on Windows Server 2008 servers and servers.
If you are running Exchange 2007 SP2 with PowerShell Version 1, you must prefix your e-mail address with “SMTP” to configure the primary SMTP address. For example, you must use the following command:
Set-DistributionGroup pp -EmailAddresses SMTP: primary@contoso.com
Note:
If you omit “SMTP” from the command, you will receive an error message stating that no primary SMTP address is set on the object.
To add multiple SMTP addresses, secondary addresses need to be prefixed with a lowercase “smtp”. For example, use the following command:
Set-DistributionGroup pp -EmailAddresses SMTP: primary@contoso.com ,smtp:second@contoso.com

Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or SP2
Applies to: Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007 Topic Last Modified: 2009-08-20
Upgrading a clustered mailbox server from the release to manufacturing (RTM) version of Microsoft Exchange Server 2007 to Exchange Server 2007 Service Pack 1 (SP1) or Exchange 2007 Service Pack 2 (SP2) is a relatively straightforward process. However, there are specific things that must be considered and planned for with respect to the upgrade.
Note:
It is recommended to make a complete backup of the clustered mailbox server before you upgrade to Exchange 2007 SP2 and again after you complete the upgrade to Exchange 2007 SP2. The backup should include a system state backup to capture schema changes if required.
To perform this procedure, you must be delegated Exchange Server Administrator role permissions.
We recommend that you carefully consider the following before upgrading any clustered mailbox servers to Exchange 2007 SP1 or SP2:
• Upgrading a clustered mailbox server to Windows Server 2008 Exchange 2007 SP1 and SP2 includes support for Windows Server 2008, including support for clustered mailbox servers running on Windows Server 2008. However, as a result of the significant changes introduced in Windows Server 2008 failover clusters (called server clusters in previous versions of Microsoft Windows), rolling upgrades of a failover cluster from Windows Server 2003 to Windows Server 2008 are not possible. Therefore, to upgrade a clustered mailbox server from Windows Server 2003 to Windows Server 2008, you must build a new failover cluster using Windows Server 2008 as the operating system for all nodes, and then migrate the data from the old cluster to the new cluster. You can use the Move Mailbox wizard or the Move-Mailbox cmdlet to move mailboxes from the old cluster to the new cluster, and you can use public folder replication to move any public folder data from the old cluster to the new cluster. For more information about migrating mailbox data, see Moving Mailboxes. For more information about migrating public folder data, see How to Move Public Folder Content from one Public Folder Database to Another Public Folder Database.
• Meeting cluster prerequisites Before you can upgrade to Exchange 2007 SP1 or SP2, the cluster nodes must be running Windows Server 2003 Service Pack 2 (SP2) or Windows Server 2008. For detailed instructions about how to upgrade a cluster to Windows Server 2003 SP2, see the Windows Server 2003 Service Pack 2 Installation and Deployment Guide.
• Upgrading truly passive nodes Only a passive node can be upgraded to Exchange 2007 SP1 or SP2. In Exchange 2007, a passive node is a failover cluster node that does not contain a clustered mailbox server. We recommend that this node not contain any other cluster groups, including the default cluster group and other resource groups that are not Exchange related. These groups should be manually moved to another node (for example, the active node) before upgrading the passive node to Exchange 2007 SP1 or SP2. Use the following command from the command line to move the default cluster group to another node:

Copy Code
Cluster.exe group “Cluster Group” /move:
• Performing the Exchange 2007 SP1 or SP2 upgrade procedure A clustered mailbox server can be upgraded to Exchange 2007 SP1 or SP2 only by using the command-line version of Setup (Setup.com). You can’t use the graphical user interface (GUI) version of Setup (also known as the Exchange Server 2007 Setup wizard or Setup.exe) to upgrade an existing clustered mailbox server to Exchange 2007 SP1 or SP2. The Exchange Server 2007 Setup wizard can only be used to create a new clustered mailbox server.
• Planning for downtime during the Exchange 2007 SP1 and SP2 upgrade procedure Exchange 2007 supports rolling upgrades of a clustered mailbox server from Exchange 2007 RTM to Exchange 2007 SP1 or SP2. However, these upgrades will involve some downtime for the clustered mailbox server. The amount of downtime will vary based on how long it takes each organization to perform the upgrade procedure for the entire cluster. The downtime begins in the middle of the procedure. The procedure is performed as follows:
1. Upgrade the passive nodes first. Cluster continuous replication (CCR) environments always contain a single passive node, but single copy cluster (SCC) environments can contain several passive nodes. During the upgrade of the passive nodes, the clustered mailbox server can remain online and available to clients.
2. After all passive nodes have been upgraded to Exchange 2007 SP1 or SP2, the clustered mailbox server must be taken offline and moved from the active node to an upgraded passive node in the cluster.
3. Next, the original active node (now a passive node) is upgraded to Exchange 2007 SP1 or SP2.
Note:
After the first passive node has been upgraded to Exchange 2007 SP1 or SP2, the clustered mailbox server can be upgraded, and then brought online on the upgraded passive node, thereby making it an active node.
• Removing update rollups and Exchange 2007 SP1 and SP2 When you install Exchange 2007 SP1 or SP2 on a computer that has one or more update rollups for Exchange 2007 installed, the update rollups will be automatically removed by Exchange 2007 SP1 or SP2 Setup before SP1 or SP2 is installed on the system. You do not need to manually remove any update rollups before installing Exchange 2007 SP1 or SP2.
For detailed steps about how to upgrade a clustered mailbox server to Exchange 2007 SP1 or SP2, see the following topics:
• How to Upgrade a Clustered Mailbox Server in a CCR Environment to Exchange 2007 SP1 or SP2
• How to Upgrade a Single Copy Cluster to Exchange 2007 SP1 or SP2

How to Upgrade a Single Copy Cluster to Exchange 2007 SP1 or SP2
Applies to: Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007 Topic Last Modified: 2009-05-20
This topic explains how to use Setup.com to upgrade a clustered mailbox server in a single copy cluster (SCC) environment from the release to manufacturing (RTM) version of Microsoft Exchange Server 2007 to Microsoft Exchange Server 2007 Service Pack 1 (SP1) or Exchange 2007 Service Pack 2 (SP2). Clustered mailbox servers can be upgraded using only the command-line version of Setup. You can’t use the graphical user interface (GUI) version of Setup (also known as the Exchange Server 2007 Setup wizard, or Setup.exe) to upgrade a clustered mailbox server.
This procedure should be used only to upgrade a clustered mailbox server in an SCC environment. For detailed steps about how to upgrade a clustered mailbox server in a cluster continuous replication (CCR) environment, see How to Upgrade a Clustered Mailbox Server in a CCR Environment to Exchange 2007 SP1 or SP2.
Before You Begin
We recommend that you make a complete backup of the clustered mailbox server prior to upgrading to Exchange 2007 SP1 or SP2 and again after successfully completing the upgrade to Exchange 2007 SP1 or SP2.
To perform these procedures, the account you use must be delegated the following:
• Membership in the Exchange Server Administrator role
• Local administrator permissions on all nodes in the cluster
For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.
Note:
Performing this procedure results in a brief outage during the upgrade process. Exchange Setup should be run only on the passive nodes in the cluster. All nodes need to be upgraded to Exchange 2007 SP1 or SP2 to be supported, but you must upgrade the nodes one at a time. After all nodes have been upgraded, the clustered mailbox server is upgraded, and then brought online.
The following procedure performs an upgrade of a two-node cluster. If your SCC has more than two nodes, Steps 12-15 will be repeated multiple times. In the following procedure, the designations for the active and passive nodes change. Therefore, for ease of reference in the following procedure, the original active node is NodeA and the original passive node is NodeB.
Procedure
To use Setup.com to upgrade a clustered mailbox server in an SCC environment to Exchange 2007 SP1 or SP2
1. Prepare NodeB to be upgraded by moving all cluster resource groups to NodeA. The clustered mailbox server can be left in an online (running) state during the first part of this procedure; however, during this procedure it will be taken offline and moved between nodes in the cluster. Perform Steps 2–11 on NodeB.
2. Stop any services that have open handles to performance counters. Known services that should be stopped include Performance Logs and Alerts and any Microsoft Operations Manager agents.
3. Stop, and then restart the Remote Registry service.
4. Open a Command Prompt window, and then navigate to the Exchange 2007 SP1 or SP2 installation files.
5. Run the following command:

Copy Code
Setup /m:upgrade
Setup performs Exchange 2007 SP1 or SP2 upgrade prerequisite checks and, after those are complete, Setup upgrades NodeB to Exchange 2007 SP1 or SP2.
6. Restart NodeB after Setup has completed the upgrade to Exchange 2007 SP1 or SP2.
7. After the restart process is complete, log on to NodeB and open the Exchange Management Shell.
8. Use the Stop-ClusteredMailboxServer cmdlet to stop the clustered mailbox server. For example, you can use the following command to stop a clustered mailbox server named EXCLUS1:

Copy Code
Stop-ClusteredMailboxServer EXCLUS1 -StopReason “Upgrade to SP2”
9. Use the Move-ClusteredMailboxServer cmdlet to move the clustered mailbox server from NodeA to NodeB. This cmdlet must be run from NodeB. For example, you can use the following command to move a clustered mailbox server named EXCLUS1 to NodeB:

Copy Code
Move-ClusteredMailboxServer EXCLUS1 -TargetMachine NODEB -MoveComment “Upgrade to SP2”
10. In a Command Prompt window, navigate to the Exchange 2007 SP1 or SP2 installation files.
11. Run the following command to upgrade the clustered mailbox server that is now owned by NodeB:

Copy Code
Setup /upgradecms
Setup performs the clustered mailbox server prerequisite checks and, after those are complete, Setup upgrades the clustered mailbox server and brings it online.
12. On NodeA, stop any services that have open handles to performance counters. Known services that should be stopped include Performance Logs and Alerts and any Microsoft Operations Manager agents.
13. Stop, and then restart the Remote Registry service.
14. Open a Command Prompt window, and then navigate to the Exchange 2007 SP1 or SP2 installation files. Run the following command on NodeA to upgrade it to Exchange 2007 SP1 or SP2:

Copy Code
Setup /m:upgrade
Setup performs Exchange 2007 SP1 or SP2 upgrade prerequisite checks and, after those are complete, Setup upgrades NodeA to Exchange 2007 SP1 or SP2.
15. Restart NodeA after Setup has completed the upgrade to Exchange 2007 SP1or SP2.
The clustered mailbox server has now been upgraded to Exchange 2007 SP1 or SP2.
During the upgrade procedure, ownership of the clustered mailbox server changed nodes. If you want, you can move the clustered mailbox server back to the original node. You can perform the move operation by using the Move-ClusteredMailboxServer cmdlet. You can also perform the move operation by using the new Manage Clustered Mailbox Server wizard in the Exchange Management Console, which is a feature of Exchange 2007 SP1 and SP2.

Advertisements