I don't think you can use wildcards for discovery
i've done something alike for a network migration we've gone through recently
although you can't use wildcards in discovery, you can use them in compliance rules
so in the template part select registry key just put
and write the rule as
Registry Value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\** Must Not Exist OR (String Value does not contain "10.1.1.12")
where 10.1.1.12 was our old nameserver we were dismissing
note that you can't direcly specify key names after the ** wildcard so the rule can potentially match keys other than NameServer
you'll have to manually review the results the filer out spurious matches
I have similar problem too in my compliance rule. Basically, I want to check Registry value:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\[GUID]\RegistrationEnabled". equal 0x00000001. The thing is GUID, on some servers that have more than one interface, will have several GUID and/or each server has different GUID. the logic behind this is, first I will check the IP address in registry, if IP address is equal to target IP address (??TARGET.IP_ADDRESS??) than check the RegistrationEnabled that inside the same GUID.
Please give your enlightenment.
I have searched around regarding registry key that contain GUID. In my humble opinion, I doubt that BL can smart enough to query that. I think I need to create EA for that purpose. Any idea from anyone? I really appreaciate for any input/advice.
in 8.x there are conditional statements in the complaince rules so you could do some if..then statements in your rule logic possibly.