One of the jobs that’s fallen to me is to report on the successes (or otherwise) of our mailbox migrations. The output needs to get to people who may not have access to any of the Exchange management tools. Now my PowerShell isn’t great but with a bit of effort I trawled through my notes and beat some of my old script notes into shape as the scrap of Powershell you see below.<\/p>\n
What it does is load up the Exchange snap-in first (so that Exchange commands will be understood), creates a text file listing the successfully migrated mailboxes and then emails it out to the recipient of your choice. In our case I added further recipients on separate lines so that it could also log a ticket in our support system. This allowed our helpdesk to get a record of the migrations without needing access to a server.<\/p>\n
Add-PSSnapin Microsoft.Exchange.Management.Powershell.E2010 -erroraction silentlyContinue
\n$file = “C:\\migsuccess.txt”
\n$mailboxdata = (Get-MoveRequest | Get-MoveRequestStatistics | where {$_.status -match “Completed”} |ft alias, TotalItemSize, TotalMailboxItemCount, PercentComplete, BytesTransferred, ItemsTransferred -auto)
\n$mailboxdata | out-file “$file”
\nStart-Sleep -s 5
\n$smtpServer = “<Hub Transport Server><\/span><\/strong>”
\n$att = new-object Net.Mail.Attachment($file)
\n$msg = new-object Net.Mail.MailMessage
\n$smtp = new-object Net.Mail.SmtpClient($smtpServer)
\n$msg.From = “<from@address.com><\/span><\/strong><\/span>”
\n$msg.To.Add(“<your email@address.com><\/span><\/strong><\/span>“)
\n$msg.Subject = “Migration Report: Successes”
\n$msg.Body = “Dear Migration Watcher,”+”`r `n”+”Attached to this email is a daily report which lists all of the mailboxes which SUCCEEDED in their migration to Exchange 2010.”+”`n”+”These have been committed to the Exchange 2010 servers in full, without logging an error. The mailboxes’ content should therefore be unaltered, simply having been transferred in full to an Exchange 2010 server.”+”`r `n”+”Kind regards”+”`n”+”`r `n”+”OUCS Nexus Team’s friendly automessenger”
\n$msg.Attachments.Add($att)
\n$smtp.Send($msg)
\n$att.Dispose()<\/p><\/blockquote>\nThe actual command I used generated four reports rather than just listing the successful ones (substitute ‘Failed’, ‘Completed with error’ or ‘autosuspended’ \u00a0for ‘completed’ on the third line). One of the downsides of reusing old bits of PowerShell, rather than starting from scratch each time, is that this bit has to supply codes (‘`r<\/span>‘ and ‘`n<\/span>‘) to generate the paragraph\/new lines within the email. Nowadays I would probably make the body text of the e-mail a Powershell ‘here’ string so that the format matches what’s in the script. That makes it more readable \/maintainable while also offering scope for the use of parameters (such as $($mbox.DisplayName)<\/span><\/em> for personalising the ‘Dear User’ line). This was first written back in the days when I was still using Notepad as my editor…<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the jobs that’s fallen to me is to report on the successes (or otherwise) of our mailbox migrations. The output needs to get to people who may not have access to any of the Exchange management tools. Now … Continue reading