by Edward van Biljon | Jan 5, 2021 | Exchange 2019 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
If you have backups in Exchange, you know that you can go to the backup and recover items, either by creating a recoverable mailbox database or performing item level restore to a mailbox or PST file. In Exchange 2016, can also be Exchange 2019 or Exchange 2013, you...
by Edward van Biljon | Oct 27, 2020 | Exchange 2019 PowerShell, Windows Server 2019 PowerShell
When you configure your POP/IMAP Service on Exchange 2019, manually going to services and changing the startup from Manual to Automatic just takes time. With PowerShell, you could add this to a script so when you license your server and enable your SSL certificate,...
by Edward van Biljon | Jul 21, 2020 | Exchange 2019 PowerShell, Exchange 2019
Here is a quick tip on how you can open the Exchange Management Shell (EMS) on Windows Server 2019 Core. In your Elevated command prompt, type in PowerShell and Press Enter. Next, type in the following command and then press enter: Add-PSSnapin...
by Edward van Biljon | Jul 17, 2020 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
Mailbox migrations in an Organization are part of many Exchange Admins duties, this can be to a newer version of Exchange or simply migrating off a large database to smaller ones. If you are looking after a big organization and need to monitor migrations, PowerShell...
by Edward van Biljon | Nov 16, 2019 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
Quick tip for the day. Ever wanted to remove an alias from a Distribution Group and wondered how to do this with the Exchange Management Shell (EMS). It is pretty simple, you run the following command below: Set-distributiongroup GroupEmailAddress –EmailAddresses...
by edward | Nov 7, 2019 | Exchange 2019 PowerShell
As you would have noticed in not only Exchange 2019 but 2016 that when you type a certain command you will receive a nice yellow warning to use the new cmdlet instead. For example, I ran the following command: Get-TransportServer And as you can see below, the warning:...
