bdam555.bsky.social
@bdam555.bsky.social
I mean, the timing is pretty epic:
February 24, 2025 at 5:44 PM
Would you be able/willing to push up a compiled binary of the latest in GitHub's releases since the download links on the website are all dead?
January 28, 2025 at 1:51 PM
Yea, I mean they wrote a whole fricken movie about it!
(Office Space)

Be sure to pour one out for the Cobol cowboys that kept society from collapsing. At least for a few more years.
January 8, 2025 at 1:59 PM
If at all possible, be great to keep the docs in the same repo as the source code. If only so they can be forked/updated alongside the code.

I'm not sure how I/anyone could help with that w/o access to the repo, but I'd be happy to play around and see if I could get them in there.
December 16, 2024 at 4:58 PM
Thanks for releasing this into the wild Jason!
December 16, 2024 at 4:36 PM
Zac Bowden has the deets that the important bits from that article are unchanged from two years ago:
x.com/zacbowden/st...
December 11, 2024 at 3:59 PM
After some digging and discussion, I do not believe this is a change at all. The recent reporting is, for the most part, bogus.

No change has been made to the OS to ignore these requirements. There are, however, known reg keys to do so.

That article clarifies what happens when you take that route.
December 11, 2024 at 3:25 PM
That's my understanding as well.

Add to that recent reporting on "MS doubling down on Win 11 TPM requirements" and I'm l'eh confused.

Is this a change? Something new? And all we get is this crummy KB?
December 11, 2024 at 2:25 PM
Yea, I can't quite figure out if that document is new or what. I saw some media outlet point to it as "MS drops Win11 hardware requirements."

Did anything actually change here?
December 11, 2024 at 1:41 PM
<looks at fiber on pole at end of street and weeps>
December 10, 2024 at 2:29 PM
Keeping them alive was its own reward though.

MBAM was staring down an EoL with no alternative until #ConfigMgr came along.
December 9, 2024 at 11:51 PM
For a while there it looked like #ConfigMgr would be the team at MS that sort of collected these key on-prem pieces that remain highly used but were outside of MS's cloud-first strategy.

MBAM for instance, some hoped MDT would join the stable as well. So WDS would have made sense.
December 9, 2024 at 7:16 PM
Your timing is spot on: @jordantheitguy.bsky.social lost the update lottery this month and after starting with a scalpel, then a screwdriver, then a hammer, the sledge didn't work either.
So ICBM: OS repair from ISO
November 22, 2024 at 3:53 PM
Which is exactly why, mentally, we all think of it as Autopilot v2.
November 21, 2024 at 1:58 PM
Thanks for confirming.
I don't have a dog in that fight; but can at least help drive clarity. I mean, disappointing clarity for some, but clarity none-the-less.
November 20, 2024 at 5:16 PM
<facepalm> Sorry, for reasons entirely unknown to me I decide to context switch over to the other OTHER W365 announcement: a Microsoft branded thin client! <ducks>

Apparently it's W365 only; wondering if that's a permanent stance.
November 20, 2024 at 4:13 PM
The blog outlines a scenario where Adele has a dedicated cloud PC logging into a shared cloud PC.

Would admins not target Adele with apps? What happens when she logs into the shared PC?
November 20, 2024 at 4:07 PM
Also, a lot of chatter about this not supporting AVD.

Is there any reason to hope for that on the horizon?
November 20, 2024 at 2:04 PM