Kim Oppalfens
My feedback
-
73 votes
An error occurred while saving the comment -
12 votesKim Oppalfens
supported this idea
·
-
870 votes
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.
-
1 voteKim Oppalfens
shared this idea
·
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
//========================