memdocs VS OfficeDocs-SharePoint

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

FYI: Here's the OneDrive parameter documentation I used: Central documentation of OneDrive.exe Command Line Options · Issue #2905 · MicrosoftDocs/OfficeDocs-SharePoint · GitHub

I went looking for OneDrive.exe command line switches that might help and discovered this: https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/2905

https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/3061 When you rename via SPO it changes the AAD domain name (linked to your .onMicrosoft profile)