Difference between revisions of "Enable Custom Site to bypass a Client Lock State"
From RiceFamily Wiki
(Created page with "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 c...") |
|||
| Line 1: | Line 1: | ||
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. | 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. | ||
| − | [[ | + | [[Category:IBM Endpoint Manager]] |
Revision as of 00:18, 15 July 2015
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.
