System Center Configuration Manager Feedback

Suggestion box powered by UserVoice


My feedback

  1. 1,829 votes
    Sign in
    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  · 

      @Stefan: I've stopped with captures alltogether for Windows 10 and recommend downloading a new base image from msdn/vl portal when needed (as these seem to be updated on a regular basis by MS directly) and deploying quality updates per usual process.
      Having customers still using Windows 7, it's even worse not one single workaround (even the one's posted by PFEs on MS Blogs) works. I've gone ahead and simply create a TS which installs the base image, then I install updates via the normal Software Center process and finally start a capture only TS from within Windows to captures the then perfectly updated Windows... I'm basically done with the TS patch process :-(

    Feedback and Knowledge Base