ExchangeBlog »

Monthly Archives: February 2013

Update Rollup 6 for Exchange Server 2010 Service Pack 2 KB2746164

  By Remigiusz Szatkowski | 13/02/2013 - 06:52 |
Leave a comment

Today 02/12/2013 Microsoft released Rollup 6 for Exchange Server 2010 SP2

After you install this Rollup 6 you will update Exchange Server 2010 SP2 version number to 14.2.342.3

This update resolves issues that were found in Exchange Server 2010 Service Pack 2 since the software was released.

 

Ex2010RU6

This is a cumulative rollup as always so you don’t need to install previous versions.

This update rollup is highly recommended for all Exchange Server 2010 Service Pack 2 customers.

Rollup 6 for Exchange Server 2010 SP2 is available here:

Update Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164)

 

List of all build numbers of Microsoft Exchange Server you can find here:

Microsoft Exchange build and version numbers

 

As always we recommend do not install new Rollups in production environment, you should test it first in LAB.

For a list of changes that are included in this update rollup, see:

Description of Update Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164)

 

Update Rollup 10 for Exchange Server 2007 Service Pack 3 KB2788321

  By Remigiusz Szatkowski | 13/02/2013 - 06:44 |
Leave a comment

Today 02/12/2013 Microsoft released Rollup 10 for Exchange Server 2007 SP3

After you install this Rollup 10 you will update Exchange Server 2007 SP3 version number to 8.3.298.3

This update resolves issues that were found in Exchange Server 2007 Service Pack 3 since the software was released.

 

Ex2007RU10

 

This is a cumulative rollup as always so you don’t need to install previous versions.

Rollup 10 for Exchange Server 2007 SP3 is available here:

Update Rollup 10 for Exchange Server 2007 Service Pack 3 (KB2788321)

 

List of all build numbers of Microsoft Exchange Server you can find here:

Microsoft Exchange build and version numbers

 

As always we recommend do not install new Rollups in production environment, you should test it first in LAB.

For a list of changes that are included in this update rollup, see:

Description of Update Rollup 10 for Exchange Server 2007 Service Pack 3

 

 

iOS 6.1 and Exchange 2010 apid growth in transaction logs, CPU use, and memory consumption KB2814847

  By Remigiusz Szatkowski | 12/02/2013 - 08:42 | ,
Leave a comment

Finally Microsoft published article about problems with iOS 6.1 and Microsoft Exchange Server.

 

When user with mobile devices with iOS 6.1 syncs mailbox Microsoft Exchange Server resources are consumed, transaction logs growth becomes excessive, memory and CPU use may increase significantly,a nd server performance is affected.

You can read about it here:

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

 

Right now, Apple and Microsoft are investigating this issue. When they find any fix, it will be published as soon as it will becomes available.

If you have such problems in your Exchange environment you should open case with Apple Support.

Now Microsoft recommend only Workarounds:

Continue reading →

Devices with iOS 6.1 cause Exchange excessive transaction log growth

  By Remigiusz Szatkowski | 11/02/2013 - 00:35 | ,
Leave a comment

apple_wormNew upgrade for Apple devices like IPhone or IPad to iOS 6.1 can couse Exchange Admins headache.

With new version of iOS (iOS 6.1) we have new problems, users connecting to Microsoft Exchange mailboxes using mobile devices with iOS 6.1 can generate excessive transaction logs.

This is caused by syncing mail and calendar services, devices with iOS 6.1 seemed to go into a loop and ended up by generating some 50GB of transaction logs.

This situation can be dangerous for Microsoft Exchange server, because when free space for transaction logs will end, then Exchange will dismount mailbox database.

Upgrading Apple devices to new iOS to fast is not recommended.

Continue reading →

Exchange 2010 remove disabled users from distribution group

  By Remigiusz Szatkowski | 08/02/2013 - 06:25 |
7 Comments

To keep Exchange Distribution Groups in order, we recommend to “clean” members of those groups.

We should remove all disabled users from distribution groups.

When we have a lot of Distribution Group we can use powershell script like below to do this.

This script gets all Distribution Groups from Exchange Organization, then will check every group for users which are disabled and they have Active Directory account in specified OU.

This script will also export all informations to a .csv file, where you can find following informations:

 

  • Name of distribution group
  • user DisplayName
  • SamAccountName
  • path in Active Directory to user account

Continue reading →

Exchange Server 2013 TechNet video

  By Remigiusz Szatkowski | 06/02/2013 - 23:01 |
Leave a comment

On TechNet websites you can find two new online videos about Microsoft Exchange Server 2013.

Both videos are about an hour long.

Watching these videos you can get familar with Exchange Server 2013.

 

Fist video: What´s new in Exchange 2013? explains what’s new in Microsoft Exchange 2013 like new architecture, HA, and features.

 

Exchange2013_video_WhatNew

Continue reading →

Exchange 2010 SP2 after install RU4 message delivery is delayed on a BlackBerry mobile device

  By Remigiusz Szatkowski | 06/02/2013 - 06:30 | ,
Leave a comment

Microsoft has confirmed problems with message delivery to BlackBerry mobile devices after installation of Rollup 4 for Microsoft Exchange 2010 SP2.

This issue occurs only in specific Microsoft Exchange and BlackBerry Enterprise Server environment.

In this scenario:

  • You install Update Rollup 4 for Microsoft Exchange Server 2010 SP2 in an environment that is running against a Blackberry Enterprise Server (BES).
  • The BES uses MAPI or Collaborative Data Objects (CDO), instead of Exchange Web Services (EWS), to communicate with Exchange servers.
  • The mailbox contains many folders. For example, the mailbox contains more than 5000 folders.

You can encounter one or more of the following issues:

  • Email message delivery to the mailbox on a BlackBerry mobile device is delayed.
  • It takes a longer time to complete a folder hierarchy scan in the mailbox. For example, before Update Rollup 4 for Exchange Server 2010 SP2 was installed, a scan that typically takes 5 minutes may now take 30 minutes to 1 hour.
  • The Microsoft Exchange Information Store process (store.exe) on the Exchange Mailbox server may use excessive CPU resources.
  • Some BES event log entries are logged on the Exchange Mailbox server. Before Update Rollup 4 for Exchange Server 2010 SP2 was installed, these entries are less in occurrence or nonexistent.
  • Some events are logged in the BlackBerry Messaging Agent (MAGT) log. These events that are logged in the BlackBerry MAGT log resemble the “Busy Working” threads that are described in the following article in the BlackBerry Knowledge Base: Users may experience delayed email after upgrading to Microsoft Exchange 2010 SP2 Rollup 4 or Microsoft Exchange 2010 SP2 Rollup 5

 

Currentl there is no HotFix to resolve those problems. Probably Rollup 6 for Exchange 2010 SP2 will fix this.

But Microsoft recommend below workaround:

Method 1

Install Exchange Server Service Pack 2 RU 6 when it becomes available.

Method 2

Add more agents on the BES if they are not already at the max of 15 agents.

Method 3

Temporarily reduce the number of folders in the mailbox of the user.

Method 4

Move all users who have high folder counts (>500) to their own instances of BESAgent.exe.

 

More informations you can find here:

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

 

Exchange 2010 how to control Mailbox Database Provisioning

  By Remigiusz Szatkowski | 04/02/2013 - 06:34 |
Leave a comment

radar

With previous versions of Microsoft Exchange (2007 and 2003) when we created mailbox we had to specify mailbox database for this mailbox.

In Microsoft Exchange 2010 during mailbox creating we can let exchange to choose the database for new mailbox, or we have to select option that we want to select mailbox database.

This feature is called Automatic Mailbox Distribution – this feature allow Exchange to choose mailbox database for newly created mailbox if we don’t specify mailbox database.

By default in Microsoft Exchange 2010 all mailbox databases are enabled for provisioning, but we can disable them by setting mailbox database parameters IsExcludedFromProvisioning or IsSuspendedFromProvisioning.

IsExcludedFromProvisioning – we should use this setting to permanently exlude mailbox database from automatic mailbox distribution

IsSuspendedFromProvisioning - we should use this setting to temporarily exclude mailbox database from automatic mailbox distribution.

To check provisioning settings for mailbox databases we can use:

Get-MailboxDatabase | select name, *provisioning

Continue reading →

Exchange Environment Report script 1.5.6 – Steve Goodman

  By Remigiusz Szatkowski | 01/02/2013 - 03:47 | ,
3 Comments

ExchangeEnvironmentscript

Few days ago Steve Goodman published new version of Get-ExchangeEnvironmentReport.ps1 script on his Blog.

This script is really cool, and using it you can easly create report of your Mircosoft Exchange environment. 

 

New version supports Microsoft Exchange 2013 and fixes bugs reported by users.

We think that every Exchange administrator should has this script.

Executing the script is straightforward – the only setting you need is to specify where to write the HTML file:

.\Get-ExchangeEnvironmentReport  -HTMLReport c:\report.html

If you want it to email the results, the follow parameters are available to allow the report to be sent directly from the script:

.\Get-ExchangeEnvironmentReport  -HTMLReport c:\report.html -SendMail:$true -MailFrom:you@example.com -MailTo:you@example.com -MailServer:smtp.example.com

 

Read more about this script: Steve Goodman Blog

You can download this script here: Get-ExchangeEnvironmentReport.ps1