Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Marc Westerink

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…

      Marc Westerink supported this idea  · 
      Marc Westerink commented  · 

      I've been able to successfully download and install updates after increasing the number of CPU's from 1 to 4 and from 4 GB to 8 GB RAM on the virtual machine used for Image Building of a Windows 10 1709 image on a ConfigMgr 1710 site based on Dr. Michael Kischel's comment.

      This makes me wonder how the Product Team test this behavior. While it is OK to figure out what to do to make this work, I'd appreciate it if the Product Team would define the system requirements that have to be in place to make the 'Install Software Updates' task work.

      We shouldn't have to work around issues to make things work or use alternative strategies due to lack of documentation. Microsoft, please specify the requirements to make this work.

      Nevertheless, I prefer to use MDT for image building but some customers simply don't want to have duplicate environments just because of these anomalies...

    Feedback and Knowledge Base