Adam Gross

There are registry keys that can be checked to see if hard blockers exist. Create CIs for these to help prevent hard blocked machines from proceeding.

Currently, this only builds out for a deployment of Windows 10. But since SetupConfig.ini also supports Compat ScanOnly, Add a set of CI/CB's to target collections for compat scan first...

To use SetupConfig.ini for compatscan, it can have 2 entries for Compat (IgnoreWarning and ScanOnly). To support ScanOnly, need to add the ability to have 2 entries for the same...

Windows 10 2004 added new post-action cmds. Currently we generate them, but need more logic around them. Maybe add a Target OS and if it's 2004+ then handle things differently.

Also fixed a few bugs

Update new-teams-bulk-install-client.md

2

fixed commandline

Update windows-365-boot-guide.md

3

This is bad and broke my prod policies!

Per this doc, the correct path for the scheduled task shouldn't have the extra Microsoft in it. https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/client-installation/configmgr-clients-reinstall-every-five-hours