Category: Exchange 2010

Exchange 2010

Issue with Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010

Recently, Windows Update began offering the Windows Management Framework 3.0 as an Optional update. This includes all forms of update distribution, such as Microsoft Update, WSUS, System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0.

Windows Management Framework 3.0 is being distributed as KB2506146 and KB2506143 (which one is offered depends on which server version you are running – 2008 Sp2 or 2008 R2 Sp1).

What does that mean to you?

Windows Management Framework 3.0 (specifically PowerShell 3.0) is not yet supported on any version of Exchange except Exchange Server 2013 (which requires it). If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Rollups that will not install, or the Exchange Management Shell may not run properly.

We have seen rollups not installing with the following symptoms:

  • If rollup is installed through Microsoft Update, the installation might error with error code of 80070643
  • If rollup is installed from a download, the error displayed is “Setup ended prematurely because of an error.”
  • In both cases, event log might show the error with an error code of “1603”

Exchange Team adviced that Windows Management Framework 3.0 should not be deployed on servers running Exchange 2007 or Exchange 2010, or on workstations with the Exchange Management Tools for either version installed. If you have already deployed this update, it should be removed. Once the update is removed, functionality should be restored.

Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2

Update Rollup 5 version 2 for Exchange Server 2010 SP2 addresses the vulnerabilities that are described in Microsoft Security Bulletin MS12-080

http://technet.microsoft.com/en-us/security/Bulletin/MS12-080

. This update also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment’

2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet

2712001 ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment

2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment

2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used

2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list

2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment

2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server

2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment

2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment

2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment

2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment

2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment.

2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment

2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment

2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging

2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment

2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment

Assume that you apply the Update Rollup 4 version 2 for Exchange Server 2010 SP2 (KB2756485), and then you apply the Update Rollup 5 version 1 (KB2719800). In this situation, when you try to run the Get-DatabaseAvailabilityGroup cmdlet, you receive the following error message:

WARNING: An unexpected error has occurred and a Watson dump is being generated: Could not load type ‘Microsoft.Exchange.Rpc.ActiveManager.AmDeferredRecoveryEntry’ from assembly ‘Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.

Download Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908)

Exchange 2010 SP1 RU8 and Exchange 2007 SP3 RU9

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

Rollup 5 for Exchange Server 2010 Service Pack 2

Exchange Team released Rollup 5 for Exchange Server 2010 Service Pack 2.

List with fixes:
2707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment

2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet

2712001 ;ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment

2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment

2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used

2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list

2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment

2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server

2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment

2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment

2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment

2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment

2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment

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

2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment

2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment

2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging

2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment

2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment.

Download

iOS 6.0.1 update available including Exchange Meetings Bug Fix

There is a update released for IOS 6,Update 6.0.1 and it includes a bug fix for an important ActiveSync issue affecting meetings. If you’ve not heard about this issue, you can read more about it here and on the Exchange Team Blog here.

The fixes included in this release include a few other fixes, but nothing mentioning the AutoDiscover issues present in iOS 6:

http://support.apple.com/kb/DL1606

IOS6 and Exchange Issue’s

If you’ve been following the Exchange and Apple-related news lately, you can’t have failed to hear about a number of bugs in the new iPhone, iPad and iPod Touch OS, iOS 6.
What’s the problem, then? Well, in iOS the two most widely reported ones relate to:

  • AutoDiscover – It doesn’t work unless the Email Address and UPN match.
  • Meeting Requests – The iOS device loses track of the organizer and replaces the device user as the organizer instead, allowing the device user to update or cancel meetings other people have asked them to attend. For more info, see KB 2768774

Another method you might want to consider is to find those iOS 6 users within your organization and tell them about the issue. It might not be practical in all situations, but with the help of the script below (which will also report future and previous versions) you’ll be able to see what the task in hand looks like.

Use the script as follows:

.\Export-iOSDeviceStatistics.ps1 -OutputCSVFile .\output.csv

You’ll see output about iOS devices shown in the PowerShell session:

image

And the resulting CSV file can be opened in Microsoft Excel, or your favourite CSV editor:

image

Download the script from the Technet Gallery

Special thanks to Steve Goodman

Exchange 2010 SP2 Management Tools on Windows 8 RTM

Some day’s ago I installed Windows 8 Enterprise x64 RTM on my Work pc.
So I wanted Exchange 2010 Management Tools on my PC.

I found the following topic: Exchange 2010 Management tools

This worked for me Smile

  1. Install the .NET Framework 3.5 Windows Feature
  2. Install the IIS 6 Management Console Feature
  3. Install the IIS Metabase and IIS 6 Configuration Compatibility Feature
  4. Modify the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion registry key from “6.2” to “6.1” as stated above
  5. DO NOT Close REGEDIT
  6. Create a MMC with the Exchange Tools on it and I saved it under c:\Windows 8 RTM Exchange 2010 SP2\ExchangeAdmin.msc 
  7. Create a Bat File

    8. set __COMPAT_LAYER=RUNASINVOKER
    set COMPLUS_Version=v2.0.50727
    c:\Windows 8 RTM Exchange 2010 SP2\ExchangeAdmin.msc

    Now you can Manage Exchange 2010 from a Windows 8 pc. I found no issues till now. Beware this is not supported by Microsoft!!!!!

     

Re-released Exchange 2010 and Exchange 2007 update rollups

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

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:

myaddress@mydomain.com

#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

Need To Now Before You Deploy Exchange 2010 SP2 RU4

Calendar and Tasks Retention Tag Support in Exchange 2010 SP2 RU4 means you’ll need to treat this update rollup differently. If you don’t use Retention Policies or if you don’t mind Calendar and Tasks items being moved to archive or deleted automatically based on the DPT settings, you can skip the rest of this post. Else reed this Blog Post: Calendar and Tasks Retention Tag Support in Exchange 2010 SP2 RU4

However, if you are concerned about the effects of this new functionality will have on your calendar and task items, you can implement the following temporary workarounds:

If you don’t want Calendar and Tasks items to ever expire, you can disable the functionality that is included in Exchange 2010 SP2 RU4. Add the following registry key to your Mailbox servers:

  • Path: HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxAssistants\Parameters
  • Name: ELCAssistantCalendarTaskRetentionEnabled
  • Type: DWORD
  • Value: 0 = Do not process Calendar and Task folders
  • Value: 1 = Process (default with RU4)

If you want Calendar and Tasks folders to expire at a different interval than DPTs, you can follow the following steps:

  1. Place all mailboxes on Retention Hold
  2. Apply Exchange 2010 SP2 RU4 to your Mailbox servers.
  3. Create RPTs for Calendar and Tasks folders with the desired retention settings.
  4. Inform users about the change.
  5. When ready, remove the retention hold from mailboxes.
Translate »