Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Ondrej Seda

My feedback

  1. 594 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  ·  27 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
      Ondrej Seda commented  · 

      Hi, i think part of this request should be also: When user do the reboot by himself (click start - reboot), SCCM will accept it and will not require reboot after real reboot again

    • 1,113 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  ·  35 comments  ·  Ideas » Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
        Ondrej Seda commented  · 

        Hi, i think part of this request should be also: When user do the reboot by himself (clisk start - reboot), SCCM will accept it and will not require reboot after real reboot again.

      • 169 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  ·  2 comments  ·  Ideas » Content  ·  Flag idea as inappropriate…  ·  Admin →
          Ondrej Seda supported this idea  · 
        • 680 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  ·  12 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
          • 399 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              14 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
              Noted  ·  sangeev responded

              Updated by bobmn for sangeev/OSD

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

                Technical description: PC not booting due to wrong resource ID
                Computers were discovered by AD Group discovery and recod was created with resource ID starting with "209". After that action Manual machine entry was created starting with resource ID "168".
                After while those two records were merged together but resource ID starting with "209" wins - that's the issue.

                TS was deployed on merged object to start staging.

                PC was not able to boot from PXE, because IDs that are higher than "200" are excluded when WDS is trying to enumerate available TS for OSD. Returned message to PC is, that there is no OSD assigned to Object.

                Ondrej Seda shared this idea  · 
              • 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…)
                  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…

                  Ondrej Seda supported this idea  · 
                • 1,294 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    24 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
                    Ondrej Seda supported this idea  · 

                  Feedback and Knowledge Base