Please bear in mind the primary function of ePO is to manage and report on McAfee installed applications rather than general machine system information.
Having said that sometimes the two do overlap, and in fact if your McAfee entitlement allows you should look for the System Information Reporter (SIR) application that allows you to more generally query system properties, environment variables, registry key values, and other installed software on your managed nodes.
You could also use the EEDK to create an ePO package that would run a script that copy the value of the key and then populate one of the McAfee custom properties keys. The Agent would then report this back into ePO.You can then also report on it.
We do something very similar here and find it works well.
I had some thoughts in the past using Distinguished Name or computer groups for ePO, here are some comments that might help:
- As you probably know by now, ePO in general and policy assignment rules mostly support AD user group and not computer groups. This is annoying if you want a policy to stick to a machine regardless the user who login.
- If you are only looking to sort machines based on DN, I think you can use the Active Directory synchronization and define the containers you want with option " Move systems from their current System Tree location to the synchronized group".
- DN originate from AD not registry, therefore, another option is to use an external server backhand that will find the information from AD, export to CSV of host list and using a server task action ("load systems from file") you can apply those systems any action you want based on a schedule.
- If you want to read the registry and act on the results you could follow the EEDK path as Schmiewliski suggested and updated the McAfee Agent custom properties.