Manual DriveLock Setup Quick Start Guide DriveLock SE 2017
Contents 1 INTRODUCTION... 2 2 REQUIREMENTS... 2 3 INSTALLATION / UPDATE... 3 3.1 DRIVELOCK ENTERPRISE SERVICE AND MANAGEMENT COMPONENTS... 3 4 SETUP DRIVELOCK... 6 4.1 DRIVELOCK QUICKSTART SETUP WIZARD... 6 4.2 DRIVELOCK CONTROL CENTER (DCC)... 10 4.3 REPORTS AND MONITORING... 11 1
1 Introduction DriveLock 7.6.6 and later includes DriveLock with Avira Antivirus to manage Avira Antivirus within the DriveLock Management Console on an enterprise level. The DriveLock QuickStart setup wizard can be used to simplify the installation and configuration of a basic DriveLock environment for Avira Antivirus only customers but also for other basic DriveLock installations either in productive environments or for evaluation purposes. use This DriveLock QuickStart Guide describes the required steps to setup DriveLock. For more information about the DriveLock Installation, Administration and Monitoring, see the manuals included in the DriveLock ISO. 2 Requirements DriveLock Software: download the DriveLock ISO from: http://drivelock.support/hc - Release & Release Notes The system requirements can be found in file Manual\DriveLock Release Notes EN.pdf resp. Handbuch\DriveLock Release Notes DE.pdf An administrative PC to install the DriveLock Management Console (MMC) and the DriveLock Control Center (DCC). The DriveLock installation ISO should be mounted on this PC to upload the installation packages to the DriveLock Enterprise Service (DES). A PC (Windows Server recommended for productive environments) to install the DriveLock Enterprise Service (DES) and the DriveLock Database (The ISO contains Microsoft SQL Express 2014 SP1). You may also install the MMC and the DCC on the DES Server PC. A user with local administration permissions on the server to run the DriveLock Enterprise Service. A user with local administration permission on the PCs to push the agent installation. File and Printer Sharing on the PCs must be active for push installation. Recommended: An AD group containing the PCs to be installed via automatic push installation. 2
3 Installation / Update 3.1 DriveLock Enterprise Service and Management components A new installation of DriveLock and an update to a newer version of DriveLock require the same steps. If you do an update, just do not select the components, which should not be updated (e.g. the Microsoft SQL Server). It is strongly recommended, always to use a same version of the DriveLock Enterprise Service (DES) and the management components. The version of the DES should be newer or equal to the most current version of the DriveLock Agent you run. When updating, you should update the DES and management components before you publish the new DriveLock Agent. As soon as published, existing DriveLock Agents will start to update themselves. Run DLSetup.exe from the ISO Select the language and accept the DriveLock EULA Select the appropriate packages. If you install the management components and the server on different PCs, install the server first. You may also install another version of Microsoft SQL-Server on your own. Follow the wizard and finish the setup Depending on the selected packages the next wizards will appear: DriveLock Management Console and DriveLock Control Center installation will be silent 3
Microsoft SQL Server Express installation will be silent DriveLock Enterprise Service (DES) Setup Wizard: Accept EULA Enter DES user and password and click Next (DO NOT continue without validation) Select or create the DES client server communication certificate Enable DES ports in Windows Firewall Click Install and finish DES Server installation Database Setup Wizard: Select Central DriveLock Enterprise Service Select Microsoft SQL-Server Click Test connection (connection to DB will be checked and Install action will be proposed) 4
Click Next to commit the database properties and Next again to start the database creation Enter the default DriveLock Management Console (MMC) and DriveLock Control Center (DCC) user (This user will be able to configure DriveLock using the MMC and to access the report data created by DriveLock using the DCC) Database maintenance: enter path to backup folder or deselect backup and click Next Follow the wizard and finish the installation 5
4 Setup DriveLock 4.1 DriveLock QuickStart setup wizard After the installation of the DriveLock Management Console has finished, the DriveLock QuickStart setup wizard appears. You may cancel the wizard at any time and restart it from the windows start menu again. You may use the wizard for an update too, to verify and adapt your configuration. Step 1: Enter the data to access the DriveLock Enterprise Service and click verify server. The checkmark becomes green, if the server can be connected. Step 2: Add license - you may add a DriveLock license file or an Avira license key (OTC) or both of them. To get a license for evaluation purposes contact your Avira or DriveLock sales partner. To activate an Avira license, an internet connection is mandatory and you must accept the Avira EULA. Step 3: Prepare Deployment the DES downloads the most current software packages from the Internet. If not yet available, you can synchronize the files from the ISO or upload packages manually. 6
Step 4: Edit policy a default company policy will be created on the DriveLock Enterprise Service. Basic settings and communication already configured is shown in the diagram. Edit the policy for your requirements or save it unchanged to start with the basic configuration. 7
Step 5: Configure push installation. Add groups and/or OUs from the Active Directory (AD), where the DES automatically shall install the Drivelock Agent and assign the default company policy. If you don t use AD you may initiate a manual push installation from the DriveLock Control Center later. Step 6: Account for push installation: Add the credentials for the user with local administration rights on the PCs where the agent shall be installed. You also may edit the credentials later in the DriveLock Management Console (MMC) under DriveLock Enterprise Service / Agent push installation / Per-server global settings / <your server> As soon as the DriveLock Agent package is uploaded and published on the DriveLock Enterprise Service, DriveLock will be installed automatically on the configured PCs and existing DriveLock Agents will be updated to the new version. 8
Finish the wizard the DriveLock Control Center may be started automatically to monitor the system actions. 9
4.2 DriveLock Control Center (DCC) Open the default Helpdesk report in the DCC and see your PCs appearing and being installed (select Helpdesk in the Navigation bar and then select Helpdesk in the working area). If you didn t configure the automatic push installation via Active Directory Groups or OUs you might initiate a manual push installation in the Helpdesk report now. Click Install Agent and select the appropriate PCs using the Computer selection dialog to add Computers, Groups or OUs from the Active Directory, from an IP-Network scan or from the Network Neighborhood to the list. 10
4.3 Reports and Monitoring DriveLock Server Events Open DriveLock Management Console and edit the Default Company Policy. The go to Global Configuration/ Settings / Event message transfer settings Example: Scroll down to section Antivirus and, in column DriveLock Enterprise Service, check or uncheck all desired events (the events will be sent to the DES and stored in the DriveLock database). Save and publish the policy (Be aware, that it may take a while, until the DriveLock agent gets the new policy) 11
Event Reports Open the DriveLock Control Center and navigate to Event report Open the report Antivirus Events For detailed information about the DriveLock Management Console and the DriveLock Control Center and how to work with event reports, statistic reports and forensic reports, see the corresponding manual included in the DriveLock ISO. 12
Copyright Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. 2017 DriveLock SE. All rights reserved. DriveLock and others are either registered trademarks or trademarks of DriveLock SE or its subsidiaries in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. 13