You are browsing the archive for query.

Intel HD Graphics driver and software for HP Models in OSD in the New Configmgr 2012 Application model

9:04 am in Application Model, ConfigMgr 2012, ConfigMgr 2012 SP1, Deployment, deployment types, Drivers, Global Conditions, query, Requirements, SCCM 2012, SCCM 2012 SP1, System Center by Kenny Buntinx [MVP]


System Center 2012 Configuration Manager has a great feature called the Application model that has many great built-in requirement rules that will help you to get the right deployment type installed on the right machine type even during OSD.

For most of the drivers you need to install during OSD , the driver alone isn’t enough. A great example here is the Intel HD graphics or IDT high definition Audio drivers.

In the old CM07 days you would build packages and programs , use them in your task sequence with a condition that uses a WMI query to apply that TS step on the right HW model. Well , forget about that and start using applications to install your “bad drivers” that need software as well. Let those global conditions figure out on what HW model hardware it is applicable.

For most of my applications the built-in rules can get the job done, but some times we need to create our own Global Conditions, to fit the requirement rules for an application/Deployment Type. In this particular case , we will use a global condition to detect the right PNP ID so we are able to detect the HW. We simply don’t care on what HW model we apply this step , as the global condition will figure it out for you . This will allow you to simplify things in your TS.

Let me give you an example on how to do it :

1. Create your Application : HP Graphics driver and Software and fill in your supported models. Note: When downloading the driver software from the HP website , in the .inf file you will find on what HW models this software is applicable.


2. Create your Deployment Type and specify the install / uninstall parameters . In this case : “Setup –s”


3. Create your “Detection Method” . In this case we will look in to the registry :

Hive: “HKLM”

Key : \Software\Wow6432Node\Intel\GFX”

Value :”Version”

Data Type : “String”

Equals version “”

Now you can detect if the app is already installed or not .


4. Create your custom Global condition under the “Global Condition” Node in the Console .


5. Create your custom Global condition called:”Video is Intel HD Graphics Compatible Adapter” and specify the following settings :

Name :”Video is Intel HD Graphics Compatible Adapter”

Device Type : “windows”

Condition Type : “Setting”

Setting Type : ”WQL query”

Data Type :”String”

Namespace : “Root\Cimv2”

Class: ”CIM_LogicalDevice”

Property : “PNPDeviceID”

WQL query where clause  :

“PNPDeviceID like ‘%VEN_8086&DEV_0166%’ or PNPDeviceID like ‘%VEN_8086&DEV_0106%’ or PNPDeviceID like ‘%VEN_8086&DEV_0102%’ or PNPDeviceID like ‘%VEN_8086&DEV_0116%’ or PNPDeviceID like ‘%VEN_8086&DEV_0112%’ or PNPDeviceID like ‘%VEN_8086&DEV_0126%’ or PNPDeviceID like ‘%VEN_8086&DEV_0122%’ or PNPDeviceID like ‘%VEN_8086&DEV_010A%’ or PNPDeviceID like ‘%VEN_8086&DEV_0162%’ or PNPDeviceID like ‘%VEN_8086&DEV_016A%’ or PNPDeviceID like ‘%VEN_8086&DEV_0152%’ or PNPDeviceID like ‘%VEN_8086&DEV_0156%’ or PNPDeviceID like ‘%VEN_8086&DEV_015A%’”


To find the above information , you must open the corresponding inf file of the specified driver


6. Attach your previous defined “Global Condition” as a requirement on your deployment type. Make your sure to select that your global condition must exist on the client device .


7. Add the application to your OSD task Sequence . You’re done.

I hope you see that the power of Applications can also be used in your OSD deployment scenarios .

Hope it Helps ,

Kenny Buntinx

Configmgr 2012 : Automate / Create User Collections from AD user Groups (based on Active Directory group discovery)

8:40 am in CM12, collection, ConfigMgr 2012, ConfigMgr 2012 SP1, query, SCCM 2012, SCCM 2012 SP1, System Center, users by Kenny Buntinx [MVP]


Did you ever wanted to automate the creation of “User Collections” based on your AD user Groups (which is based on User group discovery)

I have posted the script here ( ) and these are the steps to follow :

1) Create/Configure your AD group discovery to target your AD application groups.


2) Run this script from a site server machine and this will require appropriate RBAC rights for the user to create collections.

2) Open a command prompt and run the following cmd:

Cscript CreateCollectionForUserGroups.vbs


3) The script will create a user collection for each AD security group with the same name as the unique user group name retrieved from active directory. The appropriate AD group will be added as a direct member of that user collection. This will avoid the refresh that you would need if you would use a query method !



4) On subsequent reruns the script will check if a collection with the same name exists or not and if it does it will skip.

The only 2 things I would still add to the script and I am busy trying to figure it out is :

– Check for incremental updates ( in case you would add a user directly into it )

– Check the default collection update (7days)


Note : I have not written this script myself . I would like to thank the Configmgr Product group and in particular Bhaskar, as he created the script . However you should first try this script in a lab and see if it fits your needs . We’ll take no responsibility what so ever .


Hope it Helps ,

Kenny Buntinx