by edward | Jul 6, 2019 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
In Exchange, mailbox moves and cleanup happen all the time, especially when you upgrading to newer versions etc. Now when you move mailboxes and you not using a 3rd party app like Odin that sits as an extra layer, you cannot see the store size from the web console. In...
by edward | Jun 11, 2019 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
As an IT Admin or Exchange Admin, you might have come across the question “When were the mailboxes created”. In this quick example, we will look at the script you can run to check all users in the Organization or just an individual mailbox. To check all...
by edward | Jun 8, 2019 | Exchange 2019 PowerShell, Exchange 2019
As an Exchange Admin, you might have help desk staff that need to run commands or do things on Exchange but you don’t want them logging into the Exchange Servers directly for company policy prevents it. Each case is unique and each business has it’s set of...
by edward | Apr 18, 2019 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
Exporting mailboxes is great but what if you only wanted information for a certain period as you need it for whatever reason, legal, manager, etc. Well using the Exchange Management Shell (EMS) you can run the following command to export the data: $Users = Get-Content...
by edward | Apr 15, 2019 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
There are many ways in PowerShell to check the mailbox database copy status in Exchange, here are some examples from the Exchange Management Shell (EMS): Blanket check.Per DAG check.Per Server check. Get-MailboxDatabaseCopyStatus * The above command runs across all...
by edward | Mar 7, 2019 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
With mailbox moves, you do get the few that fail and instead of updating each one with the -BadItemLimit switch you can do this one liner command to update them all before resuming them, here is the command: Get-MoveRequest | Set-MoveRequest -BadItemLimit 500...
