Nope. There's 2 ways to create gc's. 1 lets you test for a value that you specify in your requirements rule. 2 lets you check for "boolean" or whether your query returns true. The latter in reality just validates whether your query returns 1 or more instances.
Either way the data type you specify is that of the property you're testing for, in your logic it would have always been boolean. Sent from my Windows Phone ________________________________ From: Mark Evers<mailto:[email protected]> Sent: 6/06/2014 15:37 To: MSSMS List Serv<mailto:[email protected]> Subject: RE: [mssms] Custom Global Conditions - WQL - not working correctly Okay, I thought if you set it as Boolean, it would check to see WQL query is true? ________________________________ From: [email protected] To: [email protected] Subject: RE: [mssms] Custom Global Conditions - WQL - not working correctly Date: Fri, 6 Jun 2014 13:25:17 +0000 Identifying nummer property is not a boolean but a string data type. Sent from my Windows Phone ________________________________ From: Mark Evers<mailto:[email protected]> Sent: 6/06/2014 15:17 To: MSSMS List Serv<mailto:[email protected]> Subject: [mssms] Custom Global Conditions - WQL - not working correctly I am having an issue with several custom global conditions in SCCM 2012 R2, I keep getting a a type mismatch when using them. Little bit of background; I am deploying the Lync 2013 into our environment (we are migrating from Lotus), Office is already installed on the clients, however we have 32 bit office install on fair amount of our Windows 64 bit clients(75% Windows 7). Since the lync 2013 client requires the same bit level as the version of Office installed and not the os, I created a Custom WQL query using the below options, also attached a screenshot: Setting type: WQL query Data Type: Boolean Namespace: root\cimv2 Class: Win32_Product Property: IdentifyingNumber WQL query Where clause: IdentifyingNumber='{90140000-0011-0000-1000-0000000FF1CE}' This should detect the 64 bit version of Office Professional Plus 2010 (I have a similar one for 32 bit), however when I try to deploy it to the test VMs this fails, though only on the install, to verify, I have ran the query with powershell, and my test systems that have it, the query works fine. I do find it odd, that when I deploy it, the systems that are not running any version of Office report back that they do not meet the requirements, so part of this is working. Am I missing something?
