eset - installation guide · installation guide- eset drivesecurity for safeconsoleready devices...

ESET - Installation GuideESET DriveSecurity for SafeConsoleReady Devices

Last updated July 2017

Installation guide- ESET DriveSecurity for SafeConsoleReady Devices Version 1.1

1

Table of Contents

Introduction

Prerequisites

What is ESET DriveSecurity?

Using DriveSecurity with SafeConsole

Trialing DriveSecurity

Purchasing and Activating Licenses for Devices

Installing DriveSecurity through SafeConsole

Updating DriveSecurity through SafeConsole

Deactivating/Uninstalling DriveSecurity through SafeConsole

1

1

1

2

3

3

3 - 8

9

10


2

Introduction This guide will provide instructions on how to utilize the SafeConsole features Publisher and Authorized Autorun to install the ESET DriveSecurity antivirus onto SafeConsoleReady devices such as Sentry 3.0, Sentry 3 FIPS and DataLocker DL3.This guide can be completed in 15 minutes.

Prerequisites • One or more SafeConsoleReady Devices (4.8.x) managed by SafeConsole (5.x)• Admin access to SafeConsole to change policies.• Ability to set up a network share. • The devices need to be able to connect to the network share for the device software to

download contents onto the devices.• DriveSecurity runs on any Windows 7, Windows Vista® or Windows XP computer.• DriveSecurity needs approximately 100MB of space on the flash drive.

What is ESET DriveSecurity? ESET DriveSecurity is a portable drive-based antimalware that keeps threats from spreading between computers. This means that any files you place on your USB drive are malware-free and safe to share with others. It’s easy, with no need to install anything on a host computer – DriveSecurity operates from the USB drive itself for speed and convenience.

DriveSecurity™ powered by ESET is based on the ClevX DriveSecurity technology licensed from ClevX, LLC.


3

• Using SafeConsole the DriveSecurity is deployed and runs automatically on each unlock of the SafeConsoleReady Device.

• DriveSecurity automatically performs scans in the background.

• DriveSecurity automatically scans any new content that is added during the session.

• DriveSecurity can also be invoked by the user to scan the device at any time.

• The user can utilize their device like they would normally and can unplug the device without closing the DriveSecurity application before locking or unplugging the device.

• If a file is found to be infected it will be de-leted and you will see an alert.

• DriveSecurity will not interfere with the host computer’s own on-board AV (if installed).

• Heuristic antivirus capabilities enable Dri-veSecurity to provide effective virus pro-tection even against unknown threats and without up-to-date signatures.

• DriveSecurity deployed with Publisher will be automatically whitelisted against any ac-tive file restriction policy set in SafeConsole.

• The DriveSecurity will automatically and independent of SafeConsole download the latest virus definition from ESET over the Internet as they come available.

Using DriveSecurity with SafeConsole


Trialing DriveSecurity • DriveSecurity is licensed per device based on the Device IDs (serial numbers).• Each device reports over the Internet to the Clevx/ESET central licensing system for the

activation of a license based on the device serial number.• The first time the DriveSecurity starts it activates a free 30-day trial period with full protec-

tion for the device. No further action is needed.• Get started by proceeding with the section - Installing DriveSecurity through SafeConsole.

Purchasing and Activating Licenses for Devices • Each device that is connected to SafeConsole is registered with the device serial number

and the device user. All devices that have had DriveSecurity installed through SafeConsole are therefore registered in the central management.

• By providing DataLocker a list of the device serial numbers that require DriveSecurity they will become licensed.

• Under Devices in SafeConsole you can easily export the list of Device IDs (serial numbers) to a csv-file that you can edit if needed. This list should then be provided to DataLocker to start the activation of any bought licenses. Once the activation has been initiated you will be notified.

• Each device identified in the list will through DataLocker’s assistances be assigned a license in the ClevX/ESET central licensing system. The next time the device is unlocked and has access to the Internet the device license will become activated for the period that has been purchased.

• Licenses for DriveSecurity can be bought through the DataLocker sales channel. • For renewals and upgrades a new export will be made. If no new devices have been added

the renewal can be made based on the last list exported.

Installing DriveSecurity through SafeConsole 1. Download DriveSecurity for SafeConsole and unzip the folder: https://www.clevxapps.com/sw_update/ds_datalocker/DriveSecurity.zip

2. Create your Publisher network share and place the DriveSecurity folder there. Make sure to create a root folder in the network share.

a. Create a folder named Publisher. b. Right-click the new folder Publisher and select Properties. c. Click the Sharing tab and then click the Share.. Button. d. Provide users that has devices you which to publish files to with Read permissions. e. Now inside the Publisher folder create a subfolder named published-folders-root.

4

https://www.clevxapps.com/sw_update/ds_datalocker/DriveSecurity.zip


f. Place the unzipped DriveSecurity folder in the published-folders-root.

3. Optionally you may hide the DriveSecurity from the user Main Menu in the device software of the SafeConsoleReady Device software. If you want your users to be able click in the Main Menu to access the DriveSecurity interface you can skip this step. a. To hide DriveSecurity from the user Main Menu you must create a file named safestick.ini (note the extension must be *.ini). In the ini-file you enter the following command and then save the file in the DriveSecurity folder: [starter] hidden=yes

5


With or without the DeviceSecurity hidden in the Main Menu the user can still locate the DeviceSecurity in the tray menu by left clicking the blue shield with the checkmark.

b. Without hiding the software this will be the appearance. 4. Now it is time to setup the Policies in SafeConsole. Please log on to your SafeConsole.

6


5. Go to Policies and under Publisher enter the UNC path to the published-folders-root directory. Note that your computer name will be different than the screenshots. We suggest that you copy paste the network path from the Properties of the published- folders-root and then click Save in the SafeConsole interface.

6. Still in SafeConsole under Policies click the General side tab and scroll to the Authorized Autorun policy. Enter: {store-path}\Applications\DriveSecurity\DriveSecurity.exe and then click Save.

7


The command to run is the the location on the SafeConsoleReady device where the DriveSecurity.exe will be published. This will make the DriveSecurity run automatically once the application has been published.

7. Now insert a freshly reset SafeConsoleReady device into a computer that can access the network share.8. Connect the device to SafeConsole and complete the device setup and then unlock.9. Your files will be published to the device. This will be visible in the Main Menu. DriveSecurity will not run after the install, but will do so on all unlocks that follow.

10. Lock your device and then unlock it again. DriveSecurity will now be running in the background. You installation is complete. Verify by left clicking the icon in the system tray.

8


Updating DriveSecurity through SafeConsole• The DriveSecurity will automatically and independent of SafeConsole download the latest

virus definition from ESET over the Internet as they come available.• To update the DriveSecurity exe and dll you will download the new package and unzip.

• Take a backup copy of your current published-folders-root• Remove the old DriveSecurity folder.• Place the new DriveSecurity folder in the published-folders-root.• Verify that the safestick.ini is in place in the new DriveSecurity folder if you are using this

option. You can verify from your backup copy if you are. If needed copy the backup safes-tick.ini into the new DriveSecurity folder.

• Please log on to SafeConsole.• As the executable name in the new DriveSecurity folder will have changed we will update

our Authorized autorun Policy. Click Policies and adjust the Command to run to reflect the new file name.

9


Deactivating/Uninstalling DriveSecurity through SafeConsole• Remove or unclick Enable… the Authorized Autorun command in SafeConsole under Policies

• Remove the DriveSecurity folder from the published-folders-root.• If you want to make sure that all traces of the app is removed from a device you will need

to reset the device. You can also ask you users to delete the DriveSecurity subfolder in the Applications folder that they will find in the root of their secure storage drive

under the General tab. Click save

10

eset - installation guide · installation guide- eset drivesecurity for safeconsoleready devices...

Documents