by Edward van Biljon | Feb 5, 2022 | Exchange 2019 PowerShell, Exchange 2016, Exchange 2016 PowerShell, Exchange 2019
In my previous article, we looked at configuring our TLSReceiveDomainSecureList and if you have one or two domains listed, you can view them easily, however if you have multiple items, the first few are shown and then you have …. at the end. What am I talking...
by Edward van Biljon | Feb 4, 2022 | Exchange 2019 PowerShell, Exchange 2016, Exchange 2016 PowerShell, Exchange 2019
In Exchange 2016 or 2019, you have the ability to accept TLS connections on a receive connector from a particular set of IP Addresses or single IP and have it use an SSL certificate. What I have seen happen is that receive connectors are not configured correctly in a...
by Edward van Biljon | Feb 3, 2022 | Exchange 2019 PowerShell, Exchange 2016, Exchange 2016 PowerShell, Exchange 2019
In Exchange 2019, same with Exchange 2016, you have your standard receive connectors that comes with Exchange once installed. To recap, here is the list: Default <ServerName>Client Proxy <ServerName>Default Frontend <ServerName>Outbound Proxy...
by Edward van Biljon | Mar 17, 2021 | Exchange 2019 PowerShell, Exchange 2010 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
In Exchange, whether it is Exchange 2010, Exchange 2013, Exchange 2016 or Exchange 2019, you may come across the request to set an Out off Office (OOF or OOO) for users. Generally when you set OOF for a user, they can do this from Outlook directly but there may come...
by Edward van Biljon | Jan 20, 2021 | Exchange 2019 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
In Exchange, you may notice that when you try and book a meeting room, you cannot go higher than 180 days. This is by default. To change this, you can run a simple PowerShell command and increase the value, take note you cannot go higher than 1080 days. The command to...
by Edward van Biljon | Jan 7, 2021 | Exchange 2019 PowerShell, Exchange 2013 PowerShell, Exchange 2016 PowerShell
In Exchange 2016 or even Exchange 2019, when you run cmdlets like Get-TransportServer you will receive a nice yellow warning to use the newer cmdlets. So Get-TransportServer has changed to Get-TransportService. If you head over to the event logs, the application log,...
