Tag: Exchange

The End of Life for Exchange Server 2019 and 2016

What It Means for Your Organization and How to Prepare Understanding End of Life support for Exchange Server 2019 and 2016 Microsoft Exchange Server has been a cornerstone of email and collaboration for businesses of all sizes for decades. However, as technology evolves, so too does the lifecycle of the software we rely on. Both

Exchange SE: The Simplicity of an In-Place Upgrade from Exchange Server 2019

Why Exchange SE Makes Upgrades Easier Than Ever With Exchange Subscription Edition (SE), Microsoft's latest evolution in their Exchange Server line, an in-place upgrade is possible. This is literally just a rebranded, Exchange 2019 CU16. Which is why an in-place upgrade is available. Because it is just another Cumulative Update (CU) installation. Conclusion If you

Exchange Server SE Edition Goes RTM: What Customers Need to Know

Preparing Your Organization for Deployment Success Introduction Microsoft has officially announced the Release to Manufacturing (RTM) of Exchange Server SE Edition, marking a significant milestone for organizations relying on on-premises email infrastructure. What Does "Release to Manufacturing" Mean? Release to Manufacturing (RTM) is the stage when a product's code is finalized and delivered to manufacturers

Where is OMA?

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

Can an Exchange DAG (2010 or higher) run on two different virtual platforms?

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

Exchange Server important dates

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

Will Jetstress be updated for Exchange Server 2019?

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

Set-AutoDiscoverSiteScopeExchangeServers Part 2

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

Set-AutoDiscoverSiteScopeExchangeServers Part 1

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

Exchange_AddIn updated

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