Exchange 2010 SP2 Update-Rollup 4 released

Earlier today, Microsoft released Update Rollup 4 for Exchange 2010 Service Pack 2.

The update includes a new feature as well as an important update that I would like to call out:

  • Calendar & Task (items) now support Retention Tags. Before this was not the case, as tags could only be applied to mail items/folders. Although tags for Calendar/Task (items) can only be configured by an Administrator (PowerShell), they will at least prove useful for companies that (heavily) rely on the use of Retention Policies to keep their mailboxes clean. If you are already using Retention Policies or are looking to implement them, there are some caveats to look out for when installing UR4. These items have been well described by Ross Smith IV in his article. I suggest you take a look at them.
  • a fix for a vulnerability in WebReady Document viewing that was recently reported. When the vulnerability was first reported, you were advised to temporarily disable this feature using the following command:

    Get-OwaVirtualdirectory | ?{$_.OwaVersion –eq ‘Exchange2007’ –or $_.OwaVersion –eq ‘Exchange2010’} | Set-OwaVirtualdirectory –WebReadyDocumentViewingOnPublicComputersEnabled:$False –WebReadyDocumentViewingOnPrivateComputersEnabled:$False

    After installing UR, you can safely re-enable the feature by using the following command:

    Get-OwaVirtualdirectory | ?{$_.OwaVersion –eq ‘Exchange2007’ –or $_.OwaVersion –eq ‘Exchange2010’} | Set-OwaVirtualdirectory –WebReadyDocumentViewingOnPublicComputersEnabled:$True –WebReadyDocumentViewingOnPrivateComputersEnabled:$True

 

Other updates/fixes that are included are:

  • 2536846  Email messages sent to a mail-enabled public folder may be queued in a delivery queue on the Hub Transport server in an Exchange Server 2010 environment
  • 2632409  Sent item is copied to the Sent Items folder of the wrong mailbox in an Exchange Server 2010 environment when a user is granted the Send As permission
  • 2637915 “550 5.7.1” NDR when an email message is sent between tenant organizations in a multi-tenant Exchange Server 2010 environment
  • 2677727  MRM cannot process retention policies on a cloud-based archive mailbox if the primary mailbox is in an on-premises Exchange Server 2010 organization
  • 2685001  Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
  • 2686540  Journal report is not delivered to a journaling mailbox in an Exchange Server 2010 environment
  • 2689025  Performance issues when you use the light version of Outlook Web App in an Exchange Server 2010 environment
  • 2698571  Some email messages are not delivered when you set the MessageRateLimit parameter in a throttling policy in an Exchange Server 2010 environment
  • 2698899  Add-ADPermission cmdlet together with a DomainController parameter fails in an Exchange Server 2010 environment
  • 2700172  Recipient’s email address is resolved incorrectly to a contact’s email address in an Exchange Server 2010 environment
  • 2701162  User A that is granted the Full Access permission to User B’s mailbox cannot see detailed free/busy information for User B in an Exchange Server 2010 environment
  • 2701624  ItemSubject field is empty when you run the Search-MailboxAuditLog cmdlet together with the ShowDetails parameter in an Exchange Server 2010 environment
  • 2702963  The “Open Message In Conflict” button is not available in the conflict notification message in Exchange Server 2010
  • 2707242  The Exchange Information Store service stops responding on an Exchange Server 2010 server
  • 2709014  EdgeTransport.exe process crashes intermittently on an Exchange Server 2010 server
  • 2709935  EdgeTransport.exe process repeatedly crashes on an Exchange Server 2010 server
  • 2713339  Multi-Mailbox Search feature returns incorrect results when you perform a complex discovery search in an Exchange Server 2010 environment
  • 2713371  Throttling policy throttles all EWS applications in Exchange Server 2010
  • 2719894  The Microsoft Exchange RPC Client Access service consumes 100 percent of CPU resources and stops responding on an Exchange Server 2010 Client Access server
  • 2723383  Incorrect time zone in a notification when the Resource Booking Attendant declines a meeting request from a user in a different time zone in an Exchange Server 2010 environment
  • 2724188  A subject that contains colons is truncated in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2726897  Event 14035 or Event 1006 is logged when Admin sessions are exhausted in an Exchange Server 2010 environment

Please have a look at KB2706690 and MS12-058 for more information regarding the update.

The update can be downloaded from the following webpage:
http://www.microsoft.com/en-us/download/details.aspx?id=30478

Blog Exchange

You get and Autodiscover Error : Unhandled Exception "User setting ‘PreferredSite’ is not available. " after installing Exchange 2010 SP2 Update-Rollup 3

After installing Exchange 2010 SP2 Update-Rollup 3, you might see the following error pop-up in the event logs: Unhandled Exception “User setting ‘PreferredSite’ is not available. “

image

Although at first not much information was available, Greg Taylor already said on the 13th of June that the error is known and they were looking into it.

Apparently, Scott Schnoll also mentioned this in his presentation @ TechEd, stating the following:

temp
(I haven’t had the chance to view the recording, but thanks to my colleague Dave for pointing this out!)

It’s good to see that the errors (although presenting them as critical), do no harm. Unfortunately, the more mailboxes you have, the more errors you’ll have in your event log. From what I can see, there might even be an error every few seconds; therefore possibly flooding your event log.

Microsoft will make an Interim Update available. However; at time of writing no fix was available yet.

Cheers!

Michael

 

Exchange

Enhancing (Hub) Transport Resiliency by enabling Shadow Redundancy Promotion

Hi!

It’s been a while since I wrote my last article, but I’ve been quite busy with a few other things lately…

In this article, I wanted to talk to you about a feature that has been available in Exchange Server 2010 since Service Pack 1, but is often “forgotten” about: Shadow Redundancy Promotion.

Shadow Redundancy

Over the past few edition of Exchange Server, Microsoft has made significant improvements to the high availability and resiliency of the Transport service. These improvements ensured that the risk of losing messages in transit was greatly reduced.

Exchange Server 2007 first introduced the Transport Dumpster; a feature that made an Exchange 2007 Hub Transport server keep a local queue of messages that were delivered recently. In case a failover occurred, the mailbox server would automatically request messages from the “transport dumpster” to be resubmitted. Although this mechanism prevents messages from being lost during a failover, it’s only available to mailboxes in a cluster. More importantly, it does not offer any protection for messages that are being sent between Hub Transport Servers and between Hub- and Edge Transport Servers.

Then came Exchange Server 2010 which introduced ‘Shadow Redundancy’. This feature is in a lot of ways similar to the “Transport Dumpster”: a message is kept in the local transport queue until the next hop(s) for that message acknowledge they have successfully received the message. If any of the ‘next hops’ would not acknowledge the receipt, the message(s) would be resubmitted.

The following image graphically explains how Shadow Redundancy works (in a nutshell!):

image

“The Problem”

The problem with Shadow Redundancy is, that it only works for servers that support Shadow Redundancy (seems logical, doesn’t it?). However, in some scenario’s Shadow Redundancy just might not be enough. Image the following: you receive an email from a mail server that does not support Shadow Redundancy. In this case, the Exchange server cannot use Shadow Redundancy but will try to achieve the same result by delaying receipt acknowledgement to the sending server (External) until it has received the confirmation that the message has been received by the next hop in line (Brussels).

The receipt acknowledgement, however, cannot be delayed infinitely. In some cases, the receiving server (Antwerp) cannot send the message further down the route because the next hop is unavailable. This can be due to a failure or perhaps because of maintenance happing on that server. If that’s the case, there’s a small risk that mails might get lost IF this particular Hub/Edge Transport server fails (in the example below that would be the server in Antwerp):

image
If the server in Antwerp would fail after it has sent the receipt acknowledgement but before it was able to relay the message to Brussels; the message would be lost.

The Solution

Since Service Pack 1, Exchange has a new feature called “Shadow Redundancy Promotion”. With this feature enabled, the Transport Server (Antwerp) will try to relay the message to another Transport server in the organization (Gent) whenever it’s not able to relay to the destination (Brussels). By doing so, it injects the message into the shadow redundancy pipeline. As a result, the message is now protected from failure from the server in Antwerp (or Gent):

image

Enabling Shadow Redundancy Promotion

To enable the feature, you will have to make some changes to the EdgeTransport.exe.config file which you can find in the “Bin”-directory under your Exchange Server installation path:

image

In that file, change the value for “ShadowRedundancyPromotionEnabled” from “False” to “True”:

image

Save the changes and restart the Transport Service to activate them. Et voilà, you’re done! Smile

Until later!

Michael

Exchange

Webcast about Exchange Server 2010 & Virtualization now online!

My webcast about Exchange Server 2010 and virtualization, in now online on TechNet Video. In this presentation I talk about the (non)sense of virtualizing Exchange Server 2010 and things to look out for.

Abstract

Chances are that you already are or will be running Exchange virtualized. The reasons to be virtualizing Exchange often come down to better hardware utilization, increased deployment or operational flexibility and sometimes even to align with the datacenter strategy. Whatever the reason might be, it’s important to know what the implications are when virtualizing Exchange. In this session we will talk about technologies that might impact virtualization of Exchange, compare the high availability features offered by the virtualization platform with native data protection features in Exchange 2010 and cover some scenarios where virtualization might not be the right fit.

image

Here’s the link: http://technet.microsoft.com/en-us/video/JJ149038

Enjoy!

Michael

Blog