265 votesChris Cools commented
I have no votes left today, I'll make sure I vote for this when I have votes available again. I totally support this idea, I have made a similar suggestion for 'multi-select TS deployments to collection(s)'. It should be integrated in the console. Administrators do have the need to deploy stuff to a collection or even multiple collections at one click (selection of SCCM objects like packages and task sequences) from within the console. Currently it is a burden to deploy like 20 task sequences or packages to a collection. I have to repeat the same action 20 times, manually. Working on a PS script to do this as we speak because it's too frustrating to work like this!
Updated by bobmn for sangeev/OSDChris Cools shared this idea ·
Updating status to started – see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.
Our 1905 Technical Preview is now released.
This release has the first round of changes in the App model to allow a Task sequence as a deployment type allowing task sequences to be deployed to users/user groups.
https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1905#bkmk_tsdtChris Cools commented
We use Task Sequences for most of our software deployments because we often need many dependencies to be installed aside the main application and this in a specific order. Unfortunately, you can't deploy them to user collections, only to device collections. It would be great if a TS could be targeted to users in stead of devices only. Now we have a workaround in place that in essence deploys the TS as an App and can be targeted to user collections. The app contains a PS script to start the device-targeted TS and can be triggered from App Catalog. It would be much easier if we could directly target the TS to the users.Chris Cools supported this idea ·