To implement something like that would not work for us. What we have is a few hundred locked Unix/Linux machines that never want to be patched, although we want these machines to run policy actions (relay affiliation, dynamic bandwidth throttling… and many others). If I setup that registry key for my Windows account, all of my actions are going to execute against locked machines. Our corporate policy will not allow us to create a generic Windows account used for login purposes, so we can set this like that. Essentially this setting is per user, while I need it per site. Is there any other way around this? Why can’t we use lock exemptions on custom sites?
As you see from my first post, this is what I tried. That didn’t work. I used the dns name we have configured Bigfix with instead of the servername. Would that make a difference? We pulled this value from the “Gather Status Report”.
We looked into this more and unfortunately we do not believe that custom sites will work with lock exemptions in the version you are using. When we ran the tests previously, we were using a newer development build, which had some changes in this area that we didn’t realize.
Sorry for the confusion… I am trying to think of another way to make this work for you, but I can’t think of anything except the console lock exemption that you said was not a good idea.
I think the best thing to do will be to contact BigFix Professional Services and we can publish your Fixlet in a Fixlet site that you can add as a lock exemption.