Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

HoustonAU

My feedback

  1. 80 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Remote Control  ·  Flag idea as inappropriate…  ·  Admin →
  2. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
  3. 747 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Ideas » Co-Management  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  4. 357 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU commented  · 

    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.

    HoustonAU supported this idea  · 
  5. 350 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU 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

  6. 162 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  7. 275 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  12 comments  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  8. 208 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  7 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  9. 540 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  10. 1,573 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    89 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  11. 140 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Ideas » Software Center  ·  Flag idea as inappropriate…  ·  Admin →
    HoustonAU supported this idea  · 
  12. 852 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    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  · 

Feedback and Knowledge Base