Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

LPM

My feedback

  1. 1,830 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      57 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…

      LPM commented  · 

      Thanks for your reply. Interestingly in my customers environment I am seeing 1702 clients deploy and not lay down the SU settings in the registry which CM has always done to not require anything else doing this. Has anyone else seen this or just me?

      It is the tip of an ice berg in a multi domain SUP headache I am currently working through :(

      LPM commented  · 

      What sort of virtual resources did you throw at this? I gave up in a B&C environment for now thinking a normal OSD would be fine and it seems to be struggling here aswell

      LPM commented  · 

      I would like to add a comment to this Thread.

      I have previously done this successfully in the past however a 1703 Build and Capture on ConfigMgr 1702 I am seeing the timeout issue.

      I have SMSMP specificed
      Worked of IP Range Boundary
      Tried WMIC Commands
      Added restarts

      Regardless of any combination of options the 30min timeout is triggered. I have a SUG with 12 updates contained (mix of x86 & x64) so there should not be a reason it is getting anywhere near the 30min mark.

      Does anyone else still have this issue?

    Feedback and Knowledge Base