Posts Tagged ‘exchange’

Hey Folks,

after updateing a customers’ Exchange 2010 SP3 Server to SP3 Rollup 1 we got massive Problems with the ExchangeTransport Service.

The serivce crashed repeatedly and generated several Event log entries with the following IDs:

4999,10001,10002,10003,12028

The Exchange poison quee was filled up with normal mail traffic.

After uninstalling SP3 Rollup 1 from the HT servers the problem disappeared.

Cheers,

Chris

UPDATE:

My colleague Michael Miklis pointed out to me, that this behaviour is referred in the SP§ RU1 release article:

Known Issue

After this update is applied, there is an issue in which messages stick in a poison queue and the transport service crashes.

This issue is caused by a transport rule (disclaimer) that tries to append the disclaimer to the end of HTML-Formatted messages. When this occurs, messages are put in the poison queue and the transport service crashes with an exception. We are investing resources to develop a code fix. To work around this issue, you can disable or reconfigure the disclaimer transport rule.

(Source: http://support.microsoft.com/kb/2803727/en-us)

I am often approached by clients on Exchange’s singel item recovery feature. Without tools you can only configure the single item recovery feature PowerShell. This article will provide an overview of the necessary steps.

Activation in Exchange 2010
Activate single-item-recovery for all users

get-mailbox -RecipientType ‘UserMailbox’ | Set-Mailbox -SingleItemRecoveryEnabled $true

Set the deleted-item retention for all databases to 30 days

Get-MailboxDatabase | Set-MailboxDatabase -DeletedItemRetention 30

Fetch deleted-item retention, database and server

Get-MailboxDatabase | ft name, server, deleteditemretention

Get an overview about mailbox, logon, size, deleted items filtered by city Hamburg

get-recipient  -RecipientType ‘UserMailbox’ -Filter ‘((City -like ”Hamburg”))’ | Get-MailboxStatistics | ft DisplayName,LastLogonTime,LastLogoffTime,TotalItemSize,DeletedItemCount

Recovery
Recover deleted items from user mailboxes

Mailbox export request

New-MailboxExportRequest -Mailbox “Discovery Search Mailbox” -SourceRootFolder “Folder of deleted Mail” -ContentFilter {Subject -eq “Subject of deleted Mail”} -FilePath \\FileServerName\C$\ExchangeRecovery\RecoveredMails.pst

If you got an error message that the command Search-Mailbox does not exist, simply close and reopen the Exchange Management shell

Import the messages to the user’s mailbox, use the following command:

New-MailboxImportRequest -Mailbox “Username” -TargetRootFolder “Recovered by Admin” -FilePath \\FileServerName\C$\ExchangeRecovery\RecoveredMails.pst

In the Exchange Management Shell, enter the following command:

Search-Mailbox “Discovery Search Mailbox” -SearchQuery “from:’Username’ AND Subject of deleted Mail” -TargetMailbox “Username” -TargetFolder “Recovered by Admin” -LogLevel Full -DeleteContent

Switch back to the client workstation and check if the message has disappeared from the Discovery Search Mailbox.

Open Outlook and review the new folders from the recovery processes.

Cheers,

Chris

If you install Exchange 2013 CU1 in an existing Exchange 2010 SP3 environment you might wonder why you will be redirected to Exchange 2010’s OWA/ECP when trying to open Exchange 2013 EAC.
In a mixed environment you have to add the Exchange client version as parameter:

https://yourEXCHANGE2013-CASServer.yourdomain.com/ecp?ExchClientVer=15

After adding this parameter you should be able to open the EAC.

Cheers, Chris

Originally, we stated we would deliver Exchange 2013 RTM Cumulative Update 1 (CU1) by the end of this quarter.  Unfortunately, we are not going to meet that goal. We know that many of you will be disappointed as a result of this statement. We understand your pain, however, the decision to delay is due to an issue we found in our final test pass coupled with feedback from members within our Technology Adoption Program community.

Specifically, we found an issue with Exchange 2010 coexistence. The issue actually had an easy workaround, but we made a decision; instead of burdening you with a configuration change on all of your Exchange 2010 Client Access servers, we decided to take a code change in Exchange 2013 and solve the problem so that you will not have to make any additional configuration changes. Given that the goal of CU1 is to enable coexistence with legacy versions of Exchange, we felt this was the right decision; after all, we want to ensure that your upgrade to Exchange 2013 and your coexistence period goes as smooth as possible.

As previously mentioned, Exchange 2013’s update strategy is different from previous releases; we are uncoupling security updates and reducing the number of updates we release. In addition to those changes, we will continue to evaluate issues as they are identified during development (even during the final test pass) and if we determine that the vast majority of on-premises customers are affected, we will do everything we can to mitigate the issue prior to release, even if that means delaying the release.

We regret the impact that this delay has on our customers, and as always, we continue to identify ways to better serve your needs through our regular servicing releases. The release date for Exchange 2013 RTM CU1 is currently planned for April 2nd. We will let you know if that date changes, as well as, post an announcement when the download is live.
 

Recently I had a problem while migrating a customers’  Exchange 2003 to MSX2010. The mailbox migration went well, and so we deleted all mailstorage groups on the Exchange 2003 Backend server.

After this we started to move the public folders on a Exchange 2003 Frontend server and triggered the “Move-All-Repicas” script on the Exchange 2010, too.

Nothing happened – no messages in the event log. After several attempts the customer tested to move the public folders on the original BE server and immediately appeared the error: “Error c1050000 MSexchangeIS – Profile is not configured”. (Thank you, Joerg;-))

After brief research, it turned out that this error occurs if on the public folders’ source server no mailbox storage group is configured.

After re-create a storage group and and information store mailbox replication worked as expected.

Cheers,

Chris

Earlier last year, we announced that Exchange 2010 Service Pack 3 would be coming in the first half of 2013. Later, we updated the timeframe to Q1 2013. Today, we’re pleased to announce the availability of Exchange Server 2010 Service Pack 3, which is ready to download.

Service Pack 3 is a fully slipstreamed version of Exchange 2010. The following new features and capabilities are included within SP3:

  • Coexistence with Exchange 2013:Customers who want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.NOTE: Exchange 2010 SP3 allows Exchange 2010 servers to coexist with Exchange 2013 CU1, which is also scheduled to be released in Q1 2013. Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1.
  • Support for Windows Server 2012: With SP3, you can install and deploy Exchange Server 2010 on computers that are running Windows Server 2012.
  • Support for Internet Explorer 10: With SP3, you can use IE10 to connect to Exchange 2010.
  • Customer Requested Fixes: All fixes contained within update rollups released before SP3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In addition to the customer reported issues resolved in previous rollups, this service pack also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

Note: Some of the following KB articles may not be available at the time of publishing this post.

2552121 You cannot synchronize a mailbox by using an Exchange ActiveSync device in an Exchange Server 2010 environment

2729444 Mailboxes are quarantined after you install the Exchange Server 2010 SP2 version of the Exchange Server 2010 Management Pack

2778100 Long delay in receiving email messages by using Outlook in an Exchange Server 2010 environment

2779351 SCOM alert when the Test-PowerShellConnectivity cmdlet is executed in an Exchange Server 2010 organization

2784569 Slow performance when you search a GAL by using an EAS device in an Exchange Server 2010 environment

2796950 Microsoft.Exchange.Monitoring.exe process consumes excessive CPU resources when a SCOM server monitors Exchange Server 2010 Client Access servers

2800133 W3wp.exe process consumes excessive CPU and memory resources on an Exchange Client Access server after you apply Update Rollup 5 version 2 for Exchange Server 2010 SP2

2800346 Outlook freezes and high network load occurs when you apply retention policies to a mailbox in a mixed Exchange Server 2010 SP2 environment

2810617 Can’t install Exchange Server 2010 SP3 when you define a Windows PowerShell script execution policy in Group Policy

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

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

2800080 ErrorServerBusy response code when you synchronize an EWS-based application to a mailbox in an Exchange Server 2010 environment

(Source: EHLO Team Blog)

2012 in review

Posted: January 4, 2013 in Info
Tags: , , , , ,

Hey folks,

I wish all of you a happy new year. Thank you all for visiting my site and supporting me with hints and comments. I look forward to an exciting 2013 with all the new Microsoft products – particulary Exchange 2013.

Cheers, Chris

Here is an extract of the 2012 review:

4.329 films were submitted to the Cannes Film Festival 2012. This Blog had over 17.000  in 2012. If each visitor was a movie, this blog would fill 4 Film Festivals.

Click HERE for the complete review.

Hello folks,

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.

Read more on Tony Redmonds Blog.

Cheers,

Chris

(Source: EHLO Blog )

The need to remove an Exchange 2013 server using ADSIEdit could have several reasons. The method using ADSIEdit to remove an Exchange server should only be used carefully.

The most common reasons are listed below:

  • The deinstallation didn’t finish properly and left attributes or entries in Active Directory
  • The Exchange server is permanent offline and Exchange should be removed
  • An Exchange installation didn’t finish properly and the attributes and entries should be removed

To remove the server open ADSI-Edit and go to configuration

Navigate to this path:

CN=Configuration,DC=DOMAIN,DC=LOCAL
CN=Services
->; DELETE
CN=Microsoft Exchange
CN=Microsoft Exchange Autodiscover

CN=Default naming context,DC=DOMAIN,DC=LOCAL
->; DELETE
CN=Microsoft Exchange Security Groups
CN=Microsoft Exchange Security Objects

Additional steps:

Hard Disk:
On the server’s hard disk you’ve to DELETE the Exchange Server installation folder.
Usually it’s C:\Program Files\Microsoft\Exchange Server

IIS:
DELETE the Exchange Back End and Front End websites with the IIS-Manager

AD Users and Computers:
DELETE the following users in the “Users” container:

DiscoverySearch Mailbox{GUID}
Exchange Online-ApplicationAccount
FederatedEmail.GUID
Migration.GUID
*SystemMailbox{GUID}
*HealthMailboxGUID

Registry:
DELETE the key “ExchangeServer” under:
HKLM\Software\Microsoft

DELETE the keys “MSExchange*” under:
HKLM\CurrentControlSet\Services

Cheers,

Chris

Hi folks,
for several times I wanted to dismount and re-mount one or more mailbox databases from an Exchange 2010 server. It’s a hard way to do this with the EMC so i  figured out the PowerShell commands to do this quick and easy.
Dismount one database:
Dismount-Database -Identity DBNAME -Confirm:$False
Dismount all databases of a server
Get-MailboxDatabase -Server SERVERNAME | Dismount-Database -Confirm:$False
Mount a single database
Dismount-Database -Identity DBNAME -Confirm:$False
Mount all databases of a server
Get-MailboxDatabase -Server SERVERNAME | Mount-Database -Confirm:$False

Cheers,

Chris