Release Notes 7.9 - DriveLock Online Help · 2019. 7. 30. · Title: Release Notes 7.9.6 Created...

© 2019 DriveLock SE

Release Notes 7.9.6

2Release Notes 7.9.6 © 2019 DriveLock SE

Release Notes

Table of Contents

Part I Introduction 3

31 Document Conventions

32 DriveLock Documentation

Part II System Requirements 5

51 DriveLock Agent

52 DriveLock Management Console and Control Center

53 DriveLock Enterprise Service

Part III Supported Platforms 7

Part IV Version History 9

91 DriveLock 7.9.6

102 DriveLock 7.9.4

103 DriveLock 7.9.2

Part V Known Issues 12

121 Quickstart Setup Wizard

122 Installation of Management Components Using Group Policy

123 DriveLock Device Scanner

134 Manual Updates

135 Self Service unlock

136 DriveLock iOS and iTunes

137 Windows Portable Devices (WPD)

138 DriveLock Disk Protection

159 DriveLock File Protection and Microsoft OneDrive

1510 BitLocker Management

1611 Antivirus

Part VI Test Installation and Upgrade 17

171 DriveLock Evaluation

172 Updating DriveLock Components

17General Issues

17Updating DriveLock Disk Protection

Introduction

© 2019 DriveLock SERelease Notes 7.9.6 3

1 Introduction

This document contains important information about the new version of DriveLock and changes from previous

DriveLock versions. The DriveLock Release Notes also describes changes and additions to DriveLock that were made

after the documentation was completed.

This and other documentation can be found on our online help page www.drivelock.help.

1.1 Document Conventions

Throughout this document the following conventions and symbols are used to emphasize important points that you

should read carefully, or menus, items or buttons that you need to click or select.

Caution: This format means that you should be careful to avoid unwanted results, such as

potential damage to operating system functionality or loss of data

Hint: Useful additional information that might help you save time.

Italics represent fields, menu commands, and cross-references. Bold type represents a button that you need to click.

A fixed-width typeface represents messages or commands typed at a command prompt.

A plus sign between two keyboard keys means that you must press those keys at the same time. For example, ALT+R

means that you must hold down the ALT key while you press R. A comma between two or more keys means that you

must press them consecutively. For example ‘ALT, R, U’ means that you must first press the Alt key, then the R key, and

finally the U key.

1.2 DriveLock Documentation

The DriveLock Documentation consists of the following manuals:

· DriveLock QuickStart Guide

The QuickStart Guide describes the required steps to setup DriveLock using the DriveLock QuickStart setup

wizard.The DriveLock QuickStart setup wizard can be used to simplify the installation and configuration of a

basic DriveLock environment.

· DriveLock Installation Guide

The Installation Guide describes the available installation packages, the system requirements and the steps

for install ing each DriveLock component. This is the first document a DriveLock administrator should read.

· DriveLock Administration Guide

The Administration Guide describes the DriveLock architecture and components. It contains detailed

instructions for configuring DriveLock using the DriveLock Management Console (DMC). This document is

intended for DriveLock administrators who need to become familiar with all available DriveLock

functionality.

· DriveLock Control Center User Guide

This manual describes how to configure and use the DriveLock Control Center (DCC). This document is

intended for administrators and users who will use DriveLock Control Center for reporting and forensic

analysis.

· DriveLock User Guide

The DriveLock User Guide is aimed at end users. It describes how to request the temporary unlocking of a

computer, how to use DriveLock Encryption 2-Go and how to use Network Profiles.

http://www.drivelock.help

Introduction


· DriveLock Security Awareness

This manual describes the new security awareness features, which are also included in DriveLock Smart

SecurityEducation.

You can read and download the latest version of these manuals from our online help website www.drivelock.help.


Introduction


2 System Requirements

This section contains recommendations and minimum requirements. The requirements may vary depending on your

configuration of DriveLock, its components and features, and your system environment.

2.1 DriveLock Agent

Before distributing or install ing the DriveLock agents on your corporate network, please ensure that the computers

meet these requirements and are configured properly to provide full functionality.

Main memory:

o at least 4 GB RAM

Free disk space:

o approx. 1 GB with average policies that do not include your own video fi les

o at least 2 GB if Security Awareness campaigns are used with video sequences (Security Awareness Content

AddOn)

How much disk space you need largely depends on how DriveLock agents are configured via policies and on the

settings and features they contain. It is therefore difficult to provide an exact specification here. We

recommend that you verify and determine the exact value in a test setup with a limited number of systems

before performing a company-wide roll-out.

Additional Windows components:

o .NET Framework 4.5.2 or newer (for Security Awareness Campaigns in general)

o Windows Media Player (for Security Awareness Content AddOn)

2.2 DriveLock Management Console and Control Center

Be sure to install the two management components on the same computer because the DCC will access some of the

dialogs provided by the DriveLock Management Console.

Before distributing or install ing the DriveLock management components DMC and DCC on your corporate network,

please ensure that the computers meet these requirements and are configured properly to provide full functionality.

Main memory:

o at least 4 GB RAM

Free disk space:

o approx.350 MB


o .NET Framework 4.5.2 or newer

2.3 DriveLock Enterprise Service

Before distributing or install ing the DriveLock Enterprise Service on your corporate network, please ensure that the

computers meet these requirements and are configured properly to provide full functionality.

Main memory:

o at least 8 GB RAM

Free disk space:

System Requirements


o at least 4 GB, with policies that do include Security Awareness campaigns with video sequences (Security

Awareness Content AddOn), approx. 15 GB is recommended

o if the server is also running the SQL-Server database, additional 10 GB are recommended for storing DriveLock

data


o .NET Framework 4.5.2 or newer

Depending on the number and duration of the DriveLock events that are stored, the size of the DriveLock

database can vary greatly from one system environment to another. It is therefore difficult to provide an exact

specification here. We recommend setting up a test environment with the planned settings over a period of at

least a few days to determine the exact values. These values can be used to calculate the required memory

capacity.

System Requirements


3 Supported Platforms

DriveLock has been tested and is released for all Windows versions (having the latest available patches installed),

which have been official released by Microsoft by the time this DriveLock version was released and which have not

reached their end-of-service date:

Operating System

Windows 1)XP 3) W7 SP12)

W8.1

OS X10.9+

Win-101607

Win-101703/1709

Win-10 1803/

18094)

Server 2008 SP22008R2

SP1

Server 2012

20012R2

Server2016

Agent (DC/AC)

Device Control x x x x x x x x

Application Control x x x x x x x x

File encryption

Mobile EncryptionApplication

x x x x x x x x

File Protection6) x x x x x x x x

Disk encryption

Disk Protection x13) x 7) x 7) x 7) x 7)

BitLockerManagement

x8) x x x

Management components

ManagementConsole

x x x x x x x

Control Center9) x x x x x x x

Enterprise Server x12) x12) x12) x12) x x x

DriveLockVirtual Channel

IGELUDLX

4.12.100+

WYSELinux V6

Embedded

Windows10)

eLux Thin-

Clients

ICA x x x x

RDP x x x

DriveLock Thin-Client Support

ICA (Citrix) XenApp6.0

XenApp

6.511)XenApp

7.X

RDP (Windows TS) 2008R2SP1

201220012R2

2016

Supported Platforms


Database

Microsoft SQL

Server5) 2008

SP42008R2

SP3

2012/2014 SP2

2016 SP22017

Oracle Database14) 11.2 12.2

Remarks

1) Windows Intel X86 based Systems (x86_32, x86_64, AMD64)

Windows Vista and Windows 8 are not supported any more.

2) Windows 7 SP1 KB3033929 (SHA-2 code signing support) is required on Windows 7 64-bit.

3) Windows XP Windows XP with SP3 fully patched and POSReady 2009 is supported.An additional l icense for support of legacy OS is required!

4) Windows 10-1809

Release 7.9.6 has been tested with Windows 10-1809.

5) Microsoft SQLExpress

For installations up to 200 Clients.

6) File Protection Citrix Terminal Servers are not supported.

7) Disk Protection UEFI and GPT Partitioning are only supported for disks up to 2 TB running on Windows 8.1 64bit or newer and UEFI Version V2.3.1 or newer.UEFI on Windows 7 is not supported.For UEFI running on Windows 10 Version 1703 the Update KB4032188 is mandatory.DriveLock Disk Protection is supported on Windows 10 version 1709 or newer with somelimitations (see chapter "Known issues" for more information).

8) BitLocker Windows 7 32-bit is not supported in DriveLock. For more information see "Known issues ->BitLocker Management"

9) Control Center Internet Explorer 11 is required for remote connections to an DriveLock Agent.

10) WindowsEmbedded

Der DriveLock Virtual Channel and the DriveLock Agent must not be installed on the same Client.

11) XenApp XenApp 6.5 Hotfix Roll Up 4 or newer.

12) DES On these operating systems DES should only be installed for evaluation or testing purposes.

13) FDE and XP DriveLock Disk Protection is supported only on Windows XP released for ATMs.

14) Oracle Support We stil l provide support for existing customers. We strongly recommend new customers to useSQL Server instead of Oracle Database.

Supported Platforms


4 Version History

The version history contains all changes and innovations since the last major release, DriveLock Version 7.8.

4.1 DriveLock 7.9.6

DriveLock 7.9.6 is a maintenance release

Important Bug Fixes:

General:

· The interface control is now activated correctly when the Citrix Receiver switches the virtual channel from

"Optimized" to "Generic".

· To run application control correctly, you no longer need to restart the DriveLock agent after having unlocked

and stopped it manually when rebooting the computer via agent remote control.

· Drive l ist rules are no longer applied directly to encrypted containers on an external drive.

· If you configured a DriveLock agent with a configuration fi le, then it will now use the cached last

configuration to access the original configuration fi le via a web server in case connection problems occur.

· We improved the compatibil ity between the DriveLock interface control and BitDefender Endpoint Security

(product version 6.6.5.82 and older and engine version 7.77528 and older).

· Block access to USB media on locked drives is also prevented even if the user has the right to format the drive.

· The status of an agent during agent remote control is displayed correctly again in the DMC after updating

from 7.7.14 to the latest DriveLock version.

· File fi lter will be applied correctly to an encrypted container, when drive connection has changed.

· Even when a connection is changed, fi le fi lters are stil l correctly applied to encrypted containers.

· Placing a policy assignment at the top of the l ist will no longer freeze the DMC.

· When you upgrade to version 7.9, any existing DriveLock AV service will now be completely uninstalled.

· The drive rules for USB drives connected to thin clients via the new Citrix "Generic Virtual Channel" are now

correctly applied.

· The current baramundi Agent is correctly recognized as a Trusted Installer again if it has been configured

accordingly.

BitLocker Management:

· Now the user is always prompted to change the BitLocker password, if the administrator requests this

password change via the DCC.

· Users are now not prompted to change their BitLocker password if a central password has been assigned by

an administrator.

· Before install ing BitLocker encryption, the system verifies whether a previous encryption with Disk Protection

has been completely decrypted and uninstalled.

· You can now use a l icense that contains both BitLocker Management and Disk Protection.

· On systems that have an additional encrypted data partition, only one dialog appears during recovery for

resetting the password.

Version History


· We deactivated the option in the DMC that allowed you to store recovery keys in the fi le system; it was not

used.

· Drives will no longer be decrypted if the Agent is assigned a policy completely without BitLocker l icense and

settings.

· DriveLock BitLocker Management now correctly recognizes and treats external drives as such.

· After uninstall ing, the original BitLocker menu entries are displayed again completely.

Disk Protection:

· The PBA of the DriveLock FDE is correctly initialized on HP notebooks, where "Fast Boot" is already enabled in

the UEFI settings.

· The bug that led to a blue screen on an HP Elite Desk 800 G3 Desktop Mini PC in combination with the 32bit

PBA was fixed.

· The PBA for BIOS (32bit PBA) and UEFI now also supports the following tokens: SafeNet eToken NG-OPT

(CardOS), SafeNet eToken NG-OPT 72k/Java, SafeNet eToken 5105, SafeNet eToken 5110.

· Existing Windows system settings (SSO, Fast Startup, BitLocker Extensions) are optimized while install ing Disk

Protection.

· On some Lenovo systems, keyboard layout is now available in a number of languages other than English.

· Improvements when uninstall ing Disk Protection.

File Protection:

· When you use File Protection to force encryption of USB media, Windows Explorer no longer freezes for

several seconds.

· We fixed the issue with a missing signature in the DLFldEnc.sys fi le.

4.2 DriveLock 7.9.4

DriveLock 7.9.4 is a maintenance release


· The DriveLock Agent correctly recognizes serial numbers in whitelist rules , if the policy has been created with

a DriveLock version older than 7.8.4.

4.3 DriveLock 7.9.2

DriveLock 7.9.2 is a feature release

New features:

This version allows you to manage disk encryption with Microsoft BitLocker across your company now for the first

time. As our customer you benefit from an additional range of advanced features when compared to the native

BitLocker encryption:

· Automated unlocking of encrypted extended partitions

· Centralized and secure managing of recovery information (recovery keys)

· Detailed reporting and central Helpdesk capabilities

· Passwords assigned centrally

Version History


· DriveLock BitLocker Management creates new recovery keys automatically after recovering them successfully,

which makes the old recovery key invalid to prevent it from being used multiple times

The configuration uses the established DriveLock policies. You do not need a new installation to activate this

functionality, the features are included in the update of version 7.9 and can easily be activated with a BitLocker

Management l icense.

Additional Improvements:

· Some minor fixes for managing drive categories

· The header of a usage policy now shows the triggering drive or device


· Routing works better now when unlocking agents remotely via self-service and DCC if the agents communicate

with a l inked DES

· The certificate wizard no longer overwrites an existing encryption certificate with a certificate of the same

name without notifying the user

· If an application is blocked, you will now see the properly configured custom user message

· The agent deletes security awareness content packages that are no longer used or required in rules

· The only time that events are considered duplicates within a time period is when both the ID and all

parameters are completely identical

· Policy settings are copied correctly from a template even if this template was already used as a template and

was changed later.

· All communication between the agent and the DES now requires at least TLS1.0, all older and less secure

protocols are disabled

· Usage policies are correctly displayed for SD card readers even after restart and login

Version History


5 Known Issues

This chapter contains known issues for this version of DriveLock. Familiarize yourself with the information in this

chapter to avoid unnecessary effort during testing and deployment.

5.1 Quickstart Setup Wizard

If you install DriveLock the first time using the Quickstart Wizard, you might see an error message at the last step

after creating a default company policy. You can close this message and stop the wizard, the policy will be available

in the DriveLock Management Console.

If you want to assign this policy to your DriveLock agents, open the DriveLock Management Console and assign this

policy manually:

Click "All computers assignment" and select the "Default Company Policy".

5.2 Installation of Management Components Using Group Policy

Install ing the DriveLock Management Console, the DriveLock Control Center or the DriveLock Enterprise Service by

using Group Policy is not possible. Instead, use the DriveLock Installer to install these components as described in

the Installation Guide.

5.3 DriveLock Device Scanner

Use the Device Scanner integrated in the product in all environments where only the standard client "Root" has been

set up. This applies to most customer installations. If you have a multi-client environment, you will receive an error

message when viewing and saving the scan results.

Known Issues


5.4 Manual Updates

If other policy deployment than GPO is used, on Windows 8 and higher, a manual update of the DriveLock Agent will

not finish properly, if you start the DriveLock Agent.msi from the Windows Explorer (e.g. by double clicking).

Run the MSI-package from an administrative command window with msiexec or use DLSetup.exe.

5.5 Self Service unlock

Self Service unlock and Apple iPhones

If you use the Self Service wizard to unlock connected iPhone devices, it will sti l l be possible to copy pictures

manually from the connected iPhone after the unlock period ended.

5.6 DriveLock iOS and iTunes

DriveLock recognizes and controls current generation Apple devices (iPod Touch, iPhone, iPad etc.) For older Apple

devices that are only recognized as USB drives no granular control of data transfers is available (for example, iPod

Nano).

DriveLock and iTunes use similar multicast DNS responders for automatic device discovery in networks. When

install ing both DriveLock and iTunes the installation order is important:

· If DriveLock has not been installed yet you can install iTunes at any time. DriveLock can be installed at any

later time without any special considerations.

· If DriveLock is already installed on a computer and you later install iTunes you have to run the following

command on the computer before you start the iTunes installation: drivelock -stopdnssd. Without

this step the iTunes installation will fail.

After an update of the iOS operating system on a device, iTunes will automatically start a full synchronization

between the computer and the device. This synchronization will fail if DriveLock is configured to block any of the

data being synchronized (photos, music, etc.).

5.7 Windows Portable Devices (WPD)

Locking “Portable devices” prevented, that some Windows Mobile Devices could be synchronized via "Windows

Mobile Device Center", although the special device was released in a whitelist.

Windows starting from Windows Vista and later uses a new "User-mode Driver Framework" for this kind of devices.

DriveLock now includes this type of driver. The driver is deactivated on the following systems because of a

malfunction in the Microsoft operating system:

· Windows 8

· Windows 8.1 without Hotfix KB3082808

· Windows 10 older than version 1607

5.8 DriveLock Disk Protection

Antivirus protection software may cause the DriveLock Disk Protection installation to fail if the antivirus software

quarantines fi les in the C:\SECURDSK folder. If this occurs please disable your antivirus protection for the duration

of the Disk Protection installation and re-enable it after the installation is completed. We recommend that you

configure your virus scanner with an exception for the C:\SECURDSK folder.

When Install ing DriveLock Disk Protection we strongly recommend that you deactivate the application control if they

are active in the whitelist modus. This will prevent the blocking of programs that are necessary for the installation.

Known Issues


On a small number of computer models the default DriveLock Disk Protection pre-boot environment configuration

may not work correctly and cause the computer to become unresponsive. If this occurs turn off the computer and

restart it while pressing the [Shift] key. When prompted select the option to use the 16-bit pre-boot operating

environment.

Hibernation will not work while a disk is encrypted or decrypted. After complete encryption or decryption windows

has to be restarted once to make hibernate work again.

UEFI mode

Not all hardware vendors implement the complete UEFI functionality. We recommend not to use the UEFI mode

with UEFI versions less than 2.3.1.

The full functionality of the Pre-Boot-Authentication (PBA) for UEFI is not yet available as for BIOS.

· Touchscreen is not supported. A hardware keyboard (USB or PS/2) is required.

· Mouse operation is not yet supported.

· Some PS/2 keyboards may work improperly.

· The PBA GUI is only available in English.

Additional topics:

· Secure Boot must be deactivated up to version 7.6.4. DriveLock 7.6.6 and higher supports UEFI secure boot.

· If you update the firmware, the NVRAM variables on the mainboard that DriveLock requires may be deleted.

We strongly recommend that you install the firmware updates for the mainboard /UEFI before install ing

DriveLock PBA / FDE ( this also applies to recently purchased devices or to bug fixes).

· A 32 bit Windows operating system or 32 bit DriveLock cannot be installed on 64 bit capable hardware.

Please use a 64 bit version of a Windows operating system and DriveLock instead.

· There is sti l l a l imitation to disks up to a maximum of 2 TB disk size.

· On some HP PCs Windows always will be set to position one again in the UEFI boot order and the DriveLock

PBA has to be selected manually from the UEFI boot menu. In this case fast boot has to be switched off in UEFI

to keep the DriveLock PBA at position one.

· Windows 10 Version 1703 (Creators Update) can remove the DriveLock boot entry from the UEFI boot menu

while shutting down or when hibernating. Therefore the DriveLock PBA will no longer boot at the next startup

and Windows cannot boot from the encrypted system hard disk. In August 2017 Microsoft released Update

KB4032188 which resolves this issue. Update KB4032188 will be installed automatically by Windows or can

be downloaded manually.

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4032188

Check if update KB4032188 or any later update that replaces KB4032188 is installed before you install

DriveLock Disk Protection for UEFI.

When upgrading to Windows 10 Version 1703 where DriveLock Disk Protection for UEFI is already installed,

add update KB4032188 to the Creators Update before you upgrade.

· Due to an issue in Windows 10 Version 1709 and newer, DriveLock Disk Protection for BIOS cannot identify

the correct disk if more than one hard disk is connected to the system. Therefore Disk Protection for BIOS is

not yet released for Windows 10 1709 systems with more than one hard disk attached until Microsoft

provides a fix for this issue.

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4032188

Known Issues


5.9 DriveLock File Protection and Microsoft OneDrive

Microsoft OneDrive

With Microsoft OneDrive, Microsoft Office may synchronize directly with OneDrive instead of writing the fi le to the

local folder first. Then the DriveLock encryption driver is not involved and the Office fi les will not be encrypted in the

Cloud. To switch off the Office synchronization, uncheck Use Office 2016 to sync Office files that I open or similar

settings in OneDrive. It must be assured, that Office fi les as other fi les always are stored locally.

NetApp

We currently investigate an incompatibil ity between the DriveLock encryption fi le fi lter and NetApp SAN solutions.

Before using File Protection in such system environment, please check and test the required functionality.

5.10 BitLocker Management

Supported Windows editions and versions

DriveLock BitLocker Management is supported on:

§ Windows 7 SP1 Enterprise and Ultimate, 64-Bit, TPM-Chip is required

§ Windows 8.1 Pro and Enterprise, 32/64-bit

§ Windows 10 Pro and Enterprise, 32/64-bit

Your environment already includes BitLocker encrypted computers

To manage an existing system environment that already includes computers encrypted with BitLocker, make

sure to decrypt them beforehand using the existing BitLocker Management or Group Policy.

After that, you can use DriveLock BitLocker Management to manage your computers and securely store and util ize the

recovery information.

Upcoming DriveLock versions are expected to support management of systems that have already been encrypted

with BitLocker without prior decryption.

Password complexity requirements

With DriveLock BitLocker Management, the misleading differentiation between PINs, passphrases and passwords is

simplified by using only the term "password". In addition, this password is automatically applied in the correct

BitLocker format, either as a PIN or as a passphrase.

Due to the fact that Microsoft has different requirements for the complexity of PIN and passphrase, the following

restrictions apply to the password::

§ minimum: 8 characters

§ maximum: 20 characters

Encrypting extended disks

By mistake, the user note that appears when encrypting the hard disks indicates that only the system partition C: is

encrypted, even though other drives are also encrypted if configured accordingly.

Microsoft BitLocker l imitations prevent external hard drives (data disks) from being encrypted if you have selected

"TPM only (no password)" mode, because BitLocker expects you to enter a password (so called BitLocker passphrase)

for these extended drives.

Known Issues


Group policy configuration

Because of a technical restriction, you cannot set computer-specific passwords via the DriveLock Control Center if

you have distributed the DriveLock BitLocker configuration to the agents via group policies. In this case, the

DriveLock 7.9 agent ignores the necessary computer-specific policies.

5.11 Antivirus

Antivirus generally

Since DriveLock 7.8, the on-demand scanner (Cyren) will not be included any more. Customers with a valid Avira

license/subscription can use the Avira scanner to scan external drives, until the subscription terminates.

Avira Antivirus

Since DriveLock 7.9 Avira is no longer supported.

Known Issues


6 Test Installation and Upgrade

6.1 DriveLock Evaluation

You can install the DriveLock - the Agent, the Management Console, the Control Center, the Enterprise Service and

Microsoft SQL Express - on the same computer. This topology makes it easy to evaluate DriveLock’s central reporting

features using minimal hardware.

On our website www.drivelock.help you can find a Quick Start Guide that guides you through the initial installation.

This guide also shows you how to create a test installation and set up the initial configuration with the help of the

Quick Start Wizard.

If you downloaded the DriveLock software from the Web site (www.drivelock.com), a 30-day trial l icense is

included. To evaluate DriveLock on a single computer, you don’t need to perform any license configuration. If

you install the DriveLock Agent on multiple client computers and configure DriveLock settings using Microsoft

Group Policy, a Centrally Stored Policy or a configuration fi le or if you want to tests the Disk Protection too,

you have to add a l icense key to the configuration. You can use the evaluation license key that is installed with

DriveLock Management Console (by default, C:\Program Files\CenterTools\DriveLock MMC\Tools\AgentTrial.lic).

When using the quick start wizard, this l icense is imported in the generated policy automatically.

6.2 Updating DriveLock Components

6.2.1 General Issues

The DriveLock Installation Guide describes all necessary steps required to update the components. In addition

theses release notes may contain additional information.

The DMC and the DCC will be installed in separate directories to avoid side effects when updating these components

automatically.

The DriveLock Control Center uses some components of the DriveLock Management Console for remote

maintenance. Both components must each have the same version number, which must also match the version

of the installed DES.

6.2.2 Updating DriveLock Disk Protection

After the DriveLock Agent has been updated, an existing DriveLock FDE installation will be updated automatically and

without re-encryption to the most current version. After updating the FDE components, a reboot may be required.

For further information on updating DriveLock Disk Protection or updating the operating system where DriveLock

Disk Protection is already installed, see our separate document available for download from our website

www.drivelock.help.


© 2019 DriveLock SE

Information in this document, including URL and other InternetWeb site references, is subject to change without notice. Unlessotherwise noted, the example companies, organizations, products,domain names, e-mail addresses, logos, people, places, andevents depicted herein are fictitious, and no association with anyreal company, organization, product, domain name, e-mailaddress, logo, person, place, or event is intended or should beinferred. Complying with all applicable copyright laws is theresponsibility of the user.DriveLock and others are either registered trademarks ortrademarks of DriveLock SE or its subsidiaries in the United Statesand/or other countries.The names of actual companies and products mentioned hereinmay be the trademarks of their respective owners.

Die in diesen Unterlagen enthaltenen Angaben und Daten,einschließlich URLs und anderen Verweisen auf Internetwebsites,können ohne vorherige Ankündigung geändert werden. Die in denBeispielen verwendeten Firmen, Organisationen, Produkte,Personen und Ereignisse sind frei erfunden. Jede Ähnlichkeit mitbestehenden Firmen, Organisationen, Produkten, Personen oderEreignissen ist rein zufällig. Die Verantwortung für die Beachtungaller geltenden Urheberrechte liegt allein beim Benutzer.Unabhängig von der Anwendbarkeit der entsprechendenUrheberrechtsgesetze darf ohne ausdrückliche schriftlicheErlaubnis der DriveLock SE kein Teil dieser Unterlagen fürirgendwelche Zwecke vervielfältigt oder übertragen werden,unabhängig davon, auf welche Art und Weise oder mit welchenMitteln, elektronisch oder mechanisch, dies geschieht.Es ist möglich, dass DriveLock SE Rechte an Patenten bzw.angemeldeten Patenten, an Marken, Urheberrechten odersonstigem geistigen Eigentum besitzt, die sich auf den fachlichenInhalt dieses Dokuments beziehen. Das Bereitstellen diesesDokuments gibt Ihnen jedoch keinen Anspruch auf diese Patente,Marken, Urheberrechte oder auf sonstiges geistiges Eigentum, essei denn, dies wird ausdrücklich in den schriftlichenLizenzverträgen von DriveLock SE eingeräumt.Weitere in diesem Dokument aufgeführte tatsächliche Produkt-und Firmennamen können geschützte Marken ihrer jeweiligenInhaber sein.

Release Notes

Date post:	11-Oct-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

Release Notes 7.9 - DriveLock Online Help · 2019. 7. 30. · Title: Release Notes 7.9.6 Created...

Documents