My feedback

1. "Test Detection method" button.

   11 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…)
   Noted  ·  0 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   David W supported this idea  ·  Jan 29, 2019

2. add a powershell possibility to add requirements to a deploymenttype of an application

   118 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…)
   9 comments  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   started  ·  AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded

   Changing status back to “Started” as there’s more work to do here. We plan to simplify adding requirements to DTs as well as complete the missing scenarios for detection methods in a future release. Stay tuned for more updates.

   David W supported this idea  ·  Jan 16, 2019

3. Native patching in OSD

   3 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…)
   0 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…Flag idea as inappropriate…  ·  Delete…  ·  Admin →
   David W shared this idea  ·  Mar 30, 2018

4. 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

   David W commented  ·  Dec 27, 2017  ·  Delete…

   How about the ability to deploy directly from a selected list of Update Groups instead of having to have an active software update deployment?