Version history for DeviceLock shows you how often it was updated over the past months (starting May 06, 2005) as well as 'what is new' information for each update (if available, since this information provided by the author).
v 6.2.1 updated on Jan 07, 2008
1. Added support for Microsoft Windows Vista; 2. Added integration with TrueCrypt; 3. Added real-time monitoring of DeviceLock Services across the network; 4. Now in DeviceLock management consoles it is possible to create a custom MSI package for DeviceLock Service
v 6.2 updated on Sep 19, 2007
1. Added granular access control, auditing and shadowing for Windows Mobile devices; 2. Added integration with PGP Whole Disk Encryption.
v 6.1.1 updated on Apr 26, 2007
1. DeviceLock Service now works on 64-bit platforms (Windows XP/2003); 2. Changes in the remote installation routine. Management consoles can now install DeviceLock Service to 64-bit platforms; 3. Added the new MSI package with 64-bit DeviceLock Service.
v 6.0 updated on Aug 31, 2006
1. DeviceLock now supports data shadowing - the ability to mirror all data copied to external storage devices (Removable and Floppy) and transferred via COM and LPT ports. A full copy of the files and data is saved. Shadowing is an extended function of DeviceLock Audit and like auditing can be defined on a per-user basis. 2. Added support for the Media White List feature. Media White List allows you to uniquely identify a specific DVD/CD-ROM disk by the data signature and authorize access to it, even when DeviceLock has otherwise blocked the DVD/CD-ROM drive. Any change to the content of the media will change the data signature, thus invalidating authorization. In this way, a white-listed disk cannot be used to introduce unwanted data to the network. A DeviceLock Media White List can be configured to grant access to a collection of approved DVD/CD-ROM disks by certain users and groups, so that only authorized users are able to use the approved information. 3. Added DeviceLock Enterprise Server for centralized collecting and storing of shadow files. DeviceLock Enterprise Server uses MS SQL Server to store received data.
v 5.73 updated on Dec 28, 2005
Devices in the USB White List can now be assigned to users and groups. This allows you to have more granular control over which users have access to what USB devices on their computers. One user can be allowed to use a certain device, while another user can't use it on the same computer.
v 5.72 updated on Nov 03, 2005
1. A new function, Temporary White List, has been added. Useful in exceptional situations, this function grants users temporary access to USB devices when there is no network connection. In use, DeviceLock administrators provide users with special access codes over the phone. These codes will unlock DeviceLock and enable temporary access to requested devices. Two new administration tools have also been added to support this function: "Temporary White List Administration Tool" and "Certificate Generation Tool". Also, the Control Panel applet "Temporary White List Authorization Tool" installs on computers running DeviceLock Service. 2. Now you can define a discrete list of accounts that are able to administer (install, uninstall, modify permissions and other settings, etc.) DeviceLock. Even users with local administrator privileges can't disable DeviceLock Service or remove it from their computers, if they are not in this list of DeviceLock administrators. 3. The USB White List now supports devices with unique serial numbers, so you can now allow access to a unique device and lock out all others, as long as the device vendor assigns serial numbers to its products individually. 4. You can now define a custom message to be displayed to users when a denied attempt is made to plug in a USB or FireWire device. 5. In DeviceLock Enterprise Manager you can now browse the LDAP tree and select computers for processing directly from directory services (such as MS Active Directory, Novell eDirectory, Open LDAP, etc.). 6. The new interface for DeviceLock Group Policy Manager. Now it allows you to set parameters to the "not configured" state. 7. Added the "Set Default" button on the "Audit" dialog. It allows you to add predefined accounts (Everyone and Users) to the auditing list. 8. There is now the option to "Enable access control for FireWire storage devices" for situations when you want to lock all non-storage FireWire devices on the port level and control access to storage devices on the Removable type level. 9. Using the context menu, you can add devices to the USB White List from the plug-in window "Report PnP Devices".
v 5.71 updated on May 06, 2005
1. Added the new function - Auditing. DeviceLock can audit user's activity for a particular device type. This capability allows you to audit activities that belong to a certain user or user group. DeviceLock employs the standard event logging subsystem and writes audit records to the Windows event log so they can be read using any event viewer software (such as EventViewer) as well as with DeviceLock's built-in Audit Log Viewer. 2. The new management tool is added. DeviceLock Enterprise Manager is a new generation of the "Batch Permissions" function available in DeviceLock Manager. Based on the multithreaded engine, it speeds up all activity - including installation/uninstallation of DeviceLock Service, setting permissions and reporting permissions - making it one of the most powerful management systems for large networks. 3. Now you can control DeviceLock via Group Policy in an Active Directory domain. DeviceLock Group Policy Manager allows you to manage DeviceLock settings and permissions via Group Policy as an alternative to installing DeviceLock Manager on the server. You can deploy DeviceLock Service and its settings to the entire network using standard policy management tools because Group Policy is a built-in mechanism of Active Directory. DeviceLock Group Policy Manager ships as a separate tool so you need to obtain it from our website. 4. The read-only access type can be set directly for USB and FireWire ports. However, it affects storage devices only. 5. Now you can instruct DeviceLock to use a fixed TCP port for the RPC communication between DeviceLock Service and DeviceLock Manager, making it easier to configure a firewall.
Go back to the DeviceLock review