Any problems with the update process that would result in failed updates are error handled and rolled back with the appropriate information retained in the Windows Update logs on the client machines.ĭuring this process the machine will perform a number of reboots, up to a total of 5, to complete the update process.

When Deep Freeze is controlling the update process the general flow of operations is as shown below ĭuring the update process Deep Freeze interfaces with the Windows Update Service on the client machine to ensure that updates are installed and that all appropriate steps are taken to ensure that the updates are fully installed before the system returns to a protected state. This is best done by scheduling a specific time period where the client systems will enter into a thawed (non protected) state on an automatic basis, perform the required updates, and then return to a Frozen (protected) state when the process is completed.

Owing to the nature of what Deep Freeze does to machines that are protected updates must be installed on the client machine while Deep Freeze is disabled. This document will provide details on how Deep Freeze Enterprise interacts with the Windows Update service and will provide suggestions on how best to configure the product to control the update process on client machines protected by Deep Freeze. Posted by Adam Zilliax, Last modified by Adam Zilliax on 10 June 2019 08:04 AM

Deep freeze for windows 8