Exchange server quarter updates posted early

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

Safety Net has a limit

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,

What to name your DAG?

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.

You should have notifications of RRS feeds to updates on specific websites

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,

Controlling bandwidth in a DAG reseed

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

Ever changing life cycle process

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

To stay hybrid or not to stay hybrid…

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

Using PowerShell instead of command line to keep a transcript

Ok, so all of you that use Command Line (CMD.exe), it is probably time to stop and just use PowerShell. Now there is nothing wrong with cmd, as we’ve used it for many, many years. However, there is no transcript option available. Many of you know and some do not, that PowerShell has a built

Dynamic Distribution Groups, Distribution Groups, and Exchange hybrid

I recently ran into a customer that uses: Distribution Groups (DG), leverage Dynamic Distribution Groups (DDG), have started their move to Exchange Online (EXO), while nesting several DDG’s inside of DG’s. There are known work arounds that you should implement if you are in an Exchange hybrid configuration working with DDG’s. Since each realm bifurcates the