Exchange CXP team has released Update Rollup 2 for Exchange Server 2010 RTM (KB 979611) to the download center.
Taken from: Revision: 1.0 March 4, 2010 .. Issues that the update rollup fixes
Update Rollup 2 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:
977633 Certain third-party IMAP4 clients cannot connect to Exchange Server 2003 mailboxes through an Exchange Server 2010 CAS server
In a mixed Microsoft Exchange Server 2003 and Microsoft Exchange Server 2010 environment, the Exchange Server 2003 mailboxes are accessed through an Exchange Server 2010 Client Access Server (CAS) server. In this case, users cannot access their Exchange Server 2003 mailboxes by using certain third-party IMAP4 clients. Additionally, the users may receive the following error message:
“Login to server failed”
979431 The POP3 service crashes when a user connects to a mailbox through the POP3 protocol and the user is migrated from an Exchange Server 2003 server to an Exchange Server 2010 server
Consider the following scenario:
- You migrate a mailbox from a Microsoft Exchange Server 2003 server to a Microsoft Exchange Server 2010 server.
- A user connects to this mailbox through the POP3 protocol.
In this scenario, the POP3 service on the Exchange 2010 Client Access server crashes.
979480 Users cannot receive new messages if they access mailboxes that are moved to another Exchange Server 2010 RU1 server by using IMAP4 clients
- You install Update Rollup 1 for Microsoft Exchange Server 2010 on computers that are running Exchange Server 2010.
- You move mailboxes from one server to another server within the same database availability group.
- Users access the mailboxes by using IMAP4 clients.
In this scenario, the users can view the old messages that were received before the mailboxes were moved. However, the users cannot view new messages.
979563 Exchange Server 2010 Push Notifications does not work
Microsoft Exchange Server 2010 introduces an event notification subsystem which enables client applications to subscribe to particular events. Push Notification is a notification type in which the client application provides the Client Access server a callback address to a client-side Web service. Event notifications are delivered to this Web service. However, Push Notifications does not work as expected in Exchange Server 2010. Depending on the response of the client applications, a HTTP 500 error may be logged on the Exchange Server.
979566 A 0x85010014 error is generated when linked mailbox users try to synchronize their mailboxes with mobile devices in a CAS-CAS proxying scenario in Exchange Server 2010
- Microsoft Exchange Server 2010 servers are deployed in a Client Access server to Client Access server (CAS-CAS) proxying scenario.
- Client Access server 1 locates in site 1.
- Client Access server 2 locates in site 2.
- Client Access server 1 is the Internet-facing server.
- Client Access server 1 takes the proxying role.
- There are linked mailboxes in site 2.
In this scenario, linked mailbox users receive a 0x85010014 error when the users try to synchronize their mailboxes with mobile devices
980261 This fix introduces the supports for Exchange Server 2010 page patching when a “-1022” disk I/O error is generated
Microsoft Exchange Server 2010 high availability introduces a new Extensible Storage Engine mechanism known as page patching. When a database corruption is caused by minor disk faults, Exchange Server 2010 page patching automatically repairs the corrupted database by using one of the database copies that are configured for high availability. This fix introduces the supports for page patching when the Extensible Storage Engine “-1022” disk I/O error is generated.
980262 Event ID 2156 is logged on a computer that is running Exchange Server 2010
On a computer that is running Microsoft Exchange Server 2010, the following error message is logged in the Application log:
Log Name: Application
Event ID: 2156
Task Category: Service
Description: The log copier for database ” could not send a log file to server ” because an I/O error occurred while attempting to access file ” on source server . Error: The request could not be performed because of an I/O device error.
After this error message is logged, you cannot move the database or copy a log file.