My feedback

1. Option to uninstall an application when a user or device falls out of scope of the collection

   801 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   Check!

   invalid email

   (thinking…)

   Reset

   or sign in with

   • 
   • 

   

   UserVoice password

   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…)
   30 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   started  ·  Admindjam (Admin, System Center Configuration Manager) responded

   Check out the new uninstall behavior in 1804 tp.

   Mike_C commented  ·  Jan 4, 2018  ·  Delete…

   Be careful with this one. The Radia (HP Client Automation / Persistent Accelerate) product has this functionality and I've been on multiple support calls because of mass software uninstalls especially if you use things like group membership or OUs for deployments. Too many "cooks in the kitchen" can easily cause uninstalls when someone renames a group, changes OU structure, etc. If this is implemented, it definitely needs to be optional.

2. Ability to automatically install Windows 10 ADK releases (or rollback or apply hotfix) via Updates and Servicing.

   730 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   Check!

   invalid email

   (thinking…)

   Reset

   or sign in with

   • 
   • 

   

   UserVoice password

   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…)
   13 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   Noted  ·  sangeev responded

   Updated to Noted. We’ve been discussing the same in our planning meetings.

   Thanks,
   BobMN on behalf of SangeeV for SCCM OS Deployment

   Mike_C supported this idea  ·  Jan 4, 2018

3. Fix the Software Update Task Sequence (built-in TS patching during OSD)

   1,829 votes

   Vote Vote Vote

   Vote

   Sign in

   prestine

   Your name

   Your email address

   Check!

   invalid email

   (thinking…)

   Reset

   or sign in with

   • 
   • 

   

   UserVoice password

   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…)
   58 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   started  ·  Admindjam (Admin, System Center Configuration Manager) responded

   I’m updating the status. For 1606 we’ve made some changes, listed below.
   As more are added we’ll update what Tech Preview/Release they appear in.

   Timeout scan is now configurable
   We added a new task sequence variable to allow a configurable timeout for scan. Variable name is SMSTSSoftwareUpdateScanTimeout, default is 30 minutes. Value is set in seconds so an hour is 60×60=3600

   Logging changes
   In the SMSTS.log we list the log files to check for updates download and evaluation.
   These are UpdateDeployment.log, UpdatesHandler.log, WUAHandler.log and WindowsUpdate.log

   New Option for full scan
   There’s a new checkbox added to the Install Updates step – ‘Evaluate software updates from cached scan results’
   If the checkbox is on we use cached results, if the checkbox is off we do a full scan
   Task Sequences that are upgraded will have this option checked on – this is parity with the existing behavior

   Power management changes
   Clients maintain active power state during OS deployment Software Updates tasks.
   Some devices (Surface Pro 3 for example) were going into Connected Standby state preventing completion of deployment, this was occurring in the Install Updates step

   Windows upgrade roll ups
   These are now filtered from the list of applicable updates

   I’m updating the status. For 1606 we’ve made some changes, listed below.
   As more are added we’ll update what Tech Preview/Release they appear in.

   Timeout scan is now configurable
   We added a new task sequence variable to allow a configurable timeout for scan. Variable name is SMSTSSoftwareUpdateScanTimeout, default is 30 minutes. Value is set in seconds so an hour is 60×60=3600

   Logging changes
   In the SMSTS.log we list the log files to check for updates download and evaluation.
   These are UpdateDeployment.log, UpdatesHandler.log, WUAHandler.log and WindowsUpdate.log

   New Option for full scan
   There’s a new checkbox added to the Install Updates step – ‘Evaluate software updates from cached scan results’
   If the checkbox is on we use cached results, if the checkbox is off we do a full scan
   Task Sequences that are upgraded will have this option checked on – this is parity with the existing behavior

   Power management changes… more

   Mike_C supported this idea  ·  Jan 4, 2018