Today the Exchange CXP team released the following update rollups to the Download Center. All three releases cover Security Bulletin MS12-080. Because this is a security release, the updates will also be available on Microsoft Update.
Update Rollup 8 for Exchange Server 2010 Service Pack 1
Update Rollup 9 for Exchange Server 2007 Service Pack 3
Download: Update Rollup 8 for Exchange Server 2010 Service Pack 1
Download: Update Rollup 9 for Exchange Server 2007 Service Pack 3
The Exchange Team re-released the following Rollup Updates. These updates address an issue in which digital signatures on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655.
The re-released Exchange 2010 SP2 RU4 includes the following additional fix:
2756987 Only one result is returned after you click “view all results” in Outlook 2010 or in Outlook 2013 in an Exchange Server 2010 environment
578:0x000004DC:0x0000001D Send-As permission with Outlook 2010 Exchange 2007
Error:
myaddress@mydomain.com
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required permission.
Diagnostic information for administrators:
Generating server:
#MSEXCH:MSExchangeIS:/DC=com/DC=mydomain:SERVERNAME[578:0x000004DC:0x0000001D] #SMTP
Solution:
1.Close Outlook
2.Delete the offline address book folders in
Windows 7: C:\Users\username\AppData\Local\Microsoft\Outlook\Offline Address Books
Windows XP: C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Outlook\Offline Address Books
3.Open Outlook and let it download a new copy of the offline address book.
3.1 Send/Receive Tab
3.2. Send/Reveive Groups
3.3 Download Address Book
3.4 Choose Full Details and \Global Address List
The Exchange CXP team released Update Rollup 7 for Exchange Server 2007 SP3
This update contains a number of customer-reported and internally found issues since the release of SP3 RU6. See KB2655203: Description of Update Rollup 7 for Exchange Server 2007 Service Pack 3 for more details.
Note: Some of the following KB articles may not be available at the time of publishing this post.
The most important fixes:
Note that this fix will resolve the CAS to CAS OWA proxying incompatibility with Exchange 2010 SP2 RU1 as discussed here.
Support lifecycle statement: This is the final release under standard support for Exchange 2007, as the Exchange 2007 Mainstream Support has now ended. Extended Support for Exchange 2007 SP3 will end on 4/11/2017
Note for Forefront Protection for Exchange users:
Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
The Exchange CXP team released Update Rollup 2 for Exchange Server 2010 SP2.
This update contains a number of customer-reported and internally found issues since the release of SP2 RU1. See KB2661854: Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2 for more details.
Note: Some of the following KB articles may not be available at the time of publishing this post.
The most important fixes:
Note that this fix will not cause the CAS to CAS OWA proxying incompatibility with Exchange 2007 as discussed here. No additional updates are required on Exchange 2007 for proxying to work once Exchange 2010 SP2 RU2 is installed.
Note for Forefront Protection for Exchange users:
Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
The Exchange Team did a change in CAS to CAS proxy behavior between servers running Exchange 2010 SP2 RU1 and servers running older versions of Exchange.
The SP2 RU1 package introduced a change to the user context cookie which is used in CAS-to-CAS proxying. An unfortunate side-effect is a temporary incompatibility between SP2 RU1 servers and servers running earlier versions of Exchange. The change is such that earlier versions of Exchange do not understand the newer cookie used by the SP2 RU1 server. As a result, proxying from SP2 RU1 to an earlier version of Exchange will fail with the following error:
Invalid user context cookie found in proxy response
The server might show exceptions in the event log, such as the following:
Event ID: 4999
Log Name: Application
Source: MSExchange Common
Task Category: General
Level: Error
Description: Watson report about to be sent for process id: 744, with parameters: E12, c-RTL-AMD64, 14.02.0283.003, OWA, M.E.Clients.Owa, M.E.C.O.C.ProxyUtilities.UpdateProxyUserContextIdFromResponse, M.E.C.O.Core.OwaAsyncOperationException, 413, 14.02.0283.003.
Not all customers are affected by this. But since we received a few questions about this, we wanted to let you know about the change. Many Exchange customers do not use proxying between Exchange 2010 and Exchange 2007 but rather use redirection, which is not affected by the change. However, if you are using CAS-to-CAS proxying, where an Exchange 2010 SP2 RU1 Client Access server is proxying to an earlier version of Exchange 2010 or Exchange 2007 Client Access server, then you are affected by the change.
If you are affected, it is important to note that this issue is temporary and will exist only until all of the CAS involved in the CAS-to-CAS proxy process are updated to Exchange 2010 SP2 RU1. Thus, if you are affected by this problem, simply deploy SP2 RU1 on the relevant Exchange 2010 servers and the issue no longer exists.
If you use CAS-to-CAS proxy between Exchange 2010 and Exchange 2007, we will have an interim update (IU) for Exchange 2007. Availability of the IU will be announced on this blog.
Server proxy version
Server being proxied to
Action to take
Exchange 2010 SP2 RU1 –> Any version of Exchange 2010 older than SP2 RU1
Apply Exchange 2010 SP2 RU1 to all servers involved in proxy process
Exchange 2010 SP2 –-> RU1 Exchange 2007
Hold off deployment of Exchange 2010 SP2 RU1 until you deploy the Exchange 2007 interim update (IU)
SOURCE: Exchange 2010 sp2 ru1 and cas to cas proxy incompatibility
I recently came across the following issue while performing an Exchange 2007 to Exchange 2010 migration for a company that still heavily utilised mail-enabled public folders. The client’s Exchange environment was quite old and had been previously migrated from Exchange 5.5 to 2003 and hadn’t been properly decommissioned with the original move to 2007, but that’s another story!
The issue I had was that once I moved all receive connectors to the new Exchange 2010 server, emails sent to any of the mail-enabled public folders (which were still being replicated between the 2 servers) was being rejected with the following NDR:
#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory user wasn’t found.> #SMTP#
The following error was found in Event Viewer:
Log Name: Application
Source: MSExchange Store Driver
Date: 7/09/2010 2:00:02 AM
Event ID: 1020
Task Category: MSExchangeStoreDriver
Level: Error
Keywords: Classic
User: N/A
Computer: server@domain
Description:
The store driver couldn’t deliver the public folder replication message “Folder Content (PublicFolderDatabase@domain)” because the following error occurred: The Active Directory user wasn’t found.
Given this Exchange environment was originally running versions prior to Exchange 2007, the legacy Administrative Group and all its empty subcontainers still existed. An explanation from the Microsoft Exchange Team of why this issue occurs can be found here: http://msexchangeteam.com/archive/2010/05/05/454821.aspx
The solution to this issue was to delete the empty Servers container from the legacy Administrative Group.
Using ADSIEdit.msc, connect to a domain controller and navigate to:
CN=Configuration , CN=Services, CN=Microsoft Exchange, CN=[ExchangeOrganisationName], CN=Administrative Groups, CN=[LegacyAdministrativeGroupName], CN=Servers.
Right click the Servers container and select Delete
Click Yes
Restart the Microsoft Exchange Active Directory Topology Service and the Microsoft Exchange Information Store on both the Exchange 2007 & Exchange 2010 Servers
The following is a list of current issues observed by Microsoft Support personnel for Exchange Server 2007 and Exchange Server 2010 with third-party vendor devices. If you are using Exchange Server 2007 SP3 or Exchange Server 2010 SP1 and you are experiencing an EAS issue not listed below, contact Microsoft Support Services to investigate the issue.
1. Automatic meeting processing
Issue 1.1 – Recurring meeting is removed from calendar when organizer cancels single occurrence
When you synchronize your iOS device by using Exchange ActiveSync on an Exchange Server 2007 mailbox, if the organizer cancels a single occurrence of a recurring meeting, the device may unexpectedly delete the entire recurring meeting.
Solution
There are two parts to this solution:
Install the Exchange Server 2007 Service Pack 3 (SP3) update rollup 4 (RU4). The problem details and the link to the update are documented in the following Microsoft Knowledge Base article:
2502276 A meeting request series are deleted unexpectedly from the calendar in an Exchange Server 2007 environment
Update the Apple iOS on your device to version 4.3 or later. For more details on the latest iOS version, click the following link:
Apple has documented the issue at the following web site:
http://support.apple.com/kb/ts3714
Issue 1.2 – Attendee becomes meeting organizer
When you synchronize your iOS or Android device by using Exchange ActiveSync on an Exchange Server 2007 mailbox, you may unexpectedly become the organizer for a meeting that you were invited to. This does not change the meeting for all attendees.
Solution
This can occur if you change the reminder for a single occurrence of a recurring meeting on an iOS or Android device. There may be other property changes to meeting items that may result in the same symptom.
This issue is resolved in Rollup Update 4 for Exchange Server 2007 Service Pack 3. See the KB article below for additional information.
2521063 You are incorrectly displayed as a meeting organizer after you synchronize the meeting by using your mobile device in an Exchange Server 2007 environment
Note Affected meetings must be deleted and replacement meetings must be created after the servers are patched.
Issue 1.3 – Your meeting response to the organizer appears to have been sent by someone else
When you respond to an Exchange ActiveSync (EAS) meeting invitation, the meeting originator may see someone else’s name displayed as having accepted the invitation instead of you.
Solution
Ensure the Apple iOS on your device is version 4.3 or later. For more details on the latest iOS version, click the following link:
This was fixed by Apple in iOS 3.1. For more details, visit the following Apple web site:
iPhone and iPod touch: My replies to Exchange ActiveSync invitations seem to come from someone else
http://support.apple.com/kb/TS2806
Issue 1.4 – All Day Flag is not set properly on Mobile devices when meeting is scheduled cross multiple days
Mobile device clients do not treat a meeting request as an all day event meeting request. Additionally, the All Day field is marked with "No".
Solution
This issue is resolved in Exchange 2007 Service Pack 3 Rollup 2. The problem is documented in the following articles from the Microsoft Knowledge Base online:
2201236 The "All Day" field is marked with "No" when you access a meeting request that has a duration time that is more than 24 hours by using a mobile client through ActiveSync in an Exchange Server 2007 environment
2201236 Description of Update Rollup 2 for Exchange Server 2007 Service Pack 3
Issue 1.5 – Recurring Exchange calendar events deleted
In some situations, recurring calendar events can be removed from both the iOS device and Exchange when the organizer cancels an event instance.
Solution
This issue is resolved by Apple iOS 4.3, and impacts only the 4.2.6 and earlier versions. Apple has documented the issue at the following web site:
iOS: Recurring Exchange calendar events deleted
https://support.apple.com/kb/ts3714
Issue 1.6 – Appointment exceeding 24 hours changed to multiple day All Day Event
When an appointment item’s duration exceeds 24 hours, but is not marked as an All Day Event, Exchange ActiveSync changes the item on the device to become a multi-day All Day Event. The next time that the device synchronizes with the mailbox, the change is propagated from the item on the device to the item on the Exchange Server 2010 mailbox.
Solution
Microsoft is investigating this issue. This problem can occur when using any ActiveSync device synchronizing with Exchange Server 2010.
2. Connectivity and synchronization failures
Issue 2.1 – Failures to Provision and Synchronize with Android OS
EAS policies can cause provisioning and synchronization to fail, when customized. Devices will not be provisioned if a policy is applied to the users of these devices that exceeds these limitations. This is discussed in comment 9 from the following post on Google’s Android forum:
http://code.google.com/p/android/issues/detail?id=9426
"We only support the basic (EAS 2.5) features in Froyo. So if your server requires, for example, password history or expiration, or complex characters, then it won’t be provisionable in Froyo. Our goal is to provide more policy support in future versions, but for now we support – password (PIN/alpha), minimum characters, max. fails to wipe, inactivity timeout, and remote wipe."
Solution
Updates to the Android OS version appear to resolve this problem. We encourage device users to update to the latest version available from their provider and follow vendor forums on synchronization issues. If the decision is made to allow older devices in the organization, Administrators can canvass device users, or use tools Log Parser or Export-ActiveSyncLog, to ensure that such devices are identified in the organization. Users of older devices can be grouped into a policy that can work for them.
Issue 2.2 – Unable to connect using Exchange ActiveSync due to Exchange resource consumption
There are several symptoms and remediation methods for issues with resource depletion caused by devices connecting with Exchange ActiveSync.
Solution
Administrators should review the following article in the Microsoft Knowledge Base to determine if they are experiencing the same server symptoms:
2201236 Unable to connect using Exchange ActiveSync due to Exchange resource consumption
Note This article also describes a known issue with iOS 4.0, defined by user agent 801.293 – http://support.apple.com/kb/TS3398 and is discussed in Issue 2.5, below.
Issue 2.3 – "This message has not been downloaded from the server" error when trying to open a message
You synchronize your Exchange Server mailbox with your iOS device. When you try to open a message on the iOS device, the following error may be displayed:
This message has not been downloaded from the server
Solution
You must configure the Accepted Domain using Exchange Management Shell. Use the steps in item #7 in the following post from the Exchange Team Blog:
Exchange 2010 SP1 FAQ and Known Issues
http://blogs.technet.com/b/exchange/archive/2010/09/01/3410888.aspx
This issue is being reviewed by the Microsoft Exchange product team.
Issue 2.4- You receive a synchronization failed email message when you synchronize your mobile device
When you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox, you receive a synchronization failed email message similar to the following:
From: Microsoft Exchange on Behalf of <user>
Sent: <date>
To: <other user>
Subject: Synchronization with your <ActiveSync device> failed for 1 items.
Synchronization with your <ActiveSync device> failed for 1 items.
Microsoft Exchange was unable to send the following items to your mobile device. These items have not been deleted. You should be able to access them using either Outlook or Outlook Web Access.
Item Folder: Inbox
Item Type: IPM.Schedule.Meeting.Resp.Pos
Solution
This issue is described in the following article in the Microsoft Knowledge Base:
2201236 You receive a synchronization failed email message when you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox
To resolve this issue, install the following update rollup:
2201236 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 1
Issue 2.5- Users are unable to synchronize Apple iPhone iOS 4.0 with the Exchange Server mailbox
Immediately after updating to iOS 4.0, some users may notice that Exchange ActiveSync Mail, Contacts, or Calendars do not sync, or sync very slowly. In addition, some Exchange Server administrators may notice their servers running slowly. This problem is also discussed in Issue 2.2, above.
Solution
Update the device to a later iOS version. Apple has documented the issue at the following web site:
iOS 4.0: Exchange Mail, Contacts, or Calendars may not sync after update
http://support.apple.com/kb/TS3398
Issue 2.6- ActiveSync does not work for mobile device users connecting to Exchange Server 2007 mailboxes after swapping URLs between Exchange Server 2010 and 2007
This problem occurs because the device is unable to properly redirect a user whose mailbox has been moved. The 451 redirect response to the device is not properly interpreted.
Solution
Typically, this issue is resolved by device updates to the latest operating system. Verify the following:
Verify that you have configured the LegacyURL for Exchange 2007 users. This will automatically switch the URL for the user to the appropriate target on the device. See the following blog topic:
This has been reported for several device types, to include iOS and Android operating system. If the problem is noted with the latest version of the device operating system, and the LegacyURL is correctly established and working for other devices, consult with the device vendor’s technical support.
If you are using an Apple iOS device, update the device to the iOS version 4.3.2.
Note In migrations where the mailbox moves are between different forests, a 451 is not sent. The reason for this is that the old server does not know of the new endpoint for connectivity. In such circumstances, the device must be manually reconfigured.
The Exchange team made a fix available a fix to solve the issues when using the Management Console of Exchange 2007 or 2010 in conjunction with Internet Explorer 9.
As you probably know, when using Internet Explorer 9 you can’t close the Exchange Management Console properly as it gives you the error “You must close all dialog boxes before you can close Exchange Management Console” having no dialogs open.
To solve this issue, you had to use the Task Manager to force closing the EMC process using
To properly install the hotfix:
Microsoft states it expects to incorporate this fix in a future update of Internet Explorer 9.
While releasing a fix for the IE9 issue is great after all these month, I can’t help but wonder why the fix has not been made public.
Today the Exchange Team released Rollup 5 for Exchange Server 2007 Service Pack 3 (KB2602324). This update raises Exchange 2007 version number to 8.3.213.1.
Here’s the list of changes included in this rollup:
981820 New X-headers of a message item do not appear when the message item is retrieved by IMAP4 or by POP3 in an Exchange Server 2007 SP2 environment
2292150 A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment
2411423 The Msftefd.exe process constantly consumes up to 100 percent of CPU resources when your mailbox language is set to German on an Exchange Server 2007 server
2450078 The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment
2451415 “There was a problem logging onto your mail server” error message when you use a POP3 client to access a mailbox in an Exchange Server 2007 SP3 environment
2536652 EdgeTransport.exe randomly stops responding on a Hub Transport server after you configure public folder replication in Exchange Server 2007
2536695 “Some items cannot be deleted” error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment
2536697 DBCS characters in a rule name are converted to question marks after you move a mailbox from Exchange Server 2003 to Exchange Server 2007
2537783 The EdgeTransport.exe process crashes occasionally after you install Update Rollup 2 for Exchange Server 2007 SP3
2538958 Extended Protection Warning Displayed in Exchange Management Console and Exchange Management Shell After Installing RU2 for Exchange 2007 SP3
2554575 Items accumulate in the MRM submission folder when managed folder assistant journal items in an Exchange Server 2007 environment
2556751 The EdgeTransport.exe process crashes when processing certain email messages on an Exchange Server 2007 Hub Transport server
2557304 The Store.exe process may consume excessive CPU resources and memory resources intermittently when a user opens a calendar item by using OWA in an Exchange Server 2007 SP3 environment
When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.
Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.
You can download Exchange 2007 SP3 Rollup 5 here.