Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Martin Rivard

My feedback

  1. 414 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    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/624318

    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_tsdt

    An error occurred while saving the comment
    Martin Rivard commented  · 

    While we wait for this to be officially supported, here is a workaround.

    One could add a step at the beginning of the Task Sequence to run a script or a tool like UI++ to check for credentials and group membership. If the credentials don't belong to a user in a group allowed to image computers, the Task Sequence is aborted. http://uiplusplus.configmgrftw.com/docs/actionconfig/userauth.html

    Then you simply make the Task Sequence available on all computers and if a normal tries to launch it, he'll be blocked at the credential window and can't progress further.

Feedback and Knowledge Base