Standardize package properties between SMS_TaskSequence_* SMSProviderObjects
SMSTaskSequenceRunCommandLineAction uses PackageID
SMSTaskSequenceInstallApplicationAction uses AppInfo (and ApplicationName?)
SMSTaskSequenceApplyDriverPackageAction uses DriverPackageID
SMSTaskSequenceApplyOperatingSystemAction uses ImagePackageID
SMSTaskSequenceUpgradeOperatingSystemAction uses InstallPackageID
While they are different objects and they do different things, shouldn't this be standardized across classes that can have content dependencies in a TS? This makes the data coming out of Get-CMTaskSequenceStep difficult to work with, as you have to keep a rolling library of properties to check for Package ID's.
We wouldn’t fix the backing WMI schema because that would introduce breaking changes to any SDK consumers.
We could consider a fix on the PowerShell side to allow for more consistent display of these objects (without changing the objects themselves) to make them easier to consume via automation.