Welcome to Matt Zaske Online

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.

After spending much of the month of August on a European vacation, I'm back and preparing for my sessions at MMS Flamingo Edition coming up in October.

...or, How I Suffered Through an 'If it Can Go Wrong, it Will Go Wrong' Scenario for a One-Off Export of Database Tables

This is one of those posts I'm writing up because in the moment I was so incredibly frustrated about how unnecessarily complex this action was, and I still have the various browser tabs that ultimately provided me the necessary bits open.

Many years ago I wrote about the way I automatically generate the OSDComputerName value for most devices in my fleet.

If you work with a lot of disparate dev and test devices across different domains, tenants, etc., you might run into the sort of Windows activation issue I encounter.

A recent project I worked on required setting up more SSH key authentication, and seeing as how I'd not written about it for two years since the last iteration, it seems fitting to do another quick primer on setting that up for SSH...the 2024 edition.

I've been using the Windows Subsystem for Linux (WSL) almost as long as it's been generally available, and I use it for all sorts of things.

I haven't written anything up about Google stuff in a while, and since this topic came up a few times in as many weeks (including from conversations at BrainStorm K20) I figured it's time to share the solution I've used several times.