Another scary post on Halloween. Scary that is, if you're not following security best practices. This bad actor group exposes a timing issue with O365 safe links. They create a certificate for a site, that looks ligament, and then exploit it as quickly as they can. For example: Securemail.contoso.com. Since the cert is valid and

Yes.  However, the PG chose not to extend Jetstress functionality to cover MCDB (on Flash/SSD storage), therefore, Jetstress will only validate HDD performance for Exchange Server 2019. What is JetStress? The JetStress tool (download) is a Microsoft supported tool that validates database hard drive performance before you install the Exchange Server application on a Windows

What an easy way to clean up the view of your PowerShell path. Add this into your profile if you want to save some screen space and work in a directory other than c:\. You can also grab the current time and place that in the prompt. Use Get-Location to see which path you are

The Junk E-mail Reporting Tool lets you easily report misclassified e-mail to Microsoft and its affiliates for analysis to help improve the effectiveness of the e-mail protection technologies. From the Outlook ribbon, you can click Report as Junk, Report as Phishing, or Report as Not Junk to send a report to Microsoft. You will be

Where in the world is your mailbox! While not to be confused with Get-MailboxLocation, this function is designed to just give a count and location of the data center hosting up all your mailboxes. It does run Get-Mailbox against the entire online tenant, so that process could take a while depending on the number of

In the part 1 of this function, we covered an option to set all Exchange servers to use every AD site in an organization, minus any 'deployment' ones. But what if you have a very large organization, with multiple data centers hosting Exchange servers, various regions to support, and you want to target specific locations

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