Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Steve

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…

      Steve commented  · 

      This works a lot better (1802) than it used to (2012R2) - but it's still far more temperamental than it should be, not to mention incredibly slow relative to full-OS install speed. Please can this be improved, as others have mentioned, it should be possible to have a 100% completely built machine ready for an end-user without them needing to very shortly after receipt need to install more updates.

      Steve supported this idea  · 

    Feedback and Knowledge Base