Exchange Server Subscription Edition
In this article, Jaap Wesselius provides an overview of Exchange SE, discusses possible upgrade paths, and outlines Exchange server support.
In this article, Jaap Wesselius provides an overview of Exchange SE, discusses possible upgrade paths, and outlines Exchange server support.
Exchange 2013 support ends on April 11, 2023. After that, Microsoft will not make fixes for security or functionality problems available to customers. It's time to make the decision to upgrade to Exchange 2019 or move to Exchange Online. Most organizations will find that Exchange Online is the right choice. Exchange 2019 is appropriate for organizations that have the right skills, experience, and investment to run a secure Exchange service.
For the first episode of 2022, Paul Robichaux and I didn't think we'd still be talking about Microsoft Exchange. But, here we are - as with the new year, new problems in Exchange On-Premises greeted Exchange admins. On the show this week we discuss Y2K22 first, and then take a deep dive into why 2022 is beginning, yet again, with Exchange On-Premises issues.
Microsoft has issued security updates for Exchange 2013, 2016, and 2019. The updates can only be applied to servers running up-to-date cumulative updates. Organizations running Exchange 2016 or 2019 should apply the updates as a matter of urgency because of a known vulnerability circulating in the wild.
If you've migrated to Exchange Online, make sure you stop publishing your Exchange Servers to the internet. After a standard Hybrid migration, you still might be reliant on Exchange Server and in this article you can find out why and how to move remaining web services to Microsoft 365.
A new Exchange vulnerability has been disclosed this week known as ProxyToken that allows someone who can access an Exchange 2013, 2016 or 2019 server over HTTPS to perform configuration actions against mailboxes of their choosing, such as setting forwarding rules. Find out what you need to do to protect your organization.
Microsoft has released security updates for Exchange 2013, Exchange 2016, and Exchange 2019 to fix some remote code execution vulnerabilities. It's time to update your on-premises servers again, including those used for hybrid management. Let's not give those nasty hackers any easy targets to attack.
This is the third article in a continuation of our weekly series celebrating the 10-year anniversary of Office 365. Microsoft MVP Nicolas Blank shares his experience as a Microsoft Certified Master for Exchange 2010, and how his world changed drastically over the past ten years as he followed Exchange into the Cloud.
The Hafnium attack on thousands of on-premises Exchange servers is a wake-up call for their administrators and the organizations using the email service. Ten years ago, it was a reasonable decision to stay on-premises. Five years ago, you could argue the same case and companies with bad network connectivity to the internet or specific security requirements were happy to stay on-premises. Now? In a world of increasing threat, staying on-premises looks a lot more risky. For most, it's time to move to the cloud.
Microsoft has issued critical security updates for Exchange on-premises servers. The fixes close off four known vulnerabilities which expose Exchange to day-zero attacks. It's important to apply these updates ASAP.
Microsoft has released new cumulative updates for Exchange Server 2016, Exchange Server 2013, and Exchange Server 2010 SP3 in June 2018.
Exchange Server 2013 has reached the end of mainstream support and is now in extended support, with the upcoming Cumulative Update 21 planned to be the last CU released.