Locking clients

You can change the locked status of any BigFix client in the network. This lets you exclude specific computers or groups of computers from the effects of Fixlet actions.

This could be useful, for example, if you wanted to exclude certain development computers from any changes or updates. It also provides a powerful technique for testing new Fixlet actions on a limited set of unlocked computers, while keeping the rest of the network locked down. client computers can be locked forever (until explicitly unlocked) or for a defined period of time.

Changes are made to the locked status of a client by sending an action. As a consequence, the Console operator must supply proper authentication to lock or unlock any computer.

Even though a client is locked, there is still a subset of commands that can be accepted by the client:
  • clock changes
  • relay select
  • notify client
  • client setting actions (through the Edit Settings dialog in the Console)
  • administrator management (add/delete)
  • subscribe and unsubscribe sites
  • utility
  • unlock actions
  • any actions from the BES Support site.

To lock or unlock a computer, follow these steps:

  1. Click the Computers icon in the Domain Panel navigation tree to see the List Panel of networked BigFix client computers.
  2. Select the computers that you want to lock.
  3. Right-click and select Edit Computer Settings from the pop-up menu (or select Edit Computer Settings from the Edit menu). The Edit Setting dialog opens.
  4. Click the check box to either lock or unlock the computer.

Although the console does not provide an explicit interface for setting an expiration date on the lock, you can create a custom action to do this. For more information, see the BigFix Developer site.