Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

DOH

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…

      DOH supported this idea  · 
      DOH commented  · 

      You shouldn't have mentioned that the updates still worked in MDT.. because they used to. But Microsoft probably read this comment and thought. WHAT... UPDATES STILL WORK IN MDT.. WE CAN BREAK THAT. And they did. As of Windows10 1607 we also could no longer inject updates with MDT.

      DOH commented  · 

      Here's an idea.

      Make ONE update every 2 years that actually works. Instead of 20 broken updates every year.
      All I'm doing is waiting for a hotfixxes that'll fix something that was broken in the last update.

      At this point I don't know what's broken more SCCM 1610 or Windows 10 1607.
      Anyways... we'll all be out of jobs soon... thanks for nothing.

      I could make a f*cking batchfile that would install these updates just fine.
      MAKE IT WORK.

    Feedback and Knowledge Base