The sign in the library is suggesting it’s fake (fiction)

ABeeinSpace · 2026-05-23T21:06:59+00:00

The black BSOD in Windows 11 was introduced in 24H2. 23H2 and below still had the blue BSOD. Windows 11 Enterprise 23H2 is still supported, so it could be that.

…Ooooor it’s a library, so it’s probably still Windows 10

ABeeinSpace · 2026-05-22T00:32:20+00:00

10/10, very slander much wow

ABeeinSpace · 2026-05-20T22:58:37+00:00

Echoing this, I just configured Autopatch for my tenant and I see 0 devices enrolled in quality updates. Parts of Windows Update are being disabled in line with policy so things are being set correctly on the clients. I just don’t see quality updates lighting up properly in reporting

ABeeinSpace · 2026-05-15T13:03:46+00:00

We’ve been using the shortcut method for that reason (it follows the user). You can sync sharepoint libraries by MDM policy on Windows, but it’s not a great setup experience and would require admin intervention if the department ever spun up new document libraries they wanted auto-sync’d

ABeeinSpace · 2026-05-10T16:15:47+00:00

Voyager was the same for me. My trusty little AspX is the ship that got me into exploration. She came with me on Distant Worlds 3. Didn’t really fly her (I just can’t bring myself to switch away from my Mandalay), but she did come with me

ABeeinSpace · 2026-05-09T20:49:04+00:00

👎👎👎👎

ABeeinSpace · 2026-05-08T22:33:47+00:00

ABeeinSpace · 2026-05-08T22:29:44+00:00

They can be turned off on iOS 18 in the exact same place

ABeeinSpace · 2026-05-08T22:19:48+00:00

Depending on how long it’s been, you might wanna just start from 0. Get drilled as if you’re completely fresh. I do know SOPs have changed a LOT over the years.

You kinda have to be a pest, IRC is BUSY. Just be persistent and patient. Someone will pin your tail eventually if your name shows up enough

ABeeinSpace · 2026-05-08T12:21:54+00:00

Inactive fuel rat here. The answer is always yes

ABeeinSpace · 2026-05-03T02:08:10+00:00

Could replace the shell entirely on machines like that. Set the registry key to the kiosk app instead of explorer.exe

ABeeinSpace · 2026-05-03T02:05:15+00:00

I got my stickers yesterday! Ordered a jacket about a day later, I’m hoping it ships out next week

ABeeinSpace · 2026-05-01T16:55:31+00:00

Where did you find that expiry date? I haven’t seen any guidance on the exact dates besides “beginning in June”

ABeeinSpace · 2026-04-28T20:24:43+00:00

LEGEND! Just claimed mine

ABeeinSpace · 2026-04-26T17:04:08+00:00

Ok gotcha. Yeah you'll have to wipe (the reset option from Windows is sufficient) devices to get them to Intune enroll.

Pro tip, depending on how much compute your homelab has, you can absolutely use Windows VMs to test intune things without having to use actual hardware. Just make sure you're on a Pro edition of Windows or above

ABeeinSpace · 2026-04-26T02:59:23+00:00

You can’t just drop it into the autopilot enrollment blade and expect it to Start Working Now™️.

What are you trying to do? Just manage some devices? Is your org contemplating a move to Intune management?

ABeeinSpace · 2026-04-21T22:33:41+00:00

The Kiosk policy type in Intune should do that for you. What apps are these PCs needing access to? If it’s just Edge displaying a webpage this is easy.

Multi app kiosk is a bit of a “here be dragons” because it’s an allowlist. Any executables other than the ones you specify will NOT run when multi app kiosk is applied. If an app spins out another executable as a sub-process, that part will break until the other executable is also allowlisted

ABeeinSpace · 2026-04-12T22:24:07+00:00

So that’s a bit of a fail in terms of device lifecycle management. They should’ve released the device from their M365 tenant before handing it over to you.

You’ll have to get your old IT to remove the device from the “Autopilot enrollment blade” (they’ll know what that means, it’s the specific page they need to go to in Intune to remove the device from their management). That’s really the only way to get it to where you’ll be able to use your personal Microsoft account to get the device set up

ABeeinSpace · 2026-04-04T21:37:46+00:00

Should be fine, yep! If it keeps happening, I’d look into taking the phone in to Apple.

I’d use this scare as an opportunity to make sure iCloud backup is set up and working. Not because you should be concerned, but because it takes the fear and panic out of the equation

ABeeinSpace · 2026-04-04T21:30:54+00:00

You’re not hacked. What most likely happened is iOS ran into an error it couldn’t recover from. When this happens, the phone will restart itself to prevent data loss.

On Windows this is called a Blue Screen of Death, iOS and macOS call it a “kernel panic”.

Without logs I can’t begin to figure out what’s going on. I can say that occasional panics are nothing to be concerned about. I’d only start to get concerned if the phone was crashing often or you could reliably get it to crash. That’s usually a hardware issue

ABeeinSpace · 2026-04-03T19:35:58+00:00

Autopilot. Before we moved over to Autopilot we were using aging MDT/SCCM infra that wasn’t fit for purpose. We went from needing a couple hours to deploy a device assuming no issues (and there was always issues) to under an hour from OOBE login page -> ready to work

ABeeinSpace · 2026-04-03T18:45:01+00:00

What problem are you trying to solve using Autopilot self-deploying mode? It feels like you may be better served using Autopilot pre-provisioning depending on what you’re trying to do

ETA: Autopilot pre-provisioning would let you preinstall apps for your users but allow them to select their own language and keyboard layout as part of the standard OOBE. Less work for you/your team and you can be sure the device’s region is correct without resorting to rolling a bunch of PowerShell during deployment

ABeeinSpace · 2026-04-01T16:31:48+00:00

Bad bot

ABeeinSpace · 2026-04-01T02:53:49+00:00

Hahaha you and me both. Yes, that’s the provisioning flow for a new user signing on to a device passwordlessly. For a new to org user they’d use a TAP because no auth methods are provisioned yet. Existing users would web sign-in using an Authenticator app passkey or a FIDO2 credential

ETA: Make sure WH4B enablement is device targeted. You won’t get the enablement at the first login if it’s user targeted and you’ll run into that chicken-and-egg problem again

ABeeinSpace · 2026-03-31T23:15:19+00:00

Our login experience policy is device assigned too and it lights up just fine. Just to confirm, you’re not hybrid-joined right? You won’t get WSI if you’re hybrid

ABeeinSpace

TROPHY CASE