Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Ivan

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…

      Ivan commented  · 

      I've tried putting a script based action into the Task Sequence that invokes the InstallUpdates for CCM_SoftwareUpdatesManager class. What I've noticed is that when I run the Task Sequence the updates go into "Waiting to Install" state (EvaluationState is 6) and stay like that forever. I suspect that this is because they're waiting for Task Sequence to complete. Can someone prove if that's the case and if so, is there a way to workaround it?

      Ivan commented  · 

      Hi! I'm currently running SCCM 1706 and am using a custom TS for regular maintenance on our servers contain 4 repetitions with the following steps:
      1. Scan for updates (WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE)
      2. Wait 1 minute
      3. Install Software Updates (Available for Installation - All software updates)
      4. Request Machine Assignments (WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000021}" /NOINTERACTIVE)
      5. Wait 1 minute
      6. Machine policy evaluations (WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000022}" /NOINTERACTIVE)
      7. Wait 1 minute

      Before deploying the TS, I'm also pushing out a new SUG to the machines in advance. This used to be very handy in the past when patching new servers built from RTM image (when certain patches become required only after some pre-requisite patches were installed first and machine was rebooted). However with the recent changes in the servicing model, I'm wondering if there's a better way to do this? In the past, this TS used to be working relatively quickly (usually it would complete within 3 hour window), but I've noticed that it takes longer and longer to every month (now it runs over 6 hours). Looking closer at the Task Sequence status messages, I'm seeing that the time it takes to execute the 'Install Software Updates' steps (on servers that are patched month to month) takes pretty much the same time for all the 4 runs (or subsequent runs take longer), however during the first run it does install all the updates and performs a reboot, and usually it has no updates left to be installed during the remaining three runs (and the action is configured with the ‘Evaluate software updates from cached scan results’ checkbox ticked). Is there any risk of consolidating these 4 runs down to just one (or maybe two)? Would switching to Full scan instead of using the cache help to reduce the time of execution?

      Installing all the available updates via the Software Center manually runs a lot quicker and usually takes less time than it would take to run the TS with the 'Install Software Updates' step. But I need to do it in TS, because apart from installing updates, it has some additional pre- and post- maintenance steps and because I don't always have the possibility (and/or the desire) to touch every machine during patching. An alternate approach that I'm currently considering is to have a custom script that would just invoke InstallUpdates method of CCM_SoftwareUpdatesManager class and keep waiting for completion (say, until the value of the EvaluationState property for all the updates become greater than 7)

    • 44 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        Noted  ·  5 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
        Ivan commented  · 

        I've been trying to get this functionality by creating a dummy application that requires other applications, but it turns out to be so unreliable in Task Sequences that I had to drop this idea.

        Ivan supported this idea  · 
        Ivan commented  · 

        Very good idea. One other use case for this (similar to an 'Application Bundle' in MDT) is an ability to "hardcode" it in various Task Sequences so that I could only update the list in one place (within the Application Group) and not in all the Task Sequences that share the logic.

      • 45 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          3 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
          Ivan commented  · 

          It would be great if there was a way to integrate it with some GIT repo and be able to compare versions

        • 4 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            Noted  ·  1 comment  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
            Ivan supported this idea  · 
          • 2 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              2 comments  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
              Ivan supported this idea  · 
            • 19 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                Noted  ·  5 comments  ·  Ideas » PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                Ivan supported this idea  · 

              Feedback and Knowledge Base