For several versions of Exchange Server now we’ve had the capability to manage email addresses for recipients by using policies. In Exchange Server 2010 these are referred to as Email Address Policies.

In this article I’ll provide an overview of the key concepts of email address policies and demonstrate some examples of how they can be used.

The Exchange Server 2010 Default Email Address Policy

Any Exchange 2010 organization will have one email address policy named “Default Policy”. You can view this in the Exchange Management Console under Organization Configuration -> Hub Transport, in the Email Address Policies tab.

Exchange 2010's default email address policy

One of my gripes with managing email address policies in the console is that you can’t open a Properties view to see how they are configured. However you can right-click and choose Edit to achieve the same outcome.

The first thing you’ll notice that the default policy is not scoped to any particular recipient container, so it will apply to any object in Active Directory. The other thing you’ll notice is that the policy will apply to “All recipient types”, not a limited subset of the available types such as mailboxes, contacts, or groups.

Scope of the default email address policy in Exchange 2010

At the next dialog you get a chance to preview the results of the conditions in the email address policy.

Previewing the results of email address policy conditions

If you preview the default email address policy you should see all mail-enabled objects in the organization returned.

At the next dialog you’ll see the email addresses that the policy will apply to those recipients that fall within the scope of the policy.

Email addresses applied by the default email address policy

So the outcome of this policy is that it will apply an email address of alias@exchangeserverpro.net (because alias is used if nothing else is specified) to any recipient type.

When are Exchange 2010 Email Address Policies Applied?

But when does the email address policy apply? At the next dialog we can see the schedule options for the email address policy.

Email address policy schedule options

The options we can choose from are:

• Do not apply – the email address policy will be created (or edited) but not applied to the recipients that fall within its scope
• Immediately – the email address policy will be applied immediately to the recipients that fall within its scope
• At the following time – the email address policy will be applied at the nominated time. This is convenient if you are preparing the email address policy in advance of a scheduled change (such as the rebranding exercise I mentioned earlier)

Something you need to be aware of is that no matter which of the above options you pick right now, the email address policy will continue to be assessed and applied to recipients on an ongoing basis in the future each time a recipient is created or modified.

So for example when a new mailbox is created the email address policies are assessed and applied accordingly. Similarly, if you modify an existing mailbox user, for example to change their alias or move it to another database, the email address policies will be reassessed for that recipient.

For that reason you want to be sure that any email address policy that exists in your organization is ready to be applied to recipients.

Creating a New Email Address Policy with the Exchange Management Console

Click New E-Mail Address Policy to start creating a new policy.

New Email Address Policy

For this example I’ve narrowed the scope of the email address policy to just one particular OU for “Example Corp”, the new business entity.

Select recipient container for new email address policy

If that particular OU contained users in other companies I could also narrow the scope down based on Company or Department attributes, but in this example I don’t need to. Clicking Preview shows me the one user that exists in that OU so far.

Email address policy conditions

Next I’ll add an SMTP address of %m@example.com to the policy (%m = “alias”).

Configuring SMTP addresses for an email address policy

Note that whatever domain you choose to use here needs to have already been configured as an Accepted Domain for the organization. If you haven’t already done so you can switch back to the Exchange Management Console and add the domain without having to cancel your new email address policy wizard.

Finally I will choose not to apply the email address policy just yet, so that I can demonstrate some scenarios for this.

Choosing when to apply the email address policy

Finally, click New to create the email address policy. If it all goes well you’ll see a successful completion message.

Completing the new email address policy wizard

Note that the completion dialog reveals the PowerShell commands used behind the scenes to perform the task. This will be relevant later when we look at an example of creating an email address policy in PowerShell.

Applying Email Address Policies

Now let’s check the results. Because I chose not to apply the policy yet the user Amy Lawrence does not have an @example.com email address yet.

Email addresses before the policy is applied

If I move another mailbox user into the same OU, they also do not have the email address policy applied.

User moved into OU

Jo Rigby’s email addresses haven’t changed just because her OU membership changed.

No change to email addresses yet

However, if I modify Jo Rigby’s recipient properties, such as adding the new company name, and apply that change…

Modifying recipient properties to trigger email address policies

…the new SMTP address is immediately applied by the policy, because modifying and saving any change to a recipient triggers policy assessment.

SMTP addresses after email address policy is applied

If I simply wish to apply the email address policy to all of the users in that OU I can right-click the policy and choose Apply, and choose to apply it immediately or at a scheduled time.

Manually applying an email address policy

Now Amy Lawrence also has the new @example.com email address without me having modified any of her other recipient properties, because I manually triggered the application of the policy.

SMTP addresses after email address policy is applied

You may wonder how primary SMTP address is determined when two policies are potentially valid for a recipient. The answer to that question is in the priority value of each policy. The policy with the highest priority will apply, but only that one policy applies.

For example, new user Bob Winder in the Example Corp OU gets mailbox-enabled and only receives an @example.com SMTP address from the “Example Corp” policy, but doesn’t receive an @exchangeserverpro.net address from the default policy that is of a lower priority.

SMTP address for a new mailbox user

So each policy needs to contain all of the SMTP addresses that you intend those recipients to receive, so that new recipients get them all. You can’t rely on different email address policies to apply cumulatively.

Note: Email Address Policies are Additive Only

You may have noticed in the examples above that the prior SMTP address of @exchangeserverpro.net was not removed from the mailboxes, it was simply changed to being a secondary email address.

This is due to the behavior of email address policies in that they are additive only. An email address policy will not remove or overwrite an email address on a recipient.

If the recipient falls out of scope of the email address policy they will not have any email addresses removed from the account, though their primary SMTP address may change when a different policy applies. In the case of Jo Rigby, if she is moved out of that OU and her company attribute changed again (or any other modification made to trigger policy assessment) she reverts to an @exchangeserverpro.net primary SMTP address, but retains @example.com as a secondary address.

SMTP address changed after policy no longer applies

Nor will the removal of the email address policy entirely cause recipients to lose those email addresses.

Removing an email address policy

Note that removing a policy causes those recipients to assess policies again. Amy Lawrence’s primary SMTP address changed back to @exchangeserverpro.net with no other recipient modification or manual applying of other policies required, but again she retained the @example.com secondary address.

SMTP addresses after email address policy is removed

Creating a New Email Address Policy with the Exchange Management Shell

There will be times when you find the options available in the console when creating a new email address policy are not suitable for your particular scenario. In those cases you can use the Exchange Management Shell to create a more specific filter for the email address policy.

Email address policies are created using the New-EmailAddressPolicy cmdlet. This cmdlet has a -RecipientFilter parameter that opens up a whole lot more possibilities (the documentation refers to Exchange 2007 but is unchanged for Exchange 2010) for defining the scope of your email address policies. Just be aware that it can’t be used in combination with some other parameters, all of which is spelled out here.

So let’s look at one example of creating an email address policy in PowerShell using the capabilities of -RecipientFilter.

To begin with I’ve removed the policy I created in the console earlier, and manually removed the @example.com addresses from those mailboxes to start over with a clean slate.

Example Corp users in their OU

Now I’ll create the email address policy, using a recipient filter that checks display names for the string “(Example Corp)”. The new policy will have the following properties:

• A name of “Example Corp”
• A priority of 1
• An email address template of “SMTP:%m@example.com” (the upper-case SMTP defines the primary SMTP address, lower-case would be a secondary SMTP address)
• A recipient filter for the DisplayName attribute of “*(Example Corp)” (the * is a wildcard)

Running that as a command in the Exchange Management Shell looks like this:.

New-EmailAddressPolicy -Name "Example Corp" -Priority 1 -EnabledEmailAddressTemplates "SMTP:%m@example.com" -RecipientFilter {DisplayName -like "*(Example Corp)"}

Name                                    Priority                                RecipientFilter
----                                    --------                                ---------------
Example Corp                            1                                       DisplayName -like '*(Example Corp)'

Now the new email address policy has been created, but as before it has not yet applied to any recipients. To trigger the policy for the three Example Corp users I’m going to modify their display names to append “(Example Corp) to them. I’m just doing them individually here but you could script it if you had a lot of mailbox users to modify.

[PS] C:\>Set-Mailbox Jo.Rigby -DisplayName "Jo Rigby (Example Corp)"

Jo now has the @example.com SMTP address assigned by the new policy.

[PS] C:\>Get-Mailbox Jo.Rigby | select displayname,emailaddresses | fl

DisplayName    : Jo Rigby (Example Corp)
EmailAddresses : {SMTP:Jo.Rigby@example.com, smtp:Jo.Rigby@exchangeserverpro.net}

And if I change her display name so it no longer has “(Example Corp)” in it, she reverts to the primary SMTP address @exchangeserverpro.net and retains the @example.com as a secondary SMTP address.

[PS] C:\>Set-Mailbox Jo.Rigby -DisplayName "Jo Rigby"

[PS] C:\>Get-Mailbox Jo.Rigby | select displayname,emailaddresses | fl

DisplayName    : Jo Rigby
EmailAddresses : {SMTP:Jo.Rigby@exchangeserverpro.net, smtp:Jo.Rigby@example.com}

Hopefully this article has provided you a good understanding of how email address policies work in Exchange Server 2010, and given you some ideas on how you can use them in your own Exchange organization.

Related posts:

• How to Set Up an Automated Exchange 2010 Database Backup Alert Email
• Dealing with Exchange Server Update Rollups and Forefront Protection for Exchange
• Reporting Exchange Server 2010 Message Tracking Event IDs with PowerShell
• Searching Exchange Server 2010 Message Tracking Logs with PowerShell
• The User Hasn’t Logged on to Mailbox So There is No Data to Return

This article Exchange Server 2010 Email Address Policies is © 2012 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Service Pack 2 deployment follows the same installation sequence as the initial Exchange install or any other update.

1. Client Access servers, starting with the internet-facing ones
2. Hub Transport and Edge Transport servers
3. Mailbox servers
4. Unified Messaging servers

Note: if you are installing to multi-role servers just prioritize based on the same order above.

Upgrading Client Access Servers to Exchange 2010 SP2

When you install Service Pack 2 on Client Access servers you may receive an error message for a missing IIS component. This issue and the solution are described in the following article:

• Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade

If you’re updating a CAS array of servers in a Windows Network Load Balancing cluster then refer to the following article to learn how to perform the update without disrupting clients:

• How to Install Updates on Exchange Server 2010 CAS Arrays

Upgrading Database Availability Groups to Exchange 2010 SP2

If you are updating the members of a DAG to Service Pack 2 then refer to the following article for instructions on how to perform the upgrade without requiring an outage for mailbox users:

• How to Install Updates on Exchange Server 2010 Database Availability Groups

Exchange MVP Andy Grogan has already released an updated version of his RUPS Tool for installing Service Pack 2.

• Updated version of the RUPS Tool–Installing Service Packs

Upgrading Management Tools to Exchange 2010 SP2

Any management servers or workstations that have the Exchange 2010 Management Tools installed on them will also need to be upgraded to be able to manage some of the new features of Exchange 2010 SP2 and to avoid the initialization error that can occur due to mismatched versions. Simply run the setup wizard to upgrade those computers.

Related posts:

• Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade
• What Are The Benefits of Exchange Server 2010 Compared to Exchange 2007
• Exchange 2010 FAQ: How Do I Cluster Exchange Server 2010?
• Migrating from a Single Exchange 2010 Server to High Availability
• Exchange Server 2010 High Availability Demonstration Video

This article Upgrading to Exchange Server 2010 Service Pack 2 is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Perhaps the environment is large enough that the backups are managed by a separate team to the Exchange administrators, and so the Exchange admins just want to keep an eye on their database backups. Or even in a smaller environment the administrators may just want to be sure that their backup software isn’t reporting successful backups when in fact they may be failing.

In this post I will demonstrate a PowerShell script that you can run in an Exchange Server 2010 environment to report on any databases that have not successfully backed up in the last 48 hours. Let’s take a look at how this works.

Firstly, backup time stamps are retrievable using the Get-MailboxDatabase cmdlet for mailbox databases, or Get-PublicFolderDatabase for public folder databases. Here is an example:

PS C:\Scripts> Get-MailboxDatabase -Status | ft name,last* -auto

Name     LastFullBackup       LastIncrementalBackup LastDifferentialBackup LastCopyBackup
----     --------------       --------------------- ---------------------- --------------
MB-HO-01 11/6/2011 1:40:19 PM
MB-HO-02
MB-HO-03
MB-BR-01

You can see that one of the databases above has been backed up, but the others have not. In a script that checks both mailbox and public folder databases we could use this code to generate the report.

$dbs = Get-MailboxDatabase -Status
$dbs = $dbs += Get-PublicFolderDatabase -Status
$dbs | ft name,last*

Now we can see both the mailbox and the public folder databases.

Name                    LastFullBackup          LastIncrementalBackup   LastDifferentialBackup  LastCopyBackup
----                    --------------          ---------------------   ----------------------  --------------
MB-HO-01                11/6/2011 1:40:19 PM
MB-HO-02
MB-HO-03
MB-BR-01
PF-HO-01                11/6/2011 1:40:20 PM
PF-BR-01

It would be a simple matter to run that command and read the output every single day, but that would not be the most efficient way of checking database backups. There could be dozens or even hundreds of databases in that output, and we’d have to mentally perform the calculations to determine whether the backup time stamp is within the last 48 hours or not.

Instead we want to only to see databases that have not been backed up within the 48 hour threshold. To do this we can use some date maths. Because we’ve already retrieved the database objects into a collection called $dbs we can loop through them to perform the date calculations like this. Note that in this example only Full and Incremental backups are being considered.

foreach ($db in $dbs)
{
	Write-Host -ForegroundColor Gray "Checking" $db.name"..."

	$lastbackup = @{}
	$ago = @()
	[bool]$alertflag = $false

	if ( $db.LastFullBackup -eq $nul -and $db.LastIncrementalBackup -eq $nul)
	{
		$lastbackup.time = "Never"
		$lastbackup.type = "Never"
		[string]$ago = "Never"
	}
	elseif ( $db.LastFullBackup -lt $db.LastIncrementalBackup )
	{
		$lastbackup.time = $db.LastIncrementalBackup
		$lastbackup.type = "Incremental"
		[int]$ago = ($now - $lastbackup.time).TotalHours
		$ago = "{0:N0}" -f $ago
	}
	elseif ( $db.LastIncrementalBackup -lt $db.LastFullBackup )
	{
		$lastbackup.time = $db.LastFullBackup
		$lastbackup.type = "Full"
		[int]$ago = ($now - $lastbackup.time).TotalHours
		$ago = "{0:N0}" -f $ago
	}
}

One of three possible scenarios will be true:

• If the database has not been backed up at all then both Full and Incremental time stamps will be nul, so all of the resulting values are set to “Never”
• If the most recent backup was an Incremental then the type is set to “Incremental” and the $ago variable is set to the number of hours that has passed since that Incremental backup finished
• If the most recent backup was a Full then the type is set to “Full” and the $ago variable is set to the number of hours that has passed since that Full backup finished

Now, because we’re only interested in databases that haven’t backed up in the last 48 hours (or have never been backed up at all) we can compare the $ago variable to our threshold of 48 hours, and if an alert needs to be raised set the alert flag to True and create an object with all of the desired information for our report.

if ( $ago -gt $threshold -or $ago -eq "Never")
	{
		$alertflag = $true
		$dbObj = New-Object PSObject
		$dbObj | Add-Member NoteProperty -Name "Server/DAG" -Value $db.MasterServerOrAvailabilityGroup
		$dbObj | Add-Member NoteProperty -Name "Database" -Value $db.name
		$dbObj | Add-Member NoteProperty -Name "Database Type" -Value $dbtype
		$dbObj | Add-Member NoteProperty -Name "Last Backup Type" -Value $lastbackup.type
		$dbObj | Add-Member NoteProperty -Name "Hrs Ago" -Value $ago
		$dbObj | Add-Member NoteProperty -Name "Time Stamp" -Value $lastbackup.time
		$alerts = $alerts += $dbObj
	}

That code actually goes inside the ForEach loop for the $dbs collection.

The final piece of the script is the report itself. We output it based on whether the alert flag is set to True or False.

if ($alertflag = $true )
{
	Write-Host "The following databases have not been backed up in" $threshold "hours."
	$alerts | ft -AutoSize
}
else
{
	Write-Host "No backup alerts required."
}

This example outputs the report to the PowerShell window but you could write your PowerShell script to send an email report instead if you wish.

Here is an example report:

PS C:\Scripts> .\Check-DatabaseBackups.ps1
Getting database list...
Checking MB-HO-01 ...
Checking MB-HO-02 ...
Checking MB-HO-03 ...
Checking MB-BR-01 ...
Checking PF-HO-01 ...
Checking PF-BR-01 ...
The following databases have not been backed up in 48 hours.

Server/DAG     Database Database Type Last Backup Type Hrs Ago Time Stamp
----------     -------- ------------- ---------------- ------- ----------
dag-headoffice MB-HO-02 Mailbox       Never            Never   Never
dag-headoffice MB-HO-03 Mailbox       Never            Never   Never
BR-EX2010-MB   MB-BR-01 Mailbox       Never            Never   Never
BR-EX2010-MB   PF-BR-01 Public Folder Never            Never   Never

And here is the complete script.

#
#.SYNOPSIS
#Checks the backup timestamps for the servers
#and alerts if a database hasn't been backed up
#in the last 48 hours
#
#.EXAMPLE
#.\Check-DatabaseBackups.ps1
#

#...................................
# Variables
#...................................

$ErrorActionPreference = "SilentlyContinue"
$WarningPreference = "SilentlyContinue"

$alerts = @()
[int]$threshold = 48

$now = [DateTime]::Now

#...................................
# Script
#...................................

#Get all Mailbox and Public Folder databases
Write-Host -ForegroundColor Gray "Getting database list..."
$dbs = Get-MailboxDatabase -Status
$dbs = $dbs += Get-PublicFolderDatabase -Status

#Check each database for most recent backup
foreach ($db in $dbs)
{
	Write-Host -ForegroundColor Gray "Checking" $db.name"..."

	$lastbackup = @{}
	$ago = @()
	[bool]$alertflag = $false

	if ( $db.LastFullBackup -eq $null -and $db.LastIncrementalBackup -eq $nul)
	{
		$lastbackup.time = "Never"
		$lastbackup.type = "Never"
		[string]$ago = "Never"
	}
	elseif ( $db.LastFullBackup -lt $db.LastIncrementalBackup )
	{
		$lastbackup.time = $db.LastIncrementalBackup
		$lastbackup.type = "Incremental"
		[int]$ago = ($now - $lastbackup.time).TotalHours
		$ago = "{0:N0}" -f $ago
	}
	elseif ( $db.LastIncrementalBackup -lt $db.LastFullBackup )
	{
		$lastbackup.time = $db.LastFullBackup
		$lastbackup.type = "Full"
		[int]$ago = ($now - $lastbackup.time).TotalHours
		$ago = "{0:N0}" -f $ago
	}

	if ($db.IsMailboxDatabase -eq $true) {$dbtype = "Mailbox"}
	if ($db.IsPublicFolderDatabase -eq $true) {$dbtype = "Public Folder"}

	#If backup time stamp older than threshold set alert flag and create object for alerting
	if ( $ago -gt $threshold -or $ago -eq "Never")
	{
		$alertflag = $true
		$dbObj = New-Object PSObject
		$dbObj | Add-Member NoteProperty -Name "Server/DAG" -Value $db.MasterServerOrAvailabilityGroup
		$dbObj | Add-Member NoteProperty -Name "Database" -Value $db.name
		$dbObj | Add-Member NoteProperty -Name "Database Type" -Value $dbtype
		$dbObj | Add-Member NoteProperty -Name "Last Backup Type" -Value $lastbackup.type
		$dbObj | Add-Member NoteProperty -Name "Hrs Ago" -Value $ago
		$dbObj | Add-Member NoteProperty -Name "Time Stamp" -Value $lastbackup.time
		$alerts = $alerts += $dbObj
	}
}

#If alert flag is true output the report
if ($alertflag -eq $true )
{
	Write-Host "The following databases have not been backed up in" $threshold "hours."
	$alerts | ft -AutoSize
}
else
{
	Write-Host "No backup alerts required."
}

If you’d like to schedule this report to run each day and alert you by email when databases are not being backed up then click here

Related posts:

• How to Set Up an Automated Exchange 2010 Database Backup Alert Email
• PowerShell: Configuring Settings on Multiple Exchange Mailbox Databases
• PowerShell Script: Check Exchange Mailbox Database Last Backup Time
• Get-MailboxReport.ps1 – PowerShell Script to Generate Mailbox Reports
• Using Test-Mailflow with Exchange 2003 Servers

This article PowerShell Script: Check Exchange 2010 Database Backups is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

As the name suggests, Test-ServiceHealth checks the state of the services that should be running on the Exchange server. One of the best things about this cmdlet is that it checks the services depending on the Exchange server roles that are installed.

So for example, for a Hub Transport server only those services relating to the Hub Transport role will be checked. While for a “typical” Exchange 2010 server the services for the Hub Transport, Client Access, and Mailbox server roles will be checked.

Here is an example of the Test-ServiceHealth results.

[PS] C:\>Test-ServiceHealth br-ex2010-mb

Role                    : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeIS, MSExchangeMailboxAssistants, MSExchangeMailSub
                          mission, MSExchangeRepl, MSExchangeRPC, MSExchangeSA, MSExchangeSearch, MSExchangeServiceHost
                          , MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeAB, MSExchangeADTopology, MSExchangeFBA, MSExchangeFDS, MSExchangeMailbo
                          xReplication, MSExchangeProtectedServiceHost, MSExchangeRPC, MSExchangeServiceHost, W3Svc, Wi
                          nRM}
ServicesNotRunning      : {}

Role                    : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost, MSExchangeTranspo
                          rt, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

As you can see that is a lot of useful information. But whenever possible I like to see just the minimum relevant information for my servers. In the case of Test-ServiceHealth the RequiredServicesRunning result is the thing I am most interested in.

So in this case I could run the following command to see just that information:

[PS] C:\>Test-ServiceHealth br-ex2010-mb | ft Role,RequiredServicesRunning -auto

Role                      RequiredServicesRunning
----                      -----------------------
Mailbox Server Role                          True
Client Access Server Role                    True
Hub Transport Server Role                    True

Much better.

Now suppose I wanted to run that for all of my Exchange servers. I could do that with the following command:

[PS] C:\>Get-ExchangeServer | Test-ServiceHealth | ft Role,RequiredServicesRunning -auto

Role                      RequiredServicesRunning
----                      -----------------------
Client Access Server Role                    True
Hub Transport Server Role                    True
Client Access Server Role                    True
Hub Transport Server Role                    True
Mailbox Server Role                         False
Mailbox Server Role                          True
Client Access Server Role                    True
Hub Transport Server Role                    True
Mailbox Server Role                          True
Client Access Server Role                    True
Hub Transport Server Role                    True

Interesting, especially the one that failed the test for the Mailbox server role. But in that output I can’t tell which server failed.

Let’s try this instead:

[PS] C:\>$servers = Get-ExchangeServer
[PS] C:\>foreach ($server in $servers) {
>> Write-Host "Checking" $server.name
>> Test-ServiceHealth $server | ft Role,RequiredServicesRunning -auto
>> }
>>

Now we get output that is a little more useful, and tells me which server failed the test.

Checking HO-EX2010-CAHT1

Role                      RequiredServicesRunning
----                      -----------------------
Client Access Server Role                    True
Hub Transport Server Role                    True

Checking HO-EX2010-CAHT2

Role                      RequiredServicesRunning
----                      -----------------------
Client Access Server Role                    True
Hub Transport Server Role                    True

Checking HO-EX2010-MB1

Role                RequiredServicesRunning
----                -----------------------
Mailbox Server Role                   False

Checking HO-EX2010-MB2

Role                RequiredServicesRunning
----                -----------------------
Mailbox Server Role                    True

Checking BR-EX2010-CAHT

Role                      RequiredServicesRunning
----                      -----------------------
Client Access Server Role                    True
Hub Transport Server Role                    True

Checking BR-EX2010-MB

Role                      RequiredServicesRunning
----                      -----------------------
Mailbox Server Role                          True
Client Access Server Role                    True
Hub Transport Server Role                    True

But it still isn’t quite enough, so let’s wrap this up into a handy script that will do the following:

• Run Test-SystemHealth for all of the Exchange servers in the organization
• Tell me which servers passed the test
• Tell me which servers failed the test, and why

Here is the script code that will perform those steps.

#Get the list of Exchange servers in the organization
$servers = Get-ExchangeServer

#Loop through each server
ForEach ($server in $servers)
{
	Write-Host -ForegroundColor White "---------- Testing" $server

	#Initialize an array object for the Test-ServiceHealth results
	[array]$servicehealth = @()

	#Run Test-ServiceHealth
	$servicehealth = Test-ServiceHealth $server

	#Output the results
	ForEach($serverrole in $servicehealth)
	{
		If ($serverrole.RequiredServicesRunning -eq $true)
		{
			Write-Host $serverrole.Role -NoNewline; Write-Host -ForegroundColor Green "Pass"
		}
		Else
		{
			Write-Host $serverrole.Role -nonewline; Write-Host -ForegroundColor Red "Fail"
			[array]$notrunning = @()
			$notrunning = $serverrole.ServicesNotRunning
			ForEach ($svc in $notrunning)
			{
				$alertservices += $svc
			}
			Write-Host $serverrole.Role "Services not running:"
			ForEach ($al in $alertservices)
				{
					Write-Host -ForegroundColor Red `t$al
				}
		}
	}
}

The output from running the script will look something like this.

You can now see at a glance which servers have passed the test, which ones failed, and which services aren’t running for the servers that failed.

Related posts:

• How to Migrate a Relay Connector from Exchange Server 2007 to 2010
• How to List all Users Who Have Access to Other Exchange Mailboxes
• Exchange 2007/2010: How to Clone a Mailbox Database Configuration
• Exchange 2007/2010 Public Folder Store in an Inconsistent State
• PowerShell: Configuring Settings on Multiple Exchange Mailbox Databases

This article Using Test-ServiceHealth for Exchange Server Health Checks is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

To celebrate the launch of the Exchange Server Pro forums Train Signal has generously provided two copies of their Exchange Server 2010 MCITP DVD training as prizes, valued at $594 USD each.

Each training package contains:

• Both the 70-662 and 70-663 exam training
• Online streaming access to the training materials
• Physical DVD media with the videos, audio, and PDF lessons
• Transcender practice exams

To be eligible to win all you need to do is:

1. Join the Exchange Server Pro forums
2. Read this forum thread for the next steps

This contest closes at midnight on Saturday 22nd October 2011, AEST (GMT+10) and two winners will be drawn at random from the eligible entries.

Related posts:

• Win a Free PowerGUI Pro License

This article Win Exchange Server 2010 Training from Train Signal is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

• Part 1 – How to Send SMTP Email Using PowerShell
• Part 2 - How to Add a Message Body to Emails Sent from Scripts
• Part 3 - How to Add a HTML Message Body to Emails Sent from Scripts
• Part 4 - How to Create Formatted HTML Output from Scripts

There are a few different ways to do this, depending on the version of PowerShell installed on your computer or server. You can check the version number by typing $host in a PowerShell window.

PowerShell 1.0 will show this result:

PS C:\> $host

Name             : ConsoleHost
Version          : 1.0.0.0

PowerShell 2.0 will show this result:

PS C:\> $host

Name             : ConsoleHost
Version          : 2.0

Let’s take a look at how we can send SMTP email using each version of PowerShell.

Sending SMTP Email with PowerShell 1.0

For PowerShell 1.0 we can send mail by running these commands.

PS C:\> $smtp = New-Object Net.Mail.SmtpClient("ho-ex2010-caht1.exchangeserverpro.net")
PS C:\> $smtp.Send("reports@exchangeserverpro.net","administrator@exchangeserverpro.net","Test Email","This is a test")

So what did we just do there? Let’s break it down.

1. Created a new instance of a .NET object of class SmtpClient, connected to the SMTP server ho-ex2010-caht1 (a Hub Transport server)
2. Used the Send method of the object to send an email message with the following:
• From address of “reports@exchangeserverpro.net”
• To address of “administrator@exchangeserverpro.net
• Subject of “Test Email”
• Body of “This is a test”

That works fine, though perhaps a bit cumbersome to type it out every time. Instead what we could do is create a script to send SMTP email using PowerShell 1.0.

#
#.SYNOPSIS
#Sends SMTP email via the Hub Transport server
#
#.EXAMPLE
#.\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test"
#

param(
[string]$to,
[string]$subject,
[string]$body
)

$smtpServer = "ho-ex2010-caht1.exchangeserverpro.net"
$smtpFrom = "reports@exchangeserverpro.net"
$smtpTo = $to
$messageSubject = $subject
$messageBody = $body

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($smtpFrom,$smtpTo,$messagesubject,$messagebody)

We can save that code as Send-Email.ps1 and run it from the PowerShell window.

PS C:\Scripts> .\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test"

Less typing required, especially when you hard-code some of the variables such as the From address and SMTP server.

Sending SMTP Email with PowerShell 2.0

PowerShell 2.0 makes life a little easier thanks to the built in cmdlet Send-MailMessage. To send the same email as the above example we would run this command:

PS C:\> Send-MailMessage -From "reports@exchangeserverpro.net" -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test email"

One of the first things you might notice in the command above is that no SMTP server was specified. Send-MailMessage does have a -SmtpServer parameter, but if you don’t specify one it will just use the $PSEmailServer preference variable instead. This can be set for the session by running the following command:

PS C:\> $PSEmailServer = "ho-ex2010-caht1.exchangeserverpro.net"

Another point to note with Send-MailMessage is that is uses authenticated SMTP connections. By default it will use the credentials of the user executing the command. So you need to make sure you’re using an SMTP server that either:

• Permits that authenticated user credential to send email messages via SMTP
• Accepts anonymous SMTP/relay for the IP address of the sending host (you can see how to configure a relay connector for Exchange here)

Those are just a few simple examples of how to send email using SMTP and PowerShell 1.0 or 2.0.

Related posts:

• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)
• How to Set Up an Automated Exchange 2010 Database Backup Alert Email
• Using Test-Mailflow with Exchange 2003 Servers
• PowerShell Script: Check Exchange 2010 Database Backups

This article How to Send SMTP Email Using PowerShell (Part 1) is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server 2010 is a big evolutionary step from previous versions of Exchange. I’ve delivered successful Exchange 2010 migration projects involving thousands of mailboxes. And I’ve been called in to bring customers’ migration projects back from the brink of disaster too.

The Exchange Server 2007 to 2010 Migration Guide brings together my knowledge and experience in Exchange Server migrations so that you can avoid disaster and celebrate a successful project outcome.

In the Exchange Server 2007 to 2010 Migration Guide you get:

• The migration guide itself, a 250+ page PDF with detailed, step by step instructions that take you through the entire process of migrating to Exchange Server 2010
• A planning worksheet to record the important information you need from your existing environment for a successful migration project
• A testing worksheet so you know that your new Exchange 2010 servers are working correctly before you put them into production
• BONUS: Guide to Exchange Server 2010 Backup and Recovery, to help you protect your servers from data loss

Here’s what Exchange Server expert Steve Goodman wrote in his review of the Exchange Server 2007 to 2010 Migration Guide:

From a brief read, I can tell this is a book based on real world experience. It covers the kind of things I get asked time and time again and see people stuck with on forums. There are more comprehensive volumes out there on Exchange, covering a lot more topics in a lot more detail, but where I think this book stands out is it’s the guide a lot of small to medium business admins tackling an Exchange migration themselves need to get the job done without much (or even any) help.

Click here to find out more and get your copy of the Exchange Server 2007 to 2010 Migration Guide.

Related posts:

• Exchange 2010 FAQ: How to Minimise Downtime During Mailbox Migration from Exchange 2007
• OWA Error: The Mailbox You’re Trying to Access Isn’t Currently Available
• Exchange 2010 FAQ: Is Direct Exchange Migration from 2003 to 2010 Possible Without Upgrading to 2007?
• Exchange 2010 FAQ: Can I Replace Exchange 2007 Hub Transport Servers with Exchange 2010?
• Generate SMTP Error Statistics using Log Parser and Exchange Server 2010 Protocol Logs

This article The Exchange Server 2007 to 2010 Migration Guide is Available Now is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

If you’ve never heard of TechEd before it is a conference that Microsoft runs each year in different countries, including Australia, that combines training, education, and fun for IT pros and developers alike. Here in Australia it is basically the biggest and best conference that IT pros can go to without leaving the country.

Though I’ve been to three TechEds now I actually missed last year’s due to family and work commitments, but this year I was determined to go. I had such a great time that I want to share some of the experience with you here.

The Conference Kick-Off

TechEd Australia 2011 was held at the Gold Coast Convention Centre from the 29th of August to the 2nd of September. The first two days are mostly pre-conference activities such as hands-on training and user group meetings. I didn’t plan to attend any of the training, but could have attended some of the free sessions put on by local user groups if I’d been able to make the drive from Brisbane earlier in the day. Something for me to try harder at next year.

On the Tuesday afternoon the opening keynote presentation was held in the main arena. The keynote was a celebration of “geek” and did a great job of inspiring the audience and getting us excited for what was coming in the days ahead.

The keynote was followed by the opening night party. This included dinner, drinks, the opening of the exhibitor hall (which the hordes of geeks promptly began looting for freebies) and just general networking.

After the official party came the unofficial party thrown by the AuTechHeads user group at a local bar. Around 200 people enjoyed a few hours of drinks and entertainment thanks to the AuTechHeads core team and the vendors that sponsored the party.

As it was only the first night people mostly behaved themselves although one or two were clearly going to have a rough start to the conference the next morning.

The Technical Sessions

Although I love the social aspect of TechEd the sessions are the main reason that I am there. I got started first thing on Wednesday morning at 8:15am with some Lync audio/video conferencing.

In general I stuck mostly to the Exchange/Lync track since that is the space that I work in the most, but I also sat in on a few other sessions when I had a free slot in my timetable. It is good to get some variety and open yourself up to the other things going on in the IT world that you may not come across in your own job very often.

Of the three days TechEd ran for my highlights were:

• Audio, Video and Web Conferencing Architecture and Experience
• Exchange Server 2010: High Availability Concepts
• Microsoft Lync 2010: High Availability and Resiliency
• Load Balancing with Microsoft Exchange Server 2010
• Upgrading to Exchange 2010: Notes from Field
• Exchange Server 2010: High Availability Deep Dive

You can check out the slides and videos of those sessions by clicking on the links. If the videos aren’t available straight away the team says they should be up within the next week or two.

My two favourite presenters were Andrew Ehrensing and Scott Schnoll, both Microsoft employees and both delivering high impact level 300-400 sessions on Exchange 2010 and Lync 2010.

The Networking

The other main benefit of conferences such as TechEd is the chance to meet up with other IT pros. I lost count of how many former colleagues I bumped into while I was there and had a chat with, as well as all of the new people that I had never met or only met online before.

The AuTechHeads user group has become one of the most connecting forces in the local IT professional community thanks to the efforts of their core team members Matt Marlor, Mick Huxley, Simone Bennett, Hayden McManus, and Stephen Molkentin.

TechEd is also one of the best opportunities you’ll ever have to talk face to face with the leading experts in our field. For example, besides delivering two amazing sessions on Exchange 2010 Scott Schnoll was also happy to chat at the Microsoft booth in the exhibitor hall and answer all of the questions that I had (except for the NDA stuff on E15 which he didn’t budge on )

A lot of our local talent also presented strong sessions or ran free user group training such as Shane Hoey and Chris Brown’s pre-conference PowerShell training.

The Exhibitor Hall

The exhibitor hall is always popular with the crowd due to the free giveaways that are usually on offer. I grabbed a few toys for the kids and shirts for myself but other than that there is only so many pens and beer coolers you want to own in your life

It was a decent showing this year from the vendors. Microsoft had some cool demos of their new Lightswitch development tools, Microsoft Surface, and Xbox Kinect games for the fun stuff.

I also discovered PowerShell Plus from Idera. I’ve been playing with the 30 day trial and considering buying a license for it, though so far I have been happy with the free version of PowerGUI.

I did hear a few people complaining about the vendors “leaking” out of the hall and into some of the sessions themselves. I understand that people don’t want to be “sold” when they go to a conference like TechEd, but the reality is that we work within the Microsoft partner ecosystem and we can’t ignore the third party vendors.

I will concede there may be a better way of identifying which sessions are vendor-centric and which are Microsoft-centric, so that people understand what they are sitting down to watch. But I would not personally stay away from a session just because a vendor is involved. In fact I’d prefer it if they were quite up front about it, rather than try to soften their presentation to avoid seeming “sales-ey”. If you’ve got a good product then give it a strong presentation and let us decide on merit.

My TechEd Tips

As I said earlier this was my third TechEd and definitely the best one I’ve been to so far. If you’re considering going to TechEd 2012 I’ll offer these tips.

Start the day well – eat a good breakfast with lots of protein to help keep you from getting hungry. I had a room service breakfast each morning that kept me happy until mid- to late-morning when the 30 minute morning tea break was on.

Think about packing some snacks as well. Even though meals are provided during the day there isn’t always enough time to leave a session, line up for food, and then make it to the next session in time to get a seat.

I kept a few protein bars and small boxes of dried fruits and nuts with me, which allowed me to get to the next room before the crowds.

Have a plan, but be flexible – I had at least one session in my conference planner for each time slot, and often a second one as a backup. There was one or two instances where a topic or presenter didn’t quite catch my fancy and so I would skip the next one on that topic and watch something else instead.

Knowing your sessions in advance makes it easier to meet up with people as well, especially if you know someone in the coffee line and they can grab one for you while you go and get two seats for the next session.

It also helps to know the room layout and how long it takes to get from one side of the convention centre to the other.

Be social, but go easy – the parties are a lot of fun and who doesn’t enjoy a free beer! But it is hard to concentrate through 75 minutes of level 400 content when you haven’t had enough sleep or are fighting a headache. Take it easy, drink lots of water, and get plenty of sleep.

Pack the right gear – There are plenty of places to recharge equipment and free wifi provided as well. I took my laptop and netbook with me because I wasn’t sure which one I’d prefer to carry with me to the conference each day. Luckily I did have one of them with me each day because I forgot to pack the AC adapter for my iPhone, so to charge it at the conference I had to fire up my netbook and use it to charge the iPhone.

One thing I wish I’d taken was a better camera. Neither my regular camera or my iPhone took decent photos the entire week, which was disappointing.

Make the most of it – try to find the right mix of sessions, socialising, and speaking with the vendors in the hall. Three days is a long time but it also flew by very quickly for me.

Wrapping Up TechEd Australia 2011

Overall I had an amazing time at TechEd 2011, both in and out of the sessions themselves. As it stands now I plan to be there next year. A big thanks to CodeTwo and GFI for sending me some t-shirts to wear and hand out to other attendees. IT pros love a free shirt and people were very appreciative.

For those of you planning to go to TechEd 2012, I’ll see you there!

Related posts:

• TechEd Video: Exchange 2010 Virtualization
• TechEd Video: Upgrading to Exchange 2010: Notes from Field
• TechEd Video: Load Balancing with Microsoft Exchange Server 2010
• TechEd Video: Exchange Server 2010 High Availability Deep Dive
• TechEd Video: Exchange Server 2010 High Availability Concepts

This article Microsoft TechEd Australia 2011 is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

To understand how CodeTwo Exchange Rules Pro works think of it like an add-on for the Transport Rules feature of Exchange Server 2010/2007.

There are a whole lot of things you can do with Transport Rules. But the problem is that Transport Rules are pretty awkward to work with due to the very basic configuration wizard in the Exchange Management Console.

Basically CodeTwo Exchange Rules Pro takes the capabilities of Transport Rules and makes them easier to work with, enhances them in highly useful ways, and even adds a few new capabilities to the mix.

Each rule that you configure in Exchange Rules Pro has the following attributes:

Conditions – the criteria that trigger the rule, such as email to or from particular users, or containing certain keywords.

Actions – the action that you want the rule to take, such as adding a disclaimer, removing profanity, or responding with a pre-configured message.

Exceptions – any specific criteria that the rule should not apply to.

Options – extra details such as whether to continue processing additional rules after this one, or specific time ranges that the rule applies to.

With such fine-grain controls over rules it is pretty easy to configure rules for just about any business scenario I can think of.

Installing CodeTwo Exchange Rules Pro

I installed CodeTwo Exchange Rules Pro on a Windows Server 2008 R2 server running Exchange Server 2010 SP1. The Exchange Server was installed with the typical server roles of Mailbox, Client Access, and Hub Transport.

The installation was very quick and simple. It will restart the Transport services on the server, so you just need to be aware of that and perhaps schedule your installation for outside of business hours.

When the install is finished the administration console opens and you’ll see a series of pre-configured example rules (that are disabled) to help you get started.

Features of CodeTwo Exchange Rules Pro

Although there is a long list of features for CodeTwo Exchange Rules Pro in this review I’ll focus on just a few of the ones I found the most interesting.

Email Disclaimers

Disclaimers are one of the most useful features of CodeTwo Exchange Rules Pro. Almost every customer I work with would like to standardize their corporate email signatures, but find that the built-in Transport Rules are too cumbersome to deal with and don’t make it easy to create good looking disclaimers.

CodeTwo Exchange Rules Pro solves this problem with it’s easy to use HTML editor for email disclaimers. A simple WYSIWYG interface lets you create very attractive email disclaimers without having to know any HTML code. You can add dynamic fields such as Active Directory user attributes, and even use the photos stored in Active Directory as part of the email signature you create.

The HTML editor includes a library with a few dozen sample disclaimers, including disclaimers designed to appear at the top, side and bottom of email messages. I would bet that there is a sample design in the library that would suit almost any business, with just the simple step of swapping out the place holder logo for your own company logo.

There is also an image library with useful graphics for situations such as customer support autoresponders and legal disclaimers.

As you’re configuring rules you can use the handy Rule Tester to see whether they are working as you want them to before you apply them to your production users.

There is also the option to have CodeTwo Exchange Rules Pro automatically update the sent items in user mailboxes so that they look the same as after they have been processed by rules. There is a real benefit to your users being able to see exactly the same email message in their sent items that the recipients received, complete with all of the changes made by rules.

Auto-Responders

I’ve been asked many times in the past whether Exchange can be configured to automatically respond to certain emails with a pre-configured message. The usual scenarios for this are for example a marketing team who wants to promote an email address that people can send a message to requesting an information pack, or a jobs inbox that needs to automatically acknowledge each job application email that it receives.

There are various ways to achieve some of this using Outlook rules but they usually require an Outlook client logged in somewhere to actually process the rules.

Exchange Rules Pro makes this possible with auto-response rules that can be configured centrally on the server and work regardless of whether a user is logged on or not.

Removing Profanity

This scenario has come up a few times as well, the problem of staff having to deal with profanity in emails. They’re all grownups, and aren’t too sensitive to the occasional bad word, but a few contact centers that I’ve worked with receive a constant stream of abusive email for various reasons.

Believe it or not, this has actually resulted in some lawsuits because of the working conditions that it creates for staff.

Once again CodeTwo Exchange Rules Pro solves this problem with a handy content filter. This feature comes with a series of pre-configured dictionaries, including an obscene language dictionary. But rather than just block emails with bad language in them, the program can be configured to replace those words with some harmless text, allowing the email to be dealt with by staff without them having to read the profanity.

Time Ranges

The last feature I’ll describe in this review is the Time Range settings. These can be applied to every rule you create so that they will only apply at certain times of day, or for certain days.

Being able to pre-configure a rule to start and stop at specific times takes a lot of pressure off the IT staff and removes human error from the equation.

I know a lot of customers who will enjoy this feature for situations such as:

• Adding short-term marketing campaign information to disclaimers
• Automatically turning on and off the Christmas office closure message
• Replying to overnight support emails with details of the standard support hours

Summary

It is pretty clear that CodeTwo Exchange Rules Pro solves a lot of common business problems, and adds several enhancements and ease of administration to the standard Transport Rules capabilities of Exchange Server 2007/2010.

It’s nice to see such a useful product comes at a reasonable price as well. Licensing is user-based, not –server-based, and a small business of less than 50 staff only has to pay $330 USD for the software and $67 USD for each year of support.

I recommend checking out CodeTwo Exchange Rules Pro for yourself by downloading the trial here, or by watching the demonstration videos on the CodeTwo Youtube channel.

Click to Show Screenshot Gallery »

Related posts:

• Exchange 2007/2010 Transport Rule Logging
• Avoiding Infinite Loops with Internal Relay Domains in Exchange 2007/2010
• How to Migrate a Relay Connector from Exchange Server 2007 to 2010
• How to Share an Email Domain Between Two Mail Systems
• Block Users Sending to Specific Domains with Exchange Server 2010

This article Review of CodeTwo Exchange Rules Pro is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

For example, to list the sizes of all mailboxes on a particular database we can use this command.

[PS] C:\>Get-Mailbox -Database MB-HO-01 | Get-MailboxStatistics | ft displayname,totaldeleteditemsize,totalitemsize

DisplayName      TotalDeletedItemSize    TotalItemSize
-----------      --------------------    -------------
Administrator    0 B (0 bytes)           85.42 KB (87,468 bytes)
Alan Reid        80.08 KB (82,000 bytes) 30.9 MB (32,400,667 bytes)
Alex Heyne       12.35 KB (12,644 bytes) 8.734 MB (9,158,159 bytes)
Aisha Bhari      0 B (0 bytes)           190.4 KB (194,983 bytes)
Aleisha Harrison 0 B (0 bytes)           142.4 KB (145,797 bytes)

If we wanted to know the total size of all of those mailboxes we could output the data to CSV file, import it into Excel, and use formulas to get the results. However that is time-consuming if all you are after is a quick answer.

So instead we can use the Measure-Object command in PowerShell to get the answers we’re looking for. However if we try to use it with the data shown above we’ll get this error.

Measure-Object : Input object "79.95 KB (81,870 bytes)" is not numeric.

So first we need to convert the data into numeric form.

For example, to see the sum, average, minimum and maximum size of the “total item size” for the mailboxes above we run this command.

[PS] C:\>Get-Mailbox -Database MB-HO-01 | Get-MailboxStatistics | %{$_.TotalItemSize.Value.ToMB()} | Measure-Object -sum
 -average -max -min

Count    : 5
Average  : 7.6
Sum      : 38
Maximum  : 30
Minimum  : 0
Property :

Related posts:

• The User Hasn’t Logged on to Mailbox So There is No Data to Return
• Get-MailboxReport.ps1 – PowerShell Script to Generate Mailbox Reports
• PowerShell Script: Check Exchange 2010 Database Backups
• Using Test-ServiceHealth for Exchange Server Health Checks
• PowerShell Tip: Search for Commands by Keyword

This article How to Calculate Exchange 2010 Mailbox Sizes with PowerShell is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com