Hotfix KB2899591 for Outlook 2010 add support for MAPI/HTTP

Microsoft released a hotfix  KB2899591 for Outlook 2010. This hotfix adds MAPI/http support for Outlook 2010 clients. So now can switch if you are using Exchange 2013 SP1 or later from RPC/http to MAPI/http.
See  KB2899591 for the additional fixes that are included in hotfix  as well.

You can request the hotfix for x86 and x64 versions of Outlook 2010 here.

Updated: Update Rollup 8 v2 For Exchange 2010 SP3 (KB2986475) Released

An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.

The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish further updates to this blog post regarding RU8.

This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.

Check: http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx

Updated: Update Rollup 8 v2 For Exchange 2010 SP3 (KB2986475) has been released

Security update available for Exchange 2007, 2010 and 2013

Microsoft has released a fix for Outlook Web App in all supported versions of Exchange.
In all cases, it comes to security issues that have been designated as Important.

Four security updates are also those offered by Microsoft Update, but here are the manually download links:

Rollup 15 for Exchange Server 2007 Service Pack 3
Rollup 8 for Exchange 2010 SP3
Security Update For Exchange Server 2013 SP1 (KB3011140)
Security Update For Exchange Server 2013 CU6 (KB3011140)
Cumulative Update 7 for Exchange Server 2013 (Provided not with Windows Update)

Versions that are not listed here are no longer supported or are not vulnerable. For more information read the security bulletin MS14-075: Vulnerabilities in Microsoft Exchange Server Could Allow Elevation of Privilege (3,009,712)

Cumulative Update 7 for Exchange Server 2013

Today, Cumulative Update 7 for Exchange Server 2013 was released by the Exchange Team (KB2986485). This update raises Exchange 2013 version number to 15.0.1044.22.

Note: Customers that run backups of their Exchange databases are advised to upgrade to CU7 and perform a post-upgrade full backup. This is due to a race condition which could prevent proper restoration of pre-CU7 Exchange databases.

Notes:

  • When using Exchange hybrid deployments or Exchange Online Archiving (EOA), you are required to stay current.
  • CU7 adds support for hierarchies containing 250,000 modern public folders. Consult this article for co-existence scenarios.
  • Be advised of OAB architectural changes introduced with CU5 which are documented here. If you are affected, it is recommended to update CAS servers prior to Mailbox servers.
  • If you have installed the Interim Update to fix Hybrid Configuration Wizard, you can install the Cumulative Update over it – there is no need to uninstall the IU prior to installing CU6.

This Cumulative Update includes schema and AD changes, so make sure you run PrepareSchema / PrepareAD. After updating, the schema version will be 15965.

Note that Cumulative Updates can be installed directly, i.e. no need to install RTM or Service Packs prior to installing Cumulative Updates. Note that once installed, you can’t uninstall a Cumulative Update nor any of the installed Exchange server roles. The order of upgrading servers is irrelevant, unlike with previous generations of Exchange.

Finally, for any Hotfix, Rollup, Service Pack or Cumulative Update, I’d recommend to thoroughly test this in a test and acceptance environment first, prior to implementing it in production.

You can download Exchange 2013 Cumulative Update 7 here; UM Language Packs can be found here.

This update resolves security issues that are described in December 2014 security update for Exchange Server 2013 Service Pack 1 and Cumulative Update 6.
Additionally, this update also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 3004235 Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014

  • 3012655 New-MailboxImportRequest causes unreadable characters when you import an ANSI format .pst file of Russian language

  • 3012652 CalendarProcessing cmdlet does not generate delegate permissions to universal security groups in Exchange Server 2013

  • 3009631 Advanced Find against the Sent Items folder in Outlook returns no result in Exchange Server 2013

  • 3009612 Outlook Web App shows organization details on the contact card beyond the scope of user ABP in Exchange Server 2013

  • 3009291 Shared mailbox cannot be opened in Outlook in an Exchange Server 2013 environment that has multiple domains

  • 3008453 Cannot edit or delete forms from the organizational forms library in Exchange Server 2013

  • 3008438 User who is trying to Log on to Exchange Admin Console is logged in to OWA instead

  • 3006672 Move request fails if the IsExcludedFromProvisioning option is true in Exchange Server 2013

  • 3005391 Exchange Server 2013 Cumulative Update 5 breaks free|busy lookup from Exchange Online to Exchange Server 2007

  • 3003986 RejectMessageReasonText in transport rule appears in the user section of a DSN in Exchange Server 2013

  • 3001217 TLS 1.0 is hardcoded for SMTP traffic encryption in Exchange Server 2013

  • 3001037 Distribution group cannot send email messages to a mail enabled public folder in an Exchange Server 2013 environment

  • 2999031 A cross-forest mailbox move from Exchange Server 2007 to Exchange Server 2013 finishes with CompletedWithWarnings status

  • 2998144 New-MoveRequest cmdlet with RemoteLegacy parameter cannot perform a cross-forest mailbox move

  • 2988553 Add-ADPermission and Remove-ADPermission can be run outside the management scope in Exchange Server 2013

  • 2981538 Exchange Control Panel crashes when you proxy from Exchange 2013 to Exchange 2010

  • 3014051 Cannot migrate mailboxes in a multiple domains environment in Exchange Server 2013

  • 3012986 ContentIndexRetryQueueSize value for a passive node never drops to zero in Exchange Server 2013 Cumulative Update 6

  • 3004011 Sound alerts do not work in Outlook Web App when new email or calendar notification is received in Exchange Server 2013

  • 3003580 Event ID 4999 and 4401 when the Microsoft Exchange Replication service crashes in Exchange Server 2013

  • 3003518 “550 5.7.1” NDR when you send messages to external recipients in an Exchange Server 2013 hybrid environment

  • 3003068 Cannot see online archive mailbox after you upgrade to Exchange Server 2013 Cumulative Update 6

  • 3000944 Subfolders under the Deleted Items folder are not visible in Outlook in an Exchange Server 2013 environment

  • 2997847 You cannot route ActiveSync traffic to Exchange 2007 mailboxes after you upgrade to Exchange 2013 CU6

  • 2997355 Exchange Online mailboxes cannot be managed by using EAC after you deploy Exchange Server 2013 CU6

  • 2997209 Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007

  • 2995263 OAB cannot be rebuilt if the .flt file is larger than two GB in Exchange Server 2013

  • 2994216 PublicFolderMoveRequest deletes all read or unread state in target mailbox for each user in Exchange Server 2013

  • 2993871 Resource Booking Assistant crashes after you upgrade to Exchange Server 2013 Cumulative Update 5

  • 2983216 Category setting on an item in Outlook jumps the selection to the top of the list in an Exchange Server 2013 environment

  • 2931223 MAPI virtual directory is missing from Default Web Site node

Rollup 8 v2 for Exchange Server 2010 SP3

Exchange Team released Rollup 8 for Exchange Server 2010 SP3

Update Rollup 8 for Exchange Server 2010 SP3 resolves security issues that are described in December 2014 security update for Exchange Server 2007 and Exchange Server 2010.
Additionally, this update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 3004235 Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014

  • 3009132 Hybrid mailbox moves to on-premises environment but finishes with CompletedWithWarnings status

  • 3008999 IRM restrictions are applied to incorrectly formatted .docx, .pptx, or .xlsx files in an Exchange Server 2010 environment

  • 3008370 Group members are not sorted by display name when HAB is used with OAB in Exchange Server 2010

  • 3008308 Public folder database migration issue in a mixed Exchange Server environment

  • 3007794 Hub Transport server cannot deliver messages when a database fails over to a cross-site DAG in Exchange Server 2010

  • 3004521 An Exchange server loses its connection to domain controllers if a public folder server is down in Exchange Server 2010

  • 2999016 Unreadable characters when you import ANSI .pst files of Russian language by using the New-MailboxImportRequest cmdlet

  • 2995148 Changing distribution group takes a long time in an Exchange Server 2010 environment

  • 2992692 Retention policy is not applied to Information Rights Management protected voice mail messages in Exchange Server 2010

  • 2987982 Issues caused by ANSI mode in Exchange Server 2010

  • 2987104 Email message is sent by using the “Send As” instead of “Send on Behalf” permission in Exchange Server 2010

  • 2982017 Incorrect voice mail message duration in Exchange Server 2013 and Exchange Server 2010

  • 2977279 You cannot disable journaling for protected voice mail in Exchange Server 2013 and Exchange Server 2010

Download: Rollup 8 v2 for Exchange Server 2010 SP3 (KB2986475)

Rollup 15 for Exchange Server 2007 SP3

Exchange Team released Update Rollup 15 for Exchange Server 2007 SP3

Update Rollup 15 for Exchange Server 2007 SP3 resolves security issues that are described in December 2014 security update for Exchange Server 2007 and Exchange Server 2010.
Additionally, this update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 3004235 Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014

  • 3008308 Public folder database migration issue in a mixed Exchange Server environment

Download the Exchange2007-KB2996150 package now.

Block iOS devices with Block-IOS-Devices.ps1 Script

Microsoft keeps a list of problems: Current issues with Microsoft Exchange ActiveSync and third-party devices

After some problems at a customer i looked deeper at these problems.
Most problems come’s with iOS devices (iPhone and iPad)

Sow I made a list of al iOS versions (6,7 and 8) and there problems.

To keep this simple i created a powershell script: Block-IOS-Devices.ps1 or you can download it from the Technet Script Libary: Block iOS devices with Block-IOS-Devices.ps1 Script

image

Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010, Exchange 2013 and Office 365 when a user syncs a mailbox by using an iOS 6.1-based or iOS 6.1.1-based device

Yesterday i was at customer who had problem dat transaction logs Rapid growl.
It was on a Exchange 2013 Server with CU5.

For Exchange 2010 there was released a KB http://support.microsoft.com/kb/2814847

This is still a issue for Exchange 2010, Exchange 2013 and Office 365.

Microsoft has al ready blocked IOS 6.1 – 6.1.1 devices at Office 365.

Server was OK…. But When i run Get-EASDeviceReport.ps1 i saw some IOS 6.1 devices. Sow we going to block this IOS versions.

Powershell:
New-ActiveSyncDeviceAccessRule -querystring “iOS 6.1 10B141” -characteristic DeviceOS -accesslevel block
New-ActiveSyncDeviceAccessRule -querystring “iOS 6.1 10B142” -characteristic DeviceOS -accesslevel block
New-ActiveSyncDeviceAccessRule -querystring “iOS 6.1 10B143” -characteristic DeviceOS -accesslevel block
New-ActiveSyncDeviceAccessRule -querystring “iOS 6.1 10B144” -characteristic DeviceOS -accesslevel block
New-ActiveSyncDeviceAccessRule -querystring “iOS 6.1.1 10B145” -characteristic DeviceOS -accesslevel block

Tune and optimize performance of your Office 365 connection

Microsoft has published a new course on Office 365 Performance Management at the Microsoft Virtual Academy, which contains 11 modules across planning and troubleshooting areas including:

  1. Office 365 Performance Management Course Introduction
  2. Office 365 Datacenters and Network
  3. Planning for Office 365 Internet Capacity – Exchange Online
  4. Planning for Office 365 Internet Capacity – Lync Online
  5. Planning for Office 365 Internet Capacity – SharePoint Online
  6. The Baselining Model for Internet Capacity Planning
  7. Best Practices & Real Customer Projects Planning Internet Capacity
  8. Planning for Office 365 Firewalls Whitelisting
  9. Performance Troubleshooting Process and Tools Used
  10. Performance Troubleshooting Tests
  11. Troubleshooting SharePoint Online Customizations

Certain pages or windows don’t appear in Outlook Web App or in the Exchange admin center when using Google Chrome

When you use Google Chrome to access Outlook Web App or the Exchange admin center, you’re unable to perform certain actions because certain pages or windows don’t appear expected.
For example, you’re an admin and you want to change a custom attribute for a mailbox. You open the properties of the user, and then under Custom attributes, you click Edit.
However, the page that lists custom attributes doesn’t appear.

Update the policy settings for the browser. To do this, follow these steps.

  1. Click Start, type regedit in the search box, and then click regedit.exe.
  2. Locate, and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\EnableDeprecatedWebPlatformFeatures

    Note If the Google subkey is not present, create it manually. For steps on how to do this, see the More Information section of this article.

  3. On the Edit menu, point to New, and then click String Value.
  4. Type 1, and then press Enter.
  5. Right-click the 1 string value that you created, and then click Modify.
  6. In the Value data box, type ShowModalDialog_EffectiveUntil20150430, and then click OK.
  7. Exit Registry Editor.

http://support.microsoft.com/kb/3001145/en-us?sd=rss&spid=16662

Translate »