My 1 month (failed) experiment with paying for X is nearly over. It's not worth the money. But I realised just now that I've been meaning to post the various build and customisation processes I use for our device deployments, and I can currently make long posts. So here's a🧵 So the first things I'll get out of the way are: Yes I still use ConfigMgr. And yes, I build in a Generation 2 Hyper-VM that has TPM enabled so I have a compatible Windows 11 system to build one... but one that doesn't need any special drivers and keeps the image clean; And yes, I deploy Windows 11 Education, so some of the included APPX, Optional Features, etc., may be different than what you see. That being said, most of this should be transferrable.

Lately I have come across a bunch of weird apps and installers that demand, but really don't need, admin rights. Luckily, pretty much all of these were able to be fixed. Here are a couple of things to look for, and tricks to try, when going admin less... 1. Let's say you have an app already installed, say by using Software Center, and it pops a UAC prompt on launch. Take a look at the main EXE. If it has a UAC overlay, it's not a random permission issue causing this, it's the app manifest configured to require elevation...

The #Windows11 Start Menu is a strange beast. Many schools and orgs want to override the default set of apps and pin with their own, prioritising their Line-of-Business and otherwise important apps instead. But it's trickier than you'd think to achieve this... According to the official Microsoft Docs, the correct way to configure the Windows 11 Start Menu is to configure and then export a layout JSON using the Export-StartLayout command, then use this in an Intune Configuration Profile or a Group Policy Object...