Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Kim Oppalfens

My feedback

  1. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Ideas » Desktop Analytics  ·  Flag idea as inappropriate…  ·  Admin →
    Kim Oppalfens supported this idea  · 
  2. 822 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  28 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.

  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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