Category: Exchange

One issue Exchange engineers run into from time to time, is the need to restart IIS (Internet Information Services). Here is a simple way to restart IIS on all Exchange servers in the organization: Restart-ExchangeIIS I’ve considered scoping this to say just a few servers, but then, that’s easy to remote into a machine and

This Connect-ExchangeServer function runs the PowerShell code to log into an Exchange server on premises using remote PowerShell. Using the -Computer parameter (required), tells the function which Exchange server to connect to. Using the -Prefix parameter (optional), allows a modification to the noun of the imported cmdlets, so that you can have multiple connections in

Here are some handy short links that help Exchange Server engineers keep up with what's happening within the Exchange world. As always, it's best to have some kind of RSS feed notification, using tools such as: Microsoft Flow or IFTTT.com. The Exchange Team blog, you Had Me at EHLO: aka.ms/ehlo Exchange Server build numbers and

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

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

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

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,

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

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,

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,