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:
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
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
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.
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.
http://support.microsoft.com/kb/3001145/en-us?sd=rss&spid=16662
Microsoft has recently updated the Microsoft Exchange 2013 Public Folders Directory Sync Support Scripts to version 15.00.1017.003.
Brief Description
Scripts to enable creation of public folder related objects in the O365 Active Directory and synchronization of public folder related Active Directory objects between on-premise and O365 directories.
Overview
Use this scripts if you need to do one of the following – – Initial creation of mail enabled public folder objects in the destination Active Directory for public folder migration from Exchange 2007 or 2010 to Exchange 2013 – Synchronization of mail enabled public folder objects from cloud to on-premise Active Directory – Synchronization of mail enabled public folder objects from on-premise to cloud Active Directory – Synchronization of public folder mailbox objects from cloud to on-premise Active Directory
On August 26 Microsoft released Exchange 2013 CU6, the sixth Cumulative Update since the new servicing model of Exchange.
Unfortunately this Update in is facing issues. Some customers found two issues with Exchange 2013 CU6:
Both issues were quickly identified by Microsoft and a fix is already available.
Microsoft released a new KB article about a performance issue with Exchange 2013
When you connect to a Microsoft Exchange Server 2013 server that is installed in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008 in which Microsoft .NET Framework 4.5 is included, you may experience delays to access email messages or disconnections to the Exchange server. When this issue occurs, the CPU or memory usage on the server is high for some services that include one or more of the W3wp.exe processes.
This issue occurs because too many objects are pinned on the .NET Framework 4.5 garbage collector heap. It causes heap fragmentation in addition to an increase in CPU and memory usage by the garbage collector.
Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
Apply hotfix 2803755 that needs a restart, and then use one of the following methods to enable the hotfix:
HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework
Then, restart the computer.
Create a DWORDvalue of the DisableRetStructPinning entry at the following registry subkey, and set the DWORD value to1:
HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework
Then, restart the computer.
Apply hotfix 2803754 that needs a restart, and then use one of the following methods to enable the hotfix:
HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework
The Exchange Team released Cumulative Update 6 for Exchange Server 2013 (KB2936880). This update raises Exchange 2013 build number to 15.0.995.29.
This Cumulative Update increases the Public Folder for Exchange On-Premises to 100,000. It also fixes the ‘Hybrid Configuration Wizard ‘Subtask Checkprereqs Execution Failed’ issue (2988229).
This Cumulative Update contains the following fixes:
2991934 Duplicate mailbox folders after migration to Exchange Server 2013
2983512 RPC Client Access service crashes on an on-premises Mailbox server in an Exchange Server 2013 hybrid environment
2983426 AutodiscoverSelfTestProbe fails when external URL is not set for EWS virtual directory in Exchange Server 2013
2983423 AutodiscoverSelfTestProbe fails when external URL is not set for ECP virtual directory in Exchange Server 2013
2983422 The ServerWideOffline component is set to Inactive after Exchange Server 2013 prerequisite check fails
2983207 “532 5.3.2″ NDR when you send an email message to a hidden mailbox in an Exchange Server 2013 environment
2983066 Removed Default or Anonymous permission for Outlook folders cannot be restored in an Exchange Server 2013 environment
2982769 “Topology service cannot find the OWA service” when you perform an eDiscovery search in Exchange Server 2013
2982763 Mail-enabled public folder accepts email messages from unauthorized users in an Exchange Server 2013 environment
2982762 OAB generation arbitration mailbox can be removed or disabled in an Exchange Server 2013 environment
2982760 The Enter key submits duplicate sign-in forms to Outlook Web App in an Exchange Server 2013 environment
2982759 You cannot access the archive mailbox of a delegated user after enabling MAPI over HTTP
2982017 Incorrect voice mail message duration in an Exchange Server 2013 environment
2981835 You cannot add attachments, delete or move many email messages in bulk in Outlook Web App
2981466 MAPI/CDO client cannot connect to Exchange Server 2013
2977279 You cannot disable journaling for protected voice mail in an Exchange Server 2013 environment
2975599 Exchange Server 2010 public folder replication fails in an Exchange Server 2013 environment
2975003 Calendar item body disappears in Outlook online mode in an Exchange Server 2013 environment
2974339 OAB generation fails if FIPS is used in an Exchange Server 2013 environment
2971270 Blank page after you sign in to Exchange Server 2013 EAC (formerly ECP)
2970040 Folder Assistant rule does not work correctly in an Exchange Server 2013 environment
2965689 EAS device cannot sync free/busy status if an item is created by EWS in an Exchange Server 2013 environment
2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013
2961715 “Something went wrong” error in Outlook Web App may show an incorrect date
2958434 Users cannot access mailboxes in OWA or EAS when mailbox database is removed
Download Exchange 2013 Cumulative Update 6 here; UM Language Packs download here.
The Exchange Team released Rollup 7 for Exchange Server 2010 Service Pack 3 (KB2961522). This update raises Exchange 2010 version number to 14.3.210.2.
Fixes:
Download Exchange 2010 SP3 Rollup 7 here.
An important update is now available to resolve issues customers are currently experiencing when using the Hybrid Configuration Wizard (HCW) to create a new or manage an existing hybrid deployment with Microsoft Exchange Server 2013.
If you currently have an Exchange 2013-based hybrid deployment configured, you will not notice any issues unless you rerun the HCW as part of updating or managing your existing hybrid features. Unless you need to reconfigure your hybrid deployment, you can simply wait for the next update of Exchange Server 2013 (Cumulative Update 6) to correct this issue with the HCW.
For Exchange 2013 organizations creating new or managing an existing hybrid configuration with the HCW, the following HCW error message indicates you are experiencing the issue this update addresses:
Subtask CheckPrereqs execution failed: Check Tenant Prerequisites Deserialization fails due to one SerializationException: Microsoft.Exchange.Compliance.Serialization.Formatters.BlockedTypeException: The type to be (de)serialized is not allowed: Microsoft.Exchange.Data.Directory.DirectoryBackendType
If you experience this issue, contact Microsoft support to obtain the fix as documented in KB2988229. This fix requires Exchange Server 2013 Service Pack 1 (SP1) or Cumulative Update 5 (CU5).
Once the Interim Update (IU) is applied, customers can successfully run the HCW and complete configuring a hybrid deployment with Office 365.