Microsoft Knowledge Base Wiki

• Coexistence with Exchange 2013: You can now install Exchange Server 2013 in your existing Exchange Server 2010 organization. To do this, install Exchange Server 2013 Cumulative Update 1 (CU1). You cannot install Exchange Server 2013 in your existing Exchange Server 2010 organization by using Exchange Server 2013 RTM installation media.

  Note Exchange Server 2013 CU1 is also an installation medium for Exchange Server 2013.

• Support for Windows Server 2012: You can now install and deploy Exchange Server 2010 on computers that are running Windows Server 2012.
• Support for Internet Explorer 10: You can now use Internet Explorer 10 to connect to Exchange 2010.
• Customer Requested Fixes: Exchange Server 2010 SP3 contains all the fixes that are contained in update rollups that were released before SP3. For more information about the release schedules of Exchange 2010 updates, see Exchange 2010 Servicing

  (http://technet.microsoft.com/library/ff637979.aspx)

  .

This article describes the following information about the service pack:

• The issues that the service pack resolves
• How to obtain the service pack
• The prerequisites for installing the service pack

Issues that the service pack resolves

In addition to the customer reported issues that are resolved in previous service packs, this service pack also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

• 2552121

  (http://support.microsoft.com/kb/2552121/
  )

  You cannot synchronize a mailbox by using an Exchange ActiveSync device in an Exchange Server 2010 environment

• 2729444

  (http://support.microsoft.com/kb/2729444/
  )

  Mailboxes are quarantined after you install the Exchange Server 2010 SP2 version of the Exchange Server 2010 Management Pack

• 2778100

  (http://support.microsoft.com/kb/2778100/
  )

  Long delay in receiving email messages by using Outlook in an Exchange Server 2010 environment

• 2779351

  (http://support.microsoft.com/kb/2779351/
  )

  SCOM alert when the Test-PowerShellConnectivity cmdlet is executed in an Exchange Server 2010 organization

• 2784569

  (http://support.microsoft.com/kb/2784569/
  )

  Slow performance when you search a GAL by using an EAS device in an Exchange Server 2010 environment

• 2796950

  (http://support.microsoft.com/kb/2796950/
  )

  Microsoft.Exchange.Monitoring.exe process consumes excessive CPU resources when a SCOM server monitors Exchange Server 2010 Client Access servers

• 2800133

  (http://support.microsoft.com/kb/2800133/
  )

  W3wp.exe process consumes excessive CPU and memory resources on an Exchange Client Access server after you apply Update Rollup 5 version 2 for Exchange Server 2010 SP2

• 2800346

  (http://support.microsoft.com/kb/2800346/
  )

  Outlook freezes and a high network load occurs when you apply retention policies to a mailbox in an Exchange Server 2010 environment

• 2810617

  (http://support.microsoft.com/kb/2810617/
  )

  Can’t install Exchange Server 2010 SP3 when you define a Windows PowerShell script execution policy in Group Policy

• 2787500

  (http://support.microsoft.com/kb/2787500/
  )

  Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010

• 2797529

  (http://support.microsoft.com/kb/2797529/
  )

  Email message delivery is delayed on a Blackberry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2

• 2799450

  (http://support.microsoft.com/kb/2799450/
  )

  LDAP search stops working in an Exchange Server 2010 environment

• 2800080

  (http://support.microsoft.com/kb/2800080/
  )

  ErrorServerBusy response code when you synchronize an EWS-based application to a mailbox in an Exchange Server 2010 environment

Service pack information

The following service pack is available for download from the Microsoft Download Center: Release Date: February 12, 2013

Prerequisites

• Make sure that any server on which you plan to install the service pack meets the system requirements. For more information about system requirements, see Exchange 2010 System Requirements

  (http://technet.microsoft.com/en-us/library/aa996719(v=exchg.141).aspx)

  .

• Understand the prerequisites for all server roles. For more information about prerequisites, see Exchange 2010 Prerequisites

  (http://technet.microsoft.com/en-us/library/bb691354(v=exchg.141).aspx)

  . For more information about server roles, see Overview of Exchange 2010 Server Roles

  (http://technet.microsoft.com/en-us/library/dd298026(v=exchg.141).aspx)

  .

• Actual requirements will vary based on system configuration and specific features installed. For more detailed system requirements, please refer to the Exchange Server 2010 Technical Documentation Library

  (http://go.microsoft.com/fwlink/?LinkId=135761)

  .

Restart requirement

After you install a service pack, you must restart the computer so that changes can be made to the registry and operating system.

Removal information

After you install a new service pack for Exchange 2010, you cannot uninstall the service pack to revert to an earlier version of Exchange 2010. If you uninstall the service pack, Exchange 2010 is removed from the server.

Article ID: 2808208 – Last Review: February 20, 2013 – Revision: 3.0

Our network receives frequent updates to ensure that the Virus Definitions we use are always up to date. Each of the three virus engines receives new viral definitions every fifteen minutes from their respective update servers. By default, your organization will always have at least two virus engines enabled.

In the event of a virus outbreak, the virus engine from whichever partner comes out with a patch first will be turned on for all customers. The default virus engines will be turned on again once a patch is released for the new virus.

The virus engines scan all text files, as well as the text within each message body. Any text file or message body that contains the complete code for a known virus will be blocked.

The virus engines also examine each message for partial virus code and will attempt to block these e-mail messages as well.

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2023001 – Last Review: February 20, 2013 – Revision: 2.0

A recent improvement to the DeleteExpiredSessions stored procedure increases performance and reduces blocking. This improvement minimizes the adverse effect on the execution of ASP.NET requests. This improvement will also be implemented in the next version of ASP.NET.

1. Open the SQL Server Management Studio console.
2. Click New Query.
3. If you use a non-persistent SQL session state, paste the following script into the right pane.

   USE ASPState
   GO
   
   DECLARE @ver int
   EXEC dbo.GetMajorVersion @@ver=@ver OUTPUT
   DECLARE @cmd nchar(4000)
   IF (@ver >= 
       SET @cmd = N'
           ALTER PROCEDURE dbo.DeleteExpiredSessions
           AS
               SET NOCOUNT ON
               SET DEADLOCK_PRIORITY LOW 
   
               DECLARE @now datetime
               SET @now = GETUTCDATE() 
   
               CREATE TABLE #tblExpiredSessions
               (
                   SessionId nvarchar(88) NOT NULL PRIMARY KEY
               )
   
               INSERT #tblExpiredSessions (SessionId)
                   SELECT SessionId
                   FROM tempdb.dbo.ASPStateTempSessions WITH (READUNCOMMITTED)
                   WHERE Expires < @now
   
               IF @@ROWCOUNT <> 0
               BEGIN
                   DECLARE ExpiredSessionCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY
                   FOR SELECT SessionId FROM #tblExpiredSessions 
   
                   DECLARE @SessionId nvarchar(88)
   
                   OPEN ExpiredSessionCursor
   
                   FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
   
                   WHILE @@FETCH_STATUS = 0
                       BEGIN
                           DELETE FROM tempdb.dbo.ASPStateTempSessions WHERE SessionId = @SessionId
                           FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
                       END
   
                   CLOSE ExpiredSessionCursor
   
                   DEALLOCATE ExpiredSessionCursor
   
               END 
   
               DROP TABLE #tblExpiredSessions
   
           RETURN 0'
   ELSE
       SET @cmd = N'
           ALTER PROCEDURE dbo.DeleteExpiredSessions
           AS
               SET NOCOUNT ON
               SET DEADLOCK_PRIORITY LOW 
   
               DECLARE @now datetime
               SET @now = GETDATE() 
   
               CREATE TABLE #tblExpiredSessions
               (
                   SessionId nvarchar(88) NOT NULL PRIMARY KEY
               )
   
               INSERT #tblExpiredSessions (SessionId)
                   SELECT SessionId
                   FROM tempdb.dbo.ASPStateTempSessions WITH (READUNCOMMITTED)
                   WHERE Expires < @now
   
               IF @@ROWCOUNT <> 0
               BEGIN
                   DECLARE ExpiredSessionCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY
                   FOR SELECT SessionId FROM #tblExpiredSessions 
   
                   DECLARE @SessionId nvarchar(88)
   
                   OPEN ExpiredSessionCursor
   
                   FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
   
                   WHILE @@FETCH_STATUS = 0
                       BEGIN
                           DELETE FROM tempdb.dbo.ASPStateTempSessions WHERE SessionId = @SessionId
                           FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
                       END
   
                   CLOSE ExpiredSessionCursor
   
                   DEALLOCATE ExpiredSessionCursor
   
               END 
   
               DROP TABLE #tblExpiredSessions
   
           RETURN 0'
   EXEC (@cmd)
   GO

   If you use a persistent SQL session state, paste the following script into the right pane.

   USE ASPState
   GO
   
   DECLARE @ver int
   EXEC dbo.GetMajorVersion @@ver=@ver OUTPUT
   DECLARE @cmd nchar(4000)
   IF (@ver >= 
       SET @cmd = N'
           ALTER PROCEDURE dbo.DeleteExpiredSessions
           AS
               SET NOCOUNT ON
               SET DEADLOCK_PRIORITY LOW 
   
               DECLARE @now datetime
               SET @now = GETUTCDATE() 
   
               CREATE TABLE #tblExpiredSessions
               (
                   SessionId nvarchar(88) NOT NULL PRIMARY KEY
               )
   
               INSERT #tblExpiredSessions (SessionId)
                   SELECT SessionId
                   FROM ASPState.dbo.ASPStateTempSessions WITH (READUNCOMMITTED)
                   WHERE Expires < @now
   
               IF @@ROWCOUNT <> 0
               BEGIN
                   DECLARE ExpiredSessionCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY
                   FOR SELECT SessionId FROM #tblExpiredSessions 
   
                   DECLARE @SessionId nvarchar(88)
   
                   OPEN ExpiredSessionCursor
   
                   FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
   
                   WHILE @@FETCH_STATUS = 0
                       BEGIN
                           DELETE FROM ASPState.dbo.ASPStateTempSessions WHERE SessionId = @SessionId
                           FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
                       END
   
                   CLOSE ExpiredSessionCursor
   
                   DEALLOCATE ExpiredSessionCursor
   
               END 
   
               DROP TABLE #tblExpiredSessions
   
           RETURN 0'
   ELSE
       SET @cmd = N'
           ALTER PROCEDURE dbo.DeleteExpiredSessions
           AS
               SET NOCOUNT ON
               SET DEADLOCK_PRIORITY LOW 
   
               DECLARE @now datetime
               SET @now = GETDATE() 
   
               CREATE TABLE #tblExpiredSessions
               (
                   SessionId nvarchar(88) NOT NULL PRIMARY KEY
               )
   
               INSERT #tblExpiredSessions (SessionId)
                   SELECT SessionId
                   FROM ASPState.dbo.ASPStateTempSessions WITH (READUNCOMMITTED)
                   WHERE Expires < @now
   
               IF @@ROWCOUNT <> 0
               BEGIN
                   DECLARE ExpiredSessionCursor CURSOR LOCAL FORWARD_ONLY READ_ONLY
                   FOR SELECT SessionId FROM #tblExpiredSessions 
   
                   DECLARE @SessionId nvarchar(88)
   
                   OPEN ExpiredSessionCursor
   
                   FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
   
                   WHILE @@FETCH_STATUS = 0
                       BEGIN
                           DELETE FROM ASPState.dbo.ASPStateTempSessions WHERE SessionId = @SessionId
                           FETCH NEXT FROM ExpiredSessionCursor INTO @SessionId
                       END
   
                   CLOSE ExpiredSessionCursor
   
                   DEALLOCATE ExpiredSessionCursor
   
               END 
   
               DROP TABLE #tblExpiredSessions
   
           RETURN 0'
   EXEC (@cmd)
   GO

4. Click Execute.

To determine if the session state database is configured as persistent or non-persistent SQL session state, use the following specifications:

• Non-persistent SQL session state
  ASPStateTempApplications and ASPStateTempSessions tables are created in the tempdb database to store the session data.
• Persistent SQL session state
  ASPStateTempApplications and ASPStateTempSessions tables are created in the same database as the Session State database to store the session data. 

Article ID: 973849 – Last Review: February 19, 2013 – Revision: 4.0

Additionally, Office 365 Exchange Online users receive an error message that resembles the following on an iOS 6.1 or 6.1.1-based device: 

The only option available to users is OK.

Additional Symptoms
The following additional symptoms can occur.

EAS Mailbox logging
When you review an Exchange ActiveSync (EAS) Mailbox log, you may see the following:

RequestHeader :
POST /Microsoft-Server-ActiveSync/default.eas?User=user1@contoso.com&DeviceId=ApplDMPFXZABDFHW&DeviceType=
iPad&Cmd=MeetingResponse HTTP/1.1
Connection: keep-alive
Content-Length: 55
Content-Type: application/vnd.ms-sync.wbxml
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: en-us
Authorization: ********
Host: mail.contoso.com
User-Agent: Apple-iPad2C1/1002.141
X-MS-PolicyKey: 2429156470
MS-ASProtocolVersion: 14.1

RequestBody :


      
            1
            5
            5:5
            2013-02-06T22:00:00.000Z
      

MeetingResponseCommand_OnExecute_Exception :
Microsoft.Exchange.Data.Storage.WrongObjectTypeException: The object was bound to a wrong
object type. ObjectClass = IPM.Schedule.Meeting.Request, Intended Type =
Microsoft.Exchange.Data.Storage.CalendarItem.
   at Microsoft.Exchange.Data.Storage.StoreObject.DownCastStoreObjectT()
   at Microsoft.Exchange.Data.Storage.ItemBuilder.ItemBindT(StoreSession session, StoreId
storeId, Schema expectedSchema, MapiMessageCreator mapiMessageCreator, ItemBindOption
itemBindOption, ICollection`1 propertiesToLoad)
   at Microsoft.Exchange.Data.Storage.ItemBuilder.ItemBindT(StoreSession session, StoreId id,
Schema expectedSchema, ICollection`1 propertiesToLoad)
   at Microsoft.Exchange.Data.Storage.CalendarItem.Bind(StoreSession session, StoreId id)
   at Microsoft.Exchange.AirSync.MeetingResponseCommand.GetOccurenceId(StoreObjectId
mailboxRequestId, ExDateTime instanceId)
   at Microsoft.Exchange.AirSync.MeetingResponseCommand.ProcessCommand()
   at Microsoft.Exchange.AirSync.MeetingResponseCommand.OnExecute()
AccessState :
Allowed
AccessStateReason :
Global
ResponseHeader :
HTTP/1.1 200 OK
MS-Server-ActiveSync: 14.2
ResponseBody :


      
            
            4
      

IIS Logs
In Exchange Server on-premises installations only, the following text is continually repeated in the Internet Information Services (IIS) log files on the CAS.

2013-02-06 23:41:59 192.168.137.11 POST /Microsoft-Server-ActiveSync/default.eas User=user1@contoso.com&
DeviceId=ApplDMPFXZABDFHW&DeviceType=iPad&Cmd=Sync&Log=truncated 443 user1@exchlab.com 192.168.137.246
Apple-iPad2C1/1002.141 200 0 0 187

2013-02-06 23:41:59 192.168.137.11 POST /Microsoft-Server-ActiveSync/default.eas User=user1@contoso.com&
DeviceId=ApplDMPFXZABDFHW&DeviceType=iPad&Cmd=MeetingResponse&Log=... Error:WrongObjectTypeException …
443 user1@exchlab.com 192.168.137.246 Apple-iPad2C1/1002.141 200 0 0 140

Note: The Error:WrongObjectTypeException may not be present in all cases.

If the problem continues, use one of the following methods to work around the issue.

Note: The workarounds below have been modified from the original recommendations. Specifically, the recreation of the partnership and the suggested throttling settings for Exchange ActiveSync have been removed. Analysis found they were insufficient to preserve server performance. The current methods reflect the best options.

Method 1: Use URL Rewrite to block Cmd=MeetingResponse

A workaround has been identified that will allow administrators to block the repeating MeetingResponse attempt using either a perimeter device rule or the URL Rewrite Module 2.0

(http://www.microsoft.com/en-us/download/details.aspx?id=7435)

 for Internet Information Server 7 and 7.5, for Windows Server 2008 and Windows Server 2008 R2. See the following article from the TechNet Wiki online.

Using URL Rewrite to block certain clients from Exchange

(http://social.technet.microsoft.com/wiki/contents/articles/15997.using-url-rewrite-to-block-certain-clients-from-exchange.aspx)

Warning: This solution may not work in some scenarios where a perimeter device, such as some network load balancers, are in use. You should contact the vendor to verify that the solution cannot be implemented on the perimeter device prior to modifying IIS.

Once the URL rewrite is implemented, iOS6.1 and 6.1.1-based devices can sync and receive updates. However, responses to meeting items from the device are rejected by the server. We recommend that users respond to meetings via Outlook Web App (OWA), Microsoft Outlook, or a non-iOS 6.1 or 6.1.1-device.

Method 2: Block iOS 6.1 or 6.1.1 users

You can block iOS 6.1 and 6.1.1 users by using the Exchange Server 2010 Allow/Block/Quarantine feature. For more information about this feature, see the following Exchange Team blog post: 
Also, for updated information about how to use Exchange Management Shell for Allow/Block/Quarantine, see the following Microsoft website: 

Method 1: Obtain EAS Mailbox logging for a user

To obtain EAS Mailbox logs, follow the steps in the following article in the Microsoft Knowledge Base: 

Method 2: Collect and parse IIS logs

Check for the recurrence pattern of Cmd=Sync and Cmd=MeetingResponse together with Error:WrongObjectTypeException, as was noted in the “Symptoms” section. 

You can also use Log Parser Studio

(http://blogs.technet.com/b/exchange/archive/2012/03/07/introducing-log-parser-studio.aspx)

 to parse by using the following query:

SELECT
   Cs-username AS User,
   MyDeviceId AS DeviceId,
   COUNT(*) AS Hits
USING
   EXTRACT_VALUE(cs-uri-query,'DeviceId') AS MyDeviceId
FROM 'LOGFILEPATH'
WHERE  cs-uri-query LIKE ''
GROUP BY DeviceId,User
ORDER BY Hits DESC

Article ID: 2814847 – Last Review: February 19, 2013 – Revision: 15.0

Note The HealthVault service is currently region-specific.

The following table will help you determine the HealthVault service that you should use for your particular location:

You can also find your area’s service URL by going to http://www.healthvault.com/country

(http://www.healthvault.com/country)

, selecting your country/region from the list, and then clicking Sign up or sign in.

Signing up

When you sign up for an account, you must be physically located in the area whose service URL you are using. This should be the area in which you reside. (We check your location based on your computer’s IP address. If you receive an error message when you try to sign up in your home area, you should contact HealthVault technical support and provide the IP address that is listed in the error message.) To contact technical support, go to the following Microsoft website:

Signing in

After you sign up for an account, you can sign in to HealthVault from anywhere in the world by using the service URL for your home area. Therefore, you can access and use your HealthVault account when you are traveling.

Records

The country/region of each person whose health information you are managing (each “record” in HealthVault) must be within your account’s service area.

Apps and devices

Be aware that the selection of apps and devices that are available to you is based on your account’s area. (Therefore, we advise against signing up for a new account when you are outside your home area.)

Additionally, for each person whose health information you are managing, the apps that are available may be specific to his or her location. For example, apps that work with data from the United Kingdom’s National Health Service (NHS) may be available only for people whose country/region is the United Kingdom.

Changes

The areas that are served by HealthVault, the area in which your account is served, and the availability of specific apps and devices may change at any time. Refer to the HealthVault Account Privacy Statement and the HealthVault Account Service Agreement and app-specific privacy statements and terms of service.

For additional help, contact HealthVault Customer Support to create a Support Request. For more information about how to contact HealthVault Customer Support, go to the following Microsoft website:

Article ID: 2614073 – Last Review: February 19, 2013 – Revision: 10.0

• You install Microsoft Exchange Server 2010 Service Pack 2 (SP2) or a later update rollup that was released before Update Rollup 6 in an Exchange Server 2010 organization.
• You manage a cloud-based resource mailbox that has some delegates by using the Exchange Management Console (EMC) in the on-premises organization.
• You open the Resource Policy tab in the properties dialog box of the resource mailbox. 

In this scenario, the list of the delegates for the resource mailbox is displayed as empty.

Article ID: 2788151 – Last Review: February 19, 2013 – Revision: 2.0

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Installation information

Install this hotfix on computers that are running the Microsoft Dynamics CRM 4.0 server components.

Prerequisites

You must have Microsoft Dynamics CRM 4.0 installed to apply this hotfix.

Restart requirement

If you are prompted to restart the computer, you must restart the computer after you apply this hotfix.

For more information about Microsoft Dynamics CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Article ID: 2779372 – Last Review: February 19, 2013 – Revision: 1.0

Problem: The documentation mistakenly tells you to edit the wrong file in step 1.

Solution:Perform the following steps to enable cross column rank normalization.

1. You need to disable the default rank normalization process on individual search nodes because the top level fdispatch (topfdispatch) will handle activating the rank normalized dictionaries. This is done by adding the following line to %FASTSEARCH%etcsearchrc-1.xml on each search node:

   dictionaryactivation="false"

2. Enable the rank normalization process in topfdispatch by opening %FASTSEARCH%etcsearchrc-dispatch.xml on the server running this process and adding

   normalizeinterval=""

   where is the same value you have configured in normalizeInterval in %FASTSEARCH%etcconfig_dataRTSearchwebclusterrtsearchrc.xml on your admin node (Note: if you are running a multi-cluster environment, make sure you check the rtsearchrc.xml file associated with the proper cluster.) The default value is 1800.

3. Restart search by running the following command on every search node:
4. On every node running topfdispatch, run the following:

   nctrl restart topfdispatch

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2723172 – Last Review: February 18, 2013 – Revision: 2.0

Note This issue may reduce the battery life of the mobile device.

Article ID: 2783771 – Last Review: February 18, 2013 – Revision: 2.0

Note The PermanentlyDelete retention action permanently deletes a message from a mailbox. A message that is permanently deleted cannot be recovered by using the Recoverable Items folder. Additionally, permanently deleted messages are not returned by a Discovery search, unless litigation hold or single item recovery is enabled for the mailbox.

After you apply the update rollup, you can run the following command to disable the PermanentlyDelete retention action in an Exchange Server 2010 organization:

Set-OrganizationConfig -Identity OrganizationName -PermanentlyDeleteDisabled $true

Notes

• By default, the PermanentlyDeleteDisabled parameter is set to false. Therefore, the PermanentlyDelete retention action is enabled.
• If the PermanentlyDeleteDisabled parameter is set to true, the PermanentlyDelete retention action is disabled. This setting does not change any other retention policies.

Article ID: 2793274 – Last Review: February 18, 2013 – Revision: 2.0