Hello All,
I’m curious to know, if there is a way to skip all BigFix actions deployments for a group of computers. I have 3k open actions, don’t want any kind of actions to be deployed and these are newly added machines to BigFix.
Have you considered Client Locking?
Like @JasonWalker referenced you can use a lockedState. What I do for things like this are create a ClientSettings.cfg file and put that in the same directory as the installer when I deploy the install and the client will automatically use it to apply settings. In that cfg file I have these two client settings. __LockState=True will make it so that custom actions don’t apply to the machine. I believe only tasks/fixlets from ‘Bes Support’ site will apply to them. The __DeploymentType client setting is something specific to our company and I use it as a way to tag machines so that I can track which configuration they received. We onboard our acquisitions in a lock state so that we can review security, application stack, etc. before onboarding them completely.
__LockState=True
__DeploymentType=Monitoring
2 Likes