{"id":15564,"date":"2022-10-18T07:27:27","date_gmt":"2022-10-18T07:27:27","guid":{"rendered":"https:\/\/www.insentragroup.com\/au\/insights\/uncategorized\/removing-your-last-exchange-server-part-3-reviewing-common-commands\/"},"modified":"2024-10-10T08:08:02","modified_gmt":"2024-10-10T08:08:02","slug":"removing-your-last-exchange-server-part-3-reviewing-common-commands","status":"publish","type":"post","link":"https:\/\/www.insentragroup.com\/au\/insights\/geek-speak\/modern-workplace\/removing-your-last-exchange-server-part-3-reviewing-common-commands\/","title":{"rendered":"Removing Your Last Exchange Server: Part 3 \u2013 Reviewing Common Commands"},"content":{"rendered":"\n

Welcome back to Removing Your Last Exchange Server blog series. In part two Remote Recipient Commands, we summarised the actions available for the Recipient Management PowerShell Commands<\/a>, such as \u201cget\u201d, \u201cset\u201d, \u201cenable\u201d and \u201cremove.\u201d<\/p>\n\n\n\n

For the third and final part of this series we will be reviewing the more common commands you will likely be using regularly to manage your recipients synced from on-premises to M365<\/a>.<\/p>\n\n\n\n

RemoteMailbox<\/h2>\n\n\n\n

When you finally remove your last Exchange server, the most common scenarios you will likely encounter will deal with managing your remote mailboxes. My colleague, Aaron Parker, also wrote a blog about using the Enable-RemoteMailbox Command which I highly recommend.<\/p>\n\n\n\n

From the perspective of your on-premises environment, all of your mailboxes will now be M365 mailboxes\u2026remote mailboxes.
The most likely scenario will be when you are creating new user accounts. Often my customers have first created the AD user account in Active Directory and then executed the following command to enable an M365 mailbox for the user:<\/p>\n\n\n\n

Enable-RemoteMailbox -Identity \u201cTed Williams\u201d -RemoteRoutingAddress TedWilliams@GreatestHitter.mail.onmicrosoft.com<\/code><\/pre>\n\n\n\n
The above command will take the AD user \u201cTed Williams\u201d and add the Exchange attributes to his user account. Upon a successful sync to M365, M365 will create a mailbox for Ted Williams. Remember to license the user in M365! In some cases, you may want to review the properties of a remote mailbox. To do so, you can run the following command:<\/p>\n\n\n\n
Get-RemoteMailbox -Identity \u201cTed Williams\u201d | FL<\/code><\/pre>\n\n\n\n
This will provide all the attributes for the specified user.<\/p>\n\n\n\n
Remove-RemoteMailbox vs Disable-RemoteMailbox<\/h2>\n\n\n\n
Please note Disable-RemoteMailbox will disable the user\u2019s M365 mailbox but keep the on-premises AD account. Remove-RemoteMailbox only applies to shared mailboxes in the cloud. It will delete both the shared mailbox and the associated on-premises AD account.<\/p>\n\n\n\n
To remove the mailbox but keep the AD account:<\/p>\n\n\n\n
Disable-RemoteMailbox \u201cDerek Jeter\u201d<\/code><\/pre>\n\n\n\n
Derek Jeter will still have an AD user account, but his mailbox will be deleted by M365.<\/p>\n\n\n\n
To delete a user in AD and its mailbox, I would recommend following the easiest method, which is to delete the AD object. This will remove the mailbox from M365 upon the next sync.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
As you would have noted throughout this blog series, there are several commands which come with the Remote Recipients management toolset. It may seem overwhelming at first if you\u2019re used to using a GUI, but over time you will become comfortable with the process of managing your remote recipients from on-premises. Heck, you may even decide to script your user onboarding process through scripting. Go crazy!<\/p>\n\n\n\n
If you would like Insentra’s IT Migrations<\/a> to help your company with removing your last Exchange server in your hybrid configuration, please contact us<\/a>.<\/p>\n\n\n\n