Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, September 18, 2017 8:57 PM
I'm trying to do in-place upgrades and some systems are failing due to incompatible software.
I can manually run setup /compat scanonly and see the issue after a system fails to upgrade, but this is too labor intensive.
How can I automate this so I can find all the systems that need attention either due to detected incompatible applications/drivers or other problems such as inadequate free space on the C drive?
All replies (4)
Monday, September 18, 2017 9:27 PM ✅Answered
this?
/en-us/sccm/core/clients/manage/upgrade/upgrade-analytics
Don [doesn't work for MSFT, and they're probably glad about that ;]
Tuesday, September 19, 2017 12:02 AM ✅Answered
One option is to use the Upgrade Step in the TS and check the option "Perform Windows Setup compatibility scan without starting upgrade."
You can then look at the status of the TS for the clients that run it.
Tuesday, September 19, 2017 2:04 AM ✅Answered
Hi,
You can reference the blog about Assess your environment for Windows 10 with ConfigMgr Upgrade Assessment Tool.
By reviewing smsts.log to check the information about TS.
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, September 19, 2017 12:07 AM
One option is to use the Upgrade Step in the TS and check the option "Perform Windows Setup compatibility scan without starting upgrade."
You can then look at the status of the TS for the clients that run it.
I could create separate Task Sequence that silently does the check without starting the upgrade, but how do I get a report or even a basic log on failures with the specific reason why each system failed the compatibility check?