In Exchange 2019 but in any version, you cannot mix Exchange versions so they are part of the same DAG. For example, you cannot add an Exchange 2013 server to a 2016 DAG. I though I would test Exchange 2019 to make sure we don’t have a bug like in Read more…
Strange thing how Exchange will work and after a reboot you cannot run any commands. In my previous post where we recovered the Exchange Security groups, all seemed fine until commands were run the Exchange Management Shell. The famous error “The term ‘command’ was given for the simplest command “get-queue”: Read more…
In Exchange, not only 2019, you might come across a problem where the security groups are corrupt or have been deleted, this can be by accident or maliciously. To fix this, you will need to run the setup command with the PrepareAD switch. It might sound easy but you will Read more…
With the announcement of Exchange 2019, Unified Messaging was said to be removed from this version. However if you look at the properties of an Exchange 2019 Server you will see an option for unified messaging but get an error and then the page just closes: This is probably a Read more…
Strange one in my Azure VM, booted my domain controller and then a few minutes later I booted my Exchange 2019 VM, only to find that it won’t accept connections on RDP. Received the famous NLA authentication error. That was fixed with a remote command from the domain controller, here Read more…
When you install Exchange, it can be any version like 2013 or 2019, when you connect outlook to the server it works without error. However the moment you add an SSL certificate and the names are different you start getting popups on your outlook clients: The name on the security Read more…
In Exchange 2019, like Exchange 2013 etc, you can use a wizard to configure all your External URL’s, take note this does not change the Internal URL or the Autodiscover URL, you can change the Autodiscover one as per this article. Let’s go through the wizard that is available from Read more…
In one of my previous posts, we looked at Cipher Suites and locking down Server 2016 with Exchange 2016. In my lab, I ran the same software but this time on Server 2019 running Exchange 2019. On Server 2016 almost all the protocols were selected along with the ciphers, hashes Read more…
In Exchange, adding a simple mail account would be a simple process, you enter in your information, email address and password and you confirm it and then outlook does it’s checks with autodiscover etc. and if successful your account sets up and you are able to login. In Exchange 2019 Read more…
In my Exchange lab I have been experimenting with Cipher Suite lock down and closing holes in SSL. Here are a list of items that we went through: IIS Crypto check and configure. SSL Labs website check. SSL Certificate check and validations. Strict Transport Security – IIS Firstly, I downloaded Read more…