Unlocking the Potential of Exchange Online
How to Disable New-MoveRequest for Local Mailbox Moves
Microsoft Exchange Online is one of the most popular cloud-based email services available today. It’s easy to set up, secure, and cost-effective, which makes it an ideal solution for businesses of all sizes. And with the right configuration and management, Exchange Online can unlock its full potential.
One of the most powerful features of Exchange Online is the ability to move mailboxes between different locations. This is often done when users are relocated, or when a business acquires another organization. Microsoft provides a cmdlet called New-MoveRequest which can be used to move mailboxes between different Exchange servers. However, this cmdlet does not support moving mailboxes within the same Exchange server.
In this article, we’ll discuss how to disable New-MoveRequest for local mailbox moves. We’ll also cover how to use PowerShell scripts to automate the mailbox move process.
What is New-MoveRequest?
New-MoveRequest is a cmdlet provided by Microsoft that can be used to move mailboxes between different Exchange servers. It automates the process of moving the mailbox data, and it can also be used to set up a cross-forest mailbox move.
However, this cmdlet does not support moving mailboxes within the same Exchange server. For example, if you want to move a mailbox from one database to another on the same Exchange server, you’ll need to use a different method.
Disabling New-MoveRequest for Local Mailbox Moves
The first step in disabling New-MoveRequest for local mailbox moves is to create a new policy. This policy will disable the New-MoveRequest cmdlet when it’s used to move mailboxes within the same Exchange server.
To create the policy, open the Exchange Management Shell and run the following command:
New-ThrottlingPolicy -Name ‘NoLocalMoves’ -EnableMoveMailboxes $false
This command creates a new policy called ‘NoLocalMoves’ which disables the New-MoveRequest cmdlet for local mailbox moves. Once the policy has been created, you can assign it to the mailbox you wish to move. To do this, run the following command:
Set-Mailbox -Identity ‘UserName’ -ThrottlingPolicy ‘NoLocalMoves’
This command assigns the ‘NoLocalMoves’ policy to the mailbox with the username ‘UserName’. Once the policy has been assigned, New-MoveRequest will be disabled for this mailbox.
Using PowerShell Scripts to Automate Local Mailbox Moves
Although disabling New-MoveRequest will prevent local mailbox moves, it’s still possible to move mailboxes within the same Exchange server using PowerShell scripts.
Microsoft provides a script called Move-LocalMailbox which can be used to move mailboxes within the same Exchange server. This script automates the process of moving the mailbox data and setting up the appropriate permissions. To use this script, open the Exchange Management Shell and run the following command:
Move-LocalMailbox -Identity ‘UserName’ -TargetDatabase ‘TargetDatabase’
This command moves the mailbox with the username ‘UserName’ to the database ‘TargetDatabase’. Once the mailbox has been moved, you can assign the ‘NoLocalMoves’ policy to the mailbox in order to prevent it from being moved again.
Conclusion
Microsoft Exchange Online is a powerful and cost-effective email service that can be used to unlock the potential of your business. And with the right configuration and management, Exchange Online can be used to its fullest.
In this article, we discussed how to disable New-MoveRequest for local mailbox moves. We also discussed how to use PowerShell scripts to automate the mailbox move process. With the right configuration and management, you can ensure that your Exchange Online environment is secure and efficient.
References:
Disabling New-MoveRequest for Local Mailbox Moves
