In your environment, you might have that day when you need to perform a recovery of an Exchange Server as a windows update broke exchange or the underlying storage crashed and you need to recover as the OS won’t boot. What ever the case, it is not a difficult task, Read more…
Exchange 2016 CU upgrades don’t always go according to plan. In this scenario, one of my servers just wouldn’t upgrade but the rest did without error. The upgrade runs like normal from the CLI but fails with the below error: “Cannot start service MSExchangeServicehost……” When I went to check the Read more…
Recently on 2 of my machines, I started noticing the C:\ space drop quickly over a week. Running my script (ClearLogs) removes about 30-40GB but on this 600GB drive, pretty much 500GB has been eaten up. Checking through each folder, I came across this folder in the following location: C:\Program Read more…
Exchange 2016 CU13 introduced a few more fixes and is advisable to upgrade to it. The upgrades are generally seemless and we normally do them from command line, just easier than a GUI upgrade 🙂 Firstly, you need to ensure the following is done before hand: Reboot your system (a Read more…
Ever reboot your servers and when you login, all looks good on the surface but when you try and do stuff well it doesn’t actually work? In this scenario exactly that. Running coexistence with Exchange 2016 and 2019 and after a reboot, all seemed good. Exchange Management Shell launched fine Read more…
Head over to my page on Experts Exchange to view the article in detail: https://www.experts-exchange.com/articles/33593/Installing-Exchange-2016-and-Exchange-2019-into-the-same-environment.html
Running the command Get-MailboxDatabaseCopyStatus * on an Exchange 2010 Server that has Exchange 2016 in the environment, returns all the database copies for every version but today Exchange 2010 gave a weird error: A server-side administrative operation has failed. Operation failed with message: Error 0xe0434f4d (Unknown error …. This is Read more…
In Exchange, the above event seems to log from what we have picked up when working in the Exchange Management Shell, however we cannot find what is triggering it or what the fix is. We have not only seen it here but also on Exchange 2013 and 2019. A query Read more…
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…
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…