I’ve been tasked to find out if there is a way to put clients in a read only mode where they are not able to accept deployments of any kind…Anything like that?
There is a setting called “Locked” that prevents actions being taken. If you click on an endpoint and select “Edit Computer Settings…”, the “Locked” checkbox at the top will lock that endpoint and it will not take any actions.
I believe there is also a way to create your masthead so it installed locked by default but I’ve never used this feature.
2 Likes
“Locked” is exactly what you are looking for.
what @jmaple suggests is helpful if you want to “lock” one computer, but if you want to lock many of them, then use a task with proper relevance that you can deploy to a group or set of computers all at once.
Look for a task “BES Client Setting: Lock Computer” to do this.
1 Like
both @jmaple and @jgstew are correct, although depending on your environment there technically can still be a site that actions can run from. If you open the Admin tool and click Edit Masthead you can configure your deployment to set machines to be locked/unlocked but you can also set a specific site where actions can still run from it. If you check the “Exempt the following site URL from action locking:” and add the URL for the site actions will continue to run on locked machines. In my deployment it looks something like this http://domain:52311/cgi-bin/bfgather.exe/CustomSite_LockOverrideContent where all endpoints are subscribed to the Custom Site called “LockOverrideContent”, any action created and run from this site still runs on machines regardless of the locked state.
1 Like