My feedback

1. Prompt users for reboot, but NEVER force it

   1,335 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   (thinking…)

   

   Password

   Sign in with: Facebook Google

   Forgot password?

   Create a password

   I agree to the terms of service

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   40 comments  ·  Ideas » Compliance Settings  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   planned  ·  AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded

   Updating this one to planned. We have work in this area that should address the general set of comments that are in this suggestion. While we aren’t doing the NEVER reboot, we definitely hear you that you need more than a 24 hour window. We should have more details to share in the next TP so stay tuned for updates soon.

   Anonymous commented  ·  May 03, 2018  ·  Edit…  ·  Delete…

   Give us a user option for delaying/warning about task sequences also.

   Save Submitting...

2. More Intelligent Client Cache

   92 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   (thinking…)

   

   Password

   Sign in with: Facebook Google

   Forgot password?

   Create a password

   I agree to the terms of service

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Noted  ·  4 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   Anonymous supported this idea  ·  May 03, 2018
   Anonymous commented  ·  May 03, 2018  ·  Edit…  ·  Delete…

   I frequently create multiple Deployment Types with the same exact content. Only the command line changes such as calling a different transform. Spent a couple of days trying to figure out why there were 5 or 6 identical copies of the same source in my clients cache! Just give us the option to choose "common source" for the content. Actually SCCM should easily be able to tell this as the Content Locations are all identical. Thanks MS!

   Save Submitting...