Configuring Exchange 2007

Send and Receive Connector scope.

2010-02-01T15:01:00.001Z

Receive Connectors are configured locally for each server.
Send Connectors are configured organization wide for all or some of the servers (Send Connectors are stored in Active Directory).

Receive connectors created automatically on Edge Transport

2010-02-01T14:59:00.001Z

When you deploy the Edge Transport role to a server, it automatically creates two receive connectors. One for incoming messages from the internet and one for incoming connections from Hub Transport servers.
These two Receive Connectors can only start processing email when the Edge Transport server has gone through the Edge Subscription process (or has been configured manually).

Receive Connectors created automatically

2010-02-01T14:56:00.001Z

When you deploy the hub Transport role to a server two "Receive Connectors are automatically created. One that allows clients to send messages (named Client) and one that allows Exchange users, servers and legacy Exchange servers to connect to it.

PowerShell command to enable Premium journaling

2009-11-10T06:56:00.001Z

The PowerShell command to enable premium journaling is as follows :

New-JournalRule –Name <name> –Recipient <smtpaddress> –JournalEmailAddress <smtpaddress>

PowerShell command to enable Standard journaling

2009-11-10T06:53:00.001Z

The PowerShell commands to enable standard journaling are as follows :

Enable-TransportAgent –Identity “Journaling Agent”
Set-MailboxDatabase <name> –JournalRecipient <smtpaddress)

Premium Journaling

2009-11-10T06:50:00.001Z

Journaling in the Enterprise version of Exchange 2007 is per Recipient. It captures all mail (internal or external) for selected individuals. This is sometimes called ‘per recipient’ journaling.

Standard Journaling

2009-11-10T06:48:00.001Z

Journaling in the Standard version of Exchange 2007 is per Mailbox Database only. It captures all mail (internal or external) for all members of a Mailbox Database

Move-Mailbox -RetryTimeout

2009-11-07T01:37:00.001Z

The –RetryTimeout parameter of the Move-Mailbox command specifies the maximum time that a move mailbox command may take before the process is considered failed.

Any move mailbox commands that take longer than this value will fail and the mailbox will not be moved.

Security Groups

2009-10-14T03:08:00.001+01:00

Security groups are normally used for permissions. Although they can be ‘mail enabled’ they generally are not.

Distribution Groups

2009-10-14T03:07:00.001+01:00

Distribution groups are normally used for email and therefore are normally mail enabled.

Public Folder databases

2009-10-14T03:06:00.001+01:00

You may only have one ‘Public Folder Database’ per server.

A ‘Public Folder database’ is automatically created if the user doing the install chooses the option that ‘Outlook 2003 or earlier’ users will connect to this server.

Converting Groups

2009-10-14T03:03:00.001+01:00

A ‘Universal Distribution Group’ can be converted to a ‘Universal Security Group’ as long as all members have active directory accounts.

A ‘Universal Security Group’ cannot be concerted to a ‘Universal Distribution Group’

All members of a ‘Security group’ must have an AD account

2009-10-14T03:00:00.001+01:00

All members of a "’Security Group’ must have an active directory account. That is, no ‘mail contacts’ are allowed in a ‘Security group’

Storage groups and Databases for Enterprise Edition

2009-10-14T02:57:00.001+01:00

In Exchange 2007 Enterprise version there is a maximum of 50 storage groups per server. Each storage group can have a maximum of 5 mailbox databases, one of which is reserved for recovery, per server – to a total of 50 mailbox databases per server.

Storage Groups and Databases for Standard Version

2009-10-14T02:56:00.001+01:00

In Exchange 2007 Standard version there is a maximum of 5 storage groups per server. Each storage group can have a maximum of 5 mailbox databases, one of which is reserved for recovery, per server – to a total of 5 mailbox databases per server.

BadItemLimit

2009-10-14T02:51:00.001+01:00

The ‘BadItemLimit’ parameter can be specified in the Move-Mailbox command to limit the number of corrupt/failed messages that can be tolerated before a mailbox move fails.

Filtering content to be moved

2009-10-14T02:49:00.001+01:00

The content/items that are moved to the destination mailbox when using the Move-Mailbox command can be specified with the following parameters :

-AttachmentFilenames
-ExcludeFolders
-IncludeFolders
-Contentkeywords
-Subjectkeywords
-Locale
-StartDate
-EndDate

Move-Mailbox size limits

2009-10-14T02:44:00.001+01:00

When moving a mailbox, if the mailbox size limits are not set then the mailbox will inherit the size limits of the destination mailbox database.

If the size limits are not set and the source mailbox size is bigger than the limits set on the destination mailbox then the mailbox move will fail – unless the ‘PreserveMailboxSizeLimit’ parameter of the Mailbox-Move command is specified.

Template Mailboxes

2009-10-14T02:34:00.001+01:00

It is a good practice to use a ‘template’ mailbox for Exchange Management Shell creation of new mailboxes.

The template mailbox is specified with the ‘TemplateInstance’ parameter. For example :

$t = Get-Mailbox _templateMailbox
New-Mailbox –Name “Ken Hughes” –UserPrincipalName ken.hughes@ce2007.com –Database “FirstStorageGroup\Mailbox database 1” –Organizationalunit Users –TemplateInstance $t

This allows for more effective / consistant creation of mailboxes.

Move Mailbox tools

2009-10-14T02:22:00.001+01:00

To move a mailbox within the same forest a user may use either the Exchange Management Console or the Exchange management Shell.

If moving across forests then the Exchange Management Shell must be used.

Delay for OWA users after mailbox move

2009-10-14T02:20:00.001+01:00

After moving a mailbox there may be a delay of several minutes for anyone using OWA to access their mailbox.

This is due to OWA requesting the message table, which could take a few minutes to rebuild after a mailbox move, if the mailbox is large

Moving mailboxes from Exchange 5.5

2009-10-14T02:17:00.001+01:00

It is not possible to move a mailbox from Exchange 5.5 directly to Exchange 2007. It must go via Exchange 2000 or Exchange 2003 first.

Create New Mail User using the GUI

2009-09-24T22:56:00.001+01:00

This post outlines how to create a new mail user in Exchange 2007, using the Exchange Management Console.

First open the console then expand ‘Recipient Configuration’, click on the ‘Mail Contact’ node then right click in the right hand pane and choose the ‘New Mail User…’ menu item. This starts the ‘new mail contact’ wizard.

Select the ‘New user’ option and click ‘Next >’.

Choose the ‘Organizational Unit’, populate the other fields and enter the ‘External email address’. When complete, click ‘Next >’.

Give the ‘Mail User’ and ‘Alias’ and enter the ‘External email address’. When complete, click ‘Next >’.

You are then given the opportunity to review the settings and configuration before committing the action. When you have reviewed the detail click ‘New’

The action is then executed. You get a status result telling you how long it took and whether it was successful or not.
It also provides the full Exchange PowerShell command that would create the mail contact exactly as you have just configured via the Console GUI. You can press ‘Ctrl + C’ to copy this command to the clipboard if needed.

Create New Mail Contact using the GUI

2009-09-24T22:04:00.003+01:00

This post outlines how to create a new mail contact in Exchange 2007, using the Exchange Management Console.

First open the console then expand ‘Recipient Configuration’, click on the ‘Mail Contact’ node then right click in the right hand pane and choose the ‘New Mail Contact…’ menu item. This starts the ‘new mail contact’ wizard.

Select the ‘New contact’ option and click ‘Next >’.

Choose the ‘Organizational Unit’, populate the other fields and enter the ‘External email address’. When complete, click ‘Next >’.

You are then given the opportunity to review the settings and configuration before committing the action. When you have reviewed the detail click ‘New’

Create New User Mailbox using the GUI

2009-09-24T00:17:00.001+01:00

This post outlines how to create a new mailbox in Exchange 2007, using the Exchange Management Console.

First open the console then expand ‘Recipient Configuration’, click on the ‘Mailbox Node’ then right click in the right hand pane and choose the ‘New Mailbox…’ menu item. This starts the ‘new mailbox’ wizard.

Select the ‘User Mailbox’ option and click ‘Next >’

Choose the ‘Organizational Unit’ and populate the other fields. When complete, click ‘Next >’

Enter the mailbox settings details, choose the required ‘Storage group’ and ‘Mailbox database’, and any required ‘Managed folder mailbox policy’ and/or any required ‘Exchange ActiveSync mailbox policy’.
When complete click ‘Next >’

You are then given the opportunity to review the settings and configuration before committing the action. When you have reviewed the detail lick ‘New’

The action is then executed. You get a status result telling you how long it took and whether it was successful or not.
It also provides the full Exchange PowerShell command that would create the mailbox exactly as you have just configured via the Console GUI. You can press ‘Ctrl + C’ to copy this command to the clipboard if needed.