{"id":1388,"date":"2018-03-09T09:21:28","date_gmt":"2018-03-09T07:21:28","guid":{"rendered":"https:\/\/msb365.abstergo.ch\/?p=1388"},"modified":"2023-06-23T13:25:09","modified_gmt":"2023-06-23T11:25:09","slug":"another-10-useful-powershell-cmdlets-for-exchange","status":"publish","type":"post","link":"https:\/\/www.msb365.blog\/?p=1388","title":{"rendered":"Another 10 useful PowerShell cmdlets for Exchange"},"content":{"rendered":"

After all the positive feedback to my article \u201c10 Useful PowerShell cmdlets for Exchange<\/a>\u201d (thanks again to Steve Goodman<\/a>), I have decided to write a second part of it with another 10 useful PowerShell commands for Exchange and Office 365.<\/p>\n

Same procedure as the last time. Some of you may already know the commands, but for some of you they are maybe new\u2026<\/p>\n

In any case, I wish you fun with reading this article\u2026<\/p>\n

\u00a0<\/p>\n

This time, I will start with a command for Office365 and Exchange\u2026<\/p>\n

\u00a0<\/p>\n

\n

1 GET-MIGRATIONUSER<\/h4>\n

\u00a0<\/p>\n

Migrating mailboxes from one Exchange to another, or even to Exchange Online is no rocket science anymore. How to do that, we can find in many articles in the Tech Blogs all over the world. I want to write here about how to check the status of the migration. All we need to do is to connect by PowerShell to the right endpoint. In this example, I am connecting to the Exchange Online by using the following command:<\/p>\n

$UserCredential = Get-Credential\r\n$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https:\/\/outlook.office365.com\/powershell-liveid\/ -Credential $UserCredential -Authentication Basic -AllowRedirection\r\nImport-PSSession $Session<\/pre>\n
\u00a0<\/p>\n
After I am connected to my endpoint, I can check the status of the migration batch with the following command:<\/p>\n
Get-MigrationUser -BatchId StagedBatch1 | Get-MigrationUserStatistics<\/pre>\n
As we can see in the screen shot, we get the status of any move request\u00a0within our migration batch.<\/p>\n
\"\"<\/p>\n
By knowing this command and understanding PowerShell, we are free to modify this command as well. Here\u00b4s another example:<\/p>\n
Get-MigrationUser -BatchId BATCH | where {$_.Status -ne 'Completed'} | Get-MigrationUserStatistics<\/pre>\n
In this example, only those mailboxes will be shown, which don\u2019t have the status \u201ccompleted\u201d. This is very helpful\u00a0to keep an easy overview of huge migration batches .<\/p>\n
\n
\u00a0<\/p>\n
2 GET-MESSAGETRACKINGLOG<\/h4>\n
By working as an Exchange administrator or in 2nd<\/sup> level support, one of the main tasks is to track messages. Microsoft has created the Exchange Toolbox for this.<\/p>\n
\"\"<\/p>\n
If we start it, we can see a collection of tools, which help us to investigate some issues.<\/p>\n
\"\"<\/p>\n
However, to check the Tracking Log there is a faster and easier way to do it.<\/p>\n
We simply can use the following PowerShell command for that:<\/p>\n
Get-MessageTrackingLog -Start \"02\/26\/2018 08:23:00\" -End \"02\/28\/2018 17:00:00\" -Recipients $recipientSMTP -Server $ExchServer<\/pre>\n
In my example, I was searching for all mails sent during a time range on a specific exchange server, which have been sent to a specific recipient:<\/p>\n
\"\"<\/p>\n
However, there are also some other options for searching. Instead of searching by recipient, we are also able to search by:<\/p>\n