Get-DotNETVersion
The Get-DotNETVersion function presents the current .NET version on a machine. This is part of the MO_Module PowerShell code that helps administrators in their daily tasks. From an Exchange Server perspective, .NET support is very sensitive to which version of Exchange and which .NET is allowed to be used. This value also changes based on
MO_Module introduction
I’d like to introduce you to my MO_Module. It’s a PowerShell module, combining several daily administrative tasks into simple Verb-Noun Functions for engineers to perform their jobs easier. I was developing/maintaining several different PS modules, which became more work, so I thought I’d just combine everything into one single place. Since my primary technologies are
Exchange Server 2019 role requirement calculator
Just a reminder, the Exchange Server 2019 role requirement calculator is now only available in the current Cumulative Update download. To obtain the CU downloads, you must have access to the Microsoft Volume Licensing Service Center. The main reason the role requirement calculator ships in the CU’s, is that the Exchange Product Group now owns
Exchange Server June 2019 updates
It worked out this time: 3rd month, 3rd week, on a Tuesday for the Exchange Server product updates. Not a lot of changes, but a couple of items of interest, the first one, the Exchange Product Group (PG) continues to tighten Active Directory security, which I absolutely love. They have added a few deny values,
Exchange Server: Third Month, Third Week
Just a reminder, the Exchange Product Group (PG) is (usually) following the current cadence of releasing Exchange Cumulative Updates (CU) every third month (March, June, September, December) and the third week of that month. This allows a predictable rhythm for customers to plan when to upgrade their Exchange servers. With this planning, customers should download
Does Exchange Server 2016 or 2013 allow the use of the Windows Server 2016 cluster CLOUD WITNESS feature?
https://docs.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness No, neither version supports the cloud witness option. However, Exchange Server does fully support an Exchange File Share Witness server in Azure. If you choose this option, you’ll need a writable Domain Controller and a Windows Server to host up the File Share Witness directory. The reason for a Windows Server for the FSW,
Q: Can you reduce the amount of memory Exchange is allowed to use on a physical server?
A: Yes Sometimes customers wish to use certain hardware for installing the Exchange Server application that already has a specific amount of RAM in place, and that RAM is not within the current recommended range for Exchange. Can you make this change at the hardware level and not have to take out the RAM? Yes,
Exchange needs Active Directory
I was recently called into help on a ‘Crit Sit’ (Critical Situation) that a customer had with their Exchange 2010 environment. During the previous night, a few of the Databases that have a total of 3 copies spread across a DAG flipped to different servers. This ultimately was caused by Exchange asking AD a question
Can you skip CU’s?
The question isn’t can you but should you. What’s a CU? Starting with Exchange Server 2013, the Exchange Product Group (PG) went to a quarterly updating process titled Cumulative Updates. These CU’s literally uninstall and reinstall Exchange when they are applied to a server. This is one reason a CU install process can take several hours. You’ll want to
Schema administrator has a mailbox
Q: Why does the Schema Admin have a mailbox? A: It’s by design! What? Yes, this is normal behavior for Exchange Server 2013 & 2016. If the account you are using for the install does not have a mailbox, one will be created for that account. Typically, engineers will use an Active Directory (AD) account with a mailbox when