Get-Message -Server SERVER01 -IncludeRecipientInfo | Where{$_.RetryCount -gt 0} | Where{$_.Status -ne “Active”} | SELECT FromAddress, Recipients, LastError | Format-Table

$TargetUserName = Read-Host “Enter the user you would like to Export”
$TargetArchiveDir = Get-Item “\\FILE-SERVER\ARCHIVE PST\”
$CurrentHostName = hostname
$CurrentProfile = Gwmi Win32_ComputerSystem -Comp $CurrentHostName
“Logged On As User: ” + $CurrentProfile.UserName

Write-Host “Setting Permissions” -ForeGroundColor Yellow
Add-MailboxPermission -Identity $TargetUserName -User $CurrentProfile.Username -AccessRights ‘FullAccess’

Write-Host “Exporting Mailbox” -ForeGroundColor Yellow
Export-Mailbox -identity $TargetuserName -PSTFolderPath $TargetArchiveDir -Confirm:$True
Write-Host “You can now Delete the user – I’m too scared to do it for you!” -ForeGroundColor Yellow

Note: You need to run this script on a 32-bit machine with the Exchange Administration role installed

This one is a little more useful.

Basically, this PowerShell script checks the SummaryCopyStatus and checks that it’s “Healthy” – if not, it will send an email reporting which Storage Group copy has failed.  You can run this script every hour or so, and be alerted when any SCR status has gone bad.

This is based on the same email code as my previous two posts. Bare in mind that I’m NOT a developer and my code is more than likely inefficient and ugly!

You can download the script CheckSCRStatus.ps1

Or view the code:

$SCRStatus = Get-StorageGroupCopyStatus -Server PRIMARYSERVER -StandbyMachine SECONDARYSERVER | Where {$_.StorageGroupName -eq “First Storage Group”}
if ($SCRStatus.SummaryCopyStatus -ne “Healthy”)
{
$MessageBody = “The SCR for ” + $SCRStatus.StorageGroupName + ” has failed”
$FromAddress = “FromAddress@yourdomain.com”
$ToAddress = “ToAddress@yourdomain.com”
$MessageSubject = “SCR Status Failure”
$SendingServer = “MAILSERVER”
$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody
$SMTPMessage.IsBodyHtml = $true
$SMTPClient = New-Object System.Net.Mail.SMTPClient $SendingServer
$SMTPClient.Send($SMTPMessage)
}
Else
{
Write-Host “First Storage Group All Good!”
}
$SCRStatus2 = Get-StorageGroupCopyStatus -Server PRIMARYSERVER -StandbyMachine SECONDARYSERVER | Where {$_.StorageGroupName -eq “Second Storage Group”}
if ($SCRStatus2.SummaryCopyStatus -ne “Healthy”)
{
$MessageBody = “The SCR for ” + $SCRStatus2.StorageGroupName + ” has failed”
$FromAddress = “FromAddress@yourdomain.com”
$ToAddress = “ToAddress@yourdomain.com”
$MessageSubject = “SCR Status Failure”
$SendingServer = “MAILSERVER”
$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody
$SMTPMessage.IsBodyHtml = $true
$SMTPClient = New-Object System.Net.Mail.SMTPClient $SendingServer
$SMTPClient.Send($SMTPMessage)
}
Else
{
Write-Host “Second Storage Group All Good!”
Exit
}

I’ve been playing around writing some simple PowerShell scripts today so I thought I would fix the reporting problem Microsoft haven’t.

I’ve written a simple PS script that gets the Status(Health), Replay Queue Length, Last Replayed Time and Last Full Backup Time and emails it to a specified address in a HTML table. Just use Task Scheduler to run this daily and you will receive the status of your SCR clusters.

You can download the script here EmailStorageGroupCopyStatusReport.ps1

Or view the script below:

#Replace the PRIMARYSERVER attribute with your production mail server, and the SECONDARYSERVER with your SCR replica
$MessageBody = Get-StorageGroupCopyStatus -Server PRIMARYSERVER -StandbyMachine SECONDARYSERVER | Select @{Expression={$_.StorageGroupName};Name=”Storage Group”}, @{Expression={$_.SummaryCopyStatus};Name=”Status”}, @{Expression={$_.ReplayQueueLength};Name=”Replay Que Length”}, @{Expression={$_.LastReplayedLogTime};Name=”Last Replayed Time”}, @{Expression={$_.LatestFullBackupTime};Name=”Last Full Backup”} | ConvertTo-Html

#Enter your mail server details
$FromAddress = “FromAddress@YourDomain.com”
$ToAddress = “ToAddress@YourDomain.com”
$MessageSubject = “Exch07 SCR Status”
$SendingServer = “MAILSERVER”
$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody
$SMTPMessage.IsBodyHtml = $true
$SMTPClient = New-Object System.Net.Mail.SMTPClient $SendingServer
$SMTPClient.Send($SMTPMessage)
#Written by Matt Shadbolt
#http://www.mattlog.net

Remember that you need to “Set-ExecutionPolicy RemoteSigned” in the Task Scheduler for the PS script to run correctly. Also, if you are going to run this PS script on a remote server you may need to add the MSExchange PS Snappin. To do this just add “Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin” to the first line of the script. You obviously need to change the mail server and recipient options.

Here’s the script download EmailMailboxSizeReport.ps1

And a break down of the script:

#Firstly, get the users mailbox… ONLY objects that are UserMailbox and not HiddenFromAddressListsEnabled
$MailboxUser = Get-Mailbox | Where {($_.RecipientType -eq “UserMailbox”) -and ($_.HiddenFromAddressListsEnabled -eq $False)}

#Secondly, get the mailbox statistics for the selected users. Some formatting also
$MessageBody = $MailboxUser | Get-MailboxStatistics | Sort-Object TotalItemSize | Select DisplayName, ItemCount, @{Expression={$_.TotalItemSize.Value.ToMB()};Name=”MailboxSize MB”} | ConvertTo-html

#Finally, enter your mail server details
$FromAddress = “FromAddress@YourDomain.com”
$ToAddress = “ToAddress@YourDomain.com”
$MessageSubject = “PowerShell Report Subject”
$SendingServer = “YourMailServerAddress”
$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody
$SMTPMessage.IsBodyHtml = $true
$SMTPClient = New-Object System.Net.Mail.SMTPClient $SendingServer
$SMTPClient.Send($SMTPMessage)

#Written by Matt Shadbolt
#http://www.mattlog.net

MSExchangeIS Error 9646: ” Mapi session “/o=DOMAIN/ou=Administrative Group/cn=Recipients/cn=UserName” Exceeded the maximum of 500 objects of type “objtFolder” “

As the error message suggests, the user experiencing this error has more than 500 folder objects open. Although this sounds pretty strait forward – its extremely difficult to have over 500 folders open – and highly unlikely the user has done this on purpose!

In my case, three users were experiencing this issue and didn’t have any more than the usual Outlook window open.

There are two possible causes to check:

1. The user has some sort of third party search feature installed (such as Google Desktop). These third party applications will index the mailbox and cause a huge amount of connections to occur. Either remove the search agent or disable its indexing of the Outlook folders.

2. The user has “Download shared folders (excludes mail folders)” enabled in Outlook. This feature does a similar thing to Cached Exchange Mode however it is downloading a local copy of the shared mailboxes that the user may have open. Un-tick this box and the trouble should go away.

It seems that some Cisco routers and IOS versions that use the ip inspect command on the outgoing interface have problems with the newer Exchange 07 message headers. Simply remove the ip inspect from the interface (no ip inspect) and the problem seems to disappear.

EDIT: I’ve since found that you don’t need to totally disable the ip inspect – you just need to remove the esmtp filtering from the list of ip inspect protocols. Matt.

You can check to see if your server is showing these symptoms by TELNETTing to the localhost on port 25 and attempting to manually deliver a piece of mail. You may receive the “insufficient resources” error.

A quick and dirty way to resolve this error without actually giving the server more resources is to disable the monitoring – this is recommended as a short term fix only.

To disable the Exchange Monitoring:

1. Browse to the EdgeTransport.exe.CONFIG file (normally found at %systemdrive%\Program Files\Microsoft\Exchange Server\Bin) and open the file in notepad
2. Find the string <add key=”EnableResourceMonitoring” value=”true” />and change the “true” to “false”
3. Now either restart the Exchange services or reboot the server (I like to reboot the server just to be sure!)

Again, this is only a temporary measure – and I would only suggest using it in a lab environment. However if you plan to upgrade your hardware in the short term this trick might just get you though.

Get-StorageGroupCopyStatus – StandbyMachine EXCHANGESERVERNAME

You will then receive the Copy status queues etc. If you receive the following “Suspended” output your replication isn’t working:

There are a couple of commands to restart the replication. Firstly, from the EMS suspend the replication by using:

Suspend-StorageGroupCopy -identity ‘Storage Group Name’ -StandbyMachine EXCHANGESERVERNAME

You will be prompted to confirm – choose Yes. Now restart the replication by using:

Resume-StorageGroupCopy -identity ‘Storage Group Name’ -StandbyMachine EXCHANGESERVERNAME

You should the replay the Get-StorageGroupCopyStatus command and hopefully you should find that the SummaryCopyStatus is now “Healthy”

set-publicfolder – Mapi Exception not found: Unable to set properties on object

The details in the error message suggest that it’s a permissions issue – however I found that it is not.

The fix for this error is surprisingly easy! All you need to do is create a public folder in the new public folder database. This seems to enable the new database and replication should start working.