Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice

Kim Oppalfens

My feedback

  1. 67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Client Settings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Kim Oppalfens commented  · 

    Adding this to the end of the configmgr.mof in inboxes\clifiles.src\hinv
    Will create a new wmi class on all your clients called CCM_ComputerSystemExtended2

    You can then add that class to hardware inventory.
    Not exactly what the request is, but a somewhat elegant workaround.

    //========================
    // Added extensions start
    //========================
    #pragma namespace ("\\\\.\\root\\cimv2")
    #pragma deleteclass("CCM_ComputerSystemExtended2", NOFAIL)
    [Union, ViewSources{"select Name,SystemSKUNumber, HypervisorPresent,PCSystemTypeEx, SystemFamily from Win32_ComputerSystem"}, ViewSpaces{"\\\\.\\root\\cimv2"},
    dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
    class CCM_ComputerSystemExtended2
    {
    [PropertySources{"Name"},key]
    string Name;
    [PropertySources{"SystemSKUNumber"}]
    string SystemSKUNumber;
    [PropertySources{"HypervisorPresent"}]
    Boolean HypervisorPresent;
    [PropertySources{"PCSystemTypeEx"}]
    UInt16 PCSystemTypeEx;
    [PropertySources{"SystemFamily"}]
    String SystemFamily;
    };

    //========================
    // Added extensions end
    //========================

  2. 12 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  · 
  3. 866 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 →
    An error occurred while saving the comment
    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.

  4. 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