Onelog 10 Setup and Installation Guide

SETUP AND INSTALLATION GUIDE
windows Pref
INFO TECHNOLOGY SUPPLY LTD. 2018
Setup and Installation Guide

Version 10
Contents
Contents .................................................................................................................................................. 2
Onelog Forum ..................................................................................................................................... 4
Installation Information ............................................................................................................................ 5
Server Software Requirements........................................................................................................... 5
Suggested Windows Server Specification for up to 1400 concurrent users ...................................... 5
Windows Client Software Requirements ............................................................................................ 5
Suggested Windows Client Specification ........................................................................................... 6
Mobile App Requirements .................................................................................................................. 6
Onelog Data Storage / Sizing Information .......................................................................................... 6
Onelog Client-Server Data Traffic ...................................................................................................... 6
TripleA Installation ................................................................................................................................... 8
Configuring TripleA for Active Directory ........................................................................................... 11
Configuring TripleA to Authenticate against a Text File ................................................................... 17
Performing Service Tests ................................................................................................................. 30
Group Import Test ........................................................................................................................ 32
Authenticate Test.......................................................................................................................... 33
Authenticate and Import Test ....................................................................................................... 35
Viewing Current Providers ................................................................................................................ 36
Cire Server Installation .......................................................................................................................... 38
A Cire Database Already Exists (Not applicable for a Fresh Install) ................................................ 45
Configuring Cire Mail Components ....................................................................................................... 47
Cire Integrated Mode ............................................................................................................................ 53
Create New App Pools ..................................................................................................................... 53
Checking the Application Pool is set to Network Service ..................................................................... 55
Onelog Server Installation ..................................................................................................................... 58
A Onelog Database Already Exists (Not applicable for a New Install) ............................................. 63
Onelog Integrated Mode ....................................................................................................................... 64
Create New App Pools ..................................................................................................................... 64
Checking the Application Pool is set to Network Service ..................................................................... 66
Allow ISAPI and CGI Restrictions for ASP.NET 4 ................................................................................ 69
Switching to Integrated mode using the new AppPool ......................................................................... 71
IIS Reset in Windows 2012 R2 Server ............................................................................................. 73
Client Installation ................................................................................................................................... 74
The following browser versions on Windows are supported ............................................................ 74
The Installer package ....................................................................................................................... 74
Manual Installation of the Onelog Client ........................................................................................... 74
Silent Installation of the Onelog Client .............................................................................................. 81
Creating an admin MSI package .................................................................................................. 81
Installing an admin package on a client computer ....................................................................... 81
MSI Parameters............................................................................................................................ 82
Automatic Updates ........................................................................................................................... 83
How the update works .................................................................................................................. 83
Notes ............................................................................................................................................ 83
Installation .................................................................................................................................... 84
Installing from the GUI .................................................................................................................. 84
Silent Install .............................................................................................................................. 84
Log Automatic Update .................................................................................................................. 84
Adding Browser Extensions .............................................................................................................. 85
Adding Chrome Extension ............................................................................................................ 85
Manually add the Chrome extension ....................................................................................... 85
Automatically add the Chrome extension ................................................................................ 85
Notes when using the Chrome extension in a VDI environment. ............................................ 85
Adding Firefox Extension ............................................................................................................. 86
Manually add the Firefox extension ......................................................................................... 86
Automatically add the Firefox extension .................................................................................. 86
Adding Edge Extension ................................................................................................................ 86
Onelog Edge Installation Instructions ...................................................................................... 86
© INFO TECHNOLOGY SUPPLY LTD. 2001-2018
2
Manual Installation of the Onelog Edge extension .................................................................. 87

Installing an admin package on a client computer ................................................................... 88
Automatic Update ..................................................................................................................... 88
Automatic Passwords Configuration ............................................................................................ 89
Automatic Updates ....................................................................................................................... 90
Auto Logoff from Websites ........................................................................................................... 90
Uninstalling/ Reinstalling/Upgrading ............................................................................................. 90
TripleA Uninstallation ............................................................................................................................ 91
Cire Uninstallation ................................................................................................................................. 92
Client Uninstallation (Manual) ............................................................................................................... 94
Client Uninstallation (Silent) .................................................................................................................. 95
3
Onelog Forum
Onelog has its own online forums which have both a web interface and an e-mail list feature. The
forums are the place for Onelog users to discuss the usage of the product and suggest possible
improvements to the software.
Please note that the first port of call for all technical support queries should always be ITS
Technical Support.
To join the Onelog Forum discussion, please visit:

http://forum.onelog.com/
4
Installation Information
Onelog has both a Windows Server and Windows Client that must be installed on your network to
create a Onelog system. If using Onelog Mobile the app must also be installed from a suitable app
store. The following are the requirements for these platforms.
Server Software Requirements

The Onelog Server requires the following:
 Microsoft Windows 2008 / 2012 / 2016 Server with all the latest Service Packs and updates
(32-Bit & 64-bit). Recommended 2012 / 2016 64bit.
 Microsoft .NET Framework 4.0
 Microsoft Internet Information Services (IIS) with ASP.NET installed and enabled
 Microsoft SQL Server 2012/2014/2016 (including the free Express Editions*) with the latest
Service Pack, installed in Mixed Authentication Mode.
 An Internet connection to sync scripted resource definitions and Onelog Mobile configuration
(this can be via a proxy server)
o Firewall requires outbound ports 80/443 to be open for the following domains
 cloud.onelog.com
 scripts.onelog.com
Please note that Onelog can utilise a remote Microsoft SQL Server resident on your network.
Please note that Microsoft SQL Express Editions do not include SQL Server Integration
Services and cannot be used as Onelog’s data store if Client-Matter chargeback is required.
They are also limited in capacity.
Suggested Windows Server Specification for up to 1400

concurrent users
 One 2.0 GHz dual-core or better
 4 GB RAM minimum 8GB RAM or better recommended
 8 GB free disk space or better
 We recommend a 64-bit server platform, in particular Windows 2016 Server because of
certain efficiencies in IIS
 Virtual servers are fully supported.
Windows Client Software Requirements

The Onelog Client requires the following:
 Microsoft Windows 7 / Windows 8 Desktop / Windows 10 Desktop / 2008 or 2012 Terminal

Server with all the latest Service Packs and updates (32 and 64 bit)
 Microsoft .NET Framework 4.0
 Compatible Browsers
32bit Windows 7 – IE versions 9, 10, 11
32bit Windows 8/8.1 – IE versions 10, 11
64bit Windows 7 – IE versions 9, 10, 11 with Enhanced Protection Mode switched Off
64 bit Windows 8/8.1 – IE versions 10, 11 with Enhanced Protection Mode switched Off
64 bit Windows 10 – IE 11 with Enhanced Protection Mode switched Off
Firefox 50+
Chrome 40 +
 When using the client automatic update feature the client needs outbound communication to
be open on ports 80/443 to connect to the domain
o cloud.onelog.com
5
Suggested Windows Client Specification

 1024 MB RAM or better
 100 MB free disk space or better
Mobile App Requirements

The Onelog Mobile App requires the following:
 iOS 10.0 and above on iPhone, iPad.
 Android v6 (Marshmallow) and above on both Phone and Tablet
 Windows 10 (Windows Store App)
 MacOS 10.11 and above (El Capitan or newer)
Onelog Data Storage / Sizing Information

The following data is subject to change but is correct when published
Server Installation – hard disk space required 35 MB

Windows Client Installation – hard disk space required 10 MB
Database Size – initial installation 5 MB
Database Size – Estimated yearly size 1 GB
Onelog Client-Server Data Traffic

The following data is estimated based on an anticipated average installation/configuration. The actual
data transferred changes depending on configuration of any particular resource.
Client Logon Data 12 KB

Client Logoff Data 1 KB
Obtain resource configuration (average) 2 KB
Upload Resource Usage Statistics 40 KB
Server Connection Check 1 KB
To calculate the average amount of data transferred per user, use the following calculation:
No. of workstation logons per day X (Client Logon data + Client Logoff Data)
+ Number of resources connected to per day X (Obtained Resource Configuration + Uploaded Resource Usage
Statistics) + Duration of Workstation logged on time in minutes X Server Connection Check ÷ 2
6
Please note that Microsoft SQL Express Editions do not include SQL Server Integration
Services and cannot be used as Onelog’s data store if Matter Number chargeback is required.
Please note that when installing / upgrading to the latest Onelog release a patch needs to be
present on a Windows 2008 (non R2 IIS7) server. In essence we always recommend that the
server should be patched and in this case may not need to apply this update.
However if you have issues where the server is stuck on the My Library page displaying
“Loading” please look to apply the following patch from Microsoft:
http://support.microsoft.com/kb/980368
A update is available that enables certain IIS 7.0 or IIS 7.5 handlers to handle
requests whose URLs do not end with a period
Describes an update that enables certain IIS 7.0 or IIS 7.5 handlers to handle
URLs of requests that do not end with a period. The update provides this
support for handlers that are mapped to requests that have a "*." format.
Read more...
7
TripleA Installation
To install TripleA double click on the installation program AAAStandalone.exe, which is located in the
Shared Components folder on the download site. You may be prompted to install the Microsoft .NET
2.0 Framework if it is not already present on your server. You must install this to use TripleA.
Click Next unless you wish to change the installation folder.
8
Click Next to start the installation.
Upon completion, the above screen will be shown. Click Finish.
9
After installation the TripleA Service will be installed, by default the service will listen on port 7889 on
the installed computer. This is only used for internal communications within the server so firewalls
should not be an issue. If you wish to change this port you should edit the AAA.exe.config file and
change this line:
<add key="listenPort" value="7889"/> value
Once TripleA is installed, it is necessary to configure it to authenticate against either Novell or Active
Directory, depending on the directory you have in use at your organisation. Please observe the
following steps when configuring TripleA for either Active Directory or Novell eDirectory.
If you intend to configure TripleA to authenticate against LDAP, SIP2 or an ODBC-compliant

database please contact ITS Support.
10
Configuring TripleA for Active Directory

To begin configuring TripleA, use the TripleA Wizard in Programs  TripleA. This will display the
following dialogue.
Click on the Add button.
11
Select Active Directory from default configurations.
12
Fill in the remaining details.
Provider Name This is a friendly title and can be anything you want.
Server The IP address or NetBIOS name of the server (click Add to add it to the list
of servers).
You can add multiple servers per provider, they will all have the same connection details (apart from
IP address or NetBIOS name) this is for use when you have alternative directory servers that you
want to use if the primary server is not available.
Click Next to continue.
13
This screen asks for the identity of a user who is able to access and search the directory.
Check the box next to Link Authentication Details, which will pass the same parameter from the
Search Authentication Details to ‘Import Authentication Details’ or enter the username and password
if it is different (it is same in most cases). This is the identity of a user who is able to access the
directory and import data. On some systems this user may differ from the user that performs
authentication so two different users can be specified if required.
Please note that in a Windows Active Directory environment the SamAccountName format of
domain\username must always be used.
Please note that the wizard verifies information as it progresses. If the username or password
is incorrect you will be unable to proceed.
The next screen requires you to state whether SamAccountName or UserPrincipalName will be used
as the User Identifier and Return User Identifier values.
14
Please note that in a Windows Active Directory environment the SamAccountName format of
domain\username must always be used.
There are no additional settings for AD so you will next be prompted to start the service.
15
Click Start Service or Restart Service to start or restart the TripleA service.
Please note that when any Configuration settings for a provider are changed the service must
be restarted. The service is created to auto start but is not initially running.
16
Configuring TripleA to Authenticate against a Text File

Before we can continue to add a Text file provider type, we first need to create an environment for the
provider.
To begin configuring the environment, use the TripleA Mapping Manager in Programs  TripleA.
This will display the following dialogue.
17
Step 1 Enter a new name for the environment in the Environment Name field. This can be
any friendly name.
Step 2 Select the Common Field Names that applies in your environment. The text file
should contain details such as the Username, Password, Groupname, Finestatus,
etc. Please ensure that you select all that apply.
Stage 3: Allows you to browse to the folder on your server where the file is located.
Stage 4: The mapping for the selected file is set at this stage.
Once you have entered an Environment Name of your choice you are in the position to continue
mapping the file.
Select the names under the Common Field Names. By clicking the arrow button it moves the selected
fields from the Common Field Names section to the Mapped Fields section.
Please note that you can also select multiple field names by holding down the CTRL key and
clicking the required fields and then you can us the double arrow button to move the selected
field files to the ‘Mapped Fields’ section.
Once this task is completed the screen will look similar to the one shown below.
18
Click on the Browse button.
19
Browse to the file and once located and click open. This will apply the location of the text file in the
Example File Location’ field. Select the delimiter used in the text file from the options, comma, tab or
other.
20
Click on the Set File Map button to set the mapping for the selected file.
21
A dialogue will show as shown above. Here you will need to map the fields in the text file to the
mapping fields you have selected. In the above example the columns in the file represents username,
password and group name.
To map the username column from the text file to the Username field, you have to click on the Col#1
text under the File Fields section, which will select the whole column and then click on the row next to
the Username field in the Field Mapping section.
This will map the first column in the text file to the Username filed as shown below.
The same steps should be applied to map the rest of the existing columns.
22
Click OK to continue. This will navigate you back to the Main Menu.
23
You will notice the file located in the Environment List section. Click on the Save Environment button
to save the environment created.
24
To begin configuring TripleA, use the TripleA Wizard in Programs  TripleA. This will display the
following dialogue.
25
Select File from Default Configurations and click Next to continue.
Fill in the remaining details.
Provider Name This is a friendly title and can be anything you want.
Environment Clicking on the drop down menu will provide you with the list of
environment(s) created in the TripleA Mapping Manager. Select the desired
environment from the drop down list.
Click the Browse button next to the File Location field. This will open a window where you browse to
the required text file.
26
Click Open after selecting the text file.
27
28
Click Start Service or Restart Service to start or restart the TripleA service.
Please note that when any Configuration settings for a provider are changed the service must
be restarted. The service is created to auto start but is not initially running.
29
Performing Service Tests
Click on the listed provider (shown above as Universe) and then the Service Tests button.
30
Import User Test

Select Import User to perform this test and enter a username you would like to search for, as shown
below.
Click on Run Service Test to start the test. If successful you should see returned XML from the
TripleA service in a similar format as shown above. The XML will clearly state if the import failed.
31
Group Import Test

The Group Import Test confirms that users groups are successfully found. The screenshot below
shows the result of a successful Group Import Test.
32
Authenticate Test
This is an example of a successful Authenticate Test.
33
Below is what happens when the wrong password is entered.
34
Authenticate and Import Test

This test will run the authenticate and import user test for the mentioned user at the same time.
35
Viewing Current Providers
Clicking Main Menu on any part of screen will take the user to the main menu which displays the
provider list.
Select the Provider you wish to edit and click Edit. You then have the opportunity to change any of
the options configured. You may also notice the Edit Groups button. This allows you to select which
groups to include (or exclude) as shown on the next screen. The default is that all groups are
imported.
36
You can EITHER exclude or include groups you cannot use a combination of both.
Alternatively, clicking Use ONLY Default Group will totally ignore all groups defined in the directory
and put all users into a group called _general.
Please note that in an Active Directory environment you may wish to eliminate the display of
numerous user groups by configuring TripleA to only include Domain Users.
If you have made any changes to the configuration you must ensure that you restart the service
before performing tests again.
37
Cire Server Installation

Please note that if you are running ASP.NET 4.0 in 32-bit version on a 64-bit server please
contact ITS Technical Support for assistance prior to installation.
Please note that Cire Server 2.2 or higher is required to enable “Automated Reports” in
Onelog 8.7.
Once your server is prepared to the specifications detailed previously you can commence the
installation of the Cire Server by double-clicking Cire Server Setup.exe, which is located in the Shared
Components folder on the ITS download site.
38
The subsequent screen shows the End User Licence Agreement, which must be accepted if the
installation is to continue.
Click Next to continue. A dialog will then be shown asking you to select the drive and path where Cire
will be installed. It also shows the amount of disk space required and the amount of space available.
Use the change button to change the Drive and Path if required.
39
Select the option Install all Cire Components. Click Next to continue.
Please note that you should NOT select the option Install only “Cire Mail Components” as
40
this will install the Cire Mail Service only. ONELOG requires ALL Cire components to be
installed.
This screen requests three pieces of information.
Database Server The name of the server that is running Microsoft SQL Server that
Cire will use to host its database. Often this will be the name of the
server on which you are installing the Cire Server software.
Database Username The user name that Cire should use to connect to SQL Server to
install the Cire Database. This username is normally ‘sa’, so this is
pre-filled as the default value.
Database Password The Password for the Database administrator name specified above.
Please note that if you have installed the preconfigured version of Microsoft SQL Server
2005 Express Edition included in the Shared Components folder on the download site then
your ‘sa’ password will be “manager”.
On clicking Next the Cire installer will check the credentials specified and test whether it can
successfully connect to your SQL server.
Next you will be asked to supply your Cire Product Licence File.
41
You can either type in the path and name of the licence file or browse for a valid licence file and the
select file dialog will show which is used to navigate to the location of your Cire Licence file. Select the
Licence File and click the Open button.
42
A confirmation dialog will then show displaying all the options selected.
Click on Next when you are happy to proceed.
43
If anything is incorrect, please use the Back button to return to the appropriate dialog and make any
necessary changes.
If you are happy to proceed click Next to begin the installation.
The Cire database will be created. During this period it is normal to see a Command Prompt running
OSQL.exe for a significant amount of time while the Cire database is being created.
Do not close the command prompt window!
You will be notified that Cire is being configured.
In order for IIS to function correctly click Yes. If you click No, IIS will have to be restarted manually or
the server rebooted.
When the installation has finished a confirmation screen will be displayed.
44
Click Finish. Your Cire Server is now installed.
A Cire Database Already Exists (Not applicable for a Fresh

Install)
If a Cire database already exists on the SQL server you will be presented with two additional
installation steps (warnings) after entering the database parameters mentioned in step five.
The setup will continue using your old database and upgrade it if necessary. As per the message
shown above it is recommended that you back-up your database before proceeding.
If you do not wish to use your old Cire database please contact ITS Support or your reseller to discuss
the implications of dropping your Cire database.
45
As above it is recommended that you back-up your database before proceeding.
Click OK or Cancel to continue.
Please note that before continuing with the Onelog installation, new and existing customers
must ensure to import the groups from their organisation’s Directory (Microsoft Active
Directory, Novell Directory Services, RM or a Flat file, a SIP2 compliant system or an ODBC
compliant database) into Cire. “Importing Groups in Cire” is explained in the Cire
Administration Guide.
46
Configuring Cire Mail Components

Once the Cire Server is installed you can continue to configure the Cire Mail Components.
To start the please go to:

Start Menu > Programs > Cire Server > Cire Mail Services
47
Enter a friendly name in the Provider Name field as shown in the above example. Next click on the
Send button to continue.
48
Select the Enable Send box, the following fields in will must be completed.
E-mail Address The e-mail address entered here must be a valid e-mail address. All
e-mail booking receipts will be sent from this e-mail address.
Server The Server name to enter here will be your preferred mail server.
E-mail Name The e-mail Name can be a friendly name. This name will be
displayed in the user’s e-mail client when they receive an e-mail-
mailed booking receipt.
Port Port 25 is the default SMTP port however if your mail server uses a
different port you can enter it here.
Authentication Type The authentication type provides you with three options. Anonymous,
PAP and SSL.
Username A username allowed to logon to your e-mail server and send e-mail
from the E-mail address specified.
49
Password The password for the username allowed to logon to your e-mail server and
send e-mail from the e-mail address specified.
Once the fields above completed click on the Finished button. A confirmation dialogue will show
displaying the new Account Provider, then ensure that the Cire Service is started. Click on the Start
Service button.
Select the provider account and then click on Test Service. This will show the following dialogue.
50
Check if the e-mail address is correct and click Test Service.
51
A test e-mail will also be sent to the address specified in the Send Email Address box.
52
Cire Integrated Mode

When Cire is installed on a Windows 2008 / 2012 R2 Server by default it is usually configured to use
the Classic AppPool. This is a mode which makes later versions of IIS behave like IIS6.0 (2003
Server). While Cire will work with this configuration, it will not take advantage of the performance
enhancements offered by the newer versions of IIS.
Follow the instructions below that show how to update the IIS Server configuration so that the newer
Integrated mode is used instead.
Create New App Pools

The first step is to create a new Application Pool and then be configured appropriately to work in
Integrated mode.
To create a new Application Pool in 2012 R2 Server open IIS Manager in Server Manager > Local
Server > Tools > Internet Information Services (IIS) Manager and open the Application Pool
section.
In Windows 2008 R2 use Start > Administrative Tools > Internet Information Services (IIS)
Manager.
From the Actions Pane click on Add Application Pool, call it Cire Integrated.
53
Set .Net Framework Version to .Net 4.0.xxxxx
Click OK to continue.
Please note that if an earlier version of Cire is installed it should run only in Classic .Net
AppPool.
If you are running Cire V2.1.8+ then create a new Application Pool with the settings shown
above using used the .NET Framework version V2.0.xxxxx
If Cire V3+ is being used then the .NET Framework version should be set to V4.0.xxxxx.
54
Checking the Application Pool is set to

Network Service
In order to use Cire with Windows 2012 R2 Server the following changes should be made to IIS in
Server Manager > Local Server > Tools > Internet Information Services (IIS) Manager.
Manager.
For Cire Integrated Application Pool, right click the Application Pool and select Advanced Settings.
In the Process Model section select the top line Identity.
55
Next use the picker (three dots) to change the value to Built-in Account > NetworkService.
Now change the ApplicationPoolIdentity to NetworkService. Click OK to continue.
56
57
Onelog Server Installation

Please note where organisations use multiple servers as opposed to one Onelog server a new
registry key must be added on each server when “Enable Onelog Mobile for network
PCs” and “Allow data to be transferred through Central Server Sync” is enabled.
This registry key is called “PrimaryEventServer” and is located in:

HKEY_LOCAL_MACHINE\SOFTWARE\ITS\Onelog\Server
Once your server is prepared to the specifications detailed previously you can commence the
installation of the Onelog Server by double-clicking Onelog Server Setup.exe, which is located in the
Onelog folder on the ITS download site.
The next screen shows the Onelog End User Licence Agreement, which must be accepted if the
installation is to continue.
58
In the screen below select either Local Server or Remote Server depending on the location of your
SQL Server. In this example we have installed SQL Server service on the Local Server.
Click Next to continue. The Database Parameters screen will then be shown.
59
This screen requests three pieces of information.
Database server The name of the server that is running Microsoft SQL Server that
Onelog will use to host its database. If SQL is installed locally this will
be the name of the server on which you are installing the Onelog
Server software.
Database administrator
name The user name that Onelog should use to connect to SQL Server to
install the Onelog Database. This user name is normally ‘sa’, so this
is pre-filled as a default value.
Database administrator
password The Password for the Database administrator name as specified
above.
On clicking Next the Onelog installer will then check the credentials specified and test whether it can
successfully connect to your SQL server.
60
The next step is to type in the server name where Cire is installed. It is important that you enter the
correct server name. If Onelog is to be accessed remotely pleased enter the full DNS name omitting
http://. Do not enter localhost.
61
If anything is incorrect, please use the Back button to return to the appropriate dialog and make any
necessary changes. When everything is correct please click Next to begin the installation.
Immediately after clicking Next the Onelog database will be created.
When the installation has finished a confirmation screen will be displayed.
Click Finish. Your Onelog Server is now installed.
62
A Onelog Database Already Exists (Not applicable for a New

Install)
If a Onelog database already exists on the SQL server you will be presented with an additional
installation step (warning) after entering the database parameters mentioned in step five.
The setup will continue using your old database and upgrade it if necessary. As per the message
shown above it is recommended that you back-up your database before proceeding.
If you do not wish to use your old Onelog database please contact ITS Support or your reseller to
discuss the implications of dropping your Onelog database.
Please make sure you backup both your Onelog & Cire databases before uninstallation. The
Cire database is as critical to your Onelog system as the Onelog database.
63
Onelog Integrated Mode

When Onelog is installed on a Windows 2008 / 2012 R2 Server by default it is usually configured to
use Classic AppPool. This is a mode which Onelog makes later versions of IIS behave like IIS6.0
(2003 Server). While Onelog will work with this configuration, it will not take advantage of the
performance enhancements offered by the newer versions of IIS.
Follow the instructions below that show how to update the IIS Server configuration so that the newer
Integrated mode is used instead.
Create New App Pools

The first step is to create a new Application Pool and then be configured appropriately to work in
Integrated mode.
To create a new Application Pool in Windows 2012 R2 Server open IIS Manager in Server Manager
> Local Server > Tools > Internet Information Services (IIS) Manager and open the Application
Pool section.
Manager.
From the Actions Pane click on Add Application Pool, call it Onelog Integrated.
64
Set .Net Framework Version to .Net 4.0.xxxxx
65
Checking the Application Pool is set to

Network Service
In order to use Onelog with Windows 2012 R2 Server the following changes should be made to IIS in
Server Manager > Local Server > Tools > Internet Information Services (IIS) Manager.
Manager.
For Onelog Integrated Application Pool, right click the Application Pool and select Advanced
Settings.
In the Process Model section select the top line Identity.
66
Next use the picker (three dots) to change the value to Built-in Account > NetworkService.
Now change the ApplicationPoolIdentity to NetworkService. Click OK to continue.
67
68
Allow ISAPI and CGI Restrictions for

ASP.NET 4
In order for Onelog Web Components to work correctly, the Onelog must be configured to Allow the
ISAPI and CGI Restrictions or the web interface will not function correctly. To check this, follow these
steps.
Once you have installed Onelog on the Windows 2012 R2 Server, open Internet Information Services
Manager. This is located in Server Manager > Local Server > Tools > Internet Information
Services (IIS) Manager.
Manager.
Select the Server name then click on the ISAPI and CGI Restrictions icon which will show the
screen below.
69
Ensure that ASP.NET v4.0 and is set to Allow. Do this for both ASP.NET v4.0 in the list.
70
Switching to Integrated mode using the new

AppPool
Up until now we have been doing the groundwork to switch Onelog from using Classic mode to using
the newer Integrated mode of running applications in IIS. Onelog is still running in Classic mode
therefore the next step is to switch over to the new configuration.
In an ideal world this should be done outside office hours as all access will temporarily be suspended
to the server following the transition.
To switch over in Microsoft Windows 2012 R2 Server, open IIS Manager in Server Manager > Local
Server > Tools > Internet Information Services (IIS) Manager.
Manager.
In the left hand pane open Sites and locate the Onelog entry. Right click on Onelog and select
Manage Application > Advanced Settings.
Change the Application Pool to Onelog Integrated.
71
It is best to then reset IIS by performing an IIS reset.
72
IIS Reset in Windows 2012 R2 Server

Click on the Start button and select Run.
Type cmd in the field provided and click OK.
The Command Prompt window will open as shown below. Type iisreset and click Enter.
After a few seconds the message Internet services successfully restarted will show.
73
Client Installation
Please note that .NET Framework 4.0 is required on Client PCs. If
Microsoft .NET 4.0 Framework is not present on client machines Onelog will fail to function.
The MSI installer always installs the Internet Explorer extension. See below for more
information on how to install the Chrome, Firefox and Edge extensions
Automatic Updates are enabled by default for the Onelog Client from version 8.8 and above.
More information about Automatic Updates is in the section Automatic Updates
The following browser versions on Windows are supported

 Internet Explorer 7, 8, 9, 10 & 11
 Firefox 50 and above (validated up to 60.0.1)
 Chrome 40 and above (validated up to 67.0.3396.62)
The Installer package

The Onelog Client installer is available as a 32bit installer, OnelogClient.msi
The 32 bit installer adds a 32bit version of the Internet Explorer extension. The 32bit Internet Explorer
extension is supported on the following platforms and IE versions.
a) 32bit Windows XP – IE versions 7, 8
b) 32bit Windows 7 – IE versions 9, 10, 11
c) 32bit Windows 8/8.1 – IE versions 10, 11
d) 64bit Windows 7 – IE versions 9, 10, 11 with Enhanced Protection Mode switched Off
e) 64 bit Windows 8/8.1 – IE versions 10, 11 with Enhanced Protection Mode switched Off
f) 64 bit Windows 10 – IE version 11 with Enhanced Protection Mode switched Off
Manual Installation of the Onelog Client

Once your client is prepared and meets the system requirements you can commence the installation
of the Onelog Client by double-clicking the OnelogClient.msi which is located in the Onelog Client
folder on the ITS download site.
74
75
The following screen displays the Onelog End-User Licence Agreement which must be accepted if
setup is to continue.
The screen below allows you to change where the Onelog Client is installed, ITS does not
recommend that this is changed unless necessary.
76
The following screen requires that you enter the location of the Onelog Server; acceptable values are
the server’s NetBIOS name, its DNS name or IP address. The radio buttons shown below determine
whether the client should connect to the server using HTTP or HTTPS.
Please note that your Onelog server must be configured accordingly via IIS.
The next screen requires that you state whether the Onelog client should run in Offsite or Network
Mode. In Offsite mode the client will prompt the user for their username and password. In Network
Mode the Onelog client will interrogate the local PC to ascertain who is logged on.
Please note that it is possible to disable Network Logon Mode from the server by adding a
registry key on the server machine. Please contact ITS Technical Support for assistance.
77
The next screen asks if you want to install the extension for Firefox or Chrome (the extension for IE is
always installed)
If the Firefox extension is requested, the Firefox browser will open and navigate to
https://extensions.onelog.com if Firefox is version 48 or above, if the Firefox version is 47 or below
then the MSI will install the add-on in Firefox.
78
If the Chrome Extension is requested the Chrome browser will open and navigate to the Onelog
extension page in the Chrome Web Store. The extension can then be installed.
The next screen allows you to force the Onelog client to start immediately after installation by ticking
the check box provided.
79
Click Install to begin the installation as shown below.
Upon the completion click Finish. The Onelog Client is now installed.
80
Silent Installation of the Onelog Client

The Onelog Client installer can be used normally as an interactive installer or settings can be
preconfigured using the MSI admin mode to create an admin MSI package.
Creating an admin MSI package

Essentially using the MSI admin mode allows you to pre-configure the Onelog Client MSI options so
that installation is easier on multiple machines. The basic command to do this is:
msiexec.exe -a "COMPLETE PATH\OnelogClient.msi" TARGETDIR=”COMPLETE PATH

OUTPUT”
-a denotes admin mode

TARGETDIR denotes the location where the resulting output will be placed. It must be configured as
a complete path to a folder (the folder will be created)
The admin mode does not work using the installer screens, so ANY options you wish to change have
to form part of the command line when you use admin mode. If they are not specified the default
values from the Parameter Reference table below will be used.
As a minimum you should configure the parameter for the SERVERNAME and LOGONTYPE, this will
look like:
msiexec.exe -a "COMPLETE PATH\OnelogClient.msi" SERVERNAME=XXXXXX

LOGONTYPE=MachineLogonName TARGETDIR=”COMPLETE PATH OUTPUT”
A complete configuration would look like this:

LOGONTYPE=MachineLogonName SECSERVER=false START_CLIENT=1 WRITELOG=false
MOBILEMODEOFF=false LOGONPORT=2341 SERVICESTATUSPORT=4422
SERVICETOOLBARCOMMPORT=12345 TARGETDIR=”COMPLETE PATH OUTPUT”
N.B. You may notice that there is no option to specify the installation folder. This is because the
installation folder MUST be specified when installing the client on any particular computer. See below.
Installing an admin package on a client computer

The command line to install the Onelog Client on a computer is:
msiexec.exe -i "COMPLETE PATH SET IN TARGETDIR ABOVE\OnelogClient.msi" /qn

INSTALLDIR="C:\Program Files\ITS\Onelog\Client"
INSTALLDIR denotes the destination installation folder

-i denotes that the package will be installed
81
MSI Parameters
Parameter Description
SERVERNAME The DNS/IP or machine name of your Onelog Local

Server
LOGONTYPE Determines how users will logon to Onelog, two valid
options.
FormLogonName – The user will be prompted to fill in a
logon form to connect to Onelog
MachineLogonName – The user will be automatically
logged onto Onelog using their network logon
SECSERVER Is the Onelog Local Server secure? You must have a
valid SSL certificate on your Onelog Local Server for this
to work. You should never set it to true unless it really is
secure.
START_CLIENT Determines whether the Onelog Client is started following
successful installation.
LOGONPORT Internal Component Communication Port can be changed
to any other non-used port number if conflicts exist
SERVICESTATUSPORT Internal Component Communication Port can be changed
SERVICETOOLBARCOMMPORT Internal Component Communication Port can be changed
WRITELOG Determines if the Onelog Client should write diagnostic
log files.
MOBILEMODEOFF Disable the mobile mode functionality
Parameter Reference
Parameter Default Alternative
SERVERNAME ServerName
LOGONTYPE FormLogonName MachineLogonName
SECSERVER false true
START_CLIENT 1 0
LOGONPORT 2341
SERVICESTATUSPORT 4422
SERVICETOOLBARCOMMPORT 12345
WRITELOG false 1 = LOG_ERROR
2 = LOG_INFO,
3 = LOG_EXTRA_INFO
82
Automatic Updates
Automatic Updates are enabled by default for the Onelog Client.
From Version 8.8 of the Onelog Client, the client has the ability to update itself automatically. This
allows for automatically updating the Client Service and the Internet Explorer add-on.
Updates to the extensions in Chrome, Firefox and Edge are handled separately.
The Automatic Update will only work for client versions 8.8 and above.
By default, the Update is taken from a server on the internet managed by ITS, and this will always
have the latest released version of the client. The connection to this server is performed over SSL.
There is the option to configure a web server that you manage to perform the update, so that your
users will only update to a version that your organisation has verified. More information is in the
Special Configuration Guide – Setting up a local update web Server
Automatic Updates can be turned off. See ALLOWUPDATE MSI parameter below.
How the update works

On first installation of the client from the MSI, the client will check for an update within 2 hours of
starting.
After the update check is run, the client stores the time that the check happened. The next check for
updates will happen 2 days after the last update check was run.
If an update to the client is required and IE is running then the client will try to update again within 1
hour. If IE is not running then the client will update immediately.
Notes
The Automatic Update does not run for clients installed on Citrix XenApp or Terminal Server
The time that the client was last updated and the current version are shown in the system tray on
mouse hover over About.
The client version is not updated inside Add\Remove Programs. This means that if the installed
version was 8.8.1.0, and the auto update was run to push the files for version 8.8.3.0; then if you ran
the MSI for version 8.8.2.0, the 8.8.2.0 version would be installed. After installation of the 8.8.2.0
version though, the client would be automatically updated again to 8.8.3.0.
The update process creates registry settings in the same registry location as other client registry
values:
HKLM\SOFTWARE\Wow6432\ITS\Onelog\Client
HKLM\SOFTWARE \ITS\Onelog\Client
ClientUpdated true\false
83
LastUpdateCheckTime date and time of last update check

UpdateOnRestart true\false
ClientUpdatedTime date and time the client last actually updated
These values are set during the update process, and tell the service how to behave. Generally they
should never be updated manually. However to force the update to run again sooner if needed, then
setting the value of LastUpdateCheckTime to an empty string and then restarting the client machine
will cause an update check within 2 hours of restarting.
Installation
Installing from the GUI

Run the installer from the GUI and the default values for the installer variables are used.
Silent Install
If you want to use Automatic Update with the default configuration then you can create the admin MSI
package as described in Silent Installation of the Onelog Client
The MSI parameters that can be set to change how Automatic Update works are described below:
ALLOWUPDATE true or false - default value is true
When set to true the Automatic Update runs
USELOCALUPDATE true or false - default value is false
When set to true the automatic update will use
the URL set in LOCALUPDATEURL to do the
update.
LOCALUPDATEURL The path to the local update files. The default
value is blank.

ALLOWUPDATE=”false”
This will stop client updates

USELOCALUPDATE=”true” LOCALUPDATEURL=”http://updateserver/onelogfiles/”
The update files are taken from the local update URL specified.
Log Automatic Update

A log of the update can be written in the same location as the Onelog Client files:
C:\Program Files (x86)\ITS\Onelog\Client
C:\Program Files\ITS\Onelog\Client
The file name is “OnelogClient Update Log.txt”
To turn on the update logs, then you just need to turn the client logs on.
Set the client logs by setting the Registry Value of WriteLog to 1, 2 or 3
84
Adding Browser Extensions

Please note that the Firefox and Edge extensions are not supported on Terminal Services or
Citrix XenApp*
Adding Chrome Extension

Supported versions of Chrome
 Chrome 40 and above
Manually add the Chrome extension
A user can add the Chrome extension manually by opening a Chrome browser and going to the page
https://extensions.onelog.com and following the instructions.
N.B. This is not supported when using Chrome on Terminal Services/Citrix, installation should use Group Policy.
Automatically add the Chrome extension

Administrators can force the installation of Chrome extensions using Group Policy.
To start you need to download the Chrome group policy templates from
http://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip
Unzip and add the new templates using the Group Policy Editor (Add/Remove Templates)
This will provide all the available policy settings for Chrome.
To automatically install the Regular Onelog Chrome extension using Group Policy, enable and add
an entry in
Google\Google Chrome\Extensions\Configure the list of force-installed apps and extensions
use value
onjjmhhddjeopkhboiehpmhihjmoecpi;https://clients2.google.com/service/update2/crx
To automatically install the Terminal Services Onelog Chrome extension using Group Policy, enable
and add an entry in
Google\Google Chrome\Extensions\Configure the list of force-installed apps and extensions
use value
mfcjpojnlmbhdendecninohbibcokaeh;https://clients2.google.com/service/update2/crx
Notes when using the Chrome extension in a VDI environment.

We recommend that you do not install the extension as part of a base image but rather let the policy
outlined above install it for the user.
There are many different VDI environments and they can be configured in different ways.
85
For more information about installing the Onelog Client in a VDI environment see the document
“Installing client in a VDI Environment”
Adding Firefox Extension

Supported versions of Firefox
 Firefox 50 and above (validated up to 60.0.1)
Manually add the Firefox extension

To install the client a user can navigate to https://extensions.onelog.com in a Firefox browser and
click “Download”. After accepting the prompts, the extension will be installed and will automatically
update.
Automatically add the Firefox extension

See the document “Installing the Firefox extension in a corporate environment”
Adding Edge Extension

Onelog Edge Installation Instructions
Requirements
The extension for Edge has several requirements before it can be installed.
 Windows 10 Creators Update (1703+)

 Sideloading of apps needs to be enabled
 The machine needs to be joined to a domain
 Onelog base client, version 9+
 Extensions must be enabled in Edge
Enable Sideloading
Enable using Group Policy
We recommend that Sideload Apps is enabled by Group Policy
In Group Policy Editor go to Computer Configuration\Administrative Templates\Windows

Components\App Package Deployment
Set AllowAllTrustedApps to Enabled
Enable for user
Sideloading can be enabled by a user by going to Settings->Update & Security->For Developers
and click Sideload Apps
86
Click Yes to confirm
Manual Installation of the Onelog Edge extension

The installer for Edge is called OnelogEdgeExtension.msi.
Once your machine is prepared and meets the system requirements you can begin the installation of
the Onelog Edge extension by double-clicking the OnelogEdgeExtension.msi.
Silent Installation of the Onelog Edge extension

The Edge extension can be installed silently.
Creating an admin MSI package

Using the MSI admin mode allows you to pre-configure the Onelog Edge extension MSI options so
that installation is easier on multiple machines. The basic command to do this is:
msiexec.exe -a "COMPLETE PATH\OnelogEdgeExtension.msi" TARGETDIR=”COMPLETE

PATH OUTPUT”
-a denotes admin mode
87
TARGETDIR denotes the location where the resulting output will be placed. It must be configured as
a complete path to a folder (the folder will be created)
msiexec.exe -a "COMPLETE PATH\OnelogEdgeExtension.msi" TARGETDIR=”COMPLETE

PATH OUTPUT”
Installing an admin package on a client computer

The command line to install the Onelog Client on a computer is:
msiexec.exe -i "COMPLETE PATH SET IN TARGETDIR ABOVE\OnelogEdgeExtension.msi" /qn
NOTE: The Edge extension will not immediately load in the browser. The extension
will be available in the browser after restarting the browser and waiting for a period of
time, around 30 seconds to a minute. This is a limitation of sideloading extensions
into Edge.
Automatic Update
The Edge extension will automatically update by default. To turn off automatic updates on install set
the parameter EDGEALLOWUPDATE to false in MSI install command line.
88
Automatic Passwords Configuration

If you are using the Onelog Automatic password feature you may want to turn off the native automatic
password facility in the browser. Below are details of how to do this in the supported browsers
Internet Explorer
The browser behavior can be changed through registry settings.
HKCU\Software\Microsoft\Internet Explorer\Main\FormSuggest Passwords "no"

HKCU\Software\Microsoft\Internet Explorer\Main\FormSuggest PW Ask "no"
HKCU\Software\Microsoft\Internet Explorer\Main\Use FormSuggest "no"
Setting these options to no will turn off the auto-complete settings for Forms and User names and
passwords on forms. The check boxes are still enabled so a user can turn them on again.
Chrome
The Chrome behavior can be changed with registry changes made using Group Policy*
To disable Chrome from offering to save passwords:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
PasswordManagerEnabled=0x00000000
To disable Chrome from displaying passwords in clear text that have already been saved by the user:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
PasswordManagerAllowShowPasswords=0x00000000
More details can be found at:

http://www.chromium.org/administrators/policy-list-3#PasswordManager
* From the Chrome policy page "Starting with Chromium 35, policies are read directly from the registry
if the workstation is joined to an Active Directory domain; otherwise the policies are read from GPO."
http://www.chromium.org/administrators/policy-list-3
Firefox
To turn off the setting for Firefox to remember passwords, you need to set the preference
signon.rememberSignons to false.
The preference can be locked so that a user cannot change it back. To do this you create a file called
"mozilla.cfg" and put it in the Firefox installation folder (usually C:\Program Files (x86)\Mozilla Firefox).
The file contains the two lines:

//
lockPref("signon.rememberSignons", false);
Create another file called "local-settings.js" in the default pref folder (usually C:\Program Files
(x86)\Mozilla Firefox\defaults\pref)
The file contains the lines:

pref("general.config.obscure_value", 0);
pref("general.config.filename", "mozilla.cfg");
89
Automatic Updates
The Onelog extensions for Chrome and Firefox can perform automatic updates. We recommend that
you permit the extensions to perform updates. Both browsers have frequent update cycles and
changes may be required in the extension to support later browser versions. If you have prevented
automatic upgrades of Firefox and Chrome then this is not so necessary but you will have to permit
updates to install any bug fixes.
Auto Logoff from Websites

Chrome, Firefox and will show a logoff window in the bottom right of the screen when processing a
logoff. This will appear even if you have the server option “Hide Logout Box” enabled. Both Firefox
and Chrome do not permit windows to be opened hidden as this is a potential security risk. If you do
not want logout windows to appear you should remove the Logout option from resources.
Uninstalling/ Reinstalling/Upgrading
The Chrome, Firefox and extensions cannot be removed by the Onelog installer. They should be
removed separately. If you are uninstalling to re-install again (or upgrading) the base client you do not
need to configure the Chrome, Firefox and Edge extensions again.
90
TripleA Uninstallation
This chapter details the uninstallation of TripleA. On Windows 2003 Server navigate to Control Panel,
Add or Remove Programs on Windows 2008 / 2012 R2 Server this is called Programs and Features.
Locate the entry for TripleA and click Remove or Uninstall, doing so will produce the screen shown
below.

The screen shown below will show shortly after confirming that TripleA has been removed.
Click Finish. Your TripleA Server is now uninstalled.
91
Cire Uninstallation
This chapter details the uninstallation of Cire. On Windows 2003 Server navigate to Control Panel,
Add or Remove Programs on Windows 2008 / 2012 R2 Server this is called Programs and Features.
Locate the entry for Cire and click Remove or Uninstall, doing so will produce the screen shown
below.
Click Next to continue. The screen shown below will show shortly after confirming that Cire has been
removed.
Click Finish. Your Cire Server is now uninstalled.
92
Onelog Server Uninstallation

This chapter details the uninstallation of Onelog Server. On Windows 2003 Server navigate to Control
Panel, Add or Remove Programs on Windows 2008 / 2012 R2 Server this is called Programs and
Features. Locate the entry for Onelog Server and click Remove or Uninstall, doing so will produce the
screen shown below.
Click Next to continue.The screen shown below will appear shortly after confirming that Onelog
Server has been removed.
Click Finish to complete the process.
93
Client Uninstallation (Manual)

This chapter details the uninstallation of the Onelog Client. On Windows 7 / Windows 8 navigate to
Control Panel > Programs and Features. Locate the entry for the Onelog Client and click Uninstall.
Please note that if any of the selected web browsers are open whilst uninstalling the Onelog
Client the following screenshot will display prompting you to close all applications before you
can continue the installation process. Alternatively you may leave the applications running
however a reboot may be required.
Click OK. This will remove the Onelog Client from your computer.
94
Client Uninstallation (Silent)

To perform a silent uninstall please configure your software deployment mechanism to run msiexec
with the following switches ensuring that the uninstall process is given administrative privileges.
Place the Onelog Client MSI (OnelogClient.msi) installer in an easily accessible path. Uninstalling the
Onelog Client in silent mode suppresses all user interface screens, which would appear during the
manual un-installation process. You can run uninstall in silent mode via the use of the following
command line parameters:
msiexec /x "COMPLETE PATH TO MSI \OnelogClient.msi " /quiet
95

Onelog 10 Setup and Installation Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Onelog 10 Setup and Installation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

SETUP AND INSTALLATION GUIDE

INFO TECHNOLOGY SUPPLY LTD. 2018

Setup and Installation Guide

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Manual Installation of the Onelog Edge extension .................................................................. 87

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

To join the Onelog Forum discussion, please visit:

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Server Software Requirements

Suggested Windows Server Specification for up to 1400

Windows Client Software Requirements

 Microsoft Windows 7 / Windows 8 Desktop / Windows 10 Desktop / 2008 or 2012 Terminal

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Suggested Windows Client Specification

Mobile App Requirements

Onelog Data Storage / Sizing Information

Server Installation – hard disk space required 35 MB

Onelog Client-Server Data Traffic

Client Logon Data 12 KB

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click Next unless you wish to change the installation folder.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click Next to start the installation.

Upon completion, the above screen will be shown. Click Finish.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

<add key="listenPort" value="7889"/> value

If you intend to configure TripleA to authenticate against LDAP, SIP2 or an ODBC-compliant

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Configuring TripleA for Active Directory

Click on the Add button.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Select Active Directory from default configurations.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Fill in the remaining details.

Click Next to continue.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click Next to continue.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Configuring TripleA to Authenticate against a Text File

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click on the Browse button.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click on the Add button.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Select File from Default Configurations and click Next to continue.

Fill in the remaining details.

Click Next to continue.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click Open after selecting the text file.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Click Next to continue.

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

© INFO TECHNOLOGY SUPPLY LTD. 2001-2018

Performing Service Tests