Update 2019.01.22 To include User Account that triggered the Upgrade & Unique Build Record Info. Blog Post for “Gather Account Name during IPU” HERE
Update 2018.08.01 To include Hard Blocker from Compat Scan, requires you to add a step into the TS to capture the Hard Blocker to a TS Variable, Blog Post HERE
Update 2018.06.05 – I’ve posted the first WaaS Post, which incorporates this Script into a Compatibility Scan Task Sequence. I’ve updated the script since this post, which is available to download, along with the Task Sequence Export in this POST HERE
Several years ago I started to use Jason Sandys’ OSDInfo Script. I liked the idea of having a script run during OSD that would write information to WMI, which made it easy to inventory. Now I do IPU (In Place Upgrade) so much more than OSD, and I wanted to do the same, gather important information from IPU and be able to use it for Reporting or creating collection queries.
I’ve taken Jason’s script and modified it… a lot. All of his plumbing is still in place (functionality to add information to WMI & Registry), but I’ve added a lot of logic around using the script for different functions.
The script is now broken into 3 sections, OSD (Operating System Deployment), CS (Compatibility Scan), IPU (In Place Upgrade). Using TS Variables, the script will run different sections of the script. This allows me to use the same script in numerous scenarios.
First, I’ll show you results, and then go into details about how it’s done. But I feel it’s easier to understand the script and process if you can see the end product.