FARONICS DEEP FREEZE ENTERPRISE - PATCH MANAGEMENT... User manual

TECHNICAL WHITEPAPER
Last modified: June 26, 2009
www.faronics.com
© 1999 - 2009 Faronics Corporation. All rights reserved. Faronics, Deep Freeze,
Faronics Core Console, Faronics Anti-Executable, Faronics Device Filter, Faronics
Power Save, Faronics Insight, Faronics System Profiler, and WINSelect are
trademarks and/or registered trademarks of Faronics Corporation. All other
company and product names are trademarks of their respective owners.
Faronics
Toll Free Tel: [phone]
Toll Free Fax: [phone]
International Tel: [phone]
International Fax: [phone]
Deep Freeze Enterprise - Patch Management

ENTERPRISE
2
Contents
Introduction....................................................................................................................................... 3
Scheduled Patch Maintenance........................................................................................................... 3
Scheduling Windows Updates..................................................................................................................... 3
Scheduling Windows Updates in a Deep Freeze Maintenance Period.............................................. 4
Scheduling Windows Updates through Group Policy .............................................................................5
Scheduling Antivirus Updates..................................................................................................................... 7
Scheduling Additional Program Updates .................................................................................................. 7
Logon Patch Maintenance ................................................................................................................. 8
Logon Patch Maintenance eory..............................................................................................................8
Logon Patch Maintenance Example ...........................................................................................................9
Creating the Update Script......................................................................................................................9
Creating the Group Policy.....................................................................................................................15
Modifying the Group Policy .................................................................................................................16
Enforcing the Group Policy ..................................................................................................................16
Real Time Patch Maintenance......................................................................................................... 17
Disabling Deep Freeze Locally ..................................................................................................................17
Disabling Deep Freeze rough the Enterprise Console.......................................................................17
Disabling Deep Freeze rough the Command Line Control..............................................................17
Configuring Soware to Update in a awed Location ................................................................. 17
Appendix A: Deep Freeze and SUS/WSUS FAQ ............................................................................. 18
Appendix B: Deep Freeze Update Script......................................................................................... 19
Appendix C: Common Update Scenarios ....................................................................................... 23
Scenario 1: Updating Clients in a Dynamic Update Environment ......................................................23
Scenario 2: Updating in a 24-Hour Lab Environment...........................................................................23
Scenario 3: Updating in a Mobile Environment .....................................................................................23

3
ENTERPRISE
Introduction
A major concern for all systems administrators is maintaining the security of their computers. With
new exploits and vulnerabilities being found all the time, a proper patch management strategy is critical
to ensure the health and security of computer deployment.
Deep Freeze allows systems administrators to ensure the integrity of their computers against exploits
— even ones that have yet to be discovered. However, it introduces some challenges within the process
of applying patches because Deep Freeze does not discriminate — it removes both the good and the
bad changes and returns the computer to its original, pristine state on every restart.
ere are several methods for integrating Deep Freeze with patch management. When properly done,
users can enjoy the bulletproof reliability of a Deep Freeze protected system and system administrators
can have the peace of mind that comes from knowing their systems are fully up to date.
is white paper discusses the different methods available to update soware in a Deep Freeze
environment.
ScheduledPatchMaintenance
Scheduled patch maintenance allows the administrator to specify a period of time when the client
computers restart with Deep Freeze in a awed state. During this Maintenance Period, soware
updates, Windows Updates, and antivirus definition updates can be scheduled. Scripts can be run and
batch files can be executed.
Scheduled patch maintenance is an appropriate strategy for computer labs. During certain times on
certain days of the week, labs are not in use. A Maintenance Period can be scheduled to run updates
during these times.
Maintenance Periods are configured using the Deep Freeze Configuration Administrator. e
Configuration Administrator is used to configure workstation installation files as well as configuration
files. Configuration files can be used to apply the changes to deployed computers through the Deep
Freeze Enterprise Console.
Depending on the policies in place, certain updates may need to be run. Windows and antivirus
updates tend to be the most frequent. e following information explains some of the update scenarios
encountered and the different methods available to handle these updates.
SchedulingWindowsUpdates
ere are several different methods available to run a Windows update in a Frozen environment. Deep
Freeze can be set up to start a Windows update during a Maintenance Period. Deep Freeze can also
be set up to execute a batch file during the Maintenance Period. A batch file could be used to start the
Windows update process. Finally, another program could be used to start Windows updates during the
Deep Freeze Maintenance Period.

ENTERPRISE
4
SchedulingWindowsUpdatesinaDeepFreezeMaintenancePeriod
e first method involves setting up a Maintenance Period using the Deep Freeze Configuration
Administrator. An option is selected so Deep Freeze will run Windows updates aer the computer
goes into Maintenance Mode.
Complete the following steps to configure a Maintenance Period:
1. In the Deep Freeze Configuration Administrator, click the Embedded Events tab.
2. Specify day and time the Maintenance Period will occur. e window should look similar
to the following:
In the above screen, Tuesday has been selected for Maintenance with the Run: Windows Update option.
At 1:00 AM, the computer restarts in a awed state. At 4:00 AM, the computer restarts in a Frozen
state. e Disable Keyboard and Mouse checkbox has been checked; this means that the keyboard and
mouse are locked while the computer is in Maintenance Mode.
If a client computer is configured with this option, it would attempt to download and run updates from
Microso’s web site during the Maintenance Period.

5
ENTERPRISE
If there is an SUS or WSUS server, this can be specified using the following steps:
1. Click the Maintenance tab.
2. Check Use SUS/WSUS Server and enter the IP address of fully qualified domain name of the
server. e screen should look similar to the following:
e client computer with these settings would attempt to download and run updates from the specified
SUS/WSUS server rather than from Microso’s web site.
SchedulingWindowsUpdatesthroughGroupPolicy
Although settings forWindows update can be administered through Deep Freeze, many administrators
prefer to control settings for automatic updates through the use of Group Policy in a domain
environment.
It is recommended that the following configuration be used to configure the Automatic Update client
on a computer running Deep Freeze:
Computer Configuration → Administrative Templates → Windows Update:
•Configure Automatic Updates: Enabled.
•Configure Automatic Updating: Enabled.
•Scheduled install day: 0 if Maintenance will happen every day; the specific day if Maintenance
will only occur once per week.
•Scheduled install time: Set to 30 minutes aer the start of the Deep Freeze Maintenance
Period.
•Do not display Install Updates and Shut Down option in Shutdown Windows dialog box:
Enabled
•Do not adjust default option to Install Updates and Shut Down in Shut Down Windows dialog
box: Enabled

ENTERPRISE
6
•Reschedule Automatic Updates scheduled installations: Disabled
•No auto-restart for scheduled Automatic Updates installations: Disabled
is policy will ensure that Windows updates are installed during the Maintenance Period and that
any updates that are downloaded (but not installed) will not attempt to reinstall on the client computer
while Frozen.
Administrators need to ensure that the Maintenance Period configured in Deep Freeze is long enough
to complete the download and installation of the updates from whatever source is configured and that
computers are either le on to enter the Maintenance Period or are woken up prior to the start of the
Maintenance Period.

7
ENTERPRISE
SchedulingAntivirusUpdates
ere are several different methods available to run antivirus updates depending on the antivirus
solutions being used. e following are links to white papers for several of the most common solutions.
ese white papers explain several methods that can be used. Any of these white papers explain
concepts that may be used with other solutions not listed here.
Computer Associates eTrust Anti-Virus
http://www.faronics.com/Faronics/Documents/DFEnt_CAeTrust.pdf
McAfee eTrust Orchestrator
http://www.faronics.com/Faronics/Documents/DFEnt_McAfeeEPO.pdf
Panda BusinessSecure Antivirus
http://www.faronics.com/Faronics/Documents/DFEnt_PandaAntivirus.pdf
Symantec Anti-Virus Corporate Edition
http://www.faronics.com/Faronics/Documents/DFEnt_SymantecAntivirus.pdf
Trend Micro OfficeScan
http://www.faronics.com/Faronics/Documents/DFEnt_TrendOfficeScan.pdf
For additional white papers describing antivirus products that may have been added to the Faronics
Content Library aer publication of this white paper, refer to:
http://www.faronics.com/library
SchedulingAdditionalProgramUpdates
e concepts outlined for the antivirus definition updates can also be applied to updating other
applications. However, not all methods described may work with a particular application. Refer to the
above antivirus white papers for suggested methods, or the white paper entitled Retaining User Data at
the following location: http://www.faronics.com/Faronics/Documents/DF_RetainUserData.pdf

ENTERPRISE
8
LogonPatchMaintenance
is option allows the administrator to install updates to the client computer when a certain user logs
on. In an Active Directory environment, a logon script can be executed to update the client computer.
Using Deep Freeze command line control (DFC), Deep Freeze can be disabled before the updates are
run and re-enabled aerwards.
Logon patch maintenance is appropriate in mobile environments where users are working with laptops
and are oen off the local network. When they get back to the office or school and login, a script is
executed to determine if the users require any updates. If they do, the users are prompted as to whether
they would like to run the updates. If they agree, Deep Freeze is disabled, the updates are run, and
Deep Freeze is re-enabled.
e example below assumes that the person implementing the script is familiar with Group Policy,
Active Directory, and Visual Basic Scripting.
LogonPatchMaintenanceTheory
is concept deals with updating a Frozen machine when the user logs on. With some slight
modifications, the same theory can be applied to an environment where patches are scheduled or
performed in real time. e following flowchart outlines the required steps, depending on the state of
the update process:
Star t Update running Run Patch
Update
Complete?
Prompt User
Update?
End
Insert Marker Frozen?
Run Patch
Boot into Thawed
State
Remove Marker
Boot into Frozen
State
Remove Marker Boot into Frozen
state
End
Yes
Yes
Yes Yes
No
No No
No

9
ENTERPRISE
Because the computer boots several times, the script needs to check a value to see what phase of the
script is currently running. Because the computer will be Frozen at times, a value cannot be stored
in the Frozen partition. is means the value must be stored either on the network or in a awed
partition on the computer.
It is also important to understand that the above flowchart is a very simple model. In a real-world
example, the flowchart would most likely have additional steps to disable the keyboard and mouse
and check for the current version of the patch to run. ose steps are beyond the scope of this white
paper.
LogonPatchMaintenanceExample
e following example uses an Active Directory environment to call a script file when a user logs on.
e following section describes how to create a script based on the earlier flowchart and implement
Group Policy to call this script when a user logs on.A full version of the script can be downloaded from
the following location:
http://www.faronics.com/Faronics/Documents/DFEnt_ADUpdateScript.zip
CreatingtheUpdateScript
is script checks to see if the computer requires updates. If the computer requires an update, it
prompts the user. If the user selects Yes, the computer is put into a awed state. At this point, the
patch is applied and the computer is returned to a Frozen state.
Use the following steps to create the script file one section at a time:
e script file can be created using many different editors. In this case, Notepad is used.
1. Open Notepad and enter the following text to create the global assemblies:
‘ ********** GLOBAL ASSEMBLIES **********
Set objNet = CreateObject(“WScript.NetWork”)
is code segment creates an object called objNet used throughout the script.
2. Enter the following text to create the global variables:
‘ ********** GLOBAL VARIABLES **********
strUNCPath = “\\FarDemo.local\NETLOGON\”
strMarkerFile = objNet.ComputerName & “.mar”
strMarkerCompleteFile = “COMPLETED-” & objNet.ComputerName & “.fin”
strUNCPath is a variable that maps to a server. Modify the path to match that of the server
being used. is is where the marker files are created. e Marker files are used to determine
whether the machine requires an update and whether the update is completed.
strMarkerFile is a variable holding the name of the marker file used to indicate whether an
update is running. Each marker file has the unique name equal to the machine the update is
running on.
strMarkerCompleteFile is a variable holding the name of the file to indicate if the patch has
been run. If this file exists, the update has been run and is not required to run again.

ENTERPRISE
10
3. Enter the following text to create the main routine:
‘ ********** MAIN **********
‘ Calls all of the other routines...
If UpdateRunning = True Then
RunPatch
RemoveMarker
BootFrozen
Else
If UpdateComplete = False Then
If UserPatchPrompt = True Then
InsertMarker
If Frozen = True Then
BootThawed
Else
RunPatch
RemoveMarker
BootFrozen
End If
Else
‘ Exit Script
End If
Else
‘ Exit Script
End If
End If
e main routine follows the structure of the flowchart. It calls the other routines as
required.
4. Enter the following text to create the UpdateRunning function:
‘ ********** UPDATE RUNNING? **********
‘ Check for marker file. If exists, the update is running. Return True.
Function UpdateRunning
Set objFS = CreateObject(“Scripting.FileSystemObject”)
Set objFolder = objFS.GetFolder(strUNCPath)
Set objRE = new RegExp
objRE.Pattern = strMarkerFile
objRE.IgnoreCase = True
For Each objFile In objFolder.Files
If objRE.Test(objFile.Name) Then
UpdateRunning = True
Exit Function
End If
Next
UpdateRunning = False
End Function
e UpdateRunning function checks to see if the marker file exists on the server. If it does, the
updates must be running and the function returns the value of True.

 11
ENTERPRISE
5. Enter the following text to create the UpdateComplete function:
‘ ********** UPDATE COMPLETE? **********
‘ Checks for completed marker file. If it exists, the update has already run.
Function UpdateComplete
Set objFS = CreateObject(“Scripting.FileSystemObject”)
Set objFolder = objFS.GetFolder(strUNCPath)
Set objRE = new RegExp
objRE.Pattern = strMarkerCompleteFile
objRE.IgnoreCase = True
For Each objFile In objFolder.Files
If objRE.Test(objFile.Name) Then
UpdateComplete = True
Exit Function
End If
Next
UpdateComplete = False
End Function
e UpdateComplete function checks to see if a marker file has been created which signifies
the completion of the update. If this file exists, the function returns a value of True.
6. Enter the following text to create the UserPatchPrompt function:
‘ ********** USER PATCH PROMPT **********
‘ Prompt the user whether they would like to run the updates at this time.
Function UserPatchPrompt
intAnswer=Msgbox(“Anupdatehasbeendetected.Wouldyouliketoruntheupdatenow?”&vbLF&_
“The update process will require several reboots!”, vbYesNo, “Update Detected”)
If intAnswer = vbYes Then
UserPatchPrompt = True
InsertMarker
Else
UserPatchPrompt = False
End If
End Function
e UserPatchPrompt function prompts the user with a Yes /No dialog. If the user selects Yes,
the patch runs and the function returns a value of True. If the user selects No, the function
return a value of False and the patch will not run.

ENTERPRISE
12
7. Enter the following text to create the RunPatch routine:
‘ ********** RUN PATCH **********
‘ The code to run the patches would occur here.
Sub RunPatch
‘ Enter code to execute the patch(es)
MsgBox “Patch has been applied”
InsertCompleteMarker
End Sub
e RunPatch routine is used to run the patch. Any code to start a patch can be placed into
this routine. Aer the patch is run, a message is sent to the user indicating the patch has been
completed. Another routine, called InsertCompleteMarker is run to create a marker file to
indicate the patch has been run.
8. Enter the following text to create the Frozen function:
‘ ********** DEEP FREEZE FROZEN? **********
‘ Checks to see if Deep Freeze is Frozen and returns True or False.
Function Frozen
Set objShell = CreateObject(“Wscript.Shell”)
intStatus = objShell.Run(“DFC password /ISFROZEN”, 1, True)
If intStatus = 0 Then ‘DF is Thawed
Frozen = False
Else
If intStatus = 1 Then ‘DF is Frozen
Frozen = True
Else
‘A number of other reasons.
End If
End If
End Function
e Frozen function checks to see if Deep Freeze is Frozen. If it is Frozen, the function returns
a value of True. If Deep Freeze is awed, the function returns a value of False.
9. Enter the following text to create the BootFrozen routine:
‘ ********** BOOT FROZEN **********
Sub BootFrozen
Set objShell = CreateObject(“Wscript.Shell”)
objShell.Run(“DFC password /BOOTFROZEN”)
End Sub
e BootFrozen routine is used to put computers into a Frozen State.e password in the DFC
command line must be modified to match password created for the command line control.

 13
ENTERPRISE
10. Enter the following text to create the Bootawed routine:
‘ ********** BOOT THAWED **********
Sub BootThawed
Set objShell = CreateObject(“Wscript.Shell”)
objShell.Run(“DFC password /BOOTTHAWED”)
End Sub
e Bootawed routine is used to set computers in a awed state. e password in the
DFC command line must be modified to match the password created for the command line
control.
11. Enter the following text to create the InsertMarker routine:
‘ ********** INSERT MARKER **********
‘ Insert the marker file to indicate the patch is in progress.
Sub InsertMarker
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
Set objFile = objFSO.CreateTextFile(strUNCPath & strMARKERFILE)
End Sub
e InsertMarker routine creates a marker file on the server to indicate the patch is currently
being run. is marker file remains on the server until it is removed by the DeleteMarker
routine.
12. Enter the following text to create the RemoveMarker routine:
‘ ********** REMOVE MARKER **********
‘ Remove the marker file to indicate the patch is complete
Sub RemoveMarker
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
objFSO.DeleteFile(strUNCPath & strMarkerFile)
End Sub
e RemoveMarker routine removes the marker file on the server to indicate the patch is no
longer being run.
13. Enter the following text to create the InsertMarkerComplete routine:
‘ ********** INSERT UPDATE COMPLETE MARKER **********
‘ This inserts an update completed file to prevent update looping
Sub InsertCompleteMarker
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
Set objFile = objFSO.CreateTextFile(strUNCPath & strMarkerCompleteFile)
End Sub
e InsertMarkerComplete routine creates a file to indicate if the patch has been run on a
computer. As long as this file exists on the server, the user is never prompted and the patch is
never run.

ENTERPRISE
14
14. Enter the following text to cleanup the script objects:
‘ ********** CLEANUP **********
Set objNet = Nothing
Set objFile = Nothing
Set objRE = Nothing
Set objFolder = Nothing
Set objTS = Nothing
Set objFS = Nothing
Set objTextFile = Nothing
Set objFSO = Nothing
is code cleans up all the objects that have been created throughout the script.
15. Save the file as DF Update.vbs. Make sure the file is saved as a .vbs and not a .txt. e icon
should look like the following:
e script is now ready to be implemented through a logon script in Group Policy.
NOTE: e script does not contain any error handling.

 15
ENTERPRISE
CreatingtheGroupPolicy
Before the policies are created,ensure the server has been updated to use the Group Policy Management
Console. e following documentation assumes this patch has been downloaded and installed on
the server. e utility can be found by searching Microso’s Web site for Group Policy Management
Console.
It is assumed there is an Organizational Unit (OU) for those users whom will be logging on to the
network with a laptop machine requiring updates. Use the following steps to create the Policy:
1. Right-click on the desired User OU and select Properties. e properties dialog appears.
2. Select the Group Policy tab. If the Group Policy Management console is successfully installed,
the following screen appears:
3. Click Open.
e Group Policy Management window opens, displaying all the OUs that have been created.
4. Right-click on the desired OU and select Create and Link GPO Here. e New GPO dialog
appears.
5. Type DfLogonPatchManagement and click OK.
A GPO with the name of DfLogonPatchManagement appears under the desired OU.

ENTERPRISE
16
ModifyingtheGroupPolicy
Now that the GPO has been created, it needs to be modified. In this case, the user Logon script is
modified using the following steps:
1. Right-click on DfLogonPatchManagement and select Edit. e Group Policy Object Editor
opens.
2. Browse to the Logon/Logoff scripts for the user through User Configuration>Windows
Settings>Script (Logon/Logoff).
3. Double-click Logon to open the Logon Properties dialog.
4. Click Show Files... to open Windows Explorer. Place the script file created earlier in this
folder.
5. Close Windows Explorer.
6. Click Add in the Logon Properties dialog. e Open dialog should appear and point to the
folder where the script was just placed.
7. Select DF Update.vbs and click OK.
8. Click OK on the Logon Properties dialog to save the settings.
EnforcingtheGroupPolicy
e logon script has been configured to execute when the user logs on. However, the GPO is not yet
enforced. Enforcing a GPO indicates to the Active Directory server that it needs to run.
To enforce the newly created GPO, right-click on DfLogonPatchManagement and select Enforced to
ensure the logon/logoff scripts are applied to the selected OU.
e policy now indicates that it is enforced. is can be verified by checking to see if the Enforced
column in the Group Policy Management window displays a Yes.

 17
ENTERPRISE
RealTimePatchMaintenance
is method involves patching a computer in real time. It is best used when the computers are not
in use. Sometimes a patch needs to be manually applied to a group of computers and scheduling the
task may not be an option. is method involves disabling Deep Freeze locally at the client through
the Enterprise Console or with the command line control (DFC). e update can then be applied and
Deep Freeze can be re-enabled.
DisablingDeepFreezeLocally
Use the following steps to put Deep Freeze into a awed state from the local computer:
1. To access the Deep Freeze login dialog, use one of the following methods to log on:
• Press SHIFT and double-click the Deep Freeze icon in the System Tray
• Use the keyboard shortcut CTRL+SHIFT+ALT+F6
2. e Deep Freeze login dialog appears.Enter your Deep Freeze password. is password would
have been configured in the Configuration Administrator prior to creating the workstation
installation file, or applied through a configuration update.
3. Under the Boot Control tab, select Boot awed and click OK. When the computer restarts, it
is in a awed state. At this point any changes made to the computer are permanent.
DisablingDeepFreezeThroughtheEnterpriseConsole
Use the following steps to put a computer into a awed state using the Deep Freeze Enterprise
Console:
1. Launch the Deep Freeze Enterprise Console.
2. Select the computers that need to be put into a awed state.
3. Click the Reboot awed icon in the toolbar or right-click and select Reboot awed from the
menu. e selected computers will reboot in the awed state.
DisablingDeepFreezeThroughtheCommandLineControl
e Deep Freeze command line control (DFC) can be used to disable Deep Freeze. It can be used in
scripts, batch files, and in conjunction with any third party management utility capable of pushing
scripts to systems. For more information about the different switches offered by the command line
control, refer to the following document:
http://www.faronics.com/Faronics/Documents/DF_RemoteAdministration.pdf
ConguringSoftwaretoUpdateinaThawedLocation
It is possible to update soware that resides in a awed location. In these cases, the soware would
have to exist entirely on the awed partition. Remember the following rules when configuring
soware to run from a awed location:
1. If updates have to make changes to the registry, Deep Freeze needs to be in a awed state.e
reason for this is that the registry is stored on the Frozen location.
2. Many programs store data to the user folders. e user folders can be redirected to a awed
location.However,if the user folders are not redirected,ensure that the updates are not making
changes to settings stored there.

ENTERPRISE
18
AppendixA:DeepFreezeandSUS/WSUSFAQ
Does the Run Windows Updates feature require an administrator to be logged into the computer?
e feature works while any type of user is logged in, or if the computer isn’t logged in at all. It
uses the Windows Update service running under the local system account.
How can I be sure that the updates have been installed correctly?
If you are using Deep Freeze to install the updates, you can view the status of the updates in
the DFWuLogfile.log in the Faronics folder. e location and name of this file can be changed
on the Maintenance tab of the Deep Freeze Configuration Administrator.
What happens if an update is interrupted during download or installation because the Maintenance
Period ended or the computer was restarted or powered off?
If an update is incomplete for any reason, the mechanism that Microso uses will correct and
reinstall the update the next time the service is called.
Will the computer restart during the update process if the update being installed requires it to do so?
Yes, the computer will restart as many times as required, until the updates are completed.
What do I have to configure on each computer to ensure that the updates are downloaded during the
Maintenance Period?
Deep Freeze automatically coordinates the update. Deep Freeze does not actually perform the
update but calls the Microso update service during the Maintenance Period. e Microso
update service then performs the update either via the Internet or a designated SUS/WSUS
server.
Can the IP address of the SUS/WSUS server be updated with a configuration update?
Yes, all of the Maintenance options can be changed with a configuration update.

 19
ENTERPRISE
AppendixB:DeepFreezeUpdateScript
e entire script explained in the Logon Patch Maintenance section has been included here. It can
be downloaded from the following address: http://www.faronics.com/Faronics/Documents/DFEnt_
ADUpdateScript.zip
‘ ****************************************************************
‘ *** DF SIMPLE UPDATE SCRIPT SAMPLE ***
‘ *** ***
‘ *** Author: Faronics Corporation ***
‘ *** Date: 12/29/2005 ***
‘ *** ***
‘ *** Associated Files: ***
‘ *** <ComputerName>.mar - Used to indicate patch is running ***
‘ *** COMPLETE-<ComputerName>.fin - Indicates patch complete ***
‘ *** DFC.exe - Deep Freeze Command Line Control ***
‘ ****************************************************************
‘ NOTES:
‘ The following script will turn off Deep Freeze, run updates and turn on Deep Freeze.
‘ ********** GLOBAL ASSEMBLIES **********
Set objNet = CreateObject(“WScript.NetWork”)
‘ ********** GLOBAL VARIABLES **********
‘ Modify the UNC path to match that of your server envrionment.
strUNCPath = “\\FarDemo.local\NETLOGON\”
strMarkerFile = objNet.ComputerName & “.mar”
strMarkerCompleteFile = “COMPLETED-” & objNet.ComputerName & “.fin”
‘ ********** MAIN **********
‘ Calls all of the other routines...
If UpdateRunning = True Then
RunPatch
RemoveMarker
BootFrozen
Else
If UpdateComplete = False Then
If UserPatchPrompt = True Then
InsertMarker
If Frozen = True Then
BootThawed
Else
RunPatch
RemoveMarker
BootFrozen
End If
Else
‘ Exit Script
End If
Else
‘ Exit Script

ENTERPRISE
20
End If
End If
‘ ********** UPDATE RUNNING? **********
‘ Check for marker file. If exists, the update is running. Return True.
Function UpdateRunning
Set objFS = CreateObject(“Scripting.FileSystemObject”)
Set objFolder = objFS.GetFolder(strUNCPath)
Set objRE = new RegExp
objRE.Pattern = strMarkerFile
objRE.IgnoreCase = True
For Each objFile In objFolder.Files
If objRE.Test(objFile.Name) Then
UpdateRunning = True
Exit Function
End If
Next
UpdateRunning = False
End Function
‘ ********** UPDATE COMPLETE? **********
‘ Checks for completed marker file. If it exists, the update has already run.
Function UpdateComplete
Set objFS = CreateObject(“Scripting.FileSystemObject”)
Set objFolder = objFS.GetFolder(strUNCPath)
Set objRE = new RegExp
objRE.Pattern = strMarkerCompleteFile
objRE.IgnoreCase = True
For Each objFile In objFolder.Files
If objRE.Test(objFile.Name) Then
UpdateComplete = True
Exit Function
End If
Next
UpdateComplete = False
End Function
‘ ********** USER PATCH PROMPT **********
‘ Prompt the user whether they would like to run the updates at this time.
Function UserPatchPrompt
intAnswer = Msgbox(“An update has been detected. Would you like to run the update now?” & vbLF & _
“The update process will require several reboots!”, vbYesNo, “Update Detected”)
If intAnswer = vbYes Then
UserPatchPrompt = True
InsertMarker
Else
UserPatchPrompt = False
End If
End Function