With the recent security updates released for all versions of Exchange: Exchange Server 2019 Cumulative Update 1 (KB4471391), VLSC Download Exchange Server 2016 Cumulative Update 12 (KB4471392), Download, UM Lang Packs Exchange Server 2013 Cumulative Update 22 (KB4345836), Download, UM Lang Packs Exchange Server 2010 Service Pack 3 Update Rollup 26 (KB4487052), Download, also available on Microsoft Update The question comes

If you haven’t looked lately, and I know most of us don’t, but of possible interest to many is the Exchange Sever 2019 version only has a 7-year lifecycle. The stated end date of extended support is the same as the 2016 version. Product released Lifecycle start date Mainstream support end date Extended support end

Q: I’m a student and don’t have access to a credit card, but I want to learn about cloud computing and Azure, is that possible? A: YES! Students can start building your cloud future with Azure. Leverage the power of Azure, with over 25 apps to start to work with and study how the cloud can help you and

While the Exchange product group does try and release every 3rd month (March, June, September, December) and 3rd week of that month for quarterly updates, with the chatter about a possible security vulnerability, the Exchange PG is releasing these security fixes for all currently supported Exchange versions as noted on the eHelo blog page. There

Exchange 2013 introduced another mechanism to help ensure that e-mail gets delivered to users: Safety Net. This feature creates a copy of all inbound messages cross site (by default, but configurable). Exchange stores the messages in yet another .edb file and yet another storage place on the server. You can move the location of the files,

Was helping a customer the other day and the topic of what to name your DAG (Exchange Database Availability Group) was presented. One thought is to just name it ‘DAG’. Works well, but the issue is, when migrating from Exchange Server 2010 to Exchange Server 2013, or 2010 to 2016, or 2013 to 2019, etc.

If you are in IT and work with a specific technology, or a group of technologies, then you should truly leverage the ability to get notifications from product group web sites, or at least important sites that you ought be following. Recently, Exchange servers had an issue with specific Windows Updates. Without getting a notification,

Q: Is there a way to control bandwidth within a DAG (Database Availability Group) during a reseed process? A: No. However, that’s not the complete story. The question comes up when engineers need to reseed a database (DB). And while there is no native option to control bandwidth, there is a work around. Scenario: One of the

Service Packs for Microsoft products, at the time, were provided with 12-24 months of support depending on the product after the release of the next service pack. For Exchange Server 2013, the SP1 is caught in an awkward state of support perpetuity until Exchange 2013 itself hits the end of support lifecycle as there was

That is the question and the answer is: It depends, but most like yes. You need to ensure that you have no on premises dependencies. I’ve had this conversation with more than 5 customers in the past 2 weeks, so thought I’d present the discussion of the options and thought process around removing the Exchange servers from