ExchangeBlog » Tag » Microsoft Exchange 2010

Tag Archives: Microsoft Exchange 2010

Exchange 2010 Management Pack for SCOM known issues KB2592561

  By Remigiusz Szatkowski | 15/01/2013 - 10:38 | ,
Leave a comment

In KB2592561 article you can find informations about known issues with Exchange 2010  Management Pack and SCOM 2012 or SCOM 2007

 

scom2012

 

This article is recommended for all of people using SCOM to monitor Exchange 2010 environment.

If you have any problems in SCOM with Exchange 2010 MP you shoudl first look through this document before calling for support or posting to the forums as the issue may be covered below.

This articles is applyed to:

  • Microsoft System Center Operations Manager 2007 R2
  • Microsoft System Center Operations Manager 2012

 

Guidance, Tuning and Known Issues for the Exchange 2010 Management Pack for System Center Operations Manager

 

 

 

Exchange 2010 Event ID 4999 Msftefd.exe process crashes

  By Remigiusz Szatkowski | 26/12/2012 - 03:03 |
1 Comment

When you work with Microsoft Exchange 2010 SP2 with Rollup 4 or a later update rollup that is earlier than Update Rollup 6 installed, you can meet with Event ID 4999.

If you get following events on mailbox server:

Source: MSExchange Common
Date: Date
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
Watson report about to be sent for process id: Process ID, with parameters: E12, Build Type, Version Number, ExMSFTE, M.E.Search.ExSearch, M.E.S.Crash.CrashNow, M.E.Common.FailFastException, XXXX, Version Number.
ErrorReportingEnabled: False

Log Name: Application
Source: MSFTESQL-Exchange
Date: Date
Event ID: 64772
Task Category: MSFTESQL Service
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
The filter daemon process MSFTEFD exited unexpectedly.

Log Name: Application
Source: MSFTESQL-Exchange
Date: Date
Event ID: 1053
Task Category: MSFTESQL Service
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
The system exception c000010a was raised at 000007FEF99D0F16.

Continue reading →

Exchange Server 2010 mass export mailboxes to pst file

  By Remigiusz Szatkowski | 05/12/2012 - 03:03 | ,
Leave a comment

Last time we wrote how to export mailbox from Exchange 2010 to pst file and import items from pst file to Exchange 2010 mailbox.

Exchange 2010 export import mailboxes

Now we will explain how to export few mailboxes at once from Exchange 2010.

When you want to export few mailboxes at once to .pst files you have to get aliases of those mailboxes and then run New-MailboxExportRequest in ForEach loop.

Below we present few examples how to export mailboxes with specified conditions:

To export mailboxes from specified mailbox database use:

ForEach ($mbx in (Get-Mailbox -Database DatabaseName)) {
 New-MailboxExportRequest -Mailbox $mbx -FilePath "\\server\share_pst\${$mbx.Alias).pst" 
}

Continue reading →

Exchange Server 2010 “How do I” video center

  By Remigiusz Szatkowski | 19/11/2012 - 06:00 |
2 Comments

 

On TechNet Webistes we can find few movies discussing Exchange Server 2010 administration. This films series is entitled “How do I ?”

 

 

We can find there 26th movies which discussing few issues with Exchange Server 2010 environment. Movies are available in MP4 and WMV files.

Issues discussing in movies:

  • Exchange 2010 Deploy
  • Exchange 2010 Operate
  • Exchange 2010 Migration
  • other technical issues

 

Continue reading →

Exchange 2010 SP2 Error after upgrading to Rollup 5

  By Remigiusz Szatkowski | 16/11/2012 - 06:38 |
7 Comments

 

Unfortunately last update released by Microsoft for Exchange 2010 SP2 (Rollup 5) causes many issues with Exchange DAG.

After installation of Rollup 5 for Exchange 2010 SP2 you will receive EventID 4999 in Event Log and also you won’t be able to run Get-DatabaseAvailabilityGroup -Status and the MSExchangeADTopology service started acting strangely.

Like we said first test this Rollup 5 in your test environments.

In Event Log you will find errors 4999 like below about watson:

Watson report about to be sent for process id: 792, with parameters: E12, c-RTL-ADM64, 14.02..0318.004 RemotePowershell, M Exchange Management 
M.E.C.R dagTaskHelper.GetServersInDeferredRecovery, System.TypeLoadException, 253d, 14.02.0328.005

 

and when you run below command:

Get-DatabaseAvailabilityGroup -Identity DAG01  -Status

 

you will receive error like below:

 

After uninstallation of Rollup 5 all errors goes away.

So for now we recommend do not install this rollup in production environment.

 

 

 

Update Rollup 7 Version 3 for Exchange Server 2010 SP1 (Service Pack 1) (KB2778158)

  By Remigiusz Szatkowski | 14/11/2012 - 19:31 |
Leave a comment

 

Microsoft released also new update for Microsoft Exchange Server 2010 SP1.

It’s not exactly new update, but new version of last update Rollup 7.

We wrote about Rollup 7, next Rollup 7-v2 and now we want to inform about Rollup 7-v3 for Exchange Server 2010 SP1.

This new version of Rollup 7 resolves an issue in which the digital signature on files produced and signed by Microsoft expires prematurely.

This update replaces the original KB2743248 and KB2756496 updates.

After installation of new version of Rollup 7 (Rollup 7-v3) your Exchange Server will have new version number 14.1.421.3

 

you can download this new “update” Rollup 7-v3:

 Rollup 7-v3 for Exchange Server 2010 Service Pack 1 (KB2778158)

 

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

Description of Update Rollup 7 Version 3 for Exchange Server 2010 Service Pack 1

 

Exchange 2010 unable to sent Out of Office, Mail Tips problem

  By Łukasz Giemzik | 31/07/2012 - 23:26 | , ,
1 Comment

The problem of the peculiar cycle of failure.
Exchange 2010 no longer generate an automatic response (AutoReplay Outlook Out of Office). In Outlook 2010 does not also appear in the mail tips for absence.
There was no problem with setting OOF via Outlook and OWA.
Proved to be helpful to restart the Exchange Mailbox Assistants Services on the server.
The problem is basically trivial, but maybe someone will save time. The more that in Google for similar problems przypadu meets reconfiguration proposals and EWSa Autodiscover.
So before we start all over again to configure all the paths WebServices supported by the Exchange, we first try to restart the Exchange Mailbox Assistants service, perhaps so that we save a lot of time.

The solution can also be an additional dismount the database and mount it again.

In the case of DAG environment, just for a moment change the active database to another located on another server.