windows-itpro-docs VS memdocs

Or even https://github.com/MicrosoftDocs/windows-itpro-docs/commit/2...

Indeed, it's s simplification. If you want to go down the TPM rabbit hole, read this interesting comment about IEEE 1667: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5...

You could try Repair BDE.

Which version of wscript.exe and cscript.exe do you have? On 2021-09-14, the documentation was updated to block "un-enlightened" versions of those executables. Further, on 2021-09-21, it was updated to the correct version numbers instead of just "10.0". As a result, if you are using the latest version of the recommended block list XML, those executables should not just be outright blocked from running. Instead, as described here, the underlying script being called must be allowed by the policy otherwise the call (really the script) will be prevented.

i think https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6399 can be help you

I did find this link as well that seems to suggest that this information is no longer accurate so I want to lab this up and verify myself.

same for me, apparently this only is an issue on Windows 11 pre-releases. for me, it's build 22598.200 ni_release, do you also use windows-insider-builds? you can "fix" it by disableing driver signature enforcment in commandline and reinstalling this driver. but for this, secure boot must be disabled in the BIOS. doing this will cause valorants anti-cheat to block you from playing tho, and this is probably not the only downside of disabled secure boot... i'd love to see a fix for that, i think, they already trying as seen here.

We have MDT and SCCM from Microsoft and they aren't going anywhere anytime soon. I still use MDT to create and deploy images with Windows 10 and 11 as well as SCCM. ADK for Windows 11 21H1 still works perfectly fine for both OS's in MDT. You just have to take a couple extra steps for Windows 11 captures. Windows 11 isn't radically different from Windows 10, and it's "unsupported" because there's no active development in MDT. The community is kind of taking up that support with PSD. At the end of the day it still deploys the same. And you can work around any issues with a google search. Also, keep an eye out for known issues and workarounds. https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md

Intune policy like this and assign a group with the specific user(s) you want to target

More info here: https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/intune/apps/app-configuration-managed-home-screen-app.md

Looking at MicrosoftDocs github

The organisation I work for has been using MDT (Microsoft Deployment Toolkit) to deploy Windows 10 and our applications (Office, Adobe etc) to our PCs quite successfully for several years now. We had also been expecting to use it to deploy Windows 11 (we'd tested it with an earlier Windows 11 ADK and it seemed to work), but just today I came across this bombshell:

Also, you can check how often does MS change the URLs themselves here: https://github.com/MicrosoftDocs/memdocs/commits/main/memdocs/autopilot/networking-requirements.md

I think the article on their repo is more current https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/core/understand/configuration-manager-on-azure.yml