Tag: Exchange on premises

This is a common discussion, who should be in charge of High Availability (HA), the host virtualization operating system or the application? If you ask an electrician how to fix something, they’ll tell you to rewire it. If you ask a carpenter what is wrong, they will say rebuild it. If you ask a virtualization

Some of you may ask, what is OMA? Back in the day, Exchange 2003, mobile devices were starting to make their way into the corporate world. Outlook Mobile Access (OMA) was introduced to help provide a small, thin foot print to mobile devices. You have to also remember that back in 2003, cellular networks were not what they are

Yes, it would be supported. Any supported virtualization product on this list is supported: https://www.windowsservercatalog.com/svvp.aspx From an Exchange perspective, it wouldn’t care what it rides on. You can mix and match all day long, as long as the Exchange versions are consistent. In fact, the Exchange role requirements calculator doesn’t even care about virtualization, the

Just a reminder, Exchange Server versions have some important dates coming up: Exchange Server 2010 support will end on January 14, 2020 October 14, 2020 is the new date: https://docs.microsoft.com/en-us/office365/enterprise/exchange-2010-end-of-support Exchange Server 2013 has now entered extended support and that will end April 11, 2023 Exchange Server 2016 extended support ends October 14, 2025 Exchange

Mark Nivens created this HealthChecker.ps1 file for Exchange servers for your on premises environment. This script checks various configuration items on the Exchange server to make sure they match the recommendations published in the "Exchange 2013 Sizing and Configuration Recommendations" guidance on TechNet. It also reports on Operating System and hardware information. You can run it remotely against a single

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

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