Category: Notes from the Field

I was recently called into help on a ‘Crit Sit’ (Critical Situation) that a customer had with their Exchange 2010 environment. During the previous night, a few of the Databases that have a total of 3 copies spread across a DAG flipped to different servers. This ultimately was caused by Exchange asking AD a question

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.

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

Story 1: One day, a maintenance worker went downstairs to perform some work in the company’s data center. He walked up to the door, saw a big red button, with no label, and assumed it was the way to open the door. Why not have automatic doors that need a button? He pushed it, the

Sometimes you must store a password for an account in a PowerShell script file. One option is to leverage the ConvertTo-SecureStringcmdlet. By running this cmdlet on a machine, with a specific password, a secure string is generated. You put that value into your file, and then you can run a ConvertFrom-SecureSting to run the script securely. However, I