Month: September 2019

In this blog post a few years ago: https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Exchange-Active-Directory-Deployment-Site/ba-p/604329 was a discussion around Exchange AutoDiscoverSiteScope information. The good news is, it worked perfectly in a lab, however, rarely is any production environment like a lab. Thus, there was some missing information. We're updating the article to include solutions to fix the problem. This post is

The function: Get-DAGDatabaseInformation works in Exchange versions that a DAG (Database Availability Group) exists. From 2010 through 2019, this simple little function presents information to the end user about the status of the databases. In the Exchange Admin Center (EAC), the GUI that is, one must click on each server and each DB to see

Well, the one constant in IT is change. The MO_Module was too confusing for people to know what it was for, so I went back and updated the Exchange_AddIn PowerShell Module. All of the updated functions over the past several months are being cut over, I've updated all of the helpURI values, and added in

Had this question the other day, what are current Exchange on premises limits for messages? And can end users send 10GB file attachments? This site talks about limits, but it also depends on what is available vs. what you can support. By running some PowerShell code, the answers can be provided: Get-ReceiveConnector  | Set-ReceiveConnector -MaxMessageSize

Thought this would be a good Labor Day discussion, about how much labor an Exchange administrator performs. The short answer is, you’ll still be very needed if/when your company decides to move to Exchange online in O365. So you think you’ll lose your job when your company moves Exchange on premises content into O365 using