Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Fred

My feedback

  1. 1,829 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      58 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

      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…

      Fred commented  · 

      This is a farce... every possible workaround I've found has been tested and nothing works (set reg keys to suppress contacting MS online, more CPUs for VM, more RAM for VM, higher timeout value). I'm still getting a timeout for each and every update step using CB 1710 with all hotfixes installed, capturing Win 10 1709 with nothing but updates. Nothing works! Nothing!

      Fred supported this idea  · 

    Feedback and Knowledge Base