spgsitsupport Posted September 10, 2015 Report post Posted September 10, 2015 How can one target application at specific hardware model? Or Application would be not the choice? BasicallI need to run Dell BIOS settings on-mass on all machines that are xyz model Thanks Seb Quote Share this post Link to post Share on other sites More sharing options...
h4x0r Posted September 10, 2015 Report post Posted September 10, 2015 Just create a collection for your workstation models (you could do a large collection for all Dell workstations, and then sub collections for specific models if you need it)...then just target that collection with your app/package 1 Quote Share this post Link to post Share on other sites More sharing options...
HotdogSCCM Posted September 10, 2015 Report post Posted September 10, 2015 As an added safety bonus, you can add a Global Condition to limit it to hardware. Name: Hardware Model - Whatever Device Type: Windows Condition Type: Setting Setting Type: WQL Query Data Type: String Namespace: root\cimv2 Class: Win32_ComputerSystem Property: Model WQL Query: Model LIKE "%Latitude E4300%" That'll prevent the application from running on anything but Latitude E4300; just assign that Global Condition to your Deployment Type. But yeah, targeting via Collection will be the best bet; this just adds a layer of protection against unintentional deployments. It also lets you just dump these apps into a single "Install Applications" step via OSD, instead of having to break it out into each individual type via WMI queries, if so desired. 1 Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted September 11, 2015 Report post Posted September 11, 2015 Thanks guys, much appreciated Seb Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted September 18, 2015 Report post Posted September 18, 2015 OK, no problem with targeting then, but have no idea what condition could be used for Detection Method (as they are BIOS only settings that can not be read from within Windows) Again it looks like Application is not the way to do it Seb Quote Share this post Link to post Share on other sites More sharing options...
h4x0r Posted September 18, 2015 Report post Posted September 18, 2015 Yeah, in this case you might need to see what the installer is returning on an exit code for success or failure, then script something like writing to a reg key that can be used for application detection, if there is no MSI product code being generated. Otherwise, this will have to run as a package. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted September 20, 2015 Report post Posted September 20, 2015 Package works fine, but I still think that SCCM with everything (applications and/or packages) is a mess with too many options in one place & none in the other... Quote Share this post Link to post Share on other sites More sharing options...