Question on Win10 Upgrade TS Deployment, Compatability Scan for mass computers ..

[Leo Bounds]

When deploying Windows 10 Upgrade as a task sequence, What is an easy way to scan a set of computers for compatibility before a task sequence upgrade deployment? The error codes listed here are a lot to sort through https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors#extend...

[#2]

You can use Upgrade Readiness to scan your computers prior to upgrade: https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-readiness-get-started 

---

[#3]

Hi Marc,

I appreciate the response but uploading telemetry data that relies on OMS to process it isn't an option for us right now.

We are looking for something we can run from SCCM CB that will give us the kind of compatability reports pre-Win10 Upgrade deployment on readiness of our systems.

Do you have another suggestion that does not require OMS or uploading telemetry data from our organization ?

[#4]

In that case, you can use the /Compat ScanOnly option of setup.exe: https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setu...

This will give you some indication as to wheter you will run into a compat issue when you run setup.exe. You can also use readyforwindows.com to check if there are known compat issues on a specific app.

[#5]

Thanks for the info Marc. I'll see how far I can get with that. Specifically on the first deployment tests I found the hard stop error - Compatibility issues found (hard block):  0xC1900208.

I'll have to dig in further to understand what the specific cause of this is.

[#6]

Yes. At that point in time you want to check your Panther folder. setupact.log as well as the *_APPRAISER_* files should give you a hint about what's going wrong. The other option would be to run setup.exe in non-unattended mode, that way you will get a report directly in the UI.