Tag: Exchange 2010

Exchange 2010 SP2 RU1 Change in CAS to CAS Proxy

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

Rollup 1 for Exchange Server 2010 SP2

The Exchange Team released Update Rollup 1 for Exchange Server 2010 SP2.

It’s a long list with issues that are fixed in this rollup:

  • 2465015 You cannot view or download an image on a Windows Mobile-based device that is synchronized with an Exchange Server 2010 mailbox
  • 2492066 An automatic reply message is still sent after you clear the "Allow automatic replies" check box for a remote domain on an Exchange Server 2010 server
  • 2492082 An Outlook 2003 user cannot view the free/busy information of a resource mailbox in a mixed Exchange Server 2010 and Exchange Server 2007 environment
  • 2543850 A GAL related client-only message rule does not take effect in Outlook in an Exchange Server 2010 environment
  • 2545231 Users in a source forest cannot view the free/busy information of mailboxes in a target forest in an Exchange Server 2010 environment
  • 2549255 A meeting item displays incorrectly as multiple all-day events when you synchronize a mobile device on an Exchange Server 2010 mailbox
  • 2549286 Inline contents disposition is removed when you send a "Content-Disposition: inline" email message in an Exchange Server 2010 environment
  • 2556113 It takes a long time for a user to download an OAB in an Exchange Server 2010 organization
  • 2557323 Problems when viewing an Exchange Server 2003 user’s free/busy information in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2563245 A user who has a linked mailbox cannot use a new profile to access another linked mailbox in an Exchange Server 2010 environment
  • 2579051 You cannot move certain mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server
  • 2579982 You cannot view the message delivery report of a signed email message by using Outlook or OWA in an Exchange Server 2010 environment
  • 2585649  The StartDagServerMaintenance.ps1 script fails in an Exchange Server 2010 environment
  • 2588121 You cannot manage a mail-enabled public folder in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2589982 The cmdlet extension agent cannot process multiple objects in a pipeline in an Exchange Server 2010 environment
  • 2591572 "Junk e-mail validation error" error message when you manage the junk email rule for a user’s mailbox in an Exchange Server 2010 environment
  • 2593011 Warning 2074 and Error 2153 are logged on DAG member servers in an Exchange Server 2010 environment
  • 2598985 You cannot move a mailbox from a remote legacy Exchange forest to an Exchange Server 2010 forest
  • 2599434 Public Folder Calendar folder is missing in the Public Folder Favorites list of an Exchange Server 2010 mailbox
  • 2599663 The Exchange RPC Client Access service crashes when you send an email message in an Exchange Server 2010 environment
  • 2600034 A user can still open an IRM-protected email message after you remove the user from the associated AD RMS rights policy template in an Exchange Server 2010 environment
  • 2600289 A user in an exclusive scope cannot manage his mailbox in an Exchange Server 2010 environment
  • 2600943 EMC takes a long time to return results when you manage full access permissions in an Exchange Server 2010 organization that has many users
  • 2601483 "Can’t open this item" error message when you use Outlook 2003 in online mode in an Exchange Server 2010 environment
  • 2604039 The MSExchangeMailboxAssistants.exe process crashes frequently after you move mailboxes that contain IRM-protect email messages to an Exchange Server 2010 SP1 mailbox server
  • 2604713 ECP crashes when a RBAC role assignee tries to manage another user’s mailbox by using ECP in an Exchange Server 2010 environment
  • 2614698  A display name that contains DBCS characters is corrupted in the "Sent Items" folder in an Exchange Server 2010 environment
  • 2616124 Empty message body when replying to a saved message file in an Exchange Server 2010 SP1 environment
  • 2616230 IMAP4 clients cannot log on to Exchange Server 2003 servers when the Exchange Server 2010 Client Access server is used to handle proxy requests
  • 2616361 Multi-Mailbox Search fails if the MemberOfGroup property is used for the management scope in an Exchange Server 2010 environment
  • 2616365 Event ID 4999 when the Store.exe process crashes on an Exchange Server 2010 mailbox server
  • 2619237 Event ID 4999 when the Exchange Mailbox Assistants service crashes in Exchange 2010
  • 2620361 An encrypted or digitally-signed message cannot be printed when S/MIME control is installed in OWA in an Exchange Server 2010 SP1 environment
  • 2620441 Stop-DatabaseAvailabilityGroup or Start-DatabaseAvailabilityGroup cmdlet fails when run together with the DomainController parameter in an Exchange Server 2010 environment
  • 2621266 An Exchange Server 2010 database store grows unexpectedly large
  • 2621403 "None" recipient status in Outlook when a recipient responds to a meeting request in a short period of time in an Exchange Server 2010 environment
  • 2628154 "The action couldn’t be completed. Please try again." error message when you use OWA to perform an AQS search that contains "Sent" or "Received" in an Exchange Server 2010 SP1 environment
  • 2628622 The Microsoft Exchange Information Store service crashes in an Exchange Server 2010 environment
  • 2628693 Multi-Mailbox Search fails if you specify multiple users in the "Message To or From Specific E-Mail Addresses" option in an Exchange Server 2010 environment
  • 2629713 Incorrect number of items for each keyword when you search for multiple keywords in mailboxes in an Exchange Server 2010 environment
  • 2629777  The Microsoft Exchange Replication service crashes on Exchange Server 2010 DAG members
  • 2630708  A UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2010 environment
  • 2630967A journal report is not sent to a journaling mailbox when you use journaling rules on distribution groups in an Exchange Server 2010 environment
  • 2632206 Message items rescanned in the background in an Exchange Server 2010 environment
  • 2633044 The Number of Items in Retry Table counter displays an incorrect value that causes SCOM alerts in an Exchange Server 2010 SP1 organization
  • 2639150 The MSExchangeSyncAppPool application pool crashes in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2640218 The hierarchy of a new public folder database does not replicate on an Exchange Server 2010 SP1 server
  • 2641077 The hierarchy of a new public folder database does not replicate on an Exchange Server 2010 SP1 server
  • 2642189 The RPC Client Access service may crash when you import a .pst file by using the New-MailboxImportRequest cmdlet in an Exchange Server 2010 environment
  • 2643950 A seed operation might not succeed when the source mailbox database has many log files in a Microsoft Exchange Server 2010 DAG
  • 2644047 Active Directory schema attributes are cleared after you disable a user’s mailbox in an Exchange Server 2010 environment
  • 2644264 Disabling or removing a mailbox fails in an Exchange Server 2010 environment that has Office Communications Server 2007, Office Communications Server 2007 R2 or Lync Server 2010 deployed
  • 2648682 An email message body is garbled when you save or send the email message in an Exchange Server 2010 environment
  • 2649727 Client Access servers cannot serve other Mailbox servers when a Mailbox server encounters a problem in an Exchange Server 2010 environment
  • 2649734 Mailbox replication latency may occur when users perform a Multi-Mailbox Search function against a DAG in an Exchange Server 2010 environment
  • 2649735 Warning of undefined recipient type of a user after the linked mailbox is moved from an Exchange Server 2007 forest to an Exchange Server 2010 forest
  • 2652849 The MailboxCountQuota policy is not enforced correctly in an Exchange Server 2010 hosting mode
  • 2665115 Event ID 4999 is logged on an Exchange Server 2010 Client Access server (CAS)

Download the rollup at HERE

Exchange 2010: Setting Static RPC ports when using a Kemp LoadMaster

When you use a Kemp LoadMaster for Loadbalacing Exchange 2010 you need to set static RPC ports.

By default Windows Server 2008 and 2008 R2 are configured with a dynamic RPC range of 49152-65535 for outbound connections. When the Exchange 2010 Client Access server role is installed on Windows Server 2008 or 2008 R2, the dynamic RPC port range is changed to 6005-59530 and the highest usable port number is set to 60554.

Exchange 2010 RPC Client Access Service

By default the RPC Client Access service on an Exchange 2010 Client Access server uses the TCP End Point Mapper port (TCP/135) and the dynamic RPC port range (6005-59530) for outgoing connections, every time an Outlook clients establish a connection to Exchange.

To set a static port for the RPC Client Access service on an Exchange 2010 Client Access server, you need to open the registry on the respective server and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeRPC

Here, you need to create a new key named ParametersSystem, and under this key create a REG_DWORD named TCP/IP Port. The Value for the DWORD should be the port number you want to use.

Configuring static ports for the RPC Client Access service

RPC.reg
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeRPC\ParametersSystem]
"TCP/IP Port"=dword:0000e88c

Note

Microsoft recommends you set this to a unique value between 59531 and 60554 and use the same value on all CAS in any one AD site.

When you’ve configured the port, it’s required to restart the Microsoft Exchange RPC Client Access service in order for the changes to be applied.

Exchange 2010 Address Book Service

To set a static RPC port for the Exchange Address Book Service, create a new REG_SZ registry key named “RpcTcpPort” under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters



RPCAB.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters]
"RpcTcpPort"="59533"

Microsoft recommends you set this to a unique value between 59531 and 60554 and use the same value on all Exchange 2010 Client Access servers in any one AD site.

When you’ve configured the port, it’s required to restart the Microsoft Exchange Address Book service in order for the changes to be applied.

Exchange 2010 Public Folder connections

By default public folder connections uses the TCP End Point Mapper (TCP/135) and the dynamic RPC port range (49152-65535) for outgoing connections, every time an Outlook client establish a connection to Exchange.

To set a static port for public folder connections, follow the same steps as those required for configuring static ports for the RPC CA service. Just bear in mind you need to perform them on the Exchange 2010 servers that stores public folder databases. This is because public folder connections from an Outlook client occur against the RPC Client Access service on the Mailbox server role.

Verifying the Statically Configured Ports are used

In order to verify that the static ports configured are used, the netstat.exe tool can be used:

Netstat -an -p tcp

image
Verifying the configured static ports are used on the Client Access and Mailbox servers
In my next blog post I will show how to config a Kemp Loadmaster.

Reference:
Link: Configure Static RPC Ports on an Exchange 2010 Client Access Server

Exchange 2010 DAG Maintance

When you need to performing maintenance on DAG nodes here is the process you want to go through In my environment I have two nodes in a dag. For more nodes the same process
 
All the commands below are run in an administrative exchange powershell prompt.

Type add first: cd $exscripts and press enter.

Now you are in the Exchange Scripts folder.

Exchange Node 1: 
Process for running maintenance on exchange database servers
.\StartDagServerMaintenance.ps1 -ServerName <Dag Node 1>

Run maintenance on <Dag Node 1>

When you are finished on Node 1
.\StopDagServerMaintenance.ps1 -ServerName <Dag Node 1>

Exchange Node 2:
.\StartDagServerMaintenance.ps1 -ServerName <Dag Node 2>

run maintenance on <Dag Node 2>

When you are finished on Node 2
.\StopDagServerMaintenance.ps1 -ServerName <Dag Node 2>

When done performing maintenance on one or multiple servers (hopefully one at a time to maintain full database availability for end users!) you can end up with a sub-optimal active database layout, especially if you have a cross-site DAG. To resolve this you have to rebalance the databases based on the priorities set for them upon creation.
 
Rebalance databases across dag
.\RedistributeActiveDatabases.ps1 -DagName <Your DAG Name> -BalanceDbsByActivationPreference -ShowFinalDatabaseDistribution -Confirm:$false

If you get any errors you may have to re-index the search catalog for the passive database. Rather than hunting down which ones need to be fixed you can just fix them all with the custom script I wrote below (or for only the mail servers with issues). When finished running these commands then try to run the maintenance or rebalance scripts again.
 
Fix/Rebuild Search Catalogs
Get-MailboxDatabaseCopyStatus -Server <Dag Node 1> | where {$_.Status -like "Healthy"} | Update-MailboxDatabaseCopy –catalogonly

Get-MailboxDatabaseCopyStatus -Server <Dag Node 2> | where {$_.Status -like "Healthy"} | Update-MailboxDatabaseCopy -catalogonly

Public Folder Migration from Exchange 2003 or 2007 to Exchange 2010

Step 1: Replicating Exchange 2003 or 2007  PF’s to Exchange 2010

Add PF replica’s to an Exchange 2010 Server:

.\AddReplicaToPFRecursive.ps1 -server "Exchange 2003/2007 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"

Replicate the System Folders to an Exchange 2010 Server:

.\AddReplicaToPFRecursive.ps1 -TopPublicFolder "\NON_IPM_Subtree" -ServerToAdd "exchange2010 server”

If you are planning to have multiple Exchange 2010 PF servers, you can repeat the Cmdlet

From the Exchange 2010 server: Update-PublicFolderHierarchy -Server "Exchange 2010 Server"

Step 2: Moving Exchange 2003/2007 PF’s to Exchange 2010

As a last step, after you confirmed that all the PF have been replicated to the Exchange 2010, you can move all replicas from Exchange 2003/2007 to Exchange 2010. The "move all replicas" will actually remove the Exchange 2003/2007 replicas.

To move all Exchange 2003/2007 replicas to Exchange 2010, which will actually remove the Exchange 2003/2007 replicas:

.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"

Additional Cmdlets

To view a list of the replicas in the public folder hierarchy: Get-PublicFolder -recurse |fl name,replicas

For System Folders: Get-PublicFolder -recurse \non_ipm_subtree |fl name, replicas

To compare content replicated between the source and destination servers: Get-PublicFolderStatistics

Reference

Move Public Folder Content from One Public Folder Database to Another Public Folder Database – http://technet.microsoft.com/en-us/library/bb331970.aspx

Exchange 2010 Outlook Mobile Update

This guide was created to help you deploy the new Outlook Mobile update for the Windows Mobile 6.1 devices that connect to your Exchange 2010 servers. This guide focuses on Microsoft Exchange Server 2010 RTM & SP1 & SP2 and Windows Mobile 6.1, and covers the following topics:

· Overview

· How to configure your Exchange 2010 for the Outlook Mobile update

· Details about the Outlook Mobile update

· How to get support for Outlook Mobile updates

· How to subscribe for future updates

Overview

First, we’ll review the overall update experience that’s built into Exchange 2010.

clip_image002

As part of the Outlook Mobile update, users will receive an update notification in an e-mail message in their Inbox. The purpose of this message is to inform them that there’s an Outlook Mobile update for their phone.

The message will instruct the user to click an inline link. This prompts the phone to download the Initial Setup CAB. After the Initial Setup CAB is installed, it will check for available updates specific to the user’s device type.

Next, if an Outlook Mobile update is available, it will be downloaded and installed. The user will receive a notification message that tells them they need to restart their device. After the device is restarted, it will resynchronize the data (e-mail, calendar, contacts, and tasks) with the Exchange server so it will be compatible with the new format of Exchange Server 2010. After that synchronization is complete, the user will be ready to experience the new features in the Outlook Mobile update.

How to Configure Your Exchange 2010 Server for the Outlook Mobile Update

Now that you understand the tasks that the Outlook Mobile update performs, we’ll cover how to configure your Exchange server so that your users who have Windows Mobile 6.1 devices will receive the update notification e-mail message.

How to determine whether a user will receive the update notification e-mail message

The update notification e-mail message will be sent to the user’s device if the following conditions are true:

· The user’s mailbox is on a server running Exchange Server 2010.

· The Exchange ActiveSync mailbox policy parameter AllowMobileOTAUpdate is set to $True.

· The Windows Mobile OS version is 6.1. To check which version the device is running, from the Help About screen, look for the OS and Windows Mobile 6.1 build number (Start > Settings > System > About). You should see Windows OS = “Windows CE 5.2”, and the Windows mobile build should be between 19202 and 21142.

AllowMobileOTAUpdate

The AllowMobileOTAUpdate setting is one of the standard Exchange ActiveSync mailbox policy settings. This is the main setting that determines whether the update notification e-mail message is sent to the device.

The default value for the AllowMobileOTAUpdate parameter is enabled ($True). To confirm that your Exchange ActiveSync mailbox policy has this setting enabled, follow these steps:

1. Check which policy the user is assigned to by running the following command.

Get-CasMailbox <user> | fl ActiveSyncMailboxPolicy

In the preceding example, the result is the following.

ActiveSyncMailboxPolicy : Default

2. Check that the policy returned in the preceding step has the AllowMobileOTAUpdate setting enabled by running the following command.

Get-ActiveSyncMailboxPolicy Default | fl AllowMobileOTAUpdate

If the AllowMobileOTAUpdate setting is set to $True, the following will be returned.

AllowMobileOTAUpdate : True

Details About the Outlook Mobile Update

The following section covers the end user experience for the Outlook Mobile update. The update notification e-mail message the user receives will look like this.

clip_image004

The user can click the first link in the message to start the download. This downloads the initial setup CAB, which is necessary to find the appropriate Outlook Mobile update for that user’s device.

Next, the user will see a URL Confirmation page that informs them that they’re being taken to a Web site. The user should click Yes to continue. Clicking No will cancel the update process.

clip_image006

After the file begins downloading, the user will be asked if they want to open the file, save it to a location, or click Cancel. The user should click Yes to continue opening the file, making sure that the open file after download box is selected.

clip_image008

The next screen they’ll see is the progress bar that shows that the initial setup CAB is being downloaded and installed.

clip_image010

The initial setup CAB finds the appropriate Outlook Mobile update for the user’s specific device. After the initial setup CAB is installed, it connects to the Outlook Mobile Update Service to find the update. If an update is found, the user will be asked if they want to download the Outlook Mobile update. The user should select Yes to download and install the update.

clip_image012clip_image014

clip_image016clip_image018

After the Outlook Mobile update has been installed, the user needs to restart their device to ensure that all new Outlook Mobile files loaded correctly.

clip_image020

After the user restarts their device, they’re presented with a warning message that informs them that they need to resynchronize their data with Exchange. This is necessary because the existing format of the synchronized data isn’t compatible with the new features built into Exchange Server 2010. The user should click Yes in this warning message box.

clip_image022

Occasionally, a user may see the following error, which can appear when the resynchronization hasn’t yet occurred. The user will need to manually resync their data with Exchange.

clip_image024

How to Subscribe for Future Updates

There may be updates available for your users’ Windows Mobile 6.1 phones in the future. The Outlook Mobile update package will ask users if they would like Outlook Mobile to automatically check for updates on a regular schedule. Users should click Yes to automatically check for updates and receive notification when new updates are available.

clip_image026

mail-enabled public folders stopped working after installing Exchange 2010 in existing Exchange 2003 or 2007 environment

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!

Issue

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.

Solution

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

Exchange 2007 & 2010: Current issues with Microsoft Exchange ActiveSync and Third Party Devices

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:

http://www.apple.com/ios

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:

http://www.apple.com/ios

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:

http://blogs.technet.com/b/jribeiro/archive/2009/11/26/transitioning-from-an-exchange-2007-environment-to-exchange-2010.aspx

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.

Check: http://support.microsoft.com/kb/2563324

Exchange 2010 SP2 RTM

Exchange Server 2010 Service Pack 2 (SP2) has been released, raising the Exchange version number to 14.2.247.5. You can download Exchange 2010 SP2 here.

For those still unaware, the 530Mb+ file (1,4 GB extracted) contains the full set of binaries; you can use it to upgrade existing RTM or SP1 installations or deploy new Exchange 2010 SP2 installations.

Besides the usual set of hotfixes, SP2 introduces the following features:

Address Book Policies
Address Book Policies, also known as GAL segmentation, ABPs are meant to segmentize the address book, giving users a certain view of the address book like Address List Segregation did for Exchange 2003/2007.

OWA mini
This will be a lightweight browser like OMA in the past, meant for simple browsers.

Hybrid Configuration
This wizard is to make the configuration of an on-premise Exchange and Office 365/Exchange Online more simple, reducing the steps required from 49 to 6.

OWA Cross-Site redirection
This will allow clients to be silently redirected to the proper site if they log on to a CAS server located in a site different than the site where their mailbox is hosted and externalURL has been specified there.

After preparing your forest for Exchange 2010 SP2, the schema version number will have changed. Check the Schema Versions page for information on the new ObjectVersion and RangeUpper values for Exchange 2010 SP2.

Note that SP2 introduces an additional requirement, which is the IIS 6 WMI Compatibility feature; you can add this feature using the GUI or by using the Powershell cmdlets Import-Module ServerManager followed by Add-WindowsFeature Web-WMI.

The proper method to upgrade mailbox servers that are a member of a Database Availability Group is described here.

The releases notes are not available at time of writing; we’ll update this post when they become available.

Rollup 6 for Exchange Server 2010 Service Pack 1

The Exchange CXP team released Update Rollup 6 for Exchange Server 2010 SP1 to the Download Center.

This update contains a number of customer-reported and internally found issues since the release of SP1. See ‘KB 2608646: Description of Update Rollup 6 for Exchange Server 2010 Service Pack 1’ for more details.

This update contains a number of customer reported and internally found issues since the release of RU5.

The most Important Fixes:

  • 2627769 Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment
  • 2528854 The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
  • 2544246 You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
  • 2616127 "0x80041606" error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment.
  • 2549183 "There are no objects to select" message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment

Other Fixes:

  • 2431609 An update is available that updates the message of a retention policy in OWA for Exchange Server 2010
  • 2449266 EWS drops the TCP connection to the EWS client application without any error message in a Microsoft Exchange Server 2010 environment
  • 2480474 A Users do not receive quota warning messages after applying SP1 for Exchange 2010
  • 2514820 An incoming fax message is not delivered to the recipient in an Exchange Server 2010 SP1 environment
  • 2521927 Disabling the Exchange ActiveSync Integration feature for OWA does not take effect in OWA Premium clients in an Exchange Server 2010 environment
  • 2535289 The Microsoft Exchange Information Store service crashes occasionally when you run an antivirus application on an Exchange Server 2010 Mailbox server
  • 2536313 Slow message delivery and mailbox access for journaling mailboxes on an Exchange Server 2010 server
  • 2548246 The Microsoft Exchange Information Store service crashes occasionally when a folder view is corrupted on an Exchange Server 2010 mailbox server
  • 2549289 A RBAC role assignee can unexpectedly run the Add-MailboxPermission command or the Remove-MailboxPermission command on an Exchange Server 2010 server that is outside the role assignment scope
  • 2555851 A mailbox does not appear in certain address lists after you run commands on the mailbox in an Exchange Server 2010 SP1 environment
  • 2559814 A user cannot add or remove delegates from a mailbox by using Outlook in an Exchange Server 2010 environment
  • 2561514 Exchange Server 2003 user cannot view the free/busy information of a user in a different federated organization
  • 2563860 You cannot create a new mailbox database if you already have 1000 mailbox databases in an Exchange Server 2010 environment
  • 2567409 Certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003 server
  • 2571791 Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment
  • 2572052 Certain properties of a recurring meeting request from external email accounts are missing in an Exchange Server 2010 SP1 environment
  • 2575005 You cannot start the EMC or the EMS in an Exchange Server 2010 Service Pack 1 environment
  • 2578631 Certain users cannot send email messages to a mail-enabled public folder in an Exchange Server 2010 environment
  • 2579172 Items that are deleted or moved still appear in the original folder when you use Office Outlook in online mode to access an Exchange Server 2010 mailbox
  • 2579671 No results returned when you use the ExpandGroup method in EWS to retrieve a list of members of a Dynamic Distribution Group in an Exchange Server 2010 environment
  • 2582095 The SmtpMaxMessagesPerConnection property of a send connector is not replicated to the subscribed Edge Transport server in an Exchange Server 2010 environment
  • 2600835 The RPC Client Access service crashes when you delete an attachment of an item by using Outlook in online mode in an Exchange Server 2010 SP1 environment
  • 2601701 The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases
  • 2617126 The Store.exe process crashes when you send an email message that has attachments in an Exchange Server 2010 SP1 environment

 

General Notes

An issue with management of RBAC roles when RU6 is partially deployed in the organization: Due to changes shipped in this update, certain warnings can be displayed when managing RBAC roles, if RU6 is not yet deployed to all servers in the organization. Please see the following KB article for more information:

Managing RBAC roles might display warnings or errors if Exchange 2010 SP1 RU6 is partially deployed in the organization
http://support.microsoft.com/kb/2638351

Note for Forefront users: For those of you running Forefront Protection for Exchange, before installing the update, stop all Forefront services.

Translate »