Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Microsoft has released Update Rollup 1 for Exchange Server 2007 Service Pack 3. This topic discusses the following:
Issues that the update rollup fixes
How to obtain the update rollup
For More Information
Issues That the Update Rollup Fixes
Update Rollup 1 for Exchange Server 2007 Service Pack 3 fixes the issues that are discussed in the following Microsoft Knowledge Base articles.
Event ID: 4999 is logged when the EdgeTransport.exe process crashes intermittently on an Exchange Server 2007 server |
|
"554 5.6.0 STOREDRV.Deliver; Corrupt message content" NDR is generated when you send an email message to an Exchange Server 2007 user |
|
The connecting information is not logged when a user accesses a mailbox that is hosted on an Exchange Server 2007 server by using POP3 or by using IMAP4 |
|
An incorrect user is displayed as the caller in a mail message in an Exchange Server 2007 environment |
|
The Bcc information is lost when the Exchange Server 2003 journalized messages are sent to an Exchange Server 2007 mailbox |
|
Exchange Server 2007 creates incorrect Lotus Notes proxy email addresses |
|
The “legacyExchangeDN” value is shown in the “From” field of an email message instead of the Simple Display Name in an Exchange Server 2007 environment |
|
"The message could not be opened" error message when an Exchange Server 2007 user tries to open or accept a meeting request |
|
Shared calendar items are shown incorrectly in the server time zone instead of the time zone of an Exchange Server 2007 user who is accessing the shared calendar |
|
The meeting time of a meeting forward notification is incorrect on an Exchange Server 2007 server |
|
A warning message is received when you run the Test-ReplicationHealth cmdlet on an Exchange Server 2007 server |
|
You receive an error message and Event ID: 1008 is logged when you move an Exchange Server 2007 mailbox |
|
Memory leak in the Microsoft.Exchange.Monitoring.exe process when you run the Test-OwaConnectivity cmdlet or the Test-ActiveSyncConnectivity cmdlet in Exchange Management Shell on an Exchange Server 2007 server |
|
Excluding domain names from the Sender ID filter does not take effect after you run the Set-SenderIDConfig cmdlet on an Exchange Server 2007 server |
|
Fax communication sessions are dropped by an Exchange Server 2007 Unified Messaging server |
|
The PR_REPORT_TEXT property represents an incorrect read notification in Exchange Server 2007 |
|
Internet Explorer unexpectedly focuses on an Exchange Server 2007 user's OWA inbox or on an OWA calendar that is added as a web part on a SharePoint Server-based website |
|
Public folder replication is blocked unexpected in an Exchange Server 2007 environment |
|
The Microsoft Exchange Information Store service stops responding during a Volume Shadow Copy Service backup on an Exchange Server 2007 server |
|
A multibyte character is converted into a “0xFFFD” character or into unrecognized characters when you use Exchange Web Services in an Exchange Server 2007 environment |
|
You experience issues when you move messages from one mailbox folder to another mailbox folder in an Exchange Server 2007 environment |
|
A user does not receive any new email messages by using a third-party POP3 client in a mixed Exchange Server 2007 and Exchange Server 2003 environment |
|
A second dot is added to the file names of the automatic generated attachments on an Exchange Server 2007 SP2 or later version server |
|
The Get-AgentLog cmdlet operation stops and you receive an error message Exchange Server 2007 |
|
The store.exe process crashes occasionally on an active node when you move the Exchange Virtual Server from an active node to a passive node in an Exchange Server 2007 cluster environment |
|
Unexpected issues occur after you run the Set-mailbox cmdlet on an Exchange Server 2007 server to convert a shared mailbox into a regular mailbox |
|
The VSS backup operation fails occasionally and Event ID: 2034 is generated on an Exchange Server 2007 server |
|
The display name or the address of a user is displayed in garbage characters when you reply to an email message in an Exchange Server 2007 environment |
|
The inline image of an email message that is sent by using OWA with S/MIME enabled is lost for an Exchange Server 2007 user |
|
Attachments of certain email messages disappear at the client-side when you use an ExOLEDB-based application to change email messages in an Exchange Server 2007 environment |
|
It takes a long time to copy or move items from one public folder to another public folder by using Outlook in an Exchange Server 2007 environment |
|
The Msftesql.exe process continues using memory on an Exchange Server 2007 server |
|
Exchange ActiveSync crashes on an Exchange Server 2007 server causing the client synchronization to be unavailable |
|
A NDR is not generated when an email message is not delivered after you set the value for "Maximum number of recipients" of "Transport Settings" to 0 on an Exchange Server 2007 server |
|
The EdgeTransport.exe process crashes and then restarts on an Exchange Server 2007 server |
|
"Http 500" error message when you use Exchange Troubleshooting Assistant on an Exchange Server 2007 Client Access server to diagnose issues |
Pre-Installation Tasks
Forefront Security for Exchange Server
If you are using Microsoft Forefront Security for Exchange Server, you must disable Forefront Security for Exchange Server before you install Update Rollup 1 for Exchange 2007 SP3. After you install the update rollup package, you must re-enable Forefront Security for Exchange Server. To do this, follow these steps:
To disable Forefront Security for Exchange, run the fscutility /disable command.
To enable Forefront Security for Exchange, run the fscutility /enable command.
Note
If you do not disable Forefront Security for Exchange Server before you install the update rollup, the Information Store service and the Transport service do not start.
Public Folders
If you are using public folders in your Exchange 2007 organization, and if you have set the retention period on the public folder database to a value that is greater than 123 days, you must follow the steps in the following procedure before you install Update Rollup 1 for Exchange 2007 SP3.
If you are using public folders, and if you have set the retention period on the public folder database to a value that is less than or equal to 123 days, you receive a warning message. However, Exchange 2007 continues to function correctly. In this case, you can follow these steps to fix the issue.
Click Start, type adsiedit.msc in the Start Search box, and then press Enter.
In the ADSIEdit MMC, click Action, and then click Connect to.
In the Well-known naming context list, click Configuration.
Expand the following list items and subitems in this order:
CN=Configuration,DC=Contoso,DC=com
CN=Services
CN=Microsoft Exchange
CN=<OrganizationName>
CN=Administrative Groups
CN=Servers
CN=<ServerName>
CN=Information Store
CN=Second Storage Group
Note
In this list, replace <OrganizationName> and <ServerName> with the actual names of the organization and of the server.
Double-click CN=Public Folder Database.
Double-click msExchOverallAgeLimit.
Change the existing value from seconds to days by dividing the existing value by 86,400.
Note
You must repeat these steps on all public folder databases in the Exchange 2007 environment.
Important
These changes take effect after all Exchange 2007 servers in the organization that host public folder databases are upgraded to Update Rollup 1 for Exchange 2007 SP3.
If you install Update Rollup 1 for Exchange Server 2007 SP3 without performing these steps, and if you then try to access the public folder settings by using the Exchange Management console, you receive the following error message:
TimeSpan overflowed because the duration is too long |
Also, when you try to access Exchange by using Outlook Web Access, you receive the following error message:
Exception |
Update Rollup Information
Update Rollup 1 for Exchange Server 2007 SP3 was released on September 9, 2010. To obtain this update rollup from the Microsoft Download Center, see Update Rollup 1 for Exchange Server 2007 Service Pack 3 (KB2279665).
Important
Before you install an update rollup or a service pack, see How to Install the Latest Service Pack or Update Rollup for Exchange 2007 for prerequisites, installation instructions, and known issues. Before you apply an update rollup to clustered Mailbox servers, see Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
For more information about the Exchange 2007 servicing model, see Exchange 2007 Servicing.
For a list of update rollups that apply to Exchange Server 2007 SP3, see the "Update rollups for Exchange Server 2007 Service Pack 3" section in How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007.
This update rollup does not apply to Exchange Server 2007 release to manufacturing (RTM) version, Exchange 2007 Service Pack 1 (SP1) or to Exchange 2007 Service Pack 2 (SP2). The series of update rollup packages for Exchange Server 2007 SP3 is independent of the corresponding series of update rollups for Exchange Server 2007 RTM, for Exchange 2007 SP1, or for Exchange 2007 SP2.