The trial version expires after 30 days.
The Release Notes and manual for each version of DriveLock contain detailed information about upgrading from previous versions. In general, CenterTools recommends that you first update the agent and then the administration tools.
To use the full version of DriveLock you must install a valid license key from the license file. To install the license key, either open the DriveLock Configuration console. If you are using Group Policy to implement DriveLock settings, open the DriveLock policy. On the Global Settings menu, click License, and then click Import license file. Select your license file, and then clock Import.
CenterTools DriveLock has very small hardware and software requirements. You can find details in the DriveLock Planning, Installation and Deployment Manual, available at our the Manuals page.
When you open ”Global Settings“, the DriveLock console checks for a valid license file. Depending on the location of the license file, this may cause a short delay. Incorrect DNS settings on the computer may result in a delay of up to 60 seconds.
You may experience unexpected behavior, including system crashes, when testing DriveLock with USB hardware under VMware. This is due to known problems in VMware’s USB implementation. Please consult VMware’s Web site for Knowledge Base articles on how to work around such issues. CenterTools recommends that you perform all testing on real hardware instead of a virtual environment.
When collecting DriveLock events you may see a lot of Service Startup/Shutdown events. You can turn off the reporting of these events. To turn off reporting, on the Global Settings menu, click Event message transfer settings. Disable the checkboxes for Events due to service startup / shutdown.
If you are using Windows toaming profiles or logon scripts that are very long and take longer than 20 seconds to complete you should increase a timeout set by DriveLock. Unless you perform this step, drives or devices might not be correctly locked or unlocked for the current user. To change the timeout, on the Global Settings menu, click Advanced DriveLock agent settings, and then increase the Timeout for detection of new logins value.Additional information: DriveLock need to read the user’s SID, but this information is only available after the login script has finished processing.
If you enable the Shadow Copy feature, DriveLock caches the most recently shadowed files to minimize network traffic. DriveLock keeps up to 1000 items in the cache. Each version of a file is treated as a separate item. DriveLock automatically removes older items from the cache when this limit is reached.
To ensure that DriveLock configuration files with a .cfg extension can be properly downloaded from a Web server, you must configure the server to use the MIME type application/octet-stream for files with a .cfg extension.
To access a computer with the remote agent installed you must ensure that the DriveLock administration console is installed on the management computer. On the remote computer DriveLock must be installed and running. Ensure that the permissions that the remote control permissions in the Global settings dialog dialog box allow access. If you change these permissions, restart the remote computer for these changes to take effect. If a firewall is located between the management computer and the remote computer, ensure that the firewall is configured to allow DriveLock traffic to pass through it.
To ensure proper proper operations, ensure that locking for the device class that the hardware belongs to has been activated If you recently made changes to these settings, restart the computer. The device driver that controls all device activities is loaded when the computer starts or when a device is first connected to the computer. Next, check the White List entries to ensure that the specific device is allowed. If the White List settings are correct, disconnect and then reconnect the device to allow the computer to detect the device again. If the disconnecting and reconnecting the device fixes the problem, the Restart devices if logged on user changes option may not be selected.
While DriveLock is optimized for a network that is based on Windows Active Directory, many other network environments, such as Novell NetWare, are supported. The DriveLock manual contains detailed information about this in the chapter Support of other network operating systems.
A full installation of DriveLock copies all required files to the computer’s hard disk. By default, the installation folder is C:\Program Files\Centertools\DriveLock. This includes the .msi file for a client installation. You can also download the installation file and other components from the www.centertools.com Web site. You can find further installation and upgrade instructions in the DriveLock Release Notes.
To ensure that the licenses are applied to the correct computer accounts, efine a computer list containing the computers that you want to control with DriveLock. You can find detailed instructions for defining such a list in the DriveLock manual in the chapter Problems with import of license file.
You may have registered only the DLL for the DriveLock administration console. To ensure proper operations, install DriveLock using the regular installation procedure. If you only need the DriveLock administration console, use the .msi file that is provided for this purpose.
Startup problems may occur when the service has problems reading the license data. try to start the service manually. If it stops immediately and the Windows Event Viewer shows that an event was logged that indicates that the icence nformation is invalid, contact CenterTools DriveLock technical support.
Access to the drive may have been explicit denied via a drive white-list rule. DriveLock doesn’t unlock devices that are covered by such a rule.
If DriveLock is configured locally, the registry keys are located under:HKEY_Local_Machine/Software/CenterTools/DriveLock.If DriveLock is configured via Group Policy, the registry keys are located under:HKEY_Local_Machine/Software/Policies/CenterTools/DriveLock
Most problems related Group Policy can be solved using standard Group Policy troubleshooting mechanisms. One common problem is related to Active Directory replication. If your network contains multiple domain controllers you have to allow enough time for replication to complete before Group Policy is applied correctly across the network. Replication can take from a few minutes to several hours, based on your Active Directory configuration. In addition, computers have to retrieve the most recent version of a Group Policy from a domain controller. By default the refresh operation occurs immediately, but you can force Windows to perform this operation immediately by entering one of the following commands:secedit /refreshpolicy machine_policy /enforce (Windows 2000)orgpupdate /force (Windows XP)
Group Policy settings have a higher priority than locally configured settings and override these any settings. However, in some cases you may require local exceptions to a Group Policy. For example, if you want to allow a device only on one specific computer you have to configure the white list on the local computer. To ensure that these local white list settings are not removed by a Group Policy, you must configure DriveLock to merge the drive exception list settings. To configure merging of drive exception lists, in the Group Policy, under Drives, click Settings, and then double-click "Merge drive exception lists." In the "Merge drive exception lists Properties" dialog box, select "Enable". To ensure proper operations, also confirm that all relevant settings are configured in the Group Policy and that no options are set as "Unconfigured". Configuring the options in Group Policy is necessary because DriveLock only merges the local settings for which the Group Policy also contains an entry.
A full installation of DriveLock copies all required files to the computer’s hard disk. By default, the installation folder is C:\Program Files\CenterTools\DriveLock. This includes the .msi file for a client installation. You can also download the installation file and other components from the www.centertools.com Web site. You can find further installation and upgrade instructions in the DriveLock Release Notes.