An error occurred while saving the commentAnonymous commented
I work in ConfigMgr OSD team at Microsoft. Would like to hear some feedback to the following:
At the present time driver packages cannot have associated programs that can be deployed to collections. This means that when we try to use driver package dynamically at run time, we cannot request dynamically policy for its package program and cannot get dynamically the content of the package.
A simpler solution implementation wise would be the following:
allow users to select several driver packages in the same “Apply Driver” step so that all of them will be considered package references (like it is done currently in Content Download task sequence step - always resolved and downloaded) , and also to let user to control which of these selected driver packages will be:
1) applied always like single package is applied now or
2) applying of which is controlled dynamically through some task sequence variable mechanism.
Would this be acceptable solution? Will this help you your scenario?