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