Difference between revisions of "Deep Freeze"
From RiceFamily Wiki
(→Possible workarounds) |
|||
| Line 7: | Line 7: | ||
= Possible workarounds = | = Possible workarounds = | ||
| + | The Deep Freeze product has a way to stipulate that a "partition" can be left in a thawed state, the clients could be installed in such a partition, but there needs to be a corresponding way to protect Registry Keys from Seep Freeze activities. I have not found a way to do this yet. | ||
* https://www.faronics.com/webhelp/DFE/82/EN/wwhelp/wwhimpl/common/html/wwhelp.htm#href=Chapter.1.023.html&single=true | * https://www.faronics.com/webhelp/DFE/82/EN/wwhelp/wwhimpl/common/html/wwhelp.htm#href=Chapter.1.023.html&single=true | ||
[[Category:Work]][[Category:BigFix]][[Category:Tanium]] | [[Category:Work]][[Category:BigFix]][[Category:Tanium]] | ||
Latest revision as of 20:51, 17 October 2024
What is Deep Freeze
Deep Freeze is used to restore a system to a known "good" state even is changes are made to the system.
What is the problem with Deep Freeze
This presents problems for management tools like BigFix and Tanium since it will revert changes made by them in the course of their functions.
Possible workarounds
The Deep Freeze product has a way to stipulate that a "partition" can be left in a thawed state, the clients could be installed in such a partition, but there needs to be a corresponding way to protect Registry Keys from Seep Freeze activities. I have not found a way to do this yet.
