HoustonAU
My feedback
-
98 votes
-
3 votes
-
862 votesHoustonAU
supported this idea
·
-
401 votes
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.
Doc: https://docs.microsoft.com/sccm/core/get-started/2019/technical-preview-1905
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Group-applications-into-a-single-deployment-in-ConfigMgr/ba-p/624318This 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_tsdtHoustonAU
supported this idea
·
-
1,374 votesHoustonAU
commented
As much as I would love this, it is a far wider problem with the Servicing Stack. This should be resolved at the OS level, not the Config Mgmt level.
They need to address the entire issue of SSU updates in general, why do we need them, why are they different from other updates, why aren't they identified as SSU in some way etc.
Fix the updates themselves and we wont need to modify SCCM
-
181 votes
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.
This was addressed in our 1908 Technical Preview – https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1908#bkmk_tsperf
HoustonAU
supported this idea
·
-
218 votesHoustonAU
supported this idea
·
-
651 votesHoustonAU
supported this idea
·
-
1,722 votes
Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.See https://docs.microsoft.com/en-us/sccm/core/get-started/2019/technical-preview-1905#bkmk_tsdt
& https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Group-applications-into-a-single-deployment-in-ConfigMgr/ba-p/624318HoustonAU
supported this idea
·
-
151 votesHoustonAU
supported this idea
·
-
919 votes
Check out the new uninstall behavior in 1804 tp.
HoustonAU
commented
While this can already be accomplished through creative collections, I think an integrated and supported way to do this would be much better.
If you need to do this now you can create a collection that includes all devices with the software installed but exclude devices that are in the 'Install' collection, then just do an 'uninstall' deployment to that second collection.
It works but is a bit of a pain to configure for every application.
Would be preferable to simply have a tick box on the deployment to say 'Uninstall when item is out of scope' or something similar.
I also disagree with 'Anonymous', all configuration management software is 'dangerous' if you don't know what you are doing.
HoustonAU
supported this idea
·
One use case for this is that we would rather have all OSD task sequences assigned to our Support staff. If they are not physically at the machine they can just remote in and run a rebuild rather than having to muck around with collections and groups.