Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Kim Oppalfens

My feedback

  1. 196 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  3 comments  ·  Ideas » Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
      Kim Oppalfens supported this idea  · 
    • 778 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 » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
        Kim Oppalfens commented  · 

        This blogpost should get you pretty close to what you want to achieve.
        http://www.oscc.be/sccm/osd/The-holy-grail-of-ConfigMgr-diver-management,-or-whatever-you-want-to-call-it/

        The apply device drivers step doesn't give you the same level of control, and misses the ability to apply drivers for hardware that is not detected. Which is problematic on some devices where a certain piece of hardware only pops up after a "parent" component is detected.

        Other methods require one to modify your tasksequence each time it has to support a new hardware model. This request (or the alternative implementation in the blogpost) allows for a hands-off approach, needing no TS edits to support new models.

      • 1 vote
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          Noted  ·  0 comments  ·  Ideas » Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
          Kim Oppalfens shared this idea  · 

        Feedback and Knowledge Base