Looking at locking/unlocking machines. It seems to have a “action” running for so many days/weeks. Is there a place I can modify this? (Bolded area below)
Example of the “Action: Unlock” Summary:
Behavior
Messages:
No user interface will be shown before running this action.
User:
This action will run independently of user presence.
Execution:
This action ends 3/4/2024 10:25:38 PM client local time.
It will run at any time of day, on any day of the week.
If the action becomes relevant after it has successfully executed, the action will not be reapplied.
If the action fails, it will not be retried.
It seems you’re looking to modify the execution settings. Unfortunately, you can’t directly change a running action in BigFix. You’ll need to stop the current action first, then create a custom copy of it to re-initiate. While doing so, go to the Execution tab of the action, there you’ll find all the settings you can adjust as needed before running it again.
Thanks VK. I guess maybe I’m looking to modify the ‘default’ time it does when I select lock or unlock. Right now it’s 2 weeks. I want the ‘default’ lock or unlock to be 1 week. Is that possible?
Please share your action script. The default lock does not include an expiry; it remains in place until explicitly unlocked. If needed, you can implement an automatic unlock by scheduling an unlock action with a defined time window.
Where do I modify that ‘action’ script for the lock/unlock area? I think that’s really all I need to be able to modify the ‘default’ action script for lock/unlock? (I hope I’m on the right path here!)
To view or modify the action script related to lock/unlock behavior, follow these steps:
- Go to the Actions tab in the BigFix Console.
- Find and right-click on the action you’re interested in.
- Select Custom Copy Action, this will open a new window where you can review and edit key sections like Targets, Execution, and the Action Script itself.
Look specifically at the Action Script area. If there’s logic related to temporary or “week-based” locking, that’s where it will be defined. If you’re unsure, feel free to share the script here, and we can help identify what’s enforcing the timing.
Alternatively, you can trace the action back to its source Fixlet/Task:
- Open the action and check the Details panel at the bottom.
- You’ll see a Source Fixlet/Task link, click that to navigate to the original content.
- From there, you can either view or create a Custom Copy of the Fixlet/Task to adjust the action script directly.
1 Like
Just to be clear, the 2 weeks is just so the action eventually expires for easy cleanup.
When you edit the “Locked” checkbox in the Computer Settings dialog, the action that is generated only runs one time and runs as soon as possible.
This does not make the computer “Stay Locked” for two weeks, it’s just that if the computer does not check in at all for two weeks the “Lock” action won’t run at all.
Once the computer checks in (while the action is still Active), the computer will lock, and stay Locked, until some other action unlocks the machine.
The advice @vk.khurava gives is valid, but there are some particular complexities to “Lock” and “Unlock” actions. These rely on the client allowing actions from the ‘BES Support’ site to run even while the client is Locked (after all it needs to run the Unlock action at some point). You should be able to do a Custom Copy of the Action; but if you copy the source Task to a new site, it may not run as expected (at least, the Unlock version of it may not)
1 Like