Exchange 2010 Queues export, resubmit messages

Sometimes in your Microsoft Exchange environment you can experience a problem with HUB or Edge Transport servers, when often messages stuck in Queues.

When you resolve problem with any Exchange server, sometimes it takes few minutes for Exchange to resubmit all emails, time depends on how many messages are in queues.

Until messages have one of the below status, we can manually resubmit them to the Exchange Submission Queue if queue hasn’t Suspended state:

  • mailbox Delivery queues or Remote delivery queues with status Retry
  • emails in Unreachable queue
  • emails in Poison queue


To manually resubmit messages in queues, you can use the following methods:

  • use the Retry-Queue cmdlet with parameter -Resubmit
  • export messages from queue to .eml message files and resubmit them by placing in the Replay directory. For Exchange 2010 default location:
    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Replay
  • open Queue Viewer or Resume-Message cmdlet to resubmit messages in poison message queue.


Exchange 2010 export message copy from Queue:

Continue reading

Microsoft Exchange 2010 SP3 (Service Pack 3) – announcing

The Exchange Team announced that in the first half of calendar year 2013 will be released Service Pack 3 (SP3) for Microsoft Exchange 2010.


New Service Pack (SP3) for Microsoft Exchange 2010 will contain new features like:


  • Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.
  • Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.
  • Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing

Before you will install Service Pack 3 for Exchange 2010, to add new features, you will need to update Active Directory Schema.


Shared Mailbox deleted and sent items separation

Most of us who has used Shared Mailbox in Microsoft Exchange environment, met with users complaints that emails which they sent a message using the shared mailbox account goes to Sent Items personal mailbox.

This behavior is normall for scenario when we use Microsoft Outlook with personal mailbox and automapped shared mailbox. Then when we delete or send message from shared mailbox account, the message goes to personal recycle bin or sent items.


How can we separate Shared Mailbox deleted and sent items ?

We have two solutions to separate sent and deleted items:

  1. Use Microsoft Outlook 2010 and add shared mailbox as normal mailbox account
  2. Change windows registry on client computer with different Outlook versions


1. Use Microsoft Outlook 2010 for Shared Mailbox to separate sent and deleted items

When you use Microsoft Outlook and you get permissions to shared mailbox, this mailbox will be automapped in Outlook.

After automapping when you send a message from shared mailbox this message will be saved in sent items of your personal mailbox. This behavior often is unwanted.

To make Outlook 2010 to save all sent items or deleted items from shared mailbox to sent items folder or deleted items folder in shared mailbox you have to add shared mailbox as equivalent mailbox in Outlook.

Close Microsoft Outlook 2010 with your personal mailbox, and go to Control Panel, Mail  next in Mail Setup – Outlook window choose:
E-mail Accounts…

Next in Account Settings window choose New…, and select

Manually configure server settings or additional server types

Continue reading

Disable Outlook Mailbox Auto-Mapping

When Microsoft released Microsoft Exchange 2010 SP1 we’ve discovered new feature that allows Microsoft Outlook 2010 and 2007 clients to automatically map mailbox to which a user has Full Access permission.

So if we add user Full Access permission to 10 mailboxes, he will all 10 mailboxes in his Outlook because these mailboxes will be automatically mapped in Outlook.

In Microsoft Exchange 2010 SP1 there was no option to turn this “great” feature off.

But when we get Microsoft Exchange 2010 SP2 we can use Exchange Management Shell (Exchange Powershell) to disable this feature.

When we use Exchange Management Console to add user Full Mailbox Permission to other mailbox, this mailbox will be loaded to user Outlook.


If we want to add user Full Mailbox Permission but we don’t want automap this mailbox to Microsoft Outlook we have to use powershell:

Continue reading

Exchange recipients limit

In fact, this information is easily available on technet, but sometimes it is useful to organize and put them in one place.

Exchange 2010 and Exchange 2007  recipients limit

There is an important change compared to Exchange 2003 – Distribution group are treated as one recipient.

We can restrict recipients limit at the following levels:

  • Organization
  • Transport server
  • Receive Connector
  • Mailbox


Recipient limit  at the organization level, we can check this PowerShell command:

Get-TransportConfig | fl MaxRecipientEnvelopeLimit

or in EMC

Organization Configuration | Hub Transport | Global Settings | Transport Settings tab | Transport Settings Properties

Transport Settings

Continue reading

Microsoft Forefront Product Roadmaps big changes

On September 4th 2012 Microsoft annunced “Important Changes to Forefront Product Roadmaps“.

Microsoft is making big change in server security offerings, specially their oldest server security offering ISA and TMG.


From Microsoft Forefront family product, Microsoft annunced they’re discountinuing releases for:


  • Forefront Protection 2010 for Exchange Server (FPE)
  • Forefront Protection 2010 for SharePoint (FPSP)
  • Forefront Security for Office Communications Server (FSOCS)
  • Forefront Threat Management Gateway 2010 (TMG)
  • Forefront Threat Management Gateway Web Protection Services (TMG WPS)

Continue reading

Microsoft Windows 2012 and Exchange 2010 support

Few days ago Microsoft Windows 2012 became available, but if you are using Exchange 2010 SP2 and want to test it with Windows 2012, you have to wait because Exchange 2010 SP2 is not supported on Windows 2012.

Right now Exchange Team works on update to add support between Windows 2012 and Exchange 2010.

We hope it won’t take too long.

Below you can find supported operating systems for Exchange 2010

Component Requirement
Operating system on a computer that has a 64-bit processor One of the following:

  • 64-bit edition of Windows Server 2008 Standard with Service Pack 2 (SP2)
  • 64-bit edition of Windows Server 2008 Enterprise with SP2
  • 64-bit edition of Windows Server 2008 R2 Standard with SP1
  • 64-bit edition of Windows Server 2008 R2 Enterprise with SP1
  • Windows Server 2008 Datacenter RTM or later
  • Windows Server 2008 R2 Datacenter RTM or later
Operating system for installing the Exchange management tools on a computer that has a 64-bit processor One of the following:

  • Windows Vista with SP2 for management tools only installation
  • 64-bit edition of Windows Server 2008 Standard with SP2
  • 64-bit edition of Windows Server 2008 Enterprise with SP2
  • 64-bit edition of Windows Server 2008 R2 Standard
  • 64-bit edition of Windows Server 2008 R2 Enterprise
  • 64-bit edition of Windows 7


TechEd 2012 Australia & New Zealand Video Sessions

New video sessions from TechEd 2012 in Australia and New Zealand are available at website.
Below you can find list with video sessions about Microsoft Exchange 2013 and Microsoft Lync 2013.


TechEd Australia 2012:

Microsoft Exchange Server 2003 end support

As of August 4th 2014 Microsoft will be ending its support for Microsoft Exchange 2003.

If you are using Microsoft Exchange 2003 and want to have support for Microsoft Exchange products, then you have to start thinking how to upgrade your Exchange environment to newer version Exchange 2007 or 2010.

After August 2014 Exchange 2003 will not be supported by Microsoft anymore.

All Microsoft Exchange Product Lifecycle information Table can be found here:

Microsoft Exchange Support Lifecycle


Symantec Enterprise Vault 8, 9 and 10 Video Tutorials

Anyone who is using Symantec Enterprise Vault should check free video tutorials from Symantec.
Tutorials explains how to install, upgrade, move to a newer version, manage and resolve some problem with Enterprise Vault version 8, 9 and 10.

In Symantec Enterprise Vault tutorials you can find information how to:

  • install or upgrade to newer version of Symantec Enterprise Vault
  • move archives between partitions
  • backup Enterprise Vault
  • manage Vault partitions
  • manage Desktop Policy
  • manage Client Access: OWA 2010


Below you can find list to some of these tutorials:


Symantec Enterprise Vault 9: