User manual FARONICS DEEP FREEZE ENTERPRISE 6

[. . . ] This page intentionally left blank SecurityNotice Deep Freeze does not protect against booting from a floppy drive or CD-ROM drive. The CMOS should be configured to prevent booting from the floppy drive or CD-ROM drive (i. e. set to boot to the hard drive) and the CMOS must be password protected. The Windows Registry, the computer CMOS and the boot sector are protected by Deep Freeze from within Windows. [. . . ] The Active Directory group with all its subgroups appears under User Defined Groups. NOTE: When this function is used, the console will import groups and containers from the domain that the console is logged into. AddingWorkstationstoaUserDefinedGroup Workstations can be added to a group by dragging them from the Workstations pane to the preferred group, or by using an automatic filter set during the creation of the groups. Automatic group filtering allows workstations to be added to user defined groups automatically. Wildcards (*, ?) can be used to add workstations based on a specific segment of the name. Example: Lab1-* adds all workstations with names starting with Lab1- . SortingGroupsAlphabetically To sort the User Defined Groups alphabetically, right-click on User Defined Groups and choose Sort Groups Alphabetically. ImportingorExportingGroupstoFile To import groups from a file or export groups to a file, choose the preferred option from the Tools menu. ViewingtheConsoleLogFile The Enterprise Console keeps a log of the status and activity history of all connected workstations. Information older than 48 hours is automatically deleted from the log. To view the log file for one or many workstations, right-click on the workstation(s) and select Show Log for Selected Workstations. To export the log file as a . csv file, right-click and select Export to file, as shown: InstallingDeepFreeze After a customized installation program file has been created using the Configuration Administrator, Deep Freeze can be deployed to workstations using an Attended Install, a Target Install, the Silent Install System, or as part of an imaging process. All background utilities and antivirus software should be disabled and all applications should be closed prior to installation. These programs may interfere with the installation, which could result in Deep Freeze not functioning correctly. Deep Freeze must be in a Thawed state for any type of uninstall to succeed. Any existing ThawSpace will be deleted during an uninstall if: · the option to retain existing ThawSpace was not checked in the Configuration Administrator · the ThawSpace was not created with Deep Freeze Enterprise Version 5 or later · the ThawSpace is on a Windows 95/98/Me workstation AttendedInstallorUninstall To install or uninstall Deep Freeze, complete the following steps: 1. The following screen appears. 2. Click Install to begin the installation. Follow the steps presented, then read and accept the license agreement. Uninstall can only be clicked if Deep Freeze has previously been installed. If there is an existing ThawSpace, Deep Freeze displays a dialog asking if it should be retained or deleted. UninstallingDeepFreeze The Enterprise Console can be used to uninstall Deep Freeze completely or to uninstall Deep Freeze but leave the Workstation Seed. A workstation must be in a Thawed state in order to uninstall the program. To uninstall Deep Freeze on a workstation and leave the Workstation Seed, right-click on the Thawed workstation(s) and select Uninstall - Leave Seed, as shown above. Or click the icon on the toolbar To completely uninstall Deep Freeze and the Workstation Seed, select the workstation(s) to be uninstalled and click the Uninstall icon on the Toolbar. [. . . ] The workstations were created under a different customization code than the console. When the Deep Freeze Configuration Administrator is first run, a prompt for a Customization Code appears. This means that any workstations created are encrypted with this customization code. If a console was created using another administrator that was installed with a different customization code, it cannot see workstations created under the original code. The workstations and console must be created under a configuration administrator installed using the same exact customization code. 6. [. . . ]