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

PowerShell thought process

One important aspect of leveraging PowerShell is to adjust your mindset. Listed are some topics to consider: Automate: Create scripts, functions, and modules to automate manual tasks. If you function up routine tasks, you and others can quickly and easily complete work duties more efficiently. Delegate: Once the functions and modules are built and deployed,

FieldNote: Big red button at the data center

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

PowerShell Core Support Lifecycle

Microsoft has updated the life cycle of software to the Modern Lifecycle Policy. The short answer is: faster, more frequent updates mean that version support is shorter. This makes sense in today’s agile software development environment. Instead of a three-year cycle for applications, and an additional 10+ years of support, the new agile process of

DAG’s spread across multi-domains?

Q: Can you spread an Exchange DAG (Database Availability Group) between two domains? A: No. Now the story: Say you have a single forest named: Contoso.com. In that forest, you have two child domains: East.Contoso.com and West.Contoso.com. You also have Exchange servers deployed in both East and West domains, but none in the root domain. Is it possible to host some

The Lingering Object Liquidator (LOL)

There is a tool that helps you identify Lingering Objects in an Active Directory environment. It is the Lingering Object Liquidator, or LOL for short. A description from the download site: Lingering Object Liquidator automates the discovery and removal of lingering objects from an Active Directory Domain Services forest. The tool uses the DRSReplicaVerifyObjects method