If your an NMO, you will have to find out if you have access to create custom properties. You can also accomplish the same result by creating an analysis. Each Analysis property can be used for identifying machines.
First, and this is critical. You want to make your properties as a client settings if you want cross platform availability (value of setting “Patch_Day” of client).
You can create a custom property that reads a Windows Registry key but if you make it a client setting, you can use the same property on other, non windows systems.
You can use two values to identify a system, Patch_Day and Patch_Times
If you use “manage properties” in the console, you can create the property there…
NAME: Patch_Day
if exist values of settings "Patch_Day" of client then value of setting "Patch_Day" of client else "Not Set"
Then the Time
Name: Patch_Time
if exist values of settings "Patch_Time" of client then value of setting "Patch_Time" of client else "Not Set""
Then create a task to set these values…
Name: Set Patch Day and Time
// Set Patch Day and Patch Time, prompted to enter these values
action parameter query "PatchDay" with description "Please enter the Patch day you would like to assign these systems (Monday, Tuesday...):" With default ""
action parameter query "PatchTime" with description "Please enter the Patch Time you would like to assign these systems (8:00 PM):" With default ""
setting "Patch_Day"="{parameter "PatchDay" of action}" on "{parameter "action issue date" of action}" for client
setting "Patch_Time"="{parameter "PatchTime" of action}" on "{parameter "action issue date" of action}" for client.
You can still pull this data from the registry on windows systems if you want, They are here…
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\EnterpriseClient\Settings\Client\Patch_Day
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\EnterpriseClient\Settings\Client\Patch_Time
I am not able to provide the API, hopefully someone else can do so. I do not use API.