Welcome to Matt Zaske Online

Another edition of MMS (MOA 2025) is now in the books, and by the time this post publishes it'll have been the better part of a month since it ended! How time flies! It was, as always, an outstanding event bringing the community together for the better part of a week, and I really thank those folks behind the scenes who pull it all together so swimmingly.

In the first post of this short series, I wrote about using the Deployment Researc

I've been a proponent of a dev/test CM (or just client device) lab environment for a long time.

Last summer, Let's Encrypt announced their intent to end their OCSP service, and this was formalized in December with key dates related to the change.

A couple times a year I do some spot checking and a little manual cleanup in AD. This is triggerd by inventory/asset management analysis. I say "spot checking" because by and large the existing business processes and automations take care of the vast majority of changes, but for a couple of reasons there are always a few stragglers.

A project cropped up recently that required editing a number of disparate Group Policies in our environment due to a network share path change.

I was originally given a list of GPOs that were (somehow) identified as in scope for change; however, I knew immediately the list was incomplete and omitted some valid matches. So I was left with a choice:

The last two posts were inspired by conversations at MMS Flamingo and focus on using Slack as the communication/receiver for notices relayed from a Task Sequence step

Last week I wrote about a basic process I have in place to fire off a Slack notification when a Task Sequence completes.

A number of years ago I started having my primary OSD Task Sequences "check in" as one of their last steps. Specifically check in with key information so I can follow up as necessary ("trust but verify") with downstream actions to ensure our asset management systems are properly updated.