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

This is another handy one to use, which allows connecting to Exchange Online easily. Similar to the O365_Logon module I have published, this function includes a prefix option. The prefix appends a value to the noun of cmdlets that allows you to run more than one remote session in the same PowerShell console that you

Need to know a member count of ALL distribution groups and e-mail enabled security groups in your organization that exports to a CSV file? Then this function is for you. Get-GroupMemberCount This function simply creates a .CSV file of all the e-mail enabled groups and current member count. May not be the most elaborate task,

These two are really good functions. While I just used others’ code, I do give them credit, but to be able to ‘function these up’ is very handy. Not that I’m lazy…OK, I’m efficient, but having verb-noun at your fingertips, whenever you need to run something, is very convenient. Furthermore, I can’t tell you how

Many times, when using Get-Date in PowerShell, it is very easy to have start and end times for reporting processes. However, the issue is, the Get-Date cmdlet runs and obtains the time when it is run. If you want to run a specific time, say at exactly midnight every day, there is a way to

Many times in an Exchange server, the IIS (Internet Information Services) is not the issue, but only the sub-set Autodiscover Application Pool. Therefore, once again, instead of just a one-off cmdlet against a single server, we have this function, to blast out to all Exchange servers, to restart their Autodiscover (sometimes referred to as AutoD),

Need to show time in UTC (Universal Time)? There is a 'method' with the Get-Date cmdlet. If you run: Get-Date | Get-Member You'll find that one of the methods is ToUniversalTime() which allows you to output the time of the local machine, converted to the UTC time. Run the code below to show how the