Archive pour Exchange

Ajouter le role Full acces sur une BAL exchane 2007

En rapport avec le billet precedent

Add-MailboxPermission « Mailbox » –User « Trusted User » –AccessRights FullAccess

Missing Private Key on Exchange Certificate


Lire la suite

Where are Mailbox Total Items & Size (KB) Columns?

You would have noticed that you are not able to see the Total Items and Size (KB) of user’s mailboxes in Exchange Management Console of 2007. Even you are not able to add columns optionally.


Like you were able to see in Exchange System Manager of version 2003 displayed below.


Lire la suite

How to Export and Import mailboxes to PST files in Exchange 2007 SP1

There might be times when an Exchange Administrator will need to export the contents of individual mailboxes to offline files in order to present specific users with a format that is easily portable and ready to consume using Outlook clients. To fulfill this need Exchange 2007 SP1 will have a new set of features to export and import mailboxes to and from PST files. As I know you will ask – yes, those PST files can be bigger than 2 GB, which was a limitation of Exmerge tool used for this purpose in previous versions of Exchange.

Export/Import to PST Requirements

In order to export or import mailboxes to PST files the following requirements must be met:

  • Export/Import to PST must be run from a 32 bit client machine with Exchange Management Tools installed (Version Exchange 2007 SP1 or later). The 32bit requirement comes from a dependency with the Outlook client.
  • Either Outlook 2003 or Outlook 2007 must be installed on the client machine.
  • The user running the task must be an Exchange Organization Admin or an Exchange Server Admin on the server where the mailbox to export/import lives.

Exporting mailboxes to PST files

The most basic cmdlet to export a mailbox to a PST file is as follows:

Export-Mailbox –Identity <mailboxUser> -PSTFolderPath <pathToSavePST>

PSTFolderPath must be a full path pointing either to a directory or to a (.pst) file. If a directory is specified a PST file named after the mailbox alias will be used as the target of the export. Note that if the PST file already exists the contents of the mailbox will be merged into it.


After the cmdlet finishes execution, the .pst file will be ready in the specified location:

To export multiple mailboxes to their respective .pst files at once you can pipe in the identities of those mailboxes to the export task. Notice that when bulk exporting the PSTFolderPath parameter must forcefully point to a directory since one .pst file will be created for each mailbox.


Get-Mailbox -Database ‘MDB’ | Export-Mailbox -PSTFolderPath D:PSTs

Importing mailboxes from PST files

The process for importing mailbox contents from a PST file is quite similar:

Import-Mailbox -Identity <mailboxUser> -PSTFolderPath <PSTFileLocation>

Again, PSTFolderPath must be the full path to the directory where the .pst file lives or to the (.pst) file itself. In the case where PSTFolderPath points to a directory the cmdlet will try to match the mailbox alias with the name of an existing .pst file in the specified directory and import the content of that file.


Just as with the export to PST scenario, when bulk importing mailboxes the PSTFolderPath must forcefully point to a directory and the task logic will try to match mailboxes alias with the .pst file names under that location. If no match is found for a particular mailbox, that mailbox will be skipped.


Get-Mailbox -Database ‘MDB’ | Import-Mailbox -PSTFolderPath D:PSTs

Filtering content in Export/Import to PST

When only specific content is desired in the PST file (or back into the mailbox) a common set of filters can be used to leave out the rest of the messages. Export/Import to PST support the following filters: Locale, StartDate, EndDate, ContentKeywords, SubjectKeywords, AttachmentFileNames, AllContentKeywords, SenderKeywords, and RecipientKeywords.

Example: Import only those messages that were created between 1/1/06 and 12/1/06 and contain the word « review » in the subject and any of the words {« project », »alpha »} in the body.

Import-mailbox -Identity ricardr -PSTFolderPath D:PSTs -StartDate 1/1/06 -EndDate 12/1/06 -SubjectKeywords:’review’ -ContentKeywords:’project’,’alpha’

Now, we realize that you would like to try this today, but please be patient!

Exchange Server 2007 Transport: 452 4.3.1 Insufficient system resources

Posted by Bharat Suneja at 5:24 PM In my hotel room in Orlando, getting ready for a presentation tomorrow morning at TechMentor. When trying to telnet to the SMTP port of an Exchange Server 2007 Hub Transport server, I got the following error:

452 4.3.1 Insufficient system resources

Not a good thing the night before a presentation – Murphy’s law at work again!

The Application Event Log has Event ID 15002 from MSExchangeTransport saying « The resource pressure is constant at High. Statistics… « . The event goes on to tell you that inbound mail submission has stopped, and it’s due to disk space being low on the volume where the queue database is located.

Figure 1: Event ID 15002 logged by MSExchangeTransport

Exchange Server 2007 transport queues are not the familiar .eml files you see in Exchange Server 2003/2000, which reside in the mailrootvsi <1>queue folder (<1> is the instance number of the SMTP virtual server) on the file system. Queues have been moved to a JET database.

What’s Back Pressure?
In Exchange Server 2007, the Transport service monitors system resources such as disk space and memory on Transport servers (the Hub Transport and the Edge Transport servers), and stops message submission if it is running low on these resources. It continues to deliver existing messages in the queue. When resource utilization returns to normal, it resumes message submission. The feature is called Back Pressure.

In this case, Exchange required 4 Gigs of free disk space on the volume where the Queue database was located – I had about 3.95 Gigs. 🙂

Service Pack 1
Changes to Back Pressure settings in Exchange Server 2007 SP1

The Back Pressure settings in Exchange Server 2007 RTM stop inbound mailflow if free disk space is below 4 Gigs. This static threshold has been lowered in SP1 to a more realistic 500 Mb.

The Resolution
Many configuration options for transport servers are saved in an XML file named EdgeTransport.exe.config (same file name on both Edge and Hub Transport servers) located in Exchange ServerBin. You can edit the file to disable Back Pressure, or modify the parameters to more accurately define what’s high utilization for your deployment or server configurations, as explained in the above docs.

Another resolution, and the one I used in this case, was to move the Queue database to another volume with ample of free space, using the following procedure:

  1. Add the following key in the <AppSettings> section in EdgeTransport.exe.config:

    <add key= »QueueDatabasePath » value= »D:QueueQueueDB » />

    This is documented in « How to Change the Location of the Queue Database« 

  2. Restart the MSExchangeTransport service, and message submission resumes.

Related Posts:
Exchange Server 2007: How to turn off the Back Pressure feature on transport servers

How to Install / Uninstall Anti-Spam in Exchange 2007

How to Install / Uninstall Anti-Spam in Exchange 2007

In Exchange 2003 the Anti-Spam system is part of the exchange installation and can be enabled or disabled by marking the relevant component on the SMTP Virtual Server:

Exchange 2007 is built differently and a new element called Edge was added in order to handle Spam and Viruses, and because of this the traditional Anti-spam system is not installed as a default during the Exchange 2007 installation.

When you are not installing the Edge server role as a mailrelay, but you still want to use the Anti-Spam system that that is part of Exchange 2007, you need to install it from a PowerShell script that was installed during the Exchange 2007 installation on the Hub transport role. To do this, follow the instructions listed below.

Installing Exchange 2007 Anti-spam system

  1. Close the EMC (Exchange Management Console).
  2. Open the PowerShell and navigate using the following path: « Program FilesMicrosoftExchange ServerScripts« .
  3. Run the « install-AntispamAgents.ps1 » script as shown in window (with ./ before the script name) below:


  4. Restart the « Microsoft Exchange Transport » service in order to apply configuration changes.
  5. Open the Exchange Management Console, and on the Organization configuration list, select Hub Transport. The « Anti-Spam » tab has been added to the Hub Transport properties.


Uninstalling Exchange 2007 Anti-spam system

If from some reason, you would like to uninstall the Anti-Spam system from the Hub Transport role, follow the next steps:

  1. Close the EMC (Exchange Management Console).
  2. Open the PowerShell and navigate using the following path: « Program FilesMicrosoftExchange ServerScripts« .
  3. Run the « uninstall-AntispamAgents.ps1 » script as shown in window (with ./ before the script name) below:
    Note: You will be prompt to disable and then uninstall each agent of the Anti-spam system like the Connection filtering, content filter, Sender filtering etc.


  4. Restart the « Microsoft Exchange Transport » service in order to apply configuration changes.
  5. Open the Exchange Management Console, and on the Organization configuration list, select Hub Transport. You will see that the « Anti-Spam » tab has been removed from the Hub Transport properties.