Feb 13 2019 02:42 PM - edited Feb 15 2019 04:44 AM
Recently, one of my customers was adopting their Bare Metal Win10 TaskSequence to also support starting the TaskSequence from FullOS.
So, easy as that...adding some steps to restart in WinPE etc. and give it a try. But surprise – the same TaskSequence running fine from WinPE is telling that there are some Applications missing on the DP when started from FullOS!?
Hmm, that sounds quite strange so let’s look in the cas.log
So, we can see the content with the ID Content_46562d77-698f-4c85-972a-ea7d340bb6f9.1 is getting requested but not found on any matching DPs. But what’s behind this content Id 😊
To find out I started the sql management studio an ran the following query to get the scopeId:
Now we’re able to get some more info about our missing link by running another query using the returned ScopeId
By clicking on the SDMPackageDigest link we can identify the Application behind. So, in this case an old Lexmark Software which wasn’t referenced in our TaskSequence and not distributed anymore. However, a newer Version of the App superseding the old one was referenced in the TaskSequence.
So be aware that when starting a TaskSequence from FullOS not only all direct Apps referenced in the TaskSequence are checked if available on any DP (which is super easy to check in the console) but also all the superseded Apps – which does makes sense by the way.
Now as we know about the reason, we can take action on it:
So let’s focus on point 2 and see if we can optimize our process from reactive to proactive 😉
Searching the communities only resulted in various scripts returning the direct referenced Applications but not any superseded objects.
Time to engage the superpower of my Microsoft PFE colleagues and only a few hours later one of those ninjas came up with a script willing to share.
So kudos and big thanks to Herbert Fuchs!!!
Now here’s the Application supersedence chain
and our simple Test-TaskSequence
Now let’s take the magic PFE sauce...
Outcome is a Union-GridView of all direct referenced Apps of the TaskSequence and their Supersedence Chain
As well as another Gridview detailing the Distribution Status of all these Apps
Cool isn’t it?
Link to the script Get-TSAppSupChain.zip