by DIRAK

0101100101010111001

Administration
101010101010101001
0010111010101110101
0101011101010101010

Suite
1101101010111010111
0111101010100110100
1010101010101100100
1011001010101110010
010101010101010010
0101110101011101010
101011101010101010
1101101010111010111
0111101010100110100

Deutsch / English
101010101010110010

608-0205.00-00100 - V1.3
 by DIRAK

English
01011001010101110010100101010
1010101010101010010101010101
00101110101011101010101101101

Administration
0101011101010101010101010101
01101101010111010111110010110
10111101010100110100101110101

Suite
01010101010101100100110101010
01011001010101110010100101010
1010101010101010010101010101
00101110101011101010101101101
01010111010101010101010101010
11011010101110101111100101101

Manual
01111010101001101001011101010
1010101010101100100110101010
  by DIRAK

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 4.9 Log Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4.9.1. Searching Log Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
1.1 Using Administration Suite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 4.9.2. Exporting Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
1.2 Structure of this manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 4.9.3. Deleting Log Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.10 Device and Media Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.11 Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 5 Task Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.2.1. Installation of the Administration Suite Server. . . . . . . . . . . . . . . . . . . . . . . . 65 5.1 Creating a Task Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.2.2. Installation of the Administration Suite Client. . . . . . . . . . . . . . . . . . . . . . . . . 67 5.2 Creating a Programming Job Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
2.2.3. Entering License Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.3 Creating an Individual Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
2.3 Uninstalling Administration Suite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.4 Editing a Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.5 Deleting a Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3 User Window and Basic Functions. . . . . . . . . . . . . . . . . . . . . . 69

3.1 Components of the Administration Suite Client User Window. . . . . . . . . . . . . . . . . . 69 6 Importing Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.2 Insert, Edit or Delete Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.1 Importing from a CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.3 Printing and Editing Table View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.4 Visibility of Table Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.5 Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.6 Optimizing Column Width. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 7 Microsoft® Active Directory®. . . . . . . . . . . . . . . . . . . . . . . . . 101
3.7 Resetting Column Sort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 7.1 Data Import from MS® Active Directory®. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.8 Configuration of the Administration Suite Client Software. . . . . . . . . . . . . . . . . . . . . 71 7.2 Control via the Active Directory®. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.8.1. Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.8.2. E-Mail Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.8.3. Device Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 8 Diagnosis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.8.4. Device Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.8.5. Software Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.8.6. Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.8.7. System Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 9 Multiuser-Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

4 Working with the Administration Suite Software. . . . . . . . . . . 77 10 Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4.1 User Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
10.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.2 User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
10.2 Database Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4.3 User Profile Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
10.2.1. Scheduled Backup with Windows Taskplaner. . . . . . . . . . . . . . . . . . . . . . . 106
4.4 System Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
10.3 Database Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.5 Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.5.1. Adding Devices to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.5.2. Adding Persons to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.5.3. Adding Media to a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 11 Technical Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.5.4. Adding Time Profiles to Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 11.1 Database Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.5.5. Adding Special Days to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 11.2 Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.5.6. Setting up Links in the Locking Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.5.7. Approving Programming Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.6 Extended Device Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.6.1. Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
12 Addendum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.6.2. Device Blocked and Access Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 12.1 Screen-print index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.6.3. Backlighting (only for Device Type MLR/MLU). . . . . . . . . . . . . . . . . . . . . . . . 89
4.6.4. Super Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.7 Monitor System Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.7.1. Status E-LINE by DIRAK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.7.2. System Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.7.3. Programming Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.8 Reprogramming a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

User Manual Administration Suite 63

 by DIRAK
Introduction

1 Introduction

1.1 Using Administration Suite Software

Welcome to the Administration Suite Software that enables you to

administer and monitor your E-LINE by DIRAK swinghandles for
access control and security of server cabinets via Windows PC and
Ethernet.
With this program you can configure and monitor your complete
E-LINE by DIRAK System; plus, you will be able to control access to
your server cabinets and monitor their status.
You can link up to 2000 media (transponder cards) to every E-LINE
by DIRAK swinghandle and connect them to as many as 30 Time
Profiles.

1.2 Structure of this manual

This manual is divided into the following sections:

• Installation
• Configuration of the software and the various E-LINE by
DIRAK swinghandles
• Working with Administration Suite Software

64 User Manual Administration Suite

 Installation by DIRAK

2 Installation Express Edition on your PC. This is necessary for the installation to be
complete.

This chapter includes:

• The technical requirements for an installation
• How to install Administration Suite
• How to register the software

2.1 System requirements

To install the Administration Suite, your computer must meet these

minimum requirements:
• Operating system: Windows 2000 (Service pack 3 or
higher), XP (Service Pack 2 or higher), Windows Server
2003 (SP1 or higher) Windows 7, Windows Server 2008
R2.
• Required Software: Microsoft .NET Framework 3.5. (If
the .NET Framework 3.5 not on the computer, it will be
installed during the installation of the Administration Suite
Software.)
• Hardware: Computer with Pentium III-Processor (1 GHz Screen-print 1: Database Server
or higher) and a minimum of 512 MB RAM (1024 MB
When you access the “Database Server”, select “(local)\TAS”. For
RAM or more is recommended. 600 MB hard drive space.
“connect via”, select “Windows-Authentication of the current user”.
The minimum requirements are based on the requirements for the Confirm this window by clicking the “Next” button. Then select “Cus-
operation of Microsoft SQL Server Express 2005 that serves as the tom” for Setup Type.
database for the Administration Suite server.

2.2 Installation

To install the Administration Suite you need administrative rights on

your computer. If you are working on a company network, contact your
system administrator.

2.2.1. Installation of the Administration Suite Server

Determine that there is enough disc space. Then, install the neces-
sary database, the Microsoft SQL Server 2005 Express Edition.
Start the file Administration_Suite_Server_Setup_MSSQL2005.exe
from the installation medium. The installation assistant will guide you
through the setup. If this is an initial installation, the Administration
Suite server setup will automatically install Microsoft SQL Server 2005

User Manual Administration Suite 65

 by DIRAK
Installation

menu item “Administration Suite Services” you can install the services
that are necessary to communicate with the swinghandles. In standard
applications (all swinghandles are in one location), select and install
both menu items or simply select “complete” (see screen-print 2). If
you have multiple locations with swinghandles, please read the notes
in chapter 2.2.1.1 before you continue your installation.
Confirm your selection with the “Next” button and follow the installation
assistant. After the installation of all files you will be asked to enter a
“Location Name” and a “Server IP address“.

Screen-print 2: Selection of Setup Type

In the “Custom Setup” window you have the option to install only parts
of the Administration Suite server setup:

Screen-print 4: Location Name and Server IP Address

In the field “Location Name”, specify the physical location of the
swinghandles that are connected to this server. This location name will
be listed in the Administration Suite Software and facilitates allocation
of swinghandles.
In the field “Server IP Address” enter the IP address of the Administra-
tion Suite server. If the current PC is also the Administration Suite
server, you can use the entry from the window “127.0.0.1“.
Confirm your entry by clicking “OK“.

Screen-print 3: Custom Setup

The menu item “Administration Suite Server” installs the database
service and the SQL database of the Administration Suite. With the

66 User Manual Administration Suite

 Installation by DIRAK

Screen-print 5: Installation Complete Screen-print 7: Installation of Administration Suite Services in Case of

Multiple Locations
Clicking “Finish” will complete the installation. All configuration details
can be reviewed in the “Readme.txt“-file.
2.2.2. Installation of the Administration Suite Client
For the day-to-day use of the Administration Suite, the Administration
Suite Client is sufficient. You can install it on any PC or laptop. Deter-
mine first that enough disc space is available. For installation, start
the file “Administration_Suite_Client_Setup.exe” from the installation
medium. The installation assistant guides you through the rest of the
installation.

Screen-print 6: Example Protocol for the Configuration of Services

2.2.1.1. Exception: Multiple Locations

If you are administering swinghandles in multiple locations and
these locations are also in different time zones, you can still set up
and monitor all swinghandles via one Administration Suite server. In
this case, at each location you install only the “Administration Suite
Services“. In the window “Custom Setup”, deselect the menu item
“Administration Suite Server“.

User Manual Administration Suite 67

 by DIRAK
Installation

2.3 Uninstalling Administration Suite

Uninstalling the Administration Suite Servers and the Client is done

through the Windows control panel. Select the menu item “Software”
from the control panel. In the list of installed programs you will find one
entry for the Administration Suite Server and one for the Administration
Suite Client. Select each entry one at a time and click on the “unin-
stall” button to remove the software.

Screen-print 8: Installation of the Administration Suite Client

2.2.3. Entering License Information

Screen-print 9: License Manager

Administration Suite Software can be tested up to 90 days without a
license key. After 90 days, the license key must be entered to enable
continued use. If a valid license is not available it can be obtained for a
fee by emailing: [email protected]
For assignment of this license, general contact information is needed;
the location of the installation, a contact person and the key number
generated by the license manager, Key 0 and Key 1.
After reviewing your information we will send Key 2 for activation of
the Administration Suite, which is added to the License Manager.

68 User Manual Administration Suite

 User Window and Basic Functions by DIRAK

3 User Window and Basic

Functions

3.1 Components of the Administration Suite Clicking on the group link on the navigation menu bar will allow you
Client User Window to choose the individual view you wish; e. g. devices, system, log
data, etc. Based on the view selected, the appearance of the table will
change.
This screen-print displays the most important elements of the Adminis-
tration Suite Client user window: Using the menu bar, users can log in and out, import data, change to a
different system or edit the software configuration.
Simply select the appropriate tab to change between programming
status and system notices views.

Menu Bar
Toolbar
Tabele View

Navigation Tabele View

Toolbar
for System Notices
and/or Program- View Programming Sta-
ming Status tus/System Notices

Status Bar

Screen-print 9a: Administration Suite Client User Window

User Manual Administration Suite 69

 by DIRAK
User Window and Basic Functions

3.2 Insert, Edit or Delete Records 3.4 Visibility of Table Columns

Screen-print 10: Insert, Edit or Delete Records

Screen-print 13: “Show/Hide” Button
The toolbar for Table View provides buttons to insert, edit and delete
records. A record is automatically created for each swinghandle. The The “Show/Hide” button allows you to show or hide specific columns
example in screen-print 10 shows the table view “devices”. To edit or of a table. The Administration Suite Client remembers these settings
delete an existing record, select it by clicking the appropriate button
and will keep the setup for the next time you use this table.
to the left of the record. To insert a record, click on the “add device”
button above the device list.

NOTE:
3.3 Printing and Editing Table View The layout of the tables is saved in relation to the Windows
user name and in the file specified for it: C:\Documents and
Settings\User Name\User Data\Dirak GmbH\Administration
Suite Client\ (in this case Windows XP)

Screen-print 11: “Print” Button

3.5 Refresh
Click the “Print” button to print the content of the table.

Screen-print 14: “Refresh” Button

The toolbars in the Table View have a “Refresh” button which causes
the data to be newly read from the database. Refreshing is recom-
mended when several users are using a database at the same time.
Changes made by other users are displayed after the “Refresh” button
is pressed.

Screen-print 12: Export Functions in Print Preview

In print preview you can also export the table. The export function
offers various formats (see screen-print 13).

70 User Manual Administration Suite

 User Window and Basic Functions by DIRAK

3.6 Optimizing Column Width

Screen-print 18: Reset Column Sort

Screen-print 15: Optimizing Column Width Click on the “Reset Column Sort” in the context menu of the table to
reset the column sort of the table.
To adjust the column width to its contents to improve the clarity of the
table, select the menu item “Optimize Column Width” in the context
menu of the individual table (see Screen-print 15). The context menu 3.8 Configuration of the Administration Suite
is accessed by right-clicking on the table.
Client Software

3.7 Resetting Column Sort 3.8.1. Server Configuration

Screen-print 16: Column Sort Descending

By clicking on the column header in a table, e.g. UID shown in screen-
print 16, the complete table will be sorted by the entries in this column.
An additional mouse click reverses the sort order from descending to
ascending or vice versa (see Screen-print 17).
Screen-print 19: Menu Item Server Configuration
All data in the Administration Suite is saved in the database of the
Administration Suite server. If you have installed the Administration
Suite Client on one PC that does not have the Administration Suite
server installed at the same time you must execute the server configu-
Screen-print 17: Column Sort Ascending ration before the first use of the Administration Suite Client. To do this,
click on the “Settings/Configuration/Server Configuration” to get to the
“Server Configuration” Window.

User Manual Administration Suite 71

 by DIRAK
User Window and Basic Functions

in user for the SQL server and no password needs to be added to this
window.
Should you not be able to use the “Windows Authentication” because
the Administration Suite Server doesn’t recognize the windows user
logged into the Client, you can select “SQL Server Authentication”. In
this event, the user name and password of the SQL server user must
be added into the appropriate fields.
To check the connection to the SQL server, click on the “Test Connec-
tion” button. If the test is successful, save the settings.

3.8.1.2. Manual Input of the SQL Server

Screen-print 20: Window “Server Configuration”

In the “Server Configuration” Window is the option to search for all
servers in the network using the “Search for SQL Server Instances”
button. To enter the SQL server manually, click on the “Enter SQL
Server Manually” button.

Screen-print 22: Manual Input of the SQL Server

Click on “Enter SQL Server Manually” in the Server Configuration
window to manually input the SQL server. A new window will open
in which you enter the name or the IP address of the SQL server. In
addition, you must enter the SQL instance on which the database is
installed. When installing the Administration Suite server, a Microsoft
SQL Server 2005 with the SQL Server instance “TAS” is installed by
default. It will also be entered as the default in the “SQL instance”
field and should not be changed.
Proceed with the SQL authentication setup according to chapter
3.8.1.1. After successful configuration is completed, save the settings.

Screen-print 21: Window “Server Configuration” after Automatic

Search

3.8.1.1. Automatic Search for the SQL Servers

If you have requested that the network automatically search for all
SQL servers, you will be provided with a list of all SQL servers found
(see Screen-print 21). To select the SQL server with the Administration
Suite database (TAS), click on that specific row in the table. By default
you should leave the SQL Authentication checked on “Windows
Authentication”. By doing so, you authenticate yourself as the logged-

72 User Manual Administration Suite

 User Window and Basic Functions by DIRAK

3.8.2. E-Mail Configuration 3.8.3. Device Compatibility

Screen-print 23: Menu Item E-Mail Configuration Screen-print 25: Menu Item Device Compatibility
In the Administration Suite there is the option to have all system Administration Suite Software is capable of administering various
notices, such as errors, warnings and information sent as an e-mail to devices and media (transponders). It is necessary to assign appro-
any specified e-mail address. To configure these e-mail notifications, priate media types to device types, since not all devices can com-
click on “Settings/Configurations/e-mail Configuration” on the menu municate with the same media types (transponder types). By default,
bar. This opens the e-mail configuration window (see the device compatibility is configured by the Administration Suite
Screen-print 24). Software setup, and the user doesn’t need to make changes. If, due to
a firmware update or a new device, changes are necessary, the user
can apply changes or updates afterwards. Click on “Settings/Configu-
ration/Device Compatibility” to access the device compatibility window.

Screen-print 26: Window Device Compatibility

In the device compatibility window, every device must be configured
Screen-print 24: E-Mail Configuration Window with a specific firmware-version, how many media it can administer
To configure e-mail forwarding for system notifications, enter an and with which kind of media it communicates.
SMTP server, a sender and a receiver. You can also select the type
of notification to be forwarded by clicking on the checkboxes for
errors, warnings and/or information depending on which notifications NOTE!
you would like to forward. You can test the connection by clicking the If you configure a medium for a device with which this device
“Send Test E-mail” button. If the test e-mail was successfully received, cannot communicate, it can cause a programming error in
save this configuration. Administration Suite and the programming job cannot be
completed. In this case deleting the programming job is the
only option.

User Manual Administration Suite 73

 by DIRAK
User Window and Basic Functions

Should a new firmware version 3.06 for the device type “IP-Reader
(13.56 MHz)” become available, add the entry for this firmware version
into device compatibility by clicking on the “Add New Entry” button to
open the following window (see Screen-print 27).

Screen-print 29: Selection Device Template

Via Settings –> Configuration -> Device Templates, a template for any
device type can be defined.
Screen-print 27: “Add Entry” Window
In this window, select the device type and indicate the firmware ver-
sion and the maximum number of media that the device can adminis-
ter. Exit the window by clicking the “Save” button.

Screen-print 28: Device Compatibility Window with New Entry

In the Table View you can find the entry you just added for the device
type “IP-Reader (13.56 MHz)” and the firmware 3.06, but no media
types have been assigned yet. These must be assigned in the next
step. To do this, click on the checkboxes for the appropriate media Screen-print 30: Select Device
types. You can learn from the manufacturer of the device which media
types can be linked. To apply all the changes that you made, click on In the following window default settings are defined. All variable fields
the “Save All Changes” button. are marked by a light background.

3.8.4. Device Templates

The device template defines the basic parameters for any newly
added device type:

74 User Manual Administration Suite

 User Window and Basic Functions by DIRAK

On the “General” tab you can specify the way temperature data will
be displayed in the Administration Suite Client. In the dropdown box
“Unit”, select between degrees Celsius or degrees Fahrenheit.

Screen-print 33: Software Settings Window – Tab “General”

Screen-print 31: Device Data Template
Select the “Security” tab to set up your own directives for password
Click “SAVE” to accept the changes for the selected device type. After and login.
saving, all devices that are added will be preset with these template
values. For the password directive there are four options.

3.8.5. Software Settings

Screen-print 34: Password directive

Screen-print 32: Menu Item Software Settings

NOTE:
In Software Settings there are three configuration options to customize If you activate the password directive, the default is that no
the software to your needs. password can contain the user-login name!

User Manual Administration Suite 75

 by DIRAK
User Window and Basic Functions

With the login-directive you can configure the time period allowed fol- 3.8.7. System Services
lowing a specific number of unsuccessful login attempts before a new
login attempt can be made.
If you are using a desktop reader to import the media, you can extend
the media recognition by seven additional media types.

3.8.6. Language

Screen-print 36: Menu Item System Services

“System Services” under Settings allows control of Administration
Suite Services. This is possible only when the Administration Suite
Client, the Administration Suite Server and the Administration Suite
Services are located in the same computer. With the Stop and Start
buttons, you can end or restart any service in this window. If the
Administration Suite Client is located on a computer on which no
server software is installed, the services shown in screen-print 34
cannot be stopped or started. Therefore, these buttons are grayed out.
Screen-print 35: Menu Item Settings / Configuration / Language This can also be the case if you did not start the Administration Suite
Accessing the menu item “Language” in Settings –> Configuration will Client on a Windows 7 System as an Administrator. In general these
allow you to change the language of the Administration Suite Client. services can also be stopped or started via System Control in the
The change is immediate. It does not require a system restart and will Windows operating system.
remain effective after the system is restarted.
The following languages are available:
• German
• English
• Spanish

Screen-print 37: System Services Window

76 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4 Working with the 4.2 User Administration

Administration Suite To set up a new user for the Administration Suite Software, select the
menu item “Settings/User Administration” on the menu bar.
Software

4.1 User Login

Screen-print 39: Menu Bar Settings/User Administration

In User Administration you have the option to Setup, Edit and Delete
users.

Screen-print 38: Login as ‚admin‘

By default, the Administration Suite Software displays the user “admin”
with the password “admin”. The user “admin” is the administrator of
the Administration Suite Software and cannot be deleted. You can,
however, change the password. When starting Administration Suite
Client software for the first time, you must login using the user name
“admin” with the password “admin” but you can immediately enter
your own user name and additional users for the Administration Suite
Software (see chapter 4.2).
Screen-print 40: User Administration
To add a user, click on the “Add User” button to open the “Add User”
window.

User Manual Administration Suite 77

 by DIRAK
Working with the Administration Suite Software

Screen-print 42: User Administration with New User

In User Administration you can now see the New User. If you want to
sign in as “Administrator”, select “File/User Logout” on the menu bar
and then “File/User Login”.

Screen-print 41: “Add User” Window

In the “Add User” window, enter a user name (e.g. “Administrator”).
The user name entered will be shown on the status bar of the Adminis-
tration Suite Client. For every newly set up user you must select a
user profile. By default this will be set as “Administrator” but you can
set up additional user profiles (see chapter 4.3).
The user profile defines the individual rights of each user within the
Administration Suite Software. In the example shown, the profile
“Administrator” was selected. In the “Name” field you can enter a text
in clear for the user. In addition, a password must be assigned to the
user. Screen-print 43: Login as User ‘administrator’

By checking “User must State a Reason for Remote Accessing the A login window will pop-up for the Administration Suite Client in which
Swinghandle” the user must enter a specific reason whenever he/she you can sign in as user “administrator”.
remotely accesses a swinghandle.
If a device is set up for four-eyes-mode, by clicking a second check-
box, a warning can be displayed before a remote access is allowed.
To save the New User click the “Save” button.

78 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4.3 User Profile Administration

In User Administration, the User Profile Administration can be

accessed by clicking the appropriate button (see Screen-print 40).

Screen-print 44: User Profile Administration

In User Profile Administration, you can enter, edit and delete User
Profiles. To enter a new User Profile, click on “Add User Profile”. If you
would like to set up a “Guest” profile, which has “read only” rights for
a predetermined “default” device system in the Administration Suite
Software, proceed as follows:

Screen-print 45: Window Add User Profile

First, enter the name for the “Guest” profile and enter a description
in the “Remarks” field. In the system selection, assign authorizations
for the appropriate systems. To assign administrative functions in
Administration Suite, select the “Read” and/or “Write” checkboxes in
the appropriate rows.

NOTE:
If you select “Write” in any specific line, the user automatically
has “Read” rights to that area of the software.

User Manual Administration Suite 79

 by DIRAK
Working with the Administration Suite Software

Because the user profile “Guest” should only have “Read” rights,
check only the “Read” boxes for all entries. To save the profile click the
“Save” button.

Screen-print 48: System Administration

Click the “Add System” button to add a new system and to name it
Screen-print 46: User Profile Administration with New User Profile correspondingly.

The newly added “Guest” profile will now appear in the User
Administration.

4.4 System Administration

Administration Suite Software offers the option to separate one physi-

cal Administration Suite system into various logic “systems”. In this
case a System Administration contains the data for devices, media,
persons, Time Profiles, Special Days and the Locking Plan for the
system. This data is only visible in the System Administration in which
it was set up and configured.

Screen-print 49: System Administration with New System

The new system will be visible in the Systems Administration window.

Screen-print 47: Menu Bar Settings/System Administration

To set up a new system in the software select “Settings/System
Administration” from the menu bar.

80 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4.5 Basic Steps

4.5.1. Adding Devices to the System

Screen-print 52: Device View with New Devices

In the “Devices” view all newly added devices will appear in your
system.

Screen-print 50: Device View

4.5.2. Adding Persons to the System
To add devices to a system, select “Devices” in the navigation menu,
Administration Suite can assign a “Person” record to each key medium
then select the line “Devices”. Click “Add Devices” to open the “Add
(transponder). This is easier than working with lengthy transponder ID
Devices” window (see Screen-print 51).
numbers.

Screen-print 51: “Add Devices” Window

Select one or more devices. To add these devices to the system, click
the “Add Selected Devices” button on the menu bar. Adding devices
to a system will automatically generate programming jobs. These are
necessary to set the default values for the devices. When all devices
Screen-print 53: Persons View
have been added to your system, exit the window by clicking the
“Close” button. Select “System” in the navigation menu. Next select the “Persons”
link to add a person to the system. Select “Add Person” to open the
“Persons Data” window (see Screen-print 54).

User Manual Administration Suite 81

 by DIRAK
Working with the Administration Suite Software

4.5.3. Adding Media to a System

Screen-print 54: Window Persons Data

In the “Persons Data” window, enter the personal information that
you wish to assign to a key medium. You can also add a photo of the Screen-print 56: Media View
person. To take a photo with a webcam connected to your computer, Select the “Devices” from the navigation menu, then select the “media”
right click on the empty image preview and select “Import Image from link to add media to the system. Click the “Add Medium” button to
Camera”. Or, you can select “Load Image” to load an image from file. open the “Media Data” window (see Screen-print 57).
Save this record by clicking the “Save” button.

Screen-print 55: Persons View with New Person Record

All newly added Person Records should now appear in the New
Person Record screen.

Screen-print 57: Media Data Window

Place a transponder card / chip on the desktop reader and click “Read
Medium” to import the medium (transponder). If the medium was suc-
cessfully imported, the UID (transponder-ID) is shown in the UID field.

82 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

To link the medium to a specific person, select that person from the
“owner” dropdown menu.

Screen-print 59: Media View with Newly Added Medium

To save the medium, click on the “Save” button. When you are fin-
ished entering new media, click the “Abort” button to exit. In the Media
View you should now see all newly added media.

4.5.4. Adding Time Profiles to Systems

Screen-print 58: Media Status

In the “Status” selection menu, the media status can be changed. The
Administration Suite Software distinguishes between the following
situations:
• “Not yet distributed”
• “Distributed”
• “Returned”
• “Damaged”
• “Lost”
• “Blocked”
When the media status is set to “Distributed”, the Locking Plan will
display the medium and if it can be used.
If the status is set to anything other than “Distributed”, the medium will Screen-print 60: Time Profile View
not appear in the Locking Plan. If the medium has been linked with Select “System” from the navigation menu, then select “Time Profiles”
one or more devices in the Locking Plan, these links will be deleted. To add a Time Profile to the system. Select “Add Time Profile” button
Therefore, the original connection with the swinghandle is removed to open the “Time Profiles” window (see Screen-print 61).
and the medium (the transponder) no longer has access rights to the
corresponding swinghandle.

User Manual Administration Suite 83

 by DIRAK
Working with the Administration Suite Software

Screen-print 62: Time Profile View with Newly Added Time Profile
Click on “Save” to save the Time Profile. In the “Time Profiles” view
you should see the newly added Time Profile. When creating a Time
Profile, programming jobs are automatically created for all existing
devices. Refer to chapter 4.5.7 to learn how programming jobs are
approved.

4.5.5. Adding Special Days to the System

Screen-print 61: Time Profiles Window
Using Special Days you can create special configurations for Time
In the “Time Profiles” window, enter the name of your new Time Profile Profiles. You can create a Time Profile that is valid every day from 7
and assign a color to your profile. The preview will show your Time am to 6 pm but not from December 24th until January 1st of every
Profile in the selected color. Up to 3 time windows can be configured year, because your company is closed at that time.
for every week and for Special Days (see chapter 4.5.5). In this
example, we configured a Time Profile that is valid 24 hours for every
weekday and for every configured Special Day.

Screen-print 63: Special Day View

84 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

Select “System” from the navigation menu bar, then select “Special Save the Special Day by clicking the “Save” button. The Special Day
Days” to add Special Days to the system. Next, select “Add Special view should show the newly added Special Day. Adding Special Days
Day” to open the “Special Days” window (see Screen-print 64). will automatically add programming jobs to all existing devices. Refer
to chapter 4.5.7 to learn how programming jobs are approved.

4.5.6. Setting up Links in the Locking Plan

Screen-print 66: Locking Plan View

To add a link to the Locking Plan, select “System” on the navigation
menu bar, then select “Locking Plan”.
Screen-print 64: Special Days Window
In the Special Days window, enter a name for a Special Day or time
period. Also enter the start and end of this time period.

Screen-print 67: Setting up Links in the Locking Plan

In the Locking Plan, select the devices and media that you would like
to link. Then right-click on the selection and select from the context
Screen-print 65: Special Day View with Newly Added Special Day menu the Time Profile you would like to apply to the links.

User Manual Administration Suite 85

 by DIRAK
Working with the Administration Suite Software

For every change that involves a device, Time Profile, Special Day
or Locking Plan, the device’s programming must be updated. The
software will automatically generate programming jobs. Before these
updates are applied to the appropriate device, you must approve the
programming jobs in the modification list.
Click on the “Programming” button on the menu bar of the modification
list. You can monitor the update progress in “Programming Status”
(see Screen-print 70).

Screen-print 68: Locking Plan View with Link

The Locking Plan shows the links between devices and media in the
appropriate Time Profile color. The assignment of links in the Locking
Plan automatically creates programming jobs for all the devices
involved. Refer to chapter 4.5.7 to learn how programming jobs are
approved.
If you cannot select any devices, it is possible that the devices are not
compatible with this type of application. Refer also to chapter 3.8.3
Device Compatibility. Screen-print 70: Programming Status with Active Programming Jobs

4.5.7. Approving Programming Jobs

Screen-print 71: System Ready

When all programming jobs are completed, the system status icon
Screen-print 69: List of Modifications with Outstanding Programming on the status bar of the Administration Suite Software changes from
Jobs “update in progress” to “system ready” (see Screen-print 71).

86 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4.6 Extended Device Configuration

4.6.1. Device Settings

Screen-print 72: Device View

To apply changes to the setup of a device select “Devices” in the
menu bar, then select the “Devices” line. Click on “Edit Device” to Screen-print 73: Device Details Window
open the “Device Details” window (see Screen-print 73).
In the “Device Details” window is the option to change the following
settings:
Name: Enter a name for the device. The standard name for a device
consists of the device type and it’s UID.
Opening Duration: he opening duration defines how long a latching
element remains in the open position when a valid key is recognized
by the device.
Call up Interval: The call up interval defines how often the device
reports its status to the “Administration Suite Device Port”.
Alarm Swinghandle: The time frame after which device sends an
alarm when a swinghandle remains open. If no value is entered this
function in deactivated.
Alarm Door Open: The time frame after which device sends an
alarm when a door remains open. If no value is entered this function in
deactivated.
Slave Relay Mode:
• Relay off: relay function is deactivated.
• Relay on when lever open and button pushed: the reader
relay is switched on when the swinghandle is open and
the button is pushed.

User Manual Administration Suite 87

 by DIRAK
Working with the Administration Suite Software

• Relay on when lever open: the reader relay is switched 4.6.2. Device Blocked and Access Periods
on when the swinghandle is open.
• Relay on with valid medium: the reader relay is switched
on when a valid medium is swiped in front of the device.
• Relay on during alarm: the reader relay is switched on
when the device registers an alarm.
Device active: Activate and deactivate the device.
Four-Eyes-Principle: Activate and deactivate the four-eyes-principle.
Four-Eyes-Principle Timeout: Time frame allowed while searching
for authorized media for the four-eyes-principle.
Alarm counter for unauthorized access: When the number of
access attempts with unauthorized cards is exceeded, the device will
send an alarm. If this counter value is zero, the function is deactivated.
Monitoring period for unauthorized access: time period for the
“alarm counter for unauthorized access”.
Temperature-Minimumvif the temperature measures by the device
is below this value, the device will send an alarm.
Temperature-Maximum: if the temperature measures by the device
is above this value, the device will send an alarm.
Temperature interval: if you enter a value larger than zero, the
device will send temperature data to the Administration Suite in this
interval (in minutes). The smallest interval is 5 minutes.
Ready to Open during Temperature Alarm: In case the temperature
Screen-print 74: Access Period for a Device
rises above or falls below the limits the “Ready to Open” mode is
activated. The Access Period defines the time frame during which you can
gain access to an enclosure that is locked with this device. If the
The fields “Building”, “Floor”, “Room”, “Door” and “Remarks” are
Access Period for a device is active, the device’s LED is blinking
added information for users of Administration Suite. This Information is
green. The swinghandle is then opened by pushing the button on the
not saved in the device.
swinghandle.
When changes are saved (by clicking the “Save” button), program-
Access attempts (only for handle types MLR/MLU) can restrict the
ming jobs for the appropriate devices are automatically created. In
Access Period even more. If the value 3 is entered, only 3 access
chapter 4.5.7 you can learn how to approve these programming jobs.
attempts per Access Period are permitted. When the maximum
number of access attempts has been reached the device automatically
exits the “Ready to Open” mode, so that no more access attempts are
possible.

88 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4.6.3. Backlighting (only for Device Type MLR/MLU)

For device types MLR or MLU, LED light signaling can be configured
individually on handles/locks.

Screen-print 75: Blocked Period for a Device

The Blocked Period defines the time frame during which the device
Screen-print 76: Adjustable Backlighting
cannot be accessed, not even with a valid medium. If a Blocked
Period is currently active for a device, the LED on the device is red. For easier identification in larger facilities, 7 different backlighting
During this time the handle can only be opened remotely via the colors can be selected. In addition to the backlight color, the blink
Administration Suite. MLR/MLU handle types that have a “Super User interval can also be selected along with the option to select a second
Card” assigned to them can be accessed using this medium even color. If desired, the backlighting can be turned off.
during Blocked Periods. The “Super User Card” function is explained
in chapter 4.6.4. There is also an option to turn both signal LEDs of the swinghandle
(top and bottom LED) partially or completely on or off.
If changes have been made to the Access and Blocked Periods, pro-
gramming jobs will automatically be created for the appropriate device. 4.6.4. Super Users
Refer to chapter 4.5.7 to learn how programming jobs are approved.
“Super Users” are media with authorities beyond those of regular
media.
If a Super-User-Medium is assigned to a device, it always has access
regardless of Blocked times or Locking Plan times.

User Manual Administration Suite 89

 by DIRAK
Working with the Administration Suite Software

4.7 Monitor System Status

4.7.1. Status E-LINE by DIRAK

Screen-print 78: Status E-LINE by DIRAK View

“E-LINE by DIRAK Status” provides an overview with information
about all E-LINE by DIRAK devices. This is where the most important
status and access details are displayed:

Screen-print 77: Add Super-User-Medium • Swinghandle open / closed

• Solenoid active / not active
The maximum quantity of Super-User-Media allowed is limited to 10. • Button pushed / not pushed
In general, any compatible medium can be set up as • Access active / not active
Super-User-Medium. • Door open / closed
• Relay active / not active
• Current temperature measured by the reader
• Device alarm
• Current device mode
• Device active / not active
In addition, the following functions can be accessed via the context
menu of the E-LINE by DIRAK-Status-view:
• Activate / deactivate device
• Reset device alarm
• Send remote opening command to device
• Display temperature curve for the temperature measures
by the reader
• Edit access and Blocked Periods
By clicking on the device group, you can limit the list view and only
monitor devices of a certain group. Refer to chapter 4.10 to learn how
to create groups.

90 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4.7.2. System Notifications 4.7.3. Programming Status

Screen-print 79: System Notifications Screen-print 80: Programming Status

The System Notification view (bottom left below the “programming sta- Programming Status displays an overview of all programming jobs
tus” tab) displays all errors, warnings and information from the system. that are approved, currently being transferred or not yet transferred.
You can delete programming jobs from within the context menu if a
To delete an individual System Notification, you must first confirm the device is defective, or is no longer accessible.
specific message by clicking the checkbox in the “Confirm” column.
You can select all messages, then click “Confirm All Messages”. Mul-
tiple messages of the same kind for the same device are recognized
NOTE:
automatically and can all be confirmed/checked together or individu-
The deletion of a programming job causes inconsistencies
ally by the user.
between data in the device and in the database. To synchro-
Clicking the button “Delete Confirmed Messages” will delete all nize the information the device must be reprogrammed.
selected messages.
By selecting File > Diagnosis from the menu bar you can delete pro-
gramming jobs as well. Internal database structures will be checked
this way and corrected, if needed. (see chapter 8 Diagnosis).

User Manual Administration Suite 91

 by DIRAK
Working with the Administration Suite Software

4.8 Reprogramming a Device 4.9 Log Data

4.9.1. Searching Log Events

Screen-print 81: Reprogramming a Device

A device can be reprogrammed by right-clicking in the context menu.
All device data is resent to the selected device and saved there. If the Screen-print 82: Event Log
device is already linked with Time Profiles in the Locking Plan these
will be reprogrammed as well. To access the Event Log, on the navigation menu select “Log Data”.
Next, select “Show Events”. A click on the “Search” button will start the
Reprogramming is recommended when inconsistencies occur search for Log Events.
between the device and the database. Reprogramming will compare
and synchronize the data between device and database. All Log Events are shown in table format. You can change the column
sort by clicking on the column headers. You can limit the results using
filter criteria such as Devices, Media, Users, Log Events and/or Time
Periods.
When dealing with large data volume, it is recommended that the
results be limited by entering a time period.
For a detailed explanation of Log Events, click on the “Log Event Infor-
mation” button. All log events are shown with a detailed description.

92 User Manual Administration Suite

 Working with the Administration Suite Software by DIRAK

4.9.2. Exporting Log Events The grouping process is the same for both. See below for instructions
on grouping devices:
Under Devices > Device Group Administration which brings you to the
Device Groups View (see Screen-print 84).

Field2

Field1 Field3

Screen-print 83: Saving Event Log File

Screen-print 84: Device Groups View
The “Export Table” button allows you to export the displayed log
events either as Excel-file (.xls) or as a .pdf. There is also an export Field 1: C
 ontains all device groups. The view is arranged in a tree
tool available in the print function. structure with an arbitrary number of layers. A device can only belong
to one group.
Clicking the “Print” button will open the print menu. From this menu,
you can print the displayed data or save it as one of the following file Field 2: L
 ist of all devices that belong to a group in Field 1. Devices
types: PDF-, HTML-, MHT-, RTF-, Excel-, Text- or Image-file. listed here can be moved via drag-and-drop or with arrow keys into
Field 3 – this removes the device from the group.
4.9.3. Deleting Log Events Field 3: L
 isted here are devices that have not yet been assigned to
any group. They can be moved using the arrow keys or via drag-and-
Clicking “Delete Log Events” will completely delete all selected events
drop method to be pulled into Field 2 or directly into a group in Field 1.
from the system. Depending upon data volume, you should backup
Log Events periodically by exporting them, then deleting the backed-
up data from the Administration Suite. Log Events are not automati-
cally deleted.

NOTE:
Deleting log events cannot be undone.

4.10 Device and Media Groups

Devices and media can be grouped within the Administration Suite

Software to gain a quicker overview for certain situations. This will limit
the views accordingly.

User Manual Administration Suite 93

 by DIRAK
Working with the Administration Suite Software

4.11 Change Log You should delete the Change Log records periodically, to prevent the
database from getting to big! Before deleting the records, they should
be backed-up, as deletion is final and cannot be undone.
Data can be backed-up via SQL-Backup or using the “Export” function.
The “Delete Entries” button is used to delete Change Log entries. All
entries will always be deleted.

Screen-print 85: Change Log

In the Change Log, the actions of adding, editing and deleting of
records in the Administration Suite are logged. All changes of records
can be found here and retraced.
A double-click on the selected entry will open the editing screen that
was used to make the specific change. The screen shows the historic
data that was saved at that specific time.

Screen-print 86: Deleting the Change Log

Results can be limited by entering a time period and the number of
records to display.
Like Log Events, the Change Log records can be exported either in
.xls or .pdf file formats.

94 User Manual Administration Suite

 Task Administration by DIRAK

5 Task Administration Indicate also, the execution time and if the task is “active”, i.e.
executable.
Next, enter the time interval in which the task should be executed.
Under Settings > Task Administration, you can create 3 different kinds The starting time is used for execution time along with the day that
of tasks: was specified in the intervals (see Screen-print 88).

Task Report: A  list of Log Events, saved as a file, that can be sent as
an e-mail attachment. The type and extent of log data can be defined
using a filter.
Task Programming Job: U  sing the scheduler, five different types of
programing jobs can be generated:
• Remote Opening
• Access Period
• Blocked Period
• Task Planned Access
• Task Automatic Device Takeover
For the Access and Blocked Periods, the first time slot (of 3 possible
time slots) will be overwritten with the data from the task.
Task individual: V  ery flexible task for scheduled execution of a
.bat- or .sql-file. This file definitive must be on the server on which the
“Administration Suite Scheduler” is executed! Screen-print 88: Indicating an Interval
As you can see in Screen-print 88, a weekly interval was chosen in
this example. The task is to run at the defined days.
5.1 Creating a Task Report

Click on “Enter New Task” and select “Task Report” to create a report.
Next, assign the task a descriptive title.

Screen-print 89: E-Mail and File Extensions

If you wish to send e-mail messages, establish a list of contacts to
receive Task Reports as an attachment.
Screen-print 87: Creating a Task Report

User Manual Administration Suite 95

 by DIRAK
Task Administration

E-mails are optional, however, a file path to the location of the saved The Time Period is based on the execution time specified for the Task
Task Report must be established. If the indicated directory already Report!
exists, it will not be created again!
By clicking “Create” you execute the item on the Task Report.
The file format in which the Task Report should be saved must also be
selected by indicating the file extension:
5.2 Creating a Programming Job Task
• pdf:
Task Reports, generated as pdf-files can contain a maxi-
mum of 2000 entries (otherwise the file size would be too In order to create a programming job click on “Create New Task” and
large for some mail recipients). select “Task Programming Job”. The next two steps are the same as
• xls: for “Creating a Task Report” where the name, execution time, active-
xls-files can contain up to 65535 entries (due to the MS® status and the interval are entered.
Excel®97 row limit). Next, choose from the following:
• csv:
csv-files can contain an indefinite number of entries. • Remote Opening
• Access Period
If a file format reaches its limit due to an excessive number of entries, • Blocked Period
it will automatically change to the file type that allows for the next- • Task Planned Access
bigger number of entries. • Task Automatic Device Takeover
In sending the Task Report as an e-mail, you can specify the maxi- For remote opening, the time value is the execution time of the task.
mum attachment size under “Max. Size Attachment (KB)”. If this size
is exceeded by the generated file, the Task Report will not be sent and For Access Period and Blocked Period, the effective times are the
the result of the last execution is displayed as an error message. ones entered in the text fields for “start” and “end time” (see Screen-
print 91).

NOTE:
In this situation, the time values of the first of the three possi-
ble time windows are overwritten!

Screen-print 90: Task Report Filter

In the Task Report Filter you can target your search based on:
• devices
• media
• users
• events Screen-print 93: Selection Access Period
• time period

96 User Manual Administration Suite

 Task Administration by DIRAK

The devices affected are specified in the next step (see Screen-print
92).

Define a start and end time for the automatic link between the specific
transponder media and the required devices.
Screen-print 94: Device Selection
By clicking “Create”, the Task Creation is completed.
The programming job “Task Planned Access” allows authorization of
specific media for specified devices for a configured time period.

Enter a name for this task.

User Manual Administration Suite 97

 by DIRAK
Task Administration

Once the desired task is created, its actual status can be reviewed.
Each task goes through a series of statuses. “in preparation”, “in
programming”, “active” and “expired”.

A check is performed to identify conflicts with other tasks. If no conflict

exists, the task is created by clicking “Create”.

98 User Manual Administration Suite

 Task Administration by DIRAK

5.3 Creating an Individual Task 5.4 Editing a Task

To create an Individual Task, click on “Create New Task” and select To edit a task, click on the “Edit” symbol next to the task that you want
“Task, Individual”. The next two steps are the same as “Creating a to change. This will open the editing window, in which you can make
Task Report” or “Creating a Task Programming Job” by entering the adjustments according to your requirements.
name, the execution time, the active-status and the interval.
If a task with a repetition of “only once” has been executed, it cannot
As shown in Screen-print 95, you must enter the absolute path of the be started again by simply changing the execution date. Such a task
file that is to be executed. It must be a .bat or .sql type file. It is neces- must be newly created or the repetition marker must be changed.
sary to be on the server on which the service “Administration Suite
Scheduler” is executed.
5.5 Deleting a Task
As long the individual task is active, the executable file may not be
removed from the system.
Before you can delete a task, it must be deactivated by clicking on
the “Deactivate” symbol next to the task. It can then be completely
removed by clicking on the “Delete” symbol.

Screen-print 95: Selecting the File to be Executed

To complete the process, click on “Create”.

Screen-print 96: Tasks View

User Manual Administration Suite 99

 by DIRAK
Importing Data

6 Importing Data Office, Phone Number Private, Phone Number Mobile, Fax, Email,
Remark, Personal Number, Department, Activity, Division, Cost
Center, Room.

The Administration Suite Client offers two different options for import- The menu item File > Import > CSV File opens an entry window in
ing data: which you specify the CSV file and the kind of data you are importing
(media or persons). After selecting the specific CSV file, Click the
• From a CSV-File “Import” button, select the type of import in the drop-down-box.
• From a Microsoft® Active Directory®

Screen-print 97: Data Import Selection

6.1 Importing from a CSV File Screen-print 98: Data Import Window

Data import from a CSV file is possible for Media and Persons. Begin Data Import into the system by clicking the “Import Data” button.

The structure of the CSV file must include the following columns for
importing media:
• System Id
• MediaType Id
• UID
• Media Number
• State
Optional fields are: Created At, Created From, Modified At, Modified
From.
The structure of the CSV file must include the following fields for
importing persons:
• Salutation
• First Name
• Last Name
Optional fields are: Middle Name, Windows User name, Windows
Password, Birth Date, Street, Zip Code, City, Country, Phone Number

100 User Manual Administration Suite

 Microsoft® Active Directory® by DIRAK

7 Microsoft® Active Directory®

7.1 Data Import from MS® Active Directory®

Administration Suite Software offers extensive options to import or

sync data from the Active Directory®. It is possible to control access
authorizations only from the Active Directory®. More on this subject
can be found in the chapter “AD Group Mapping”.
In order to use this function, the Active Directory® service must be
available. “Read” rights to the Active Directory® will be needed.
If you have questions about this feature, please contact your network Screen-print 100: Connection to the Active Directory® Successful
administrator.
This configuration need only be done once. The Administration Suite
The import function makes administration much easier. The elabo- Software saves the entered values. Next, change to the “AD User
rate input of users into the Administration Suite Software becomes Import Settings” tab and select the sub tab “AD User Import Mapping.
obsolete. If/when objects in the Administration Suite Software have names other
Before importing the data from the Active Directory®, several settings than in the Active Directory® appropriate links can be created in this
must be adjusted. Select AD Synchronization->Settings from the menu configuration overview according to your specifications.
on the left. An overview for the Active Directory® administration should This will define which values from the Active Directory® are linked
appear on the right. Select the tab Domaincontroller Administration. to those from the Administration Suite Software and how they are
automatically synced.
With the “add” button additional links can be created and with the
“delete” button previously created links can be removed.
You can only delete links that have been created manually. Links that
were created by the system cannot be deleted.

Screen-print 99: Window AD Sync Setting

Under Domain Controller, enter your Domain or your Domain Control-
ler into Active Directory® (e.g. mycompany.com or the server name
of the Domain Controller). If you don’t have this information, contact
your network administrator. Under User Name and Password enter
the user authorized to read data in your Active Directory® and his/
her password. Click on the “test” button. If all values are correct, the Screen-print 101: Link list
following window should pop up.

User Manual Administration Suite 101

 by DIRAK
Microsoft® Active Directory®

Next, click on the sub tab OU for User Import. Select the branch from During automatic synchronization, the system only considers those
the Active Directory® that you want to include in the synchronization. branches that have been selected (Screen-print 101). It will automati-
You can add one or more branches. By clicking “Add” you can add a cally set up users and groups from these branches in the Administra-
new synchronization source. By clicking “Delete” you are removing the tion Suite Software.
marked synchronization source.
In order to start the synchronization with Active Directory® only a
Names used in the Active Directory®. couple more steps are needed.
DC – Domain Component First, change to the tab ‘AD Synchronization’.
OU – Organizational Unit
CN – Common Name
Example: CN=Peter Sample,OU=Sales,DC=actme,DC=de

Screen-print 104: AD Synchronization

Mark the AD Synchronization active and select an interval for the
synchronization cycle (e.g. 5 min).
Screen-print 102: Active Directory® Select Branch
Next, select whether you only want to synchronize existing users,
Once a branch in the Active Directory® has been selected, click on the (users that have already been entered into the Administration Suite
“Save” button to finalize the selection. Software), or all users from the Active Directory®. In order to synchro-
nize all users from the Active Directory®, select ‘AD Users and All’.
You can select only DC or OU for the synchronization.
If you also wish to implement groups form the Active Directory®, select
‘AD Groups’.
Save all changes and synchronization will start automatically when
interval time has expired. If the interval entered is 5 minutes, synchro-
nization will begin after 5 minutes. The Administration Suite Software
will search the configured branch of the Active Directory® for all users
and will add them to the administration-database. Changes that occur
in the configuration of the Active Directory® are regularly transferred.

7.2 Control via the Active Directory®

Another useful function of the Administration Suite Software offered

via the Active Directory® is group mapping. This function allows
access control solely via the Active Directory®.
Screen-print 103: Active Directory®

102 User Manual Administration Suite

 Microsoft® Active Directory® by DIRAK

Device groups can be established in the Administration Suite Software Select from the menu on the left the Active Directory® group to
and are linked (via mapping) to groups in the Active Directory®. Map- which you would like to map. In the area to the right of the window,
ping to individual devices can be set up as well. All users added to select devices and device groups and map them with a time profile
an established group in the Active Directory® are automatically given to the Active Directory® group. Select the device or device group in
access privileges. the lower right window and click the “up” arrow. All mapped (linked)
devices should now be listed in the upper window.
Please note that the user names in the Administration Suite Software
and the Active Directory® must be identical and the user must be Close the window to apply all changes.
linked to a medium that is set up as “Distributed” in order for this func-
tion to work correctly.

NOTE:
Use the Active Directory® synchronization.

The following example explains the process.

Step 1: S
 et up a group in the Active Directory®, e.g. AD_Group1.
Step 2: S
 et up a group in the Administration Suite Software, e.g.
Group 1.
Step 3: S
 et up mapping.
Select AD Synchronization->AD Group Mapping from the menu on the
left. Screen-print 106: AD Group Mapping Overview

Click on Group Mapping on the menu bar at the top. The following In the overview, all mappings should be visible. When needed,
mapping window will appear. individual or all mappings can be deleted from this screen using the
“Delete” button.

Screen-print 105: Active Directory® Group Mapping

User Manual Administration Suite 103

 by DIRAK
Diagnosis

8 Diagnosis Below the status bar in the Administration Suite, the status should now
display as “System Ready”.

Some programming jobs may not be properly completed if the server

is suddenly disrupted (crashes). If this occurs, a Diagnosis Tool can be
Screen-print 109: System Status after Diagnosis
selected that will clean up all Programming Jobs and restore normal
operating status. Reset Planned Access

Screen-print 107: Opening the Diagnosis Tool

Select File > Diagnose to open the tool to clean up programming jobs.
The following services must be stopped before starting the Diagnosis
Tool.
• Administration Suite Database Service
• Administration Suite Scheduler.
When these services are stopped, the diagnosis can begin. The
diagnosis program deletes all programming jobs or fragments of jobs
that were not executed during the normal operating status.

Screen-print 108: Diagnosing

Once a diagnosis has been performed, the devices must be re-pro-
grammed since the system would no longer be synced!

104 User Manual Administration Suite

 Multiuser-Operation by DIRAK

9 Multiuser-Operation
Multiple users can operate the Administration Suite Software at the
same time. If changes are made by two different users in the Admin-
istration Suite Client at the same time, the software will transfer only
the data for programming that was saved last. It will possibly display a
message if you are trying to change a record that has previously been
deleted by another user.

User Manual Administration Suite 105

 by DIRAK
Backup

10 Backup BACKUP DATABASE TAS

TO
DISK = @PATH
GO
When the path has been verified or changed (if needed), save the file
10.1 Requirements “TAS_Backup.sql”.

To run a database backup or restoration, the following is required:

Operating system: Windows 2000 (Service pack 4 or higher), Win-
dows XP (Service Pack 2 or higher), Windows Server 2003 (SP1 or
higher) or Windows 7, Windows Server 2008 R2.
Required software: Microsoft .NET Framework 3.5, Microsoft SQL
Server Management Studio 2005 Express.

10.2 Database Backup

Starting with the Administration Suite Server 1.0.0.36 a SQL-Script

is available for the database backup. The script “TAS_Backup.sql” is
Screen-print 110: Accessing the SQL-Script via Batch File
located in the folder “c:\Program Files\Administration Suite\Backup”
and can be accessed via the batch file “TAS_Backup.bat”. Before To test the path in the SQL Backup script, select the script via the file
the first access you must indicate the path where backup files should “TAS_Backup.bat”. As you can see in Screen-print 110, the last mes-
be saved in the file “TAS_Backup.sql”. By default the following path sage should indicate that the backup was successful.
is listed: “c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\
Backup\”. Verify that this location exists on your PC and correct it if
10.2.1. Scheduled Backup with Windows Taskplaner
necessary. You can enter any other location, e.g. a network drive.
Create a scheduled task that calls up the batch file “TAS_Backup.bat”.
It is found in the Windows Start menu under “­Start\Programs\
NOTE: Acce­ssories\System programs\Scheduled Tasks”. Using the Assistant
The path must be set in apostrophes (‘) and must end with a you can add a new task which will call up the batch file according to
backslash (/), e.g.: the schedule you establish.
SET @PATH = ‘c:\Program Files\Microsoft SQL Server\MS-
SQL.1\MSSQL\BACKUP\’

USE [TAS]
GO
DECLARE @PATH varchar(255)
SET@PATH = ‘c:\Program Files\Microsoft SQL Server\MSSQL.1\
MSSQL\BACKUP\’
+ ‘TAS_’ + right(‘0’ + rtrim(day(CURRENT_TIMESTAMP)),2)
+ ‘-’ + right(‘0’ + rtrim(month(CURRENT_TIMESTAMP)),2)
+ ‘-’ + rtrim(year(CURRENT_TIMESTAMP))
+ ‘_’ + right(‘0’ + rtrim(DATEPART(hh, CURRENT_TIMESTAMP)), 2)
+ ‘-’ + right(‘0’ + rtrim(DATEPART(mi, CURRENT_TIMESTAMP)), 2)
+ ‘-’ + right(‘0’ + rtrim(DATEPART(ss, CURRENT_TIMESTAMP)), 2)
+ ‘.BAK’

106 User Manual Administration Suite

 Backup by DIRAK

10.3 Database Restoration

Screen-print 111: Scheduled Task - Database Backup

It is not necessary to be logged into the computer for the scheduled Screen-print 112: Ending Administration Suite Database Service
task to run. Only the server must be started on which the services are
installed so that the task can be executed. Before restoring the Administration Suite database, determine if the
“Administration Suite Database Service” is still active. If so, please end
this service before proceeding.
NOTE: To restore the Administration Suite Database, first select the TAS-
Please make sure that the Taskplaner Service has been database in the “Microsoft SQL Server Management Studio Express”.
started on the server in question. Then select the “Task/Restore/Database” command from the context
menu.

User Manual Administration Suite 107

 by DIRAK
Backup

Screen-print 113: Restoring the TAS-Database Screen-print 115: Restoring from a File
In the “Restore Database” window (see Screen-print 113) select “from Select a backup file. The backup sets contained in this file will be
medium” as source for the restoration. Then select the desired backup displayed. Normally, every file has only one backup set. Select the
file with the “…” button. backup set you would like to use.

NOTE:
In the “Database Restoration” window on the “Options” page
select “Overwrite Existing Database”.

Screen-print 114: Select Restore Source

108 User Manual Administration Suite

 Backup by DIRAK

Screen-print 116: Restore Options

To start the restoration, click on the “OK” button. When the database
restoration has been completed, the appropriate message will appear
as in Screen-print 117.

Screen-print 117: Database Successfully Restored

User Manual Administration Suite 109

 by DIRAK
Technical Information

11 Technical Information SERVER: c ontains all program files for the Administration Suite
Database service.
The Administration Suite Device Port and Administration Suite Device
Contained in this chapter: Layer are located directly in the folder “c:\Program Files\Administration
Suite”.
• The database format that the Administration Suite uses
• The directories setup on your computer by the Administ-
ration Suite
• The kinds of problems that can occur during the operation
or installation of the Administration Suite.

11.1 Database Technology

The Administration Suite uses Microsoft SQL Server 2005 Express

as its database, which is provided free of charge by Microsoft. The
database-files TAS.mdf and TAS_log.ldf are installed in the default
directory of the SQL-server (c:\Program Files\Microsoft SQL Server\
MSSQL.x\MSSQL\Data in which x stands for the number of the data-
base instance). Information regarding backup of the Administration-
Suite-Database can be found in chapter 9.

11.2 Directory Structure

Settings and log data for the Administration Suite Client are user spe-
cific and are saved in Windows folder “C:\Documents and Settings\
User name\Application data\Dirak GmbH\Administration Suite Client”
(in this case user name stands for the Windows user name). This
folder contains the following files:
Config.xml: c ontains XML-data with the program settings, e.g. the
language or the database address for the Administration Suite server.
Client.log: c ontains all log data for the Administration Suite Client
All XML Files that start with Layout … : c ontain layout settings for
the individual views within the Administration Suite Client.
All files for the Administration Suite Server can be found by default
under “c:\Program Files\Administration Suite” and its sub-directories:
CMD_OUT, JOBS_IN, JOBS_LOG and JOBS_OUT: contain encryp-
ted programming jobs and data for the devices.
Data: contains information about all devices, as well as the code for
the encryption of communication (OA_SYSTEM.lic).
LOG: c ontains the log files for the Administration Suite Device Port
service, the Administration Suite Device Layer service and the Admi-
nistration Suite Database service.

110 User Manual Administration Suite

 Addendum by DIRAK

12 Addendum Screen-print 34: Password directive.................................................................. 75

Screen-print 35: Menu Item Settings / Configuration / Language..................... 76
Screen-print 36: Menu Item System Services................................................... 76
Screen-print 37: System Services Window....................................................... 76
Screen-print 38: Login as ‚admin‘...................................................................... 77
12.1 Screen-print index
Screen-print 39: Menu Bar Settings/User Administration.................................. 77
Screen-print 40: User Administration................................................................. 77
Screen-print 41: “Add User” Window................................................................. 78
Screen-print 1: Database Server....................................................................... 65
Screen-print 42: User Administration with New User........................................ 78
Screen-print 2: Selection of Setup Type............................................................ 66
Screen-print 43: Login as User ‘administrator’.................................................. 78
Screen-print 3: Custom Setup........................................................................... 66
Screen-print 44: User Profile Administration..................................................... 79
Screen-print 4: Location Name and Server IP Address..................................... 66
Screen-print 45: Window Add User Profile........................................................ 79
Screen-print 5: Installation Complete................................................................ 67
Screen-print 46: User Profile Administration with New User Profile.................. 80
Screen-print 6: Example Protocol for the Configuration of Services................. 67
Screen-print 47: Menu Bar Settings/System Administration.............................. 80
Screen-print 7: Installation of Administration Suite Services in Case of Multiple
Locations..................................................................................... 67 Screen-print 48: System Administration............................................................ 80
Screen-print 8: Installation of the Administration Suite Client............................ 68 Screen-print 49: System Administration with New System................................ 80
Screen-print 9: License Manager...................................................................... 68 Screen-print 50: Device View............................................................................ 81
Screen-print 9a: Administration Suite Client User Window............................... 69 Screen-print 51: “Add Devices” Window........................................................... 81
Screen-print 10: Insert, Edit or Delete Records................................................. 70 Screen-print 52: Device View with New Devices............................................... 81
Screen-print 11: “Print” Button........................................................................... 70 Screen-print 53: Persons View.......................................................................... 81
Screen-print 12: Export Functions in Print Preview........................................... 70 Screen-print 54: Window Persons Data ........................................................... 82
Screen-print 13: “Show/Hide” Button................................................................. 70 Screen-print 55: Persons View with New Person Record................................. 82
Screen-print 14: “Refresh” Button..................................................................... 70 Screen-print 56: Media View............................................................................. 82
Screen-print 15: Optimizing Column Width....................................................... 71 Screen-print 57: Media Data Window................................................................ 82
Screen-print 16: Column Sort Descending........................................................ 71 Screen-print 58: Media Status........................................................................... 83
Screen-print 17: Column Sort Ascending.......................................................... 71 Screen-print 59: Media View with Newly Added Medium.................................. 83
Screen-print 18: Reset Column Sort................................................................. 71 Screen-print 60: Time Profile View.................................................................... 83
Screen-print 19: Menu Item Server Configuration............................................. 71 Screen-print 61: Time Profiles Window ............................................................ 84
Screen-print 20: Window “Server Configuration”............................................... 72 Screen-print 62: Time Profile View with Newly Added Time Profile................... 84
Screen-print 21: Window “Server Configuration” after Automatic Search......... 72 Screen-print 63: Special Day View.................................................................... 84
Screen-print 22: Manual Input of the SQL Server............................................. 72 Screen-print 64: Special Days Window............................................................. 85
Screen-print 23: Menu Item E-Mail Configuration............................................. 73 Screen-print 65: Special Day View with Newly Added Special Day.................. 85
Screen-print 24: E-Mail Configuration Window................................................. 73 Screen-print 66: Locking Plan View................................................................... 85
Screen-print 25: Menu Item Device Compatibility............................................. 73 Screen-print 67: Setting up Links in the Locking Plan....................................... 85
Screen-print 26: Window Device Compatibility................................................. 73 Screen-print 68: Locking Plan View with Link.................................................... 86
Screen-print 27: “Add Entry” Window................................................................ 74 Screen-print 69: List of Modifications with Outstanding Programming Jobs .... 86
Screen-print 28: Device Compatibility Window with New Entry........................ 74 Screen-print 70: Programming Status with Active Programming Jobs.............. 86
Screen-print 29: Selection Device Template...................................................... 74 Screen-print 71: System Ready........................................................................ 86
Screen-print 30: Select Device.......................................................................... 74 Screen-print 72: Device View............................................................................ 87
Screen-print 31: Device Data Template............................................................. 75 Screen-print 73: Device Details Window........................................................... 87
Screen-print 32: Menu Item Software Settings.................................................. 75 Screen-print 74: Access Period for a Device..................................................... 88
Screen-print 33: Software Settings Window – Tab “General”............................ 75 Screen-print 75: Blocked Period for a Device................................................... 89

User Manual Administration Suite 111

 by DIRAK
Addendum

Screen-print 76: Adjustable Backlighting........................................................... 89

Screen-print 77: Add Super-User-Medium........................................................ 90
Screen-print 78: Status E-LINE by DIRAK View................................................ 90
Screen-print 79: System Notifications............................................................... 91
Screen-print 80: Programming Status............................................................... 91
Screen-print 81: Reprogramming a Device....................................................... 92
Screen-print 82: Event Log................................................................................ 92
Screen-print 83: Saving Event Log File............................................................. 93
Screen-print 84: Device Groups View............................................................... 93
Screen-print 85: Change Log............................................................................ 94
Screen-print 86: Deleting the Change Log....................................................... 94
Screen-print 87: Creating a Task Report........................................................... 95
Screen-print 88: Indicating an Interval............................................................... 95
Screen-print 89: E-Mail and File Extensions..................................................... 95
Screen-print 90: Task Report Filter.................................................................... 96
Screen-print 93: Selection Access Period......................................................... 96
Screen-print 94: Device Selection..................................................................... 97
Screen-print 95: Selecting the File to be Executed........................................... 99
Screen-print 96: Tasks View.............................................................................. 99
Screen-print 97: Data Import Selection........................................................... 100
Screen-print 98: Data Import Window............................................................. 100
Screen-print 99: Window AD Sync Setting...................................................... 101
Screen-print 100: Connection to the Active Directory® Successful................. 101
Screen-print 101: Link list................................................................................ 101
Screen-print 102: Active Directory® Select Branch......................................... 102
Screen-print 103: Active Directory®................................................................ 102
Screen-print 104: AD Synchronization............................................................ 102
Screen-print 105: Active Directory® Group Mapping...................................... 103
Screen-print 106: AD Group Mapping Overview............................................. 103
Screen-print 107: Opening the Diagnosis Tool................................................ 104
Screen-print 108: Diagnosing.......................................................................... 104
Screen-print 109: System Status after Diagnosis............................................ 104
Screen-print 110: Accessing the SQL-Script via Batch File............................. 106
Screen-print 111: Scheduled Task - Database Backup................................... 107
Screen-print 112: Ending Administration Suite Database Service................... 107
Screen-print 113: Restoring the TAS-Database.............................................. 108
Screen-print 114: Select Restore Source........................................................ 108
Screen-print 115: Restoring from a File........................................................... 108
Screen-print 116: Restore Options.................................................................. 109
Screen-print 117: Database Successfully Restored........................................ 109

112 User Manual Administration Suite

DIRAK GmbH DIRAK INC.

Königsfelder Str. 1 22560 Glenn Drive

58256 Ennepetal / Germany Sterling, VA 20164
Phone +49 (0) 23 33 / 837-0 Tel.: +1-703-378-7637
Fax +49 (0) 23 33 / 837-103 Fax: +1-703-378-7638
[email protected] [email protected]

www.elinebydirak.de www.elinebydirak.com