Policy to add Custom setting to all Win clients

Content Authoring
1

I need to add our Custom setting to all Windows systems that do not already have it. Can this be done with an action script?
Custom Setting is “Win Patch_Group_Membership”. My Non Master operators need to populate this setting but will not have access to add it to clients. I figure this can be set up as a policy to run often. Any ideas?

2

Something I’ve done in the past is created an action that applies dynamically to new computers and left the action open to pick up any new ones that are created. That way the setting is applied and can be manipulated by the Non-MO. The action would simply be:

setting "Win Patch_Group_Membership"="" on "{parameter "action issue date" of action}" for client

This would make the setting available for edit without a group inserted.

3

That worked great except I am having issues working out the Relevance code that will not do anything if the setting already exists. Any client with any value for this setting is non relevant.

4

Put your relevance in here. You are trying to globally set this everywhere and override the local setting or?

5

Globally for all Win clients. But if the setting already exists I do not want to override it.This will cover any new systems that come on line.

6

Then the action relevance would be as follows:

not exists setting "Win Patch_Group_Membership" of client

This way the action would only apply to PC’s or servers that don’t already have the setting.

7

After some testing we now use this in production! Works great!!! Thanks for the help,
Frank