ERMCO FAQs

This article will cover how to use the Evoko Liso and its features.

Status LED colors

Passive mode

Active mode

Check-in

Calendar

Room finder

Report room equipment

Administration menu

Status LED colors

The Liso have three status LED colors:

Green - room is free for more than 10 minutes.

Amber - a meeting is about to start in less than 10 minutes and/or the room requires check-in.

Red -room is busy (amber trumps red in conflicting scenarios e.g. for back 2 back meetings).

Passive mode

When the Evoko Liso is not used, it will be in "passive mode" and show an overview of a clock and room availability, with the room name clearly visible. The watch hands show the current time, and the green areas show when the room is available while the red areas show when it is booked. here

Active mode

When moving close the proximity sensor (if enabled) will trigger and the Evoko Liso will automatically go into "active mode". Here you can see more details about the meeting room, book new meetings and extended/end ongoing meetings.

Check-in

The Check-in feature is an efficient way to prevent "ghost meetings" i.e. to free up rooms where no-one shows up for the booking.

If enabled, a check-in button will appear 10 minutes before the meetings start and remain until5-30 minutes after the meetings start. If no check-in is made on the screen during the check-in time frame the meeting will be ended short to free up the meeting room for others to use.

Calendar

The Liso have a calendar view that you can access from the active screen by pressing the calendar icon.

From the calendar you can get an overview of the rooms schedule.

You can also book meetings by tapping on an available time slot or edit/remove existing meetings by tapping on them.

Room finder

The room finder is useful to find a room that fits your needs, based on availability, location, size and equipment. From the Room Finder you can book both instant and future meetings for other rooms.You access the room finder by pressing the search icon in the top left corner.

Use the filters to find an available room suitable for your meeting.

Report room equipment

Reporting room equipment from the Liso can be an great way of signaling other users of room equipment issues and notifying the person responsible through an automated email.

You access the report screen by pressing the icon in the top right corner.

To submit a report, highlight the equipment icons and then press "Report".

In active mode the reported equipment will now be displayed in the top right corner.

Administration menu

To access the administrator panel pressADMIN LOG INat the bottom part of the report screen.

This will prompt you to authenticate as an admin using PIN/RFID.

Once authenticated the administrator panel will be shown. From the Administrator panel you can:

Button

Description

Copy logs to USB

Copies log files from the Liso to a folder calledliso_logs on the inserted USB stick.

Update via USB

Update the Liso firmware from USB stick, more information can be found.

Information

Displays information about the current configuration the Liso is running.

Reboot now

Reboots the Liso.

Network

Opens the network configuration menu where the two network interfaces (wired Ethernet and Wifi) can be configured.

Change room

Gives the option to change the room displayed on the Liso to another room in the same configuration.

Server IP

Gives the option to changes the IP address and port for the Evoko Home server the Liso is pointing to.

Diagnostics

Opens a diagnostics menu which allows for test of the LEDs, the touch panel, network connection etc.

This part will go through how to install Evoko Home in Default mode on Windows server.

Server prerequisites

Install Evoko Home

Server prerequisites

Important! The following prerequisites arerequired to be installed prior to installing Evoko Home.

Nodejs 4.8.0- Nodejsv4.8.0-x64 can be downloaded here and Nodejsv4.8.0-x86 here.

MongoDB 3.4.x - MongoDB 3.4.15 can be downloaded here.

.NET framework - .NET framework 4.5.2can be downloaded here.

A server running Windows Server 2008 R2 or later.

A static IP (the Liso units will point to this IP).

Access to booking system (e.g. Office 365) over HTTPS (port 443).

Access to an NTP server over NTP (port 123 UDP).

Two free and accessible application ports (default port 3000 and 3002).

Install Evoko Home

Download the latest version of Evoko Home for Windows available here. Step 4: Connect Evoko Home to booking system

Extract the downloaded folder "EvokoHome vx.yz".

Run the "EvokoHomeService vx.yz.msi" file.

Note!in version v1.36.0 Evoko Home comes in both a 32-bit and 64-bit version.Please make sure the installed version of Nodejs (e.g. node-v4.8.0-x64.msi) corresponds with the version of Evoko Home (e.g. EvokoHomeService v.1.36.0 (x64).msi) you're about to install.

This will prompt a wizard, press "Next".

If you have installed the necessary prerequisites, press "Next".

Select the installation folder, then press "Next".

Configure credentials for the Mongo database.

Confirm that you want to install Evoko Home by pressing "Next".

Press "Next".

Wait for the installation to complete.

The following will be displayed once the installation is completed, press "Close".

To verify that the service is running, open up the Windows services ("services.msc").

Now you should find a service named "ERM Service", make sure its status is Running.

Once installed you should be able to access Evoko Home via http://localhost:3000

Once successfully done with installation of Evoko Home move on to

When a Room Manager for some reason cannot connect to the server it will display the below icon. Please make sure the number of max concurrent connections to your Room admin account is not exceeded.

Server connection issuescould be due to a lot of different things, it could be due to network cables, firewalls, wrong settings in the Evoko Control Panel, expired passwords and anything in between.

First of all, please make sure that you read and followed our guidance of how to set up the accounts in a right way. In our "Getting started!" section, we have covered the most common setups, so please read these guides first and make sure that no steps have been missed.

Verify that the Room Manager receives a valid IP address and can communicate on the network.

Instructions on how to check the IP address on a Room Manager and ping via the command prompt:

Login as System Admin on the Room Manager.

Press "Exit Application" and wait until the Windows CE desktop is displayed.

Double click (tap) the LAN-icon in the bottom right corner on the Windows CE taskbar to view the Room Managers network credentials (e.g IP, Subnet mask, Default-gateway).

If you receive a valid IP, mask and gateway then we can move on with testing to ping other devices on the network (e.g. your booking system)

To ping other devices from a Room Manager you need to access the command prompt, this is done by navigating to "Start" >"Programs" >"Command Prompt"

Type ping <server DNS/IP> (e.g ping 8.8.8.8or ping outlook.office365.com).

Open up the Evoko Control Panel and make sure that your room test out with a green tick.

Note! All changes made in the Evoko Control Panel has to be uploaded to the Room Manager in order to be applied. For example if you notice that the issue is due to a expired password then you need to export and upload the updated configuration containing the new password to the Room Manager.

Verify that the configuration is correct on the Room Manager.

In case there are multiple Room Managers in the installation and the connection issue only occurs on oneor several Room Managers but not all of them - try the following to narrow down the cause of the issue:

Is the issue related to the specific cable or switch port?

Does thedisconnected Room Manager connect when plugged in to another known connecting Room Managers place (i.e same cable/port)?

Additionally please check the opposite - does a known connecting Room Manager still connect when plugged in to the disconnected Room Managers place (i.e same cable/port)?

Is the issue related to one or several rooms in the configuration?

Instructions on how to change the room in the configuration on a Room Manager:

Login as System Admin on the Room manager.

Press "Change Room" in the system admin menu.

Select the desired room in the configuration.

Does another known connecting Room Manager connect if loaded with the same room in the configuration as the disconnected Room Manager?

Furthermore please check the opposite - does the disconnected Room Manager connect if loaded with the same room as a known connecting Room Manager?

Perform a factory reset, OS update and update the software to the latest available version on the Room Manager.

Check with your IT department for recent changes within your environment that's in relation with when the Room Manager disconnected. Updated SSL/TLS certificate configuration? Proxies (not supported)? Migrated to a new booking system?

Using Office 365/Exchange and experiencing intermittent disconnection issues across 10+ Room Managers?

Important!The following instructions applies to the Evoko Room Manager (ERM1001) andNOTits successor, the Evoko Liso (ERM2001).

Introduction

Create users in Active Directory

Create a Room Admin account

Create a Remote Management account (If youre going to use the EVO functionality)

Create and configure Room accounts

Configuration via Evoko Control Panel

Introduction

The Evoko Room Manager is a system for booking and managing rooms. The Evoko Room Manager is mounted outside the room and display the booking status on beautiful touch-sensitive screens, the red or green background illumination of the screen allows you to see at a distance whether or not the room is free. You book meetings just as you have always done in MS Outlook. The Evoko Room Manager also makes it possible to create and manage bookings directly on the touch-sensitive screen.

Account reference

Account type

No. of accounts

Comment

Room admin account

User Mailbox

1 + x/9

The Room admin accountis needed to manage the Room accounts.Up to9resources per room admin account is what we recommend and this is due to Microsofts default throttling policy of concurrent connections.

Remote Management account

User Mailbox

1

This account is used for the EVO features (Remote Upgrade / Monitoring / Statistics). Since a large number of emails are processed through this account we recommend a dedicated account for this purpose.

Room account

Room Mailbox

x

Resource accounts or room mailboxesdon'thave any passwords and cannot be manged on their own. The Room admin accounthas to be granted Send on behalf and Full access permissions to its belonging Room accounts to synchronize meeting data.

Note! Please make sure that no security functions or programs block or restrict a direct http/https (80/443) connection between Exchange and the Evoko Room Manager (e.g. domain control, firewalls, proxies, network logins etc.)

Create users in Active Directory

In most organisations running Exchange, users are first created in Active Directory before created in Exchange. For our installation in this guide we have already setup the following accounts in our Active Directory:

Account reference

Display name

E-mail

Room admin account

Room Admin 1

[email protected]

Remote Management account

Remote Manager

[email protected]

Note! The accounts stated above are examples and you can use other account names if you wish. Furthermore several Room Admin accounts might be necessary depending on the number of Room accounts and the configured EWSMaxConcurrency for your Exchange 2016 environment.

Createa Room Admin account

Go to https://<servername>/ecp and login with your Exchange Admin account. website

Go to Recipients > Mailboxes.

Press the + and select User mailbox.

Fill in the alias of the Room Admin account(1)and select the user in Active Directory, then press save.

Your Room Admin account should now appear in the list of mailboxes.

Create aRemote Management account (If youre going to use the EVO functionality)

In the Exchange admin center go to Recipients > Mailboxes.

Press the + and select User mailbox.

Fill in the alias of the Room Management account and select the user in Active Directory, then press save.

Your Remote Management accountshould now appear in the list of mailboxes.

Create and configure Room accounts

A Room account or room mailbox is the calendar that will be used for booking the room via e.g. Outlook and the calendar the Room Manager will synchronize meeting data with. OneRoom account per Room Manager is necessary unless you want two or more Room Managers synchronizing meeting information with the same Room account calendar.

Note!If you already have all the Room accounts setup for your organisation you can proceed to step 4 in this chapter with granting your Room admin account the necessary permissions.

In the Exchange admin centergo to Recipients> Resources.

Press the + and select Room mailbox.

Enter the name of the Room account, specify the email address of the account and select the Organizational Unit (OU) where you want the Room account to be placed.

Your Room account should now appear in the list of resources. Double click on the Room account, OR highlight it and press edit.

Go to "mailbox delegation".

Under the section "Send on Behalf", press add.

Add your Room admin account, then press "ok".

Under the section "Full Access", press add.

Add your Room admin account, then press "ok".

Note! If you would like to setup several Room accounts simply repeat above steps in this chapter.

Configuration via the Evoko Control Panel

Download and install the Evoko Control Panel. The software is available at our.

Launch the Evoko Control Panel.

Choose Exchange 2016 as your mail server, enable EVO if you would like to use the EVO features (remote upgrade, monitoring, statistics) and if you have set up a Remote Management account.

Click on Continue to connectivity settings in the bottom right corner to continue.

Fill in your Exchange 2016 mail server address. If you are unsure which address to use to use you could try the Autodiscover feature.

Optional: Test your accounts for functionality.

Exchange user - Fill in your Room Admin account.

Exchange password Fill in your Room Admin account password.

Mailbox owner Fill in the email-address for your Room account.

Click on System properties in the bottom right corner to continue.

Choose your Time format.

Choose the language which will be displayed on the Evoko Room Manager.

Optional setting: Enter the name of your Organization.

Enter the email-address to your System Administrator.

Choose a system Admin PIN code, the code is used to access the Admin menu on the Room Manager.

Add one or two email-addresses to the Facility manager.

Choose a Facility manager PIN code, the code is used to access the Facility manager menu on the Evoko Room Manager.

Fill in your Remote Management account.

Remote Management user Fill in your Remote Manager account user.

Remote Management password Fill in the password for your Remote Manager account.

Remote Management email Fill in the email-address to your Remote Manager account.

Remote monitor update duration - (This sets how often each Room Manager send email- reports for the monitoring feature).

Add a unique Security key (Max 16 characters).

Choose if you want the Evoko Room Manager always on or set by time.

Choose your Time zone at the Evoko Room Manager unit location.

Optional Setting: Assign one or multiple NTP-servers, separate the servers with a comma. e.g. 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org

Click on Admin credential in the bottom right corner to continue.

Click on button Add users.

Add your Room Admin account(s).

Click on Room dashboard in the bottom right corner to continue.

Click on Add group to create a group.

Choose method to add a room, for this guide well go with Quickly.

Fill in Room Name, Exchange User (Room Admin account) and Mailbox owner (Room account).

Fill in the amount of seats in the room and choose the room facilities.

Enable the optional features that you would like to configure your Evoko Room Manager with.

Setting

Description

Book meeting

Enables the user to book a meeting on the Evoko Room Manager.

Extend meeting

Enables the user to extend a meeting on the Evoko Room Manager.

End meeting

Enables the user to end a meeting on the Evoko Room Manager.

Report issue

Enables the user to report any of the chosen facilities. When reporting any of the chosen facilities an email is generated to the assigned facility manager.

Display Subject

Enables the subject of the meeting to be displayed on the Room Manager.

Display Organizer

Enables the organizer of the meeting to be displayed on the Evoko Room Manager.

Confirm Meeting (5-30min)

Enables a check in feature which will trigger a confirm/check-in button that will popup on the Evoko Room Manager 10 min prior to the meeting start and will be displayed 5-30 min post to the meeting start. If the confirm buttonisn'tpressed within the selected time frame the meeting room will be released.

Confirm Reminder

Enables a reminder-email which will be sent to the organizer of the meeting. This email is triggered 5 minutes before the confirm time expires and is only sent out if the room hasnt already been confirmed/checked in.

Note!To add several Rooms to your configuration simply repeat step 6.25-6.28.

Insert an empty USB-stick in your computer (4 GB or less and FAT-formatted is recommended).

Click on Export to USB in the bottom right corner to export your configuration.

Now that youre done with the configuration, to proceed simply upload the configuration to the Evoko Room Manager via your USB-stick and follow the instructions on the screen.

PleasetryenablingTLS 1.2 support inEvokoControl Panel andreconfigurethe panelsusingthisconfiguration. ItseemsMicrosofthasdisabledTLS 1.1 in O365prematurely.We'renot sureifthisistemporaryor permanent - thechangewasplannedfor June 2020:

https://docs.microsoft.com/en-us/office365/troubleshoot/security/prepare-tls-1.2-in-office-365

To dothis, go to theConnectivitySettingstabinEvokoControl Panel andclickthe checkbox:

Updating the Liso firmware should normally be done remotely over the network using Evoko Home or by using a USB flash drive, but in some scenarios a firmware reset might be necessary.

A firmware reset is different from a firmware update in that it resets all settings and leaves the Liso in an unconfigured state. After firmware resetting a Liso you will have to reconnect it to Evoko Home and assign it to a room. Scenarios where performing a firmware reset can be necessary include rare issues with the running software on the Liso device or configuration conflicts

If a Liso is running a very old firmware, performing a firmware reset can also be the quickest and easiest way of bringing it up to date.

The process of performing a firmware reset can be split into two parts:

Part 1: Create a bootable firmware reset USB

Part 2: Boot Evoko Liso with the firmware reset USB

Part 1: Create a bootable firmware reset USB

To write the firmware reset image to an USB flash drive you will need to use some kind of disk imaging software. In the below example we will use Etcher which is open source and free to use. If you are more familiar with Win32 Disk Imager or Rufus, those tools also work.

Note!We recommend using a quality USB flash drive of at least 4GB and physically small enough to fit into the Liso.

Important! Some Kingston brand USB flash drives are known to be incompatible with the Liso.

Start of by downloading theFirmware Resetfile from the Evoko Liso download page.Please select the version that corresponds to your Evoko Home install (1.x/2.x). download Etcher

Next and install/run it on your PC.If you do not want to install the software, there is a portable option that can be run directly after download without installing.

In Etcher press Select image.

Select the downloaded firmware reset image and press Open.There is usually no need to uncompress the .sdcard image as Etcher will take care of that.

Insert and select your USB flash drive.

Caution!All existing data on the USB flash drive will be deleted. To proceed, press Flash!

The process usually takes around 5-10 minutes depending on the write speed of the USB flash drive.

Once Etcher is finished writing the firmware reset image to the USB flash drive it should be ready to use.

The USB drive name should now be Boot imx6dl and should contain some new files.

Please note that there are partitions not normally visible by Windows and you might get error messages saying you need to format the drive before it can be used. Please ignore these messages.

Part 2: Boot Evoko Liso with the firmware reset USB

Next step is to boot the Liso from the newly created firmware reset USB rather than the internal storage.

Power off the Liso by removing the PoE or power cable.

Insert the firmware reset USB into the Liso USB port.

Power on the Evoko Liso by inserting the PoE or power cable and wait.

If successfully booted from the USB stick the following text should be displayed:

If you do not want to flash the device, remove the USB image and reboot the device, otherwise it will start flash in 30 seconds

Once the firmware reset is complete the following text should be displayed:

Flash has been successfully completed! Please plug-out the USB and reboot the device.

Remove the USB flash drive and reboot the Liso.

A screen calibration software can be found on the Room Manager and can be used by accessing the underlying operating system.

Login as System Admin on the Room Manager.

Press "Exit Application" and wait until the Windows CE desktop is displayed.

Fromthe Windows CE Desktop open "My Device".

Then navigate to the folder "TOUCH_APP".

Launch "Touchkit" and select either the "4 Pts Cal" or "25 Pts Cal" option and proceed according to instructions on screen.

Once done close the "Touchkit" application along with open windows and launch the "RoomManager.exe".

We recommend keeping Evoko Home up-to-date with the latest version along with the latest Evoko Liso firmware. Please find instructions below on how to update Evoko Home on your server to the latest version.

Note! Please read the release notes for newer versions of Evoko Home than what is currently running on your server, as there might be special instructions for upgrading from specific versions to the current one.

Update Evoko Home on Windows

Update Evoko Home on Linux

Update Evoko Home on Windows

Important!This guide is for Evoko Home 1.x.

To migrate Evoko Home from 1.x to 2.x, instead see this article.

To update Evoko Home 2.x to a newer version, please download the new version, unzip the archive and run setup.exe.

Important!If you did not use the default credentials for MongoDB when originally installing Evoko Home, make sure you have a backup of your credentials before proceeding. Without the correct MongoDB credentials your Evoko Liso system will need to be reset.

Download the latest version of Evoko Home for Windows here. here

Extract the contents of the zip file to a folder.

Open Services by going to the start menu and searching for Services or open Run and type services.msc

Select the ERM Service and click Stop.

Go to Add or remove Programs and Uninstall Evoko Home.

Note!Starting with version 1.36, Evoko Home comes in a 32-bit and a 64-bit version. We recommend using the 64-bit version. Please make sure the architecture of NodeJS (i.e. 32-bit or 64-bit) corresponds with the architecture of Evoko Homeyou're about to install.

To go from 32-bit to 64-bit, follow steps a-b below.

Uninstall NodeJS

Install NodeJS 4.8.0 x64

Open the folder where you extracted the Evoko Home install files and run the "EvokoHomeService vy.xz.msi" for the new version. Be careful to select the correct architecture (x86/x64) ifapplicable.

Follow the steps in the wizard.

When asked about the MongoDB credentials, make sure to enter the same credentials as before if you did not use the default credentials.

Wait for the installer to complete. This normally takes a few minutes.

Check the services window to make sure that the ERM Service is running.

Make sure you can access the Evoko Home web interface via a web browser. There can be a few minutes delay after reinstalling Evoko Home before the Evoko Home web interface responds.

Update Evoko Home on Linux

Note! These instructions are for both Evoko Home 1.x and 2.x even though the Evoko Home 2.x install process might differ very slightly from the steps below.

Download the latest version of Evoko Home for Linux and put the installation package on the server.

Extract the downloaded installation package sudo tar -xzf installation_vx.yz.tar.gz.

Change directory to the to the newly extracted directorycd vx.yz.

Run the installation scriptsudo bash install.sh

Accept to remove nodejs by typing y followed by Enter.

To continue and install, select Yes by typing1followed byEnter.

Select Yes by typing1 followed by Enter to update using your existing configuration/database.

Set the maximum amount of memory Evoko Home can use by typing the amount e.g. 2048 and followed by pressing Enter.

Done!

Make sure that MongoDB is running by entering service mongod status, the output should say "active (running)". If MongoDB is not already running please enterservice mongod startand then check the status again.

Next make sure that Evoko Home is running by enteringsudo supervisorctl, the output should say "RUNNING". Please run start evoko_home in the supervisor if Evoko Home is not already running or starting.

Finally make sure that you can access the Evoko Home web interface as usual via a web browser.

This document provides instructions on how to integrate the Evoko Room Manager in Evoko Home. After completing this procedure, your Room Managers will no longer be managed by Evoko Control Panel. **You must be running v2.2 of Evoko Home to try this BETA.**

Important! Please read through this document before starting, and contact Evoko support if you have any questions.

Benefits The main benefits of integrating the Evoko Room Manager into Evoko Home are:

Centralized management even with mixed environments (Liso/Room Manager)

Simpler booking system configuration since it only needs to be configured for Evoko Home.

Better support for newer ciphers and technologies (including support for the Office 365 oAuth transition)

Drawbacks There are also a few drawbacks:

Integration requires additional software and setup.

Not currently possible to end meetings early from the Room Manager screen.

Some Evoko Home settings need to be changed for the integration to work.

Contents

Server setup - WebAPI application

Evoko Home settings

Evoko Room Manager setup

Server Setup - WebAPI application

Prerequisites

Evoko Home v2.2needs to be installed and configured. For setup instructions, please see Evoko Liso / Getting started v2.x

Download Evoko Room Manager Bridge: https://www.evoko.se/downloads/ (Select EvokoRoom Manager --> Software --->Evoko Room Manager Bridge)

Open "Turn Windows features on or off".

Enable Internet Information Services, then enable the following.:

All options under World Wide Web Services\Application Development Features

All options under World Wide Web Services\Common HTTP Features.

Security\Windows Authentication

Run the setup.exe located in the Integration subfolder of the ERM Integration.

After install has finished successfully, reboot if needed, then open Internet Information Services (IIS) Manager.

Navigate to Sites -> Default Web Site -> EvokoWebAPI and click Edit Permissions.

Go to the Security tab, click Edit, select IIS_IUSRS and click Full Control. Then click OK on the two dialog boxes.

Restart IIS by clicking on the server name in the top left corner and selecting Restart under the Manage Server menu.

Open a web browser and open http://[IP]/EvokoWebAPI, where [IP] is the ip of the server.

Log in using EvokoAdmin and Password123.

Under EH end point, enter the Evoko Home server IP and port, for example 192.168.1.108:3002

Important! Only enter IP:PORT! Do not enter protocol, slashes or path.

Open Evoko Home, go to global settings and copy the default API token, then paste it in the "Set MongoDB User details" tab in EvokoWebAPI.

This concludes the ERM WebAPI Endpoint configuration.

Evoko Home settings

In Evoko Home, the following settings need to be changed for the rooms that are going to be used with Room Managers.

Go to Rooms -> Settings and select the rooms that are going to have Room Managers assigned to them. Click Edit Settings.

Under booking settings, make sure everything is enabled except for Delete Future Meeting and Modify Future Meeting as the Room Manager does not currently support these features. Also disable all authentication settings as shown in the screenshot below.

Evoko Room Manager setup

This section will tell you how to configure the Room Manager for use with Evoko Home. Please note that after performing the steps below, your Room Manager will need a factory reset and reconfiguration if you would want to go back to using Evoko Control Panel.

Preparation: Copy the MeetingManagementSetup.CAB file to a FAT-formatted USB stick.

On the Room Manager, log on using an admin PIN and select Exit Application.

Open My Device on the desktop by double tapping it.

Open ResidentFlash, select the MeetingManagementSetup folder, tap the Edit menu and select Delete.

Insert the USB stick with the MeetingManagementSetup.CAB file, open My Device on the Room Manager and navigate to "Hard Disk".

Copy MeetingManagementSetup.CAB to the desktop and then run it from the desktop by double clicking the icon.

When prompted, enter the IP address to the WebAPI using the touch screen, then tap the green check mark.

The Room Manager will connect to the WebAPI and download the configuration which will take a few minutes. The Room Manager will restart and you will be presented with the Select a Room screen.

Select the room this Room Manager should be assigned to.

Note! To use the VNC feature you must use

Evoko Home 1.34 (or later) and

Liso firmware version 2017_12_11_v1.34 (or later).

Contents

Enable VNC

Evoko Home 2.x

Evoko Home 1.x

Connect to the Liso

Video Demonstration

Enable VNC

Evoko Home 2.x

To enable VNC, go to Monitoring, expand the room structure if needed, and click on a room. Select the Device tab and click the Activate VNC button.

VNC Viewer from RealVNC

Evoko Home 1.x

To enable VNC, go to the monitoring tab in Evoko Home. On the row of the Liso you would like to remote control, click the VNC button on the far right.

You should get a confirmation message that VNC is activated for that device.

Connect to the Liso

Using a VNC client of your choice, enter the IP number of the Liso from the previous step. In this example we are using, because it is free and easy to use.

When VNC Viewer opens, enter the IP number of the Liso in the server address field and press enter.

You might get a warning about the connection being unencrypted. Just click OK and you should be able to see and control the Liso screen.

Note!Once the VNC client disconnects from the Liso, VNC is disabled. To reconnect, first re-enable VNC on the Liso from Evoko Home -> Monitoring.

Video demonstration

Warning!Performing the below steps will remove the configuration loaded on the Room Manager and reset the Room Manager back to factory settings.

Download the latest Factory reset software from our website.

Extract the downloaded factory reset files in the root of a USB-stick (4GB or less, FAT-Formatted is recommended). Getting started! section

Insert the USB-stick into the Room Manager and reboot.

Wait until "ERM Diagnostics" is launched and press "Reset (Factory)".

On the prompt "Are you sure...", press "Yes".

Note!If you're prompted "Exception occurred: Filed to collect files" please ignore and press "Ok" to proceed.

Once the factory reset is finished "Reset (Factory) completed successfully" will be displayed in the statusbox. Press "Exit".

Now the factory reset is completed, simply wait until the "Welcome screen" is displayed.

To get a configuration running on the Room Manager, export your configuration from the Evoko control panel to a suitable USB-stick which you insert in the Room Manager and upload the configuration by pressing "upgrade", then selecting the room on screen. If you don't have an existing configuration then please check the for setup guides.

Thank you for choosing Evoko Liso The next generation Room Manager.You are now on your way to magnificent meetings!

The series of articles in this section "Getting started!" will guide you trough the installation process to get started.

Step 1: Introduction

Step 2: Booking system preparation

Step 2a: Office 365

Step 2b: Exchange 2016

Step 2c: Exchange 2013

Step 2d: Exchange 2010

Step 2e: Google G Suite

Step 3: Evoko Home installation

Step 3a: Windows (Default mode)

Step 3b: Linux (Default mode)

Step 3c: Windows (Limited mode)

Step 4: Connect Evoko Home to Booking System

Step 4a: Office 365

Step 4b: Exchange 2016

Step 4c: Exchange 2013

Step 4d: Exchange 2010

Step 4e: Google G Suite

Step 5: Basic Evoko Home setup

Step 6: Evoko Liso installation

How is the Evoko Liso mounted on the wall, powered and connected to the network?

Evoko Liso user guide - how do I use the screen?

System overview

The Evoko room booking system consist of Evoko Liso devices that are installed outside the meeting rooms, and the Evoko Home application which connects to the booking system and is used to manage the Liso devices.

Evoko Home can be installed as a service in the company network, on-premises or in the cloud, which enables several features like user management, statistics and remote management of the Liso devices ( Default mode ).

Optionally, you can manage the Liso devices manually by installing Evoko Home on a desktop where you set up the configuration and transfer it with a USB stick to the devices ( Limited mode ).

Default mode Step 2: Booking system preparations

We recommend that you install Evoko Home on a server in your network. This enables full functionality, including remote management, multi-site support, user management, monitoring and statistics. This is especially important for larger installations.

General installation process

Make the necessary preparations in the booking system

Install Evoko Home on a Windows or Linux server

Connect Evoko Home to booking system

Use Evoko Home to configure rooms, users etc.

Connect Evoko Liso to Evoko Home server and select room

System architecture

Minimum system requirements for default mode

Debian based Linux distribution (e.g. Ubuntu server 16.04 LTS), Windows Server 2008 R2 or later.

Static IP address (IPv4) for Evoko Home.

On-premises or cloud based, virtual or physical server with dual core CPU, 2GB RAM, 8GB storage.

Note! Large environments with many Liso units require higher specifications than the minimum requirements.

Two free and accessible application ports (default port 3000 and 3002).

The system must be set up so that https (port 443) is allowed between Evoko Home and the booking systemusing EWS for Exchange or other API endpoint depending on environment.

A booking system service account with a mailbox.

Access to an NTP server over NTP (port 123 UDP).

Limited mode

If youcan'tinstall Evoko Home on a server, you can use Evoko Liso devices and connect them directly to your booking system.You do however still need to install Evoko Home andconfigure the rooms before exporting the configuration to a USB memory that is used to set up the devices.

Important! Running Evoko Home in Limited mode doesnt give the full functionality and we strongly advice against using it for more than 10 Liso devices. In Limited mode you donotget:

Remote upgrade (to easily change settings and upgrade to new versions)

Monitoring (to see the status of the units)

Statistics (to see how much the rooms are used and how to increase efficiency)

Room Finder (to easily find rooms to fit your needs)

PIN/RFID identification or Permission control

Simplified installation process, decreased server load or added security

Overview screen (BETA - not yet released)

Get a room smartphone app (BETA - not yet released)

General installation process

Make the necessary preparations in booking system

Install Evoko Home on a Windows or Linux Desktop

Connect Evoko Home to booking system

Use Evoko Home to configure rooms, users etc and export a configuration file

Configure Evoko Liso by uploading the configuration file via USB

System architecture

System requirements for limited mode

Debian based Linux distribution (e.g. Ubuntu Desktop or Mint), or Windows 7 (64-bit) or later

The system must be set up so that https (port 443) is allowed between Evoko Liso and the booking system using EWS for Exchange or other API endpoint depending on environment.

A booking system service account with a mailbox.

Access to an NTP server from each Evoko Liso unit over UDP port 123, either to the internet or an on-premises NTP server.

Now that you've gone through the introduction, move on to

This part will go through the necessary preparations needed in Office 365 to integrate Evoko Liso.

Create a service account

Grant the service account Impersonation rights

Option #1: Grant Impersonation with management scope using Windows Powershell

Option #2: Grant Impersonation without management scope via the Exchange admin center

Create resource accounts

Create room list using Windows PowerShell (Optional)

Create a service account

We recommend using a dedicated service account (e.g. [email protected] ) for integrating Evoko Liso with an Office 365 environment. This account will be used for authentication and carrying out requests between the Evoko software and Office 365 via EWS (Exchange Web Services).

Note! These instructions applies to the general Office 365 setup for setting up a normal user account. If e.g. running a hybrid environment within your organisation the setup process for a new user account might be different. Please visit the Hybrid Environment setup Guidelines for more information.

Go to the Office 365 Admin center and login with your Office 365 admin account.

In the Office 365 admin center click Add a user under Users. Step 3: Evoko Home installation

Enter the information for your service account, assign a licence and continue by clicking "Add".

Important! The service account needs a mailbox and therefore also a license.

Once the account is created, chose if you want to email the password or not and click Close.

Grant the service account Impersonation rights

Impersonation can be granted via either Windows PowerShell ( Option #1 ) or via the Office 365 Admin center ( Option #2 ) and with or without a management scope, we have listed two options below. For security practices we recommend granting Impersonation with a management scope and to not apply it system wide.

You can read more about our decision on using impersonation rather than delegation in this article.

Important!Having the service account granted with Impersonation permission is arequirementto successfully integrate Evoko Liso with your Office 365 environment.

Option #1: Grant Impersonation with management scope using Windows Powershell

The below method will grant your service account with impersonation permissions restricted only to resources (room and equipment mailboxes) by applying a management scope/Write scope.

Start of by connecting to your Office 365 environment via Windows PowerShell and authenticate with your Office 365 admin account. This is typically done by running the following commands:

On the Execution Policy Change question type Y and click Enter.

Set-ExecutionPolicy RemoteSigned

This will prompt a pop-up asking for credentials. Enter the user name and password for your Office 365 admin account and click Ok.

$UserCredential = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange

-ConnectionUri https://outlook.office365.com/powershell-liveid/

-Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

Create a management scope which will be used in the next step to restrict the impersonation right. The below command will limit the scope to resources (room and equipment mailboxes):

New-ManagementScope -Name "ResourceMailboxes" -RecipientRestrictionFilter

{ RecipientTypeDetails -eq "RoomMailbox" -or RecipientTypeDetails -eq

"EquipmentMailbox" }

This will grant the service account Impersonation using the management scope:

New-ManagementRoleAssignment Name "ResourceImpersonation" Role ApplicationImpersonation

-User "[email protected]" CustomRecipientWriteScope

"ResourceMailboxes"

Note!"[email protected]" in the above command is put there as an example, please use the equivalent for your service account.

Confirm that impersonation has been granted to your service account:

Get-ManagementRoleAssignment -Role "ApplicationImpersonation" -GetEffectiveUsers

The above command will display a table of accounts assigned with impersonation. Please make sure that in the Role column the value is ApplicationImpersonation, and in that same row under theEffectiveUsername is the name of your service account. If so, that means the setup of the impersonation was successful.

Option #2: Grant Impersonation without management scope via the Exchange admin center

The below method will grant your service account with impersonation permission for all accounts.

Go to the Office 365 Exchange admin center and login with your Office 365 admin account.

In the Exchange admin center, navigate to permissions >admin roles">and click the add-button.

Under "Name" enter Application Impersonation". The "Description" can be left empty and the "Write scope" can be kept at "Default".

Tip!If a management scope is created in your environment (as done in step 2 of option #1 ) then it will be displayed in the drop-down list under "Write scope" and possible to apply.

Under "Roles" click add and add the admin role "ApplicationImpersonation".

Under "Members" add your service account and then click "Save".

Create resource accounts

A resource account or room mailbox is the calendar that is used to book the room via e.g. Outlook and the calendar the Evoko Liso/Home will synchronize meeting data with. Oneresource account per Evoko Liso is necessary unless you want two or more Evoko Liso synchronizing meeting information with the same calendar.

Note!If you already have all the resource accountssetup for your organisation you can proceed to the next section.

Go to Office 365 Exchange admin center and login with your Office 365 admin account.

In the Exchange admin center navigateto "Recipients" > "Resources".

Click the "+" and select "Room mailbox".

Enter the "Room name" and specify the resource accounts "Email address". Optionally add a "Location" and enter the "Capacity" and continue by clicking "Save".

Your resource account should now appear in the list of resources.

We recommend you configure the resource account with the below cmdlet using Windows PowerShell:

Set-CalendarProcessing [email protected] -AutomateProcessing

AutoAccept -AddOrganizerToSubject $False -DeleteComments $False -DeleteSubject

$False -RemovePrivateProperty $false

Note! If you would like to create several resource accounts simply repeat above steps in this section.

Create room list using Windows PowerShell (Optional)

Room lists help you to organize your rooms. If your company has several buildings with rooms that can be booked for meetings, it might help to create a room lists per building or even per floor.

Room lists are specially marked distribution groups that you can use the same way you use distribution groups. In Evoko Home you can import room lists which makes it a convenient way to add your rooms.

The below commands will help you to create a single room list and then add rooms, or create a single room list that holds all existing rooms in one go in Office 365 using Windows PowerShell:

The following command creates a new room list named My Rooms:

New-DistributionGroup -Name "My Rooms" RoomList

The following command to adds a resource account ("[email protected]") to an already existing room list ("My Rooms"):

Add-DistributionGroupMember -Identity "My Rooms" -Member

[email protected]

The following command fetches all resources (room mailboxes) and puts them in a single new room list named My Rooms:

$RoomAlias = Get-Mailbox -RecipientTypeDetails RoomMailbox | select -ExpandProperty

Alias New-DistributionGroup -RoomList -Name 'My Rooms'

-Members $RoomAlias

The following command to displays a table of all room lists in your Office 365 environment:

Get-DistributionGroup | Where { $_.RecipientTypeDetails -eq "RoomList"

} | Format-Table DisplayName, Identity, PrimarySmtpAddress

Once done with the necessary preparations in Office 365 please move on to

This issue is usually due to the configuration of the resource account (room mailbox) in Office 365 / Exchange which adds the meeting organizers name to the subject hence it being displayed doubled.

To address this we suggest running the following command in PowerShell / Exchange Management Shell.

Set-CalendarProcessing [email protected] -AddOrganizerToSubject $False-DeleteSubject $False

Note!Replace [email protected] with the equivalent of your resource account (room mailbox).

One of the features of Evoko Home is providing you with meeting room statistics, which hopefully allows you to gain better insight on how your meeting rooms are being utilized. Meeting room information such as the average number of meetings in a particular room, the meeting rooms utilization rate or the number of meetings not checked-in are some examples of what can be presented.

Evoko Home calculates various metrics by analyzing the meeting data stored in the database on a daily basis. To fully evaluate and index the data, it takes up to two days before the data can be viewed or exported.

Viewing statistics

Under Rooms>Statistics in Evoko Home you can view statistics. Simply adjust the date interval to set the period.

Exporting statistics

The option to export statistics to a .csv file is also made available via 3 options by pressing Export:

Export to CSV - generates a file (statistics_08_01_2019_08_10_2019.csv) with all statistics values (see table below for more information).

Export raw data to CSV - generates a file (e.g. statistics_08_01_2019_08_10_2019_raw.csv) containing the raw meeting data during the selected time interval with all raw data information. Note that this section does not allow you to see information about which user ended or extended a meeting - only who created the meeting event is shown in the raw data.

Statistics scheduled export - sends statistic reports to an given email account. If 'Activate Update' is enabled, updates of meeting data will be send on a daily basis. You can also enable the 'Save local copy' function, which allows you to download a local copy to your computer.

Note!Please use a modern web browser (e.g. a recent version of Chrome, Firefox, Safari or Edge) when exporting to ensure compatibility. Internet Explorer is not compatible with Evoko Home statistics section.

Calculated values

The below table provides a description of all the available values found in the web interface and regular .csv export.

Value

Description

ROOM NAME

The meeting rooms name.

SEATS

The meeting rooms seating capacity.

MEETINGS

Displays the total number of meetings.

MEETINGS PER DAY (AVG. NUMBER)

Calculates the average number of meetings per day.

UTILIZATION DURING WORKING HOURS (%)

Total meeting time which takes place inside non-sleeping hours period of Liso devices. Meetings that take place outside working hours will not be taken into the calculations. Tentative meetings are also not calculated. If the meeting starts or ends outside working hours, while taking place inside working hours, only part of the meeting that is inside working hours will be taken into account.

TOTAL MEETING TIME (HOURS)

Total duration of meetings inside working hours.

DURATION PER MEETING (AVG. HOURS OF ALL)

Average duration of meetings inside working hours.

DURATION PER MEETING (AVG. HOURS EXCLUDING NOT CHECKED IN*)

Average duration of confirmed/not cancelled meetings inside working hours.

DEVIATION FROM SCHEDULED (AVG. HOURS)

The total difference between the planned time of a meeting and actual ending time. This deviation is caused by meetings being shortened by the user, extended by the user or cancelled by the check-in functionality.

MEETINGS EXTENDED (%)

Share of meetings extended by a user.

MEETINGS ENDED EARLY BY USER (%)

Share of meetings shortened/ended before scheduled by the user.

MEETINGS ENDED NOT CHECKED IN* (%)

Share of meetings cancelled by the check-in functionality.

MEETINGS ENDED AS SCHEDULED (%)

Share of meetings ended as scheduled.

MEETINGS SCHEDULED IN CALENDAR SYSTEM(%)

Share of meetings created using the calendar system calendar (Outlook, Google, Domino).

MEETINGS BOOKED ON SCREEN (%)

Share of meetings booked on the Evoko Liso device.

MEETINGS NOT CHECKED IN*

Total number of not checked-in meetings for a selected period.

TOTAL TIME BOOKED BUT NOT CHECKED IN (HOURS)

Total planned time of meetings not checked-in.

TIME RECOVERED BY ENDING MEETINGS THAT WERE NOT CHECKED IN (HOURS)

Total time difference between planned time and actual time for meetings that were not checked-in.

This is the revised configuration guide for Evoko Home with Office 365 using Modern Authentication/OAuth. The previous oAuth guide was using the legacy oAuth implementation.

To use oAuth with EWS for Office 365, You have to register a custom application in the Azure Active Directory for the Office 365 tenant and gather some information. Please follow the guide below.

Article contents

Preparations

Collect information for the Evoko Home configuration wizard

Register App for use with oAuth in EWS

Login using OAuth in the Evoko Home configuration Wizard

Preparations

Follow the Booking system preparation guide for Office 365.

Important! The booking system preparation instructions have been updated. If you configured impersonation in the past, please revisit the impersonation section and re-apply the impersonation.

Configure the Azure app and collect information

Find the tenant name or ID for your Office 365 Tenant in Azure Active Directory

You can use either tenant name or ID in the Evoko Home configuration wizard. Note this down for use in the Evoko Home configuration wizard.

Alternative 1: Use the tenant ID

Login to Office 365 Admin Portal and open Azure AD Admin Portal by clicking Azure Active Directory under Admin Centers (click Show All to show Admin Centers if menu hidden). https://aad.portal.azure.com

This will open Azure Active Directory admin center Dashboard. You can also visit this dashboard by URL:

Click Azure Active Directory in left panel and click Properties under Manage section.

Make a note of Directory ID, in this case 5024441e-8554-4dbf-9a00-d90e298448e8. This is Office 365 Azure AD Tenant ID

Alternative 2: Use the tenant name

When you signed up for Office 365, Microsoft generated a unique tenant name for your tenant. It is in the form of <customer id>.onmicrosoft.com. You can also find this in Domains section under Setup in the Office 365 Admin Portal. There will be only one domain with suffix onmicrosoft.com. Success! You have the information needed for Office 365 Azure AD Tenant ID.

Register App for use with oAuth in EWS

In the Azure AD portal, click App Registrations to open the App registrations blade.

Click the New Registration button. Fill in name and redirect URI and click Register.

Once application is created, you can see the details page. Make a note of Application (client) ID value for the Evoko Home configuration wizard. Success! You have the information needed for Office 365 Azure AD Application ID.

Click onAuthentication.Scroll down and enableTreat application as public clientby selectingYes. Note! Make sure that Access Token and ID Tokens are not selected.

Go to API permissions setting.

Click Add a permission button, scroll down and select Exchange.

In the permission selection page, select Delegated Permission, which will open the list of permissions for Delegated access. Expand EWS and select EWS.AccessAsUser.All. Click the Add permission button.

You should now see the application permissions.

Login using OAuth in the Evoko Home configuration Wizard

Select Modern (OAuth) from the drop down on the credentials page.

Use the notes from the previous steps for the appropriate fields and click Connect.

Login to Service Account

The wizard will now wait for you to log on using the provided URL and code.

Important! Make sure to login with the service account created for this purpose, if you sign in with other account it will succeed in the authentication but the application will not work.

Login at Microsoft Azure

On the provided URL, enter the code from the wizard then click "Next".

Notice the application name you configured for this.

Once you sign in using service account credential, it will prompt for the consent dialog. This happens only for first login to this application, subsequent login remembers the consent.

Review the dialog and click "Accept".

You should now see the following screen which informs you to safely close this window.

Switch back to the Evoko Home Setup Wizard and continue to the next step.

All configuration of the Room Manager is made through the configuration tool "Evoko Control Panel".

The version of the Evoko Control Panel that you use to export your configuration is the same software version that will be used on the Room Manager. For example if you use version 8.0.6.1 of the Evoko Control Panel to export your configuration and upload to your Room Manager then the Room Manager will run software version 8.0.6.1.

Tip! Don't have your existing configuration file (MeetingRoomConf.xml)? Please see How do I extract an existing configuration from a Room Manager and import it to the Evoko Control Panel?

Important!Due to version incompatibility you will not be able to update a Room Manager from version 8.0.3.0 (or below) to version 8.0.3.6 (or above) via USB without first performing a factory reset.

Export the configuration from Evoko Control Panel

Make sure that you're running the latest version of the Evoko Control Panel which can be found here.

Once satisfied with the configuration entered in the Evoko Control Panel, insert a suitable USB in your PC and navigate to the tab Dashboard.To export the configuration to the USB press Export to USB.

Remove the USB from your PC

Import the configuration to a Room Manager

Insert the USB stick in the Room Manager.

On the Room Manager login with the system adminPIN code for your configuration.

To load the new configuration/update press Upgrade.

Once the new configuration/update has been copied, press Okand then wait for the Room Manager to finish.

This guide should only be used as a part of another guide. If you arrived on this article without being directed here from a support article or support agent, please contact our support for guidance.

Important! Editing the database is done at your own risk. Any damage done might be irreversible. Make sure you have a backup of the database.

Difficulty: Advanced. You will directly edit the database which could potentially lead to data loss. Tools:

Robo 3T - download the portable version from this link: https://robomongo.org/download. The portable version does not require to be installed but can be run directly after download.

Time required:10 minutes or less

Recommended preparation: Perform a backup. See separate instructions.

Instructions:

Run Robo 3T.

Create a connection with the following variables: Connection tab: Leave values at defaults, name the connection if you want Authentication tab: Make sure Perform Authentication is checked, then enter Database:evoko_db (on Windows) or evoko_home_db (on Linux) Username:evoko_user (default, custom credentials could have been entered during setup) Password:evoko_pass(default, custom credentials could have been entered during setup) Auth Mechanism: SCRAM-SHA-1 Click Test and if successful, Save. If the connection test fails, check the credentials in the config file: For Windows Service: C:\Program Files (x86)\EVOKO\EvokoHome\ErmService.exe.config On Linux:/etc/supervisor/conf.d/evoko_home_run_script.conf

Connect to the database.

Use the tree on the left to expandevoko_db -> Collections.

Go back to the instructions which brought you to this article and continue there, editing the database as needed.

Disconnect Robo 3T by right clicking on the connection and selecting Disconnect.

Some procedures require a restart of the ERMservice service before taking effect.

If you do not need Robo3T and you are certain you will not need to edit the database again, you can delete the connection and close Robo 3T. Delete the Robo3T folder and zip file you downloaded earlier.

You're almost there! All that remains is to setup the Liso units which this article will cover.

Network configuration

Setup in Default mode

Check the following article for mounting instructions and possible power/network options.

Network configuration

The Evoko Liso can be connected via either a wired Ethernet connection or Wifi using a dynamic or static IP (support for configuring a static IP was introduced in firmware 2018_09_06_v2.0.029). By default, a Liso unit will automatically obtain an IP address using DHCP once connected via a wired Ethernet connection.

Setup in Default mode

To connect a Evoko Liso unit to Evoko Home (which connects to your booking system) you need to enter the IP address and port for your Evoko Home server on the Liso unit and then select the appropriate room in your configuration.

Note!Make sure the connecting Liso unit to is running version2018_04_16_v1.36.0 (or later), otherwise please update the firmware to ensure compatibility before proceeding.

From the configuration screen press "Continue".

Select "Default mode".

Enter the IP address and HTTPS application port (default3002) for your Evoko Home server.

Wait for it to connect and load.

You can filter the listed rooms, this is especially helpful for larger installations.

Once the Liso is connected to your Evoko Home server it should display a list of allactivatedrooms in your configuration. Highlight the appropriate room and press "Select".

Now the Liso unit should be setup and ready to use!The Liso unit should now appear under the "Monitoring" tab in Evoko Home.

Success! You're now all setup, continue by connecting the rest of your Liso units and start booking.

As usual, please find downloads at https://www.evoko.se/downloads/

Changed: The Room Manager will now reboot once exiting sleep mode.

Release (2019-10-15)

Important! Evoko Home v2.2 requires MongoDB 3.4. If you are using MongoDB 3.2 or are unsure, please contact our support team and we will help.

Known issues

If you are currently running v2.1 and have Evoko Home configured with Modern oAuth for Office 365 do not upgrade to v2.2! Environments on v2.1 configured with oAuth can upgrade to v2.2 when the patch release is made available.

Wrong status may be shown for Lisos running firmware 2.1.x. We recommend always running matching version numbers on Liso and Evoko Home.

The Majors

New - Liso: Support for new NFC module.

New - Liso: Korean and Thai added to Liso Languages.

New - Evoko Home: SNMP Support v1.0 Implemented

New- Evoko Home:Room CSV Import with full structure.

New - Evoko Home: *BETA*ERM Integration Server - Service to use ERMs with Evoko Home. Read more.

New - Evoko Home: CPU Scalability - NodeJS PM2 Implementation

New - Evoko Home: Reworked Monitoring Page for Performance and Usability.

Improvement - Evoko Home:Full implementation of LDAP with scheduling and handling of adding, editing, and deleting.

Improvement - Evoko Home: oAuth Changes for O365

Improvement - Evoko Home: Fix for 802.1 CSR request introduced in v2.1.1 (command injection vulnerability)

The Minors

Improvement - Evoko Liso: Changed Liso Hostname

Improvement - Evoko Liso:Russian and Icelandic for "Filtering by Equipment" issue resolved.

Improvement - Evoko Liso: Updated onboard diagnostics tools.

Improvement - Evoko Home: Totals for Active/Inactive Devices Shown

Improvement - Evoko Home: Ability to remote restart Evoko Liso

Improvement - Evoko Home: Time Stamps Now Added to Logs on Linux.

Improvement - Evoko Home: Room overview now displays differently if device is sleeping or offline.

Improvement - Evoko Home: Device Details now available in Monitoring Page.

Improvement - Evoko Home: Added proxy support for firmware download.

Improvement - Evoko Home: Created Read Only User that can check statistics in Evoko Home only.

Improvement - Evoko Home: Resolved issue with local admins getting an error when landing on the room overview screen.

Improvement - Evoko Home: Limited the publishing of settings for Local Admin Users.

Improvement - Evoko Home: ERM Service now restarts after installation.

Improvement - Evoko Home: GMT Time-Zones are now in order.

Improvement - Evoko Home:Display numbers of meetings in statistics.

Improvement - Evoko Home: Evoko Home now reports on device being down or unresponsive.

Improvement - Evoko Home: Pie Charts now reflect chosen rooms only.

Improvement - Evoko Home: Can now schedule daily statistic report.

Improvement - Evoko Home: Implement latest NFS API changes to NFS Backend Connector.

Improvement - Evoko Home: Encrypted password for MongoDB credentials when using external MongoDB instance.

Improvement - Evoko Home: Scheduled imports can now be downloaded from a path rather than a selected file.

Improvement - Evoko Home: Customize CSR - 802.1x and upload script implemented.

Improvement - Evoko Home: Addressed stack based buffer overflow, brute force on password reset verification as well as pairing key verification.

Overview Screen (v2.0.3)

Improved: Updated some dependencies.

Improved: SSL/TLS certificate changes should now be automatically picked up by the server.

Improved: Improved resilience for temporary network issues by a 30 second timeout before starting to display disconnected....

Changed: Adjusted the position slightly of the displayed logos.

Changed: Adjusted the displayed subject on the Overview Screen in some scenarios (when private, ad-hoc and when subject is disabled) to Booked to match Liso.

Fixed: Issue with room tiles not turning amber 10 minutes before a meetings starts if check-in was disabled.

Fixed: Issue with multi-day meetings only being displayed during the first day.

Fixed: Issue with the wrong room name value being displayed in the layout configurator.

Fixed: Issue with display settings (subject/organizer) not applying with all Evoko Home environments.

Get A Room App (v2.0.2)

Improved: Updated some dependencies.

Improved: SSL/TLS certificate changes should now be automatically picked up by the server.

Fixed:Compatibility issue with Evoko Home v2.2.

To connect Evoko Home to your Google G Suite environment you need to go though the Evoko Home web wizard. Start by selectingGoogle G Suiteas your booking system and then press "Next". Step 5: Basic Evoko Home setup

Enter the server URL https://www.googleapis.comfollowed by your service account and uploading you .p12 key, then press "Next".

Enter the email address of a super admin account that is subscribed to the resource calendars in Google G Suite.

Enter the https application port you would like to use (default3002). Additionally, you can opt to upload your own SSL/TLS certificate. If no certificate is uploaded, a unique auto generated self-singed certificate will be used.

Enter a NTP server (e.g. time.google.com) that the Evoko Home server and Liso units have access to.

Agree to the conditions of the EULA and press "Next".

Credentials should have been generated for your instance of Evoko Home, please make note of these credentials since they are only shown once.

Once successfully done with connecting Evoko Home to Google G Suite move on to

Important! Evoko Control Panel version8.0.6.1(or above) and Room Manager OS version of V1.5 / V2.5 (or above) is required.

Ok, but how can I tell the OS on a Room Manager? And.. how doI update the OS on a Room Manager?

NTP servers can be entered under the tab "System Properties" in the Evoko Control Panel.

If you'd like to assign multiple NTP servers as a fallback then simply separate them with a comma e.g. 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org

Note! All changes made in the Evoko Control Panel has to be uploaded to the Room Manager in order to be applied.

The Overview screen is a great way to get a quick look on the status of meeting rooms or finding your way to a specific meeting.

By using a large screen to display an overview of certain meeting rooms of your choice you are providing a way for guests/employees to easily find their way to your meeting or find an available room for instant meetings.

The overview screen displays the status of each room using the same familiar Liso colors (green/amber/red) as well as in which direction it is located. submitting a request

Every few seconds, the tiles flip to display meeting details. And then back to displaying the direction again.

To use the Overview Screen you need to setup a server. The Overview Screen server is written as a separate Node.js application from Evoko Home which runs on it's own dedicated port (default 4000) that utilizes the Evoko Home API to fetch meeting room data. Since the Overview Screen server is separate from Evoko Home you get to decide for yourself if you want to run it on the same server as Evoko Home or on a separate server.

Another thing, it runs in a web browser! Meaning that you don't need to have any particular media player or screen. As long as you can get a fairly modern web browser with a connection to your Overview Screen server running on your screen, you're good to go.

Install the Evoko Overview Screen server on Windows

Install the Evoko Overview Screen sever on Linux

How do I use the Evoko Overview screen?

Install the Evoko Overview Screen sever on Windows

This part will go through how to install Evoko Overview Screen server on a Windows server.

Windows server prerequisites

A server running a Windows server 2008 R2 (or later).

A free and accessible application port (default4000).

Access to the Evoko Home server running v2.Xon the application port (default 3000/ 3002).

SSL/TLS certificate to use HTTPS (recommended). HTTP can be used however is discouraged for accessing the Overview Screen admin portal from anything other than localhost as Evoko Home admin credentials will need to be submitted to login to the admin portal.

Windows installation steps

Download the latest version of Overview Screen server for Windows to the server.

Run the executable evoko-overview-screen-server-v2.x.y.exe.

Select where to install.

Make sure to install the Overview Screen server as service so it always will run in the background.

Once complete, press "Finish" and open the configuration file.

Edit the configuration file (C:\ProgramData\Evoko\config.toml) according to your environment and then save.See below table for more details.

[evokohome]

# If Evoko Home is installed on another host, replace localhost with

# the address of your Evoko Home installation. Note that you may

# need to change the protocol as well: use "wss://" for encrypted

# and "ws://" for unencrypted communication.

uri = "ws://localhost:3000/websocket"

# Replace email/pass with a valid admin user in Evoko Home

email = "[email protected]"

password = "evoko-home-admin-password"

[appconnector]

# Replace with your external hostname

domain = "server.domain.tld"

# Appconnector server port

port = 8443

[overview]

# Overview server port

port = 4000

[ssl]

# Path to private key and certificate. These are required to enable

# encrypted HTTP (HTTPS). If left empty (default) an attempt is made

# to locate and use the certificates of Evoko Home on the same host.

# If no usable certificates was found, overview and get-a-room will

# fall back to using unencrypted HTTP, which is not recommended for

# real use.

key = ""

cert = ""

[smtp]

# The adress used in the from field in sent emails

from = "User Name <[email protected]>"

host = "smtp-relay.gmail.com"

# port = 25

# ssl = true

# tls = true

# user = "smtpusername"

# password = "smtppassword"

# timeout = 5000

# domain = "evoko.test.org"

# authentication = ["PLAIN", "LOGIN", "CRAM-MD5", "XOAUTH2"]

Value

Description

uri

URL for the Evoko Home server.

Use "ws://localhost:3000/websocket" if Evoko Home runs on the same host.

Use"wss://evokohomeserver.tld:3002/websocket" if Evoko Home runs on another host.

email

Email address of an Evoko Home admin account to use for API authentication.

password

Password for the Evoko Home admin account.

port

The Overview Screen server listen port (default4000).

key

Path to SSL/TLS key. Both *.pemand*.keyformats are valid. If left empty the Appconnector will check for a key in the default Evoko Home install folderC:\Program Files\EVOKO\EvokoHome\liso_files\certificates\server.key.

cert

Path to SSL/TLS certificate. Both *.pemand*.crtformat should be accepted. If left empty the Appconnector will check for a certificate in the default Evoko Home install folderC:\Program Files\EVOKO\EvokoHome\liso_files\certificates\server.crt.

In order for changes in config.toml to be applied we need to restart the service under services.msc.

Look for a service namedEvoko Overview Screenand restart it.

If there are no errors in the configuration nor any firewall blocking you should be able to access the Overview Screen admin portal via a web browser (e.g. https://localhost:4000/admin ).

Install the Evoko Overview Screen server on Linux

This part will go through how to install Evoko Overview Screen server on a Linux server.

Linux server prerequisites

A server running aDebian baseddistribution(Ubuntu Server 18.04 LTS recommended).

A free and accessible application port (default 4000).

Access to the Evoko Home server running v2.Xon the application port (default 3000/ 3002).

A user withsudopermission.

Internet access during installation to download dependencies.

Node.js (v8.x) (already installed with Evoko Home ifusing the same server).

SSL/TLS certificate to use HTTPS (recommended). HTTP can be used however is discouraged for accessing the Overview Screen admin portal from anything other than localhost as Evoko Home admin credentials will need to be submitted to login to the admin portal.

Linux installation steps

Download the latest version of Overview Screen server for Linux to the server.

Make sure that Node.js and npm is installed, you can do this by checking the version:

nodejs -v && npm -v

If not, then you can install Node.js/npm using the below command:

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -

sudo apt install -y nodejs

Install using npm with the below command:

sudo npm install -g evoko-overview-screen-server-v2.*.tgz

Once the installation is finished, to test that it was successful and to view available commands run:

evoko-overview--help

To proceed, generate a configuration file using:

sudo evoko-overview config

Note! The Overview Screen server and Get A Room Appconnector share the same configuration file so no need to run the above command if you already have a configuration file generated.

Open the configuration file with a text editor (we're going to use nano):

sudo nano /etc/evoko/config.toml

Edit the configuration file according to your environment and save (ctrl + x>y>enter).

[evokohome]

# If Evoko Home is installed on another host, replace localhost with

# the address of your Evoko Home installation. Note that you may

# need to change the protocol as well: use "wss://" for encrypted

# and "ws://" for unencrypted communication.

uri = "ws://localhost:3000/websocket"

# Replace email/pass with a valid admin user in Evoko Home

email = "[email protected]"

password = "evoko-home-admin-password"

[appconnector]

# Replace with your external hostname

domain = "server.domain.tld"

# Appconnector server port

port = 8443

[overview]

# Overview server port

port = 4000

[ssl]

# Path to private key and certificate. These are required to enable

# encrypted HTTP (HTTPS). If left empty (default) an attempt is made

# to locate and use the certificates of Evoko Home on the same host.

# If no usable certificates was found, overview and get-a-room will

# fall back to using unencrypted HTTP, which is not recommended for

# real use.

key = ""

cert = ""

[smtp]

# The adress used in the from field in sent emails

from = "User Name <[email protected]>"

host = "smtp-relay.gmail.com"

# port = 25

# ssl = true

# tls = true

# user = "smtpusername"

# password = "smtppassword"

# timeout = 5000

# domain = "evoko.test.org"

# authentication = ["PLAIN", "LOGIN", "CRAM-MD5", "XOAUTH2"]

Value

Description

uri

URL for the Evoko Home server.

Use "ws://localhost:3000/websocket" if Evoko Home runs on the same host.

Use"wss://evokohomeserver.tld:3002/websocket" if Evoko Home runs on another host.

email

Email for an Evoko Home admin account to use for API authentication.

password

Password for the Evoko Home admin account.

port

The Overview Screen server listen port (default4000).

key

Path to SSL/TLS key, both *.pemand*.keyformat should be accepted. If left empty the Appconnector will check for key in the default Evoko Home install folder/home/$USER/Evoko Home/liso_files//certificates/server.key.

cert

Path to SSL/TLS certificate, both *.pemand*.crtformat should be accepted. If left empty the Appconnector will check for certificate in the default Evoko Home install folder /home/$USER/Evoko Home/liso_files//certificates/server.crt.

To make sure the configuration checks out, temporarily start the overview server by running:

sudo evoko-overview start

If started successfully you should get a similar output to the below:

Starting Evoko Overview Screen 2.0.0

* Loading config from /etc/evoko/config.toml: OK

- Found Evoko Home installation

- SSL certificates found. Using secure HTTPS.

If successful you should be able to access the Overview Screen admin portal via a web browser (e.g. https://localhost:4000/admin ).

Press Ctrl + Cin the shell once done with the temporary test to stop the Overview Screen server.

We want the Overview Screen server to run as a service so it will continue running even after we close our shell, we can accomplish this using systemd by running:

sudo evoko-overview install

Enable the Overview Screen server to start on boot:

sudo systemctl enable evoko-overview-screen

Start the Overview Screen server:

sudo systemctl start evoko-overview-screen

Now that the installation is finished you may remove the installation package:

sudo rmevoko-overview-screen-server-v2.*.tgz

How do I use the Evoko Overview Screen?

Once you got the Overview Screen server installed you can start creating Layouts and connecting Screens (i.e. web browsers). The Overview Screen is rather simple and consists of two web pages:

/overview - where you display

/admin - where you administer

Web browser support

Before jumping straight into a web browser, consider which one to use.Use the below list as a general guideline when picking a web browser (we of course recommend running the latest version available).

Mozilla Firefox 32+

Microsoft Edge 15+

Google Chrome 51+

Apple Safari 11+

Internet Explorer 11 (and below versions) are known to be incompatible and is not supported.

Note! The Overview Screen uses web browser local storage (similar to cookies) to store configuration details, if these details are cleared then the screen will return to unconfigured state.

/overview - where you display

To get started, open the web browser you've decided to use on your screen and enter your Overview Screen server URL followed by /overview (e.g. https://localhost:4000/overview ). If successful, a page similar to the below image should be displayed along with a uniquescreen name, in our case "Remarkable meeting".

That's it! It's that simple to register a new screen. To configure the screen move on to the admin portal.

If you want to register several screens then you can do so by entering the same Overview Screen URL (e.g. https://localhost:4000/overview ) in the web browser running on the other screens and each screen will get their own unique screen name.

/admin - where you administer

Now that we have a screen registered and connected to the Overview Screen server we can configure it from the admin portal by entering the Overview Screen server address followed by/admin (e.g. https://localhost:4000/admin ).

This will prompt a login form, sign in with an Evoko Home admin account.

Once signed in, we can now see our our screen "Remarkable meeting" under Online screens.

Navigate to Layouts and press the blue button in the bottom right corner to create a new layout. There are a few options that goes into a layout, mainly setting up your grid of rooms by declaring the number of columns/rows you want followed by selecting the appropriate room for each tile.

Now navigate back to Screensand select the newly created layout for the screen, then press Save.

Once we've saved our layout for our screen it will start to be display on our screen.

Optionally under Settingsa logo in.png format can be uploaded to be displayed on our screens.

Once uploaded the logo will be displayed in the bottom left corner.

Note! Time, date and time zone displayed on the Overview Screen will be fetched locally from the Overview Screen server it's running on. Meaning you will currently not be able to have multiple overview screens in different time zones all displaying the correct time.

Success! Now that we've gone through the setup you've hopefully learned a thing or two how it works. If you wish to leave feedback then we suggest you do so by .

As usual, please find Evoko Room Manager downloads at https://www.evoko.se/downloads/

New: Setting to enable/disable daily error logs to be sent to the assigned system admin email. The setting can be found under the tab "Support" in the Evoko Control Panel and is disabled by default.

New:Room Manager will automatically reboot everyday to refresh memory. Reboot will occur around midnight for Room Managers configured to be "always on" and for Room Managers with sleep/wake configured it will reboot around an hour prior to sleep ends.

Improved: Enabling TLS v1.1 / TLS v1.2 between the booking system and Room Manager will now disable TLS v1.0 / SSL 3.0 / SSL 2.0 and vice versa.

Fixed: Bug when calculating statistics in the Evoko Control Panel.

Fixed: Issue introduced in 8.0.7.2 with some Room Managers rebooting themselves around each hour.

Next up is to setup Evoko Home and add rooms/users which this article will cover.

Global settings

Default room settings

Adding structures and rooms

Managing users

Global settings

Once you've signed in with your Evoko Home admin credentials you will have the option to edit your Global settings. Step 6: Evoko Liso installation

Setting

Description

Organisation name

NTP server IP

The DNS or IP address for the NTP server that should be used to fetch time/date (e.g. pool.ntp.org).

Download URL

The URL that the Evoko Home server will use to check for firmware updates, default ishttps://download-liso.evoko.se/

Firmware search location

Determines where Evoko Home will look for new Liso firmware:

Remote- checks release server https://download-liso.evoko.se/

Local- checks the local folder ../liso_files/

Service account email

The email/username for your service account (e.g. [email protected] ) granted with impersonation rights.

Service account password

The password for your service account (e.g. [email protected] ) granted with impersonation rights.

Working hours

Determines when a work day starts and ends by configuring Start/End.

Sync meetings for 1 day every

Sync meetings for 7 days every

Authentication

This can be set to eitherPINorPIN or RFIDand determines the possible ways to authenticate on a Liso.

RFID Enrollment

Determines the different ways RFID can be enrolled and associated with a user in Evoko Home.

Autoallow users to associate a new RFID tag with their user account by scanning their RFID tag on a Liso unit and then identifying themselves with their PIN.

Adminallows a Evoko Home administrator to add an RFID to a user in Evoko Home by editing the user under the tab "Users".

Requestedis basically the same asAuto. The difference being that after the RFID data is enrolled via the Liso device, the user cannot use their RFID tag until an administrator approves it in Evoko Home.

Authentication 802.1x

This option can either be enabled or disabled, if enabled it allows for use of 802.1x with the Liso panels. Please find more information on how to set it up here.

Pairing Key Authentication

Log Level

Determines how extensive the Evoko Home logging should be and can be set to 4 values ofError,Warning,Info,Debug.

PIN length

Determines the length of the user PIN and can be set to between3-9 Digits.

Proximity

Enables/disables the proximity sensor on the Liso devices.

Legacy API Authentication

Default room settings

Next up is to set the default rooms settings which will apply to all rooms until configured otherwise.

Setting

Description

Display on screen

Organizer- If enabled the meeting organaizer will be displayed on the Liso device.

Subject- If enabled the meeting subject will be displayed on the Liso device.

Time format

Determines the time format (12h or 24h) that should be used on the Liso device and can be set to either24 hour formator12 hour format.

Date format

Determines the date format (e.g.YYYY-MM-DD) that should be displayed on the Liso device.

Time Zone

Determines the time zone that should be used on the Liso device.

Language

Determines the language that should be used on the Liso device.

Sleep start and Sleep end

Determines the time period the Liso device should entered sleep, a minimum of 4 hours sleep is required.

Enable wake up on touch

Enables users to "wake up" Liso device from sleep by pressing on the touch panel.

Work days

Determines the days the Liso device should be active and used.

Below settings can all be set to Require authentication which means, if enabled that users will authenticate using PIN/RFID on screen.

Setting

Description

Enable Screen Reporting

Enables/disables users to report room equipment via the Liso unit.

Reporting email

Determines the email address room equipment reports should be sent to for the "Report from screen" feature.

Enable Book Instant Meeting

Enables/disables users to book meetings via the Liso unit.

Enable book future meeting

Enables/disables users to book future meetings via the Liso unit.

Enable end ongoing meeting

Enables/disables users to end an ongoing meeting via the Liso unit.

Enable delete future meeting

Enables/disables users to end/delete future meetings via the Liso unit.

Enable extend ongoing meeting

Enables/disables users to extend an ongoing meeting via the Liso unit.

Enable modify future meeting

Enables/disables users to extend/edit future meetings via the Liso unit.

Check-in required

Enables/disables a check-in feature which, if enabled, requires the user confirm their meeting on the Liso device within a set time limit to keep their booking.

Send check-in reminder

Check-in duration

Determines how long after the meetings start it should be possible to check-in before the system ends the meeting. Configurable values are5min,10min,15min,20min,25minand30min.

Adding structures and rooms

Start by adding structures.

Add/Import roomsin the left pane and assign to structures by drag-n-drop.

Under Rooms > Settings you can further configure your rooms by setting room equipment and capacity.

Managing users

Under "Users" in Evoko Home you are able to add and administer users.

Adding usersis notrequired unless you want to take advantage of the PIN/RFID Authentication to book meetings directly on the Liso. You can add users two ways:

Create single users

Click on the "Create User" button and enter credentials of the user you would like to add.

Import a list of users from a .csv file

Please see the attached users_.xlsx file which you can use to list your user information. Be sure to export the file as a .csv when completed.

It's very important to note if you are importing from a .csv file:

The .csv must have name and email fields at least.

The type field either needs to be Admin or User.

password needs to contain at least one capital letter and number.

First character of password must be letter.

password needs to be at least 8 characters long.

If any of the rows in the CSV do not meet this criteria than the respect rows will be skipped during import.

name

email

pin

rfid

type

password

Ben Mendoza

[email protected]

2008

1568452582

Admin

Pass4EvokoHome

Bob Andersson

[email protected]

9494

15F4B3D2

User

Once done setting up Evoko Home move on to

This document contains instructions on how to backup and restore the Evoko Home database. It is strongly recommended to create a backup copy of the database before manually editing the database contents.

Contents

Create a backup of the Evoko Home database on Windows

Create a backup of the Evoko Home database on Linux

Restore a backup to Evoko Home on Windows

Restore a backup to Evoko Home on Linux

Create a backup of the Evoko Home database on Windows

Start an elevated Command Prompt, for example by searching for cmd on the start menu, then right clicking and selecting Run as administrator. contact us

Change into the MongoDB bin folder. The location of this folder might vary, but the default location is C:\Program Files\MongoDB\Server\3.4\bin\ if you are running MongoDB 3.4.x and C:\Program Files\MongoDB\Server\3.2\bin\ if you are running MongoDB 3.2.x. We will use MongoDB 3.4 installed in the default folder throughout this guide, so please adjust the paths accordingly if you are using MongoDB 3.2 or have MongoDB installed in a non-default location. Example command:

cd "C:\Program Files\MongoDB\Server\3.4\bin"

Start another elevated Command Prompt window and change into the same directory as before. To do this, repeat step 1 and 2.

Go to Services and stop the ERM Service.

Downtime! Stopping the ERM Service make all Lisos fail to connect to the booking system, which means

No booked meetings will be synced to the Liso devices

No meetings can be booked on screen

If you wish to minimize the Liso downtime you can restart the ERM Service after step 7 in this section.

Switch to one of the Command Prompt windows you previously opened and start MongoDB by typing or pasting the following command:

mongod --dbpath ..\data

Troubleshooting If you are presented with a prompt after the step above, something went wrong and MongoDB could not be started. Please see the error messages in the command prompt window and either try to correct the issues yourself or copy them and contact us for assistance.

Leave this Command Prompt window open. You can minimize it if you want to.

Switch to the other Command Prompt window and type or paste the following to perform a dump (backup) of the database:

mongodump

The output should be similar to this screenshot: If you still have the other Command Prompt window visible, you will see information scrolling by there as well.

Note: Your database backup is now stored in the dump subfolder. If you repeat the process, the dump files are overwritten so make sure to save them securely until you are certain they are no longer needed.

Close the Command Prompt window where you ran the mongodump command, then switch to the first Command Prompt window and exit mongod cleanly by pressing ctrl-c on the keyboard. You can then close that Command Prompt window too. After this you can start the ERM Service if you wish to minimize downtime for the Liso system.

Success! You now have a backup copy of your database.

Create a backup of the Evoko Home database on Linux

Change into the correct directory: cd ~/Evoko\ Home/

Run the backup script: sudo bash backupdb.sh

The output will let you know where the backup is created. Copy or move this folder to a safe location as it is overwritten if you run the backup script again.

Success! You now have a backup copy of your database.

Restore a backup to Evoko Home on Windows

Steps 1-5 in the restore instructions are the same as in the backup instructions.

Start an elevated Command Prompt, for example by searching for cmd on the start menu, then right clicking and selecting Run as administrator.

Change into the MongoDB bin folder. The location of this folder might vary, but the default location is C:\Program Files\MongoDB\Server\3.4\bin\ if you are running MongoDB 3.4.x and C:\Program Files\MongoDB\Server\3.2\bin\ if you are running MongoDB 3.2.x. We will use MongoDB 3.4 installed in the default folder throughout this guide, so please adjust the paths accordingly if you are using MongoDB 3.2 or have MongoDB installed in a non-default location. Example command:

cd "C:\Program Files\MongoDB\Server\3.4\bin"

Start another elevated Command Prompt window and change into the same directory as before. To do this, repeat step 1 and 2.

Go to Services and stop the ERM Service.

Downtime! Stopping the ERM Service make all Lisos fail to connect to the booking system, which means

No booked meetings will be synced to the Liso devices

No meetings can be booked on screen

If you wish to minimize the Liso downtime you can restart the ERM Service after step 7 in this section.

Switch to one of the Command Prompt windows you previously opened and start MongoDB by typing or pasting the following command:

mongod --dbpath ..\data

Troubleshooting If you are presented with a prompt after the step above, something went wrong and MongoDB could not be started. Please see the error messages in the command prompt window and either try to correct the issues yourself or copy them and contact us for assistance.

Leave this Command Prompt window open. You can minimize it if you want to.

Copy the backup folder named dump to the MongoDB bin folder. In this example the path to the dump folder containing all backup files should be C:\Program

Files\MongoDB\Server\3.4\bin\dump

Switch to the second Command Prompt window and type or paste the following to drop (i.e. delete) the contents currently in the database and restore from the backup:

mongorestore --drop dump\

Important! This command deletes all data from the MongoDB server, replacing it with the data in your backup. If this is not what you want, do not run this command and for assistance.

The output should be similar to this: (truncated) If you still have the other Command Prompt window visible, you will see information scrolling by there as well.

Close the Command Prompt window where you ran the mongodump command, then switch to the first Command Prompt window and exit mongod cleanly by pressing ctrl-c on the keyboard. You can then close that Command Prompt window too. After this you can start the ERM Service if you wish to minimize downtime for the Liso system.

Success! You now have a backup copy of your database.

Restore a backup to Evoko Home on Linux

Change into the correct directory: cd ~/Evoko\ Home/

Run the restore script: sudo bash restoredb.sh

The output will ask whether you would like to remove the backup. Answer 1 to have the backup removed or 2 to keep it.

Evoko Home and MongoDB restarts.

The below instructions cover how to properly configure a static DNS on a Room manager.

Important! The Room Manager needs to be running OS version v2.6 (or above).Furthermore the following steps only applies to "ERM2"/"ERM2A" (v2.x) models and NOT "ERM" (v1.x).

Ok, but how can I tell the OS on a Room Manager? And.. how doI update the OS on a Room Manager?

1. Download the "ipconfig.ini" file, select mode and assign the desired static address(es):

Download the "ipconfig.ini" file here.

Extract and open the "ipconfig.ini" file with a regular text editor (e.g. notepad).

Set "MODE" to either 0 or 1 depending on if you would like to use DHCP or set a static IP along with your static DNS.

MODE=0 - For static DNS, IP, subnet and gateway.

MODE=1 - For static DNS with DHCP.

Assign the desired address(es) as displayed in the examples above.

Save the changes made to the "ipconfig.ini" file and put the file on your USB-stick.

2. Place the "ipconfig.ini" file in the appropriate folder on your room manager:

Insert the USB-stick containing your edited "ipconfig.ini" file in the Room Manager.

Login as System Admin on your room manager.

Press "Exit Application".

On the Windows CE desktop navigate to My Device > "Hard disk" (Which is your USB).

Mark/highlight the "ipconfig.ini" file and press Edit > Copy in the top menu.

Navigate to "My Device" > "ResidentFlash" > "MeetingManagementSetup".

Paste the "ipconfig.ini" file in the "MeetingManagementSetup" folder.

3. Reboot your room manager and make sure that the DNS-server has been assigned:

Reboot your Room manager.

Login as System Admin on your room manager.

Press "Exit Application".

In Windows CE go to "Start" > "Programs" > "Command Prompt".

Type "ipconfig" and check under "DNS servers".

Now that the necessarybooking system preparations have been made and Evoko Home is installed we can start integrating the two.

To connect Evoko Home to your booking system, you need to complete a wizard in your web browser. The wizard vary slightly depending on the booking system so please see the section that applies for your installation in this article.

Step 4a: Office 365

Step 4b: Exchange 2019 / 2016 / 2013 / 2010

Step 4c: Google G Suite

Step 4d: IBM Domino

Note! For security reasons it is not possible to upload SSL/TLS certificates or Google G Suite *.p12 key via a remote host.

Step 4a: Office 365

To connect Evoko Home to your Office 365 environment you need to go through the Evoko Home web wizard. Start by selecting Office 365 as your booking system and then click Next. Step 5: Basic Evoko Home setup

Select if you want Evoko Home to connect to Office 365 via a direct connection or a proxy, then click Next.

Enter the credentials (e.g. [email protected]) for your service account granted with application impersonation rights and then click Log In.

Important! If you are using modern (oAuth) authentication, please see additional information on how to set it up here.

Enter the https application port you would like to use (default 3002). Additionally, you can opt to upload your own SSL/TLS certificate (this needs to be done from localhost and not a remote host) and then click Next. If no certificate is uploaded, a unique auto generated self-singed certificate will be used.

Enter a NTP server (e.g. pool.ntp.org) that the Evoko Home server and the Evoko Liso units will have access to and then click Next.

Agree to the conditions of the EULA and then click Accept.

Credentials should have been generated for your instance of Evoko Home, please make note of these credentials since they are shown only once and then click Finish.

Once successfully done with connecting Evoko Home to Office 365 move on to Step 5: Basic Evoko Home setup

Step 4b: Exchange 2019 / 2016 / 2013 / 2010

To connect Evoko Home to your Exchange 2019 / 2016 / 2013 / 2010 environment you need to go through the Evoko Home web wizard. Start by selecting your booking systemand then click Next. (In this example we have chosen Exchange 2016, the steps for Exchange 2013 and 2010 is the same).

Enter the credentials (e.g. [email protected]) for your service account granted with application impersonation along with your Exchange server EWS URL (e.g. https://exchangeserver.tld/EWS/Exchange.asmx) and a administration email (e.g. [email protected]).Then click Log In.

Enter the https application port you would like to use (default 3002). Additionally, you can opt to upload your own SSL/TLS certificate (this needs to be done from localhost and not a remote host) and then click Next. If no certificate is uploaded, a unique auto generated self-singed certificate will be used.

Enter a NTP server (e.g. pool.ntp.org) that the Evoko Home server and the Evoko Liso units will have access to and then click Next.

Agree to the conditions of the EULA and then click Accept.

Credentials should have been generated for your instance of Evoko Home, please make note of these credentials since they are shown only once and then click Finish.

Once successfully done with connecting Evoko Home to Exchange 2016 / 2013 / 2010 move on to Step 5: Basic Evoko Home setup

Step 4c: Google G Suite

To connect Evoko Home to your Google G Suite environment you need to go through the Evoko Home web wizard. Start by selecting Google G Suite as your booking system and then click Next.

Enter the server URL https://www.googleapis.comfollowed by your service account and then upload your .p12 key (this needs to be done from localhost and not a remote host), then enter the email address of a super admin account that is subscribed to the resource calendars in Google G Suite. Then click Log In.

Enter the https application port you would like to use (default 3002). Additionally, you can opt to upload your own SSL/TLS certificate (this needs to be done from localhost and not a remote host) and then click Next. If no certificate is uploaded, a unique auto generated self-singed certificate will be used.

Enter a NTP server (e.g. pool.ntp.org) that the Evoko Home server and the Evoko Liso units will have access to and then click Next.

Agree to the conditions of the EULA by clickingAccept.

Credentials should have been generated for your instance of Evoko Home, please make note of these credentials since they are shown only once and then click Finish.

Once successfully done with connecting Evoko Home to Google G Suite move on to Step 5: Basic Evoko Home setup

Step 4d: IBM Domino

To connect Evoko Home to your IBM Domino environment you need to go though the Evoko Home web wizard. Start by selecting IBM Domino as your booking system and then click Next.

Enter theIBM Domino server URL (e.g.https://dominoserver.tld/evoko/evoko.nsf/ResourceReservation?OpenWebService) with your credentials and a Evoko Home administration email (e.g. [email protected]) and then click Log In.

Enter the https application port you would like to use (default 3002). Additionally, you can opt to upload your own SSL/TLS certificate (this needs to be done from localhost and not a remote host) and then click Next. If no certificate is uploaded, a unique auto generated self-singed certificate will be used.

Enter a NTP server (e.g. pool.ntp.org) that the Evoko Home server and the Evoko Liso units will have access to and then click Next.

Agree to the conditions of the EULA and then click Accept.

Credentials should have been generated for your instance of Evoko Home, please make note of these credentials since they are shown only once and then click Finish.

Once successfully done with connecting Evoko Home to IBM Domino move on to

Note! The following applies to Office 365, Exchange 2019, Exchange 2016, Exchange 2013 and Exchange 2010.

Evoko Liso uses impersonation as it has many key advantages over delegation which is used by its predecessor, Evoko Room Manager.

Using delegation, each connection made to EWS (Exchange Web Services) is done by a specific account with delegation. This is no problem with smaller installs as the default EWSMaxConcurrency value will allow up to 27 concurrent connections to Office 365. But for larger installations, this requires a lot of service accounts to avoid the risk of connection throttling.For example, if you had 500 rooms in Office365 where the limit is fixed to 27 simultaneous connections, with delegation you would need to configure 20 separate service accounts. With impersonation, one service account is enough.

Developing the Evoko Liso, making the setup experience more streamlined and straight-forward. Eliminating the impact of throttling policies also made for a more "real-time" experience, with instant feedback from the Liso system.

Using impersonation, only a single service account (e.g. [email protected] ) is used for all communication, but from the Exchange server's view it is the individual rooms that makes the connection and therefore there are no issues with EWSMaxConcurrency, EWSMaxSubscriptions or any other throttling policy that could cause unwanted behavior.

Just when granting any other permission, impersonation needs to be configured in a responsible way.Please find more information about impersonation vs. delegation here and impersonation here.

In order to integrate Evoko Liso with your existing booking system some preparation in the booking system is necessary. Please select the booking system which you want to integrate with Evoko Home in the list below and go though the section.

Step 2a: Office 365

Step 2b: Exchange 2019 / 2016 / 2013

Step 2c: Exchange 2010

Step 2d: Google G Suite

Step 2e: IBM Domino

Step 2a: Office 365

This part will go through the necessary preparations needed in Office 365 to integrate Evoko Liso.

Create a service account

Grant the service account Impersonation rights

Option #1: With a management scope using Windows Powershell

Option #2: Without a management scope via the Exchange admin center

Create resource accounts

Create room lists using Windows PowerShell (Optional)

Create a service account

We recommend using a dedicated service account (e.g. [email protected] ) for integrating Evoko Liso with an Office 365 environment. This account will be used for authentication and carrying out requests between the Evoko software and Office 365 via EWS (Exchange Web Services).

Note! These instructions applies to the general Office 365 setup for setting up a normal user account. If e.g. running a hybrid environment within your organisation the setup process for a new user account might be different. Please visit the Hybrid Environment setup Guidelines for more information.

Go to the Office 365 Admin center and login with your Office 365 admin account.

In the Office 365 admin center click Add a user under Users. Step 3: Evoko Home installation

Enter the information for your service account, assign a licence and continue by clicking"Add".

Important! The service account needs a mailbox and therefore also a license.

Once the account is created, chose if you want to email the password or not and click Close.

Grant the service account Impersonation rights

Impersonation can be granted via either Windows PowerShell ( Option #1 ) or via the Office 365 Admin center ( Option #2 ) and with or without a management scope, we have listed two options below.For security practices we recommend granting Impersonation with a management scope.

You can read more about our decision on using impersonation rather than delegation in this article.

Important!Having the service account granted with Impersonation permission is arequirementto successfully integrate Evoko Liso with your Office 365 environment.

Option #1: With a management scope using Windows Powershell

The below method will grant your service account with impersonation permissions restricted only to resources (room and equipment mailboxes) by applying a management scope/Write scope.

Start of by connecting to your Office 365 environment via Windows PowerShell and authenticate with your Office 365 admin account. This is typically done by running the following commands:

##On the Execution Policy Change question type Y and press Enter.

Set-ExecutionPolicy RemoteSigned

## This will prompt a pop-up asking for credentials.

## Enter the user name and password for your Office 365 admin account and click Ok.

$UserCredential = Get-Credential

## Create session

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

## Import session

Import-PSSession $Session

Create a management scope which will be used in the next step to restrict the impersonation right. The below command will limit the scope to resources (room and equipment mailboxes):

New-ManagementScope -Name "ResourceMailboxes" -RecipientRestrictionFilter { RecipientTypeDetails -eq "RoomMailbox" -or RecipientTypeDetails -eq "EquipmentMailbox" -or PrimarySmtpAddress -eq "[email protected]"}

This will grant the service account Impersonation using the management scope:

New-ManagementRoleAssignment Name "ResourceImpersonation" Role ApplicationImpersonation -User [email protected] CustomRecipientWriteScope "ResourceMailboxes"

Note!make sure to replace [email protected] in the above command with the equivalent for your service account.

Confirm that impersonation has been granted to your service account:

Get-ManagementRoleAssignment -Role ApplicationImpersonation -GetEffectiveUsers

The above command will display a table of accounts assigned with impersonation. Please make sure that in the Role column the value is ApplicationImpersonation, and in that same row under the EffectiveUsername is the name of your service account. If so, that means the setup of the impersonation was successful.

Option #2: Without a management scope via the Exchange admin center

The below method will grant your service account with impersonation permission for all accounts.

Go to the Office 365 Exchange admin center and login with your Office 365 admin account.

In the Exchange admin center, navigate to permissions >admin roles">and click the add-button.

Under "Name" enter Application Impersonation". The "Description" can be left empty and the "Write scope" can be kept at "Default".

Tip!If a management scope is created in your environment (as done in step 2 of option #1 ) then it will be displayed in the drop-down list under "Write scope" and possible to apply.

Under "Roles" click add and add the admin role "ApplicationImpersonation".

Under "Members" add your service account and then click "Save".

Create resource accounts

A resource account or room mailbox is the calendar that is used to book the room via e.g. Outlook and the calendar the Evoko Liso/Home will synchronize meeting data with. Oneresource account per Evoko Liso is necessary unless you want two or more Evoko Liso synchronizing meeting information with the same calendar.

Note!If you already have all resource accounts properly setup you can proceed to the next section.

Go to Office 365 Exchange admin center and login with your Office 365 admin account.

In the Exchange admin center navigateto "Recipients" > "Resources".

Click the "+" and select "Room mailbox".

Enter the "Room name" and specify the resource accounts "Email address".Optionally add a "Location" and enter the "Capacity" and continue by clicking "Save".

Your resource account should now appear in the list of resources.

We recommend you configure the resource account with the below cmdlet using Windows PowerShell:

Set-CalendarProcessing [email protected] -AutomateProcessing AutoAccept -AddOrganizerToSubject $False -DeleteComments $False -DeleteSubject $False -RemovePrivateProperty $false

Note!to create several resource accounts simply repeat above steps in this section.

Create room lists using Windows PowerShell (Optional)

Room lists help you to organize your rooms. If your company has several buildings with rooms that can be booked for meetings, it might help to create a room lists per building or even per floor.

Room lists are specially marked distribution groups that you can use the same way you use distribution groups. In Evoko Home you can import room lists which makes it a convenient way to add your rooms.

The below commands will help you to create a single room list and then add rooms, or create a single room list that holds all existing rooms in one go in Office 365 using Windows PowerShell:

Creates a new room list named My Rooms:

New-DistributionGroup -Name "My Rooms" RoomList

Adds a resource account ([email protected]) to an existing room list (My Rooms):

Add-DistributionGroupMember -Identity "My Rooms" -Member [email protected]

Fetches all resources (room mailboxes) and puts them in a single new room list named My Rooms:

$RoomAlias = Get-Mailbox -RecipientTypeDetails RoomMailbox | select -ExpandProperty Alias New-DistributionGroup -RoomList -Name "My Rooms" -Members $RoomAlias

Displays a table of all room lists in your Office 365 environment:

Get-DistributionGroup | Where { $_.RecipientTypeDetails -eq "RoomList" } | Format-Table DisplayName, Identity, PrimarySmtpAddress

Once done preparing Office 365 move on to Step 3: Evoko Home installation

Step 2b: Exchange 2019/2016/2013

This part will go through the necessary preparations needed in Exchange 2016/2013 to integrate Evoko Liso.

Create a service account

Grant the service account Impersonation rights

Option #1: With a management scope using the Exchange Management Shell

Option #2: Without a management scope via the Exchange admin center

Create resource accounts

Create room lists using the Exchange Management Shell (Optional)

Create a service account

We recommend using a dedicated service account (e.g. [email protected] ) for integrating Evoko Liso with an Exchange 2016 / 2013 environment. This account will be used for authentication and carrying out requests between the Evoko software and Exchange 2016 / 2013 via EWS (Exchange Web Services).

Open "Active Directory Users and Computers" and create a user. This is typically done by navigating to the desired Organizational Unit (OU) >right click> "New" > "User".

Fill in the necessary information for your service account and click Next to continue.

Enter the password for your service account and click Next.

Review the data and click Finish to create the user in Active Directory.

Next go tohttps://<Exchange server>/ecp/and login with your Exchange admin account.

In the Exchange admin center navigate to "recipients" > "mailboxes".

Click add and select "User mailbox".

Fill in an alias and select the service account in Active Directory, then click "save".

Once your service account is created it should appear in the list of mailboxes.

Grant the service account Impersonation rights

Impersonation can be granted via either Exchange Management Shell ( Option #1 ) or via the Exchange Admin center ( Option #2 ) and with or without a management scope, we have listed two options below.For security practices we recommend granting Impersonation with a management scope.

You can read more about our decision on using impersonation rather than delegation in this article.

Important!Having the service account granted with Impersonation permission is arequirementto successfully integrate Evoko Liso with your Exchange 2016 / 2013 environment.

Option #1: With a management scope using the Exchange Management Shell

The below method will grant your service account with impersonation permissions restricted only to resources (room and equipment mailboxes) by applying a management scope/Write scope.

Start of by launching the Exchange Management Shell on the Exchange server.

Create a management scope which will be used in the next step to restrict the impersonation right. The below command will limit the scope to resources (room and equipment mailboxes):

New-ManagementScope -Name "ResourceMailboxes" -RecipientRestrictionFilter { RecipientTypeDetails -eq "RoomMailbox" -or RecipientTypeDetails -eq "EquipmentMailbox" }

This will grant the service account Impersonation using the management scope:

New-ManagementRoleAssignment Name "ResourceImpersonation" Role ApplicationImpersonation -User [email protected] CustomRecipientWriteScope "ResourceMailboxes"

Note!make sure to replace [email protected] in the above command with the equivalent for your service account.

Confirm that impersonation has been granted to your service account:

Get-ManagementRoleAssignment -Role ApplicationImpersonation -GetEffectiveUsers

The above command will display a table of accounts assigned with impersonation. Please make sure that in the Role column the value is ApplicationImpersonation, and in that same row under the EffectiveUsername is the name of your service account. If so, that means the setup of the impersonation was successful.

Option #2: Without a management scope via the Exchange admin center

The below method will grant your service account with impersonation permission for all accounts.

In the Exchange admin center, navigate to permissions >admin roles">and click the add-button.

Under "Name" enter Application Impersonation". The "Description" can be left empty and the "Write scope" can be kept at "Default".

Tip!If a management scope is created in your environment (as done in step 2 of option #1 ) then it will be displayed in the drop-down list under "Write scope" and possible to apply.

Under "Roles" click add and add the admin role "ApplicationImpersonation".

Under "Members" add your service account and then click "Save".

Create resource accounts

A resource account or room mailbox is the calendar used to book the room via e.g. Outlook and the calendar Evoko Liso/Home will synchronize meeting data with. Oneresource account per Evoko Liso is necessary unless you want two or more Evoko Liso synchronizing with the same calendar.

Note!If you already have all resource accounts properly setup you can proceed to the next section.

In the Exchange admin center navigateto "Recipients" > "Resources".

Click the "+" and select "Room mailbox".

Enter the "Room name" and specify the resource accounts "Email address".Optionally add a "Location" and enter the "Capacity" and continue by clicking "Save".

Your resource account should now appear in the list of resources.

We recommend you configure the resource account with the below cmdlet using the Exchange Management Shell:

Set-CalendarProcessing [email protected] -AutomateProcessing AutoAccept -AddOrganizerToSubject $False -DeleteComments $False -DeleteSubject $False -RemovePrivateProperty $false

Note!to create several resource accounts simply repeat above steps in this section.

Create room lists using the Exchange Management Shell (Optional)

Room lists help you to organize your rooms. If your company has several buildings with rooms that can be booked for meetings, it might help to create a room lists per building or even per floor.

Room lists are specially marked distribution groups that you can use the same way you use distribution groups. In Evoko Home you can import room lists which makes it a convenient way to add your rooms.

The below commands will help you to create a single room list and then add rooms, or create a single room list that holds all existing rooms in one go using the Exchange Management Shell:

Creates a new room list named My Rooms:

New-DistributionGroup -Name "My Rooms" RoomList

Adds a resource account ([email protected]) to an existing room list (My Rooms):

Add-DistributionGroupMember -Identity "My Rooms" -Member [email protected]

Fetches all resources (room mailboxes) and puts them in a single new room list named My Rooms:

$RoomAlias = Get-Mailbox -RecipientTypeDetails RoomMailbox | select -ExpandProperty Alias New-DistributionGroup -RoomList -Name "My Rooms" -Members $RoomAlias

Displays a table of all room lists in your Office 365 environment:

Get-DistributionGroup | Where { $_.RecipientTypeDetails -eq "RoomList" } | Format-Table DisplayName, Identity, PrimarySmtpAddress

Once done preparing Exchange 2016 / 2013 move on to Step 3: Evoko Home installation

Step 2c: Exchange 2010

This part will go through the necessary preparations needed in Exchange 2010 to integrate Evoko Liso.

Create a service account

Grant the service account Impersonation rights

Create resource accounts

Create room lists using the Exchange Management Shell (Optional)

Create a service account

We recommend using a dedicated service account (e.g. [email protected] ) for integrating Evoko Liso with an Exchange 2010 environment. This account will be used for authentication and carrying out requests between the Evoko software and Exchange 2010 via EWS (Exchange Web Services).

Open "Active Directory Users and Computers" and create a user. This is typically done by navigating to the desired Organizational Unit (OU) >right click> New > User.

Fill in the necessary information for your service account and click Next to continue.

Enter the password for your service account and click Next.

Review the data and click Finish to create the user in Active Directory.

Open up the Exchange Management Console and navigate to "Recipient Configuration" >"Mailbox".

In the menu on the right, select "New Mailbox".

Select "User Mailbox" and click "Next".

Choose "Existing users"and select the service accountfrom Active Directory, then click "Next".

Specify an Alias forthe service account and click "Next".

Your mailbox is now ready for provisioning, click "New".

Your service account is now created, click "Finish".

Grant the service account Impersonation rights

You can read more about our decision on using impersonation rather than delegation in this article.

Important!Having the service account granted with Impersonation permission is arequirementto successfully integrate Evoko Liso with your Exchange 2010 environment.

The below method will grant your service account with impersonation permissions restricted only to resources (room and equipment mailboxes) by applying a management scope/Write scope.

Start of by launching the Exchange Management Shell on the Exchange server.

Create a management scope which will be used in the next step to restrict the impersonation right. The below command will limit the scope to resources (room and equipment mailboxes):

New-ManagementScope -Name "ResourceMailboxes" -RecipientRestrictionFilter { RecipientTypeDetails -eq "RoomMailbox" -or RecipientTypeDetails -eq "EquipmentMailbox" }

This will grant the service account Impersonation using the management scope:

New-ManagementRoleAssignment Name "ResourceImpersonation" Role ApplicationImpersonation -User [email protected] CustomRecipientWriteScope "ResourceMailboxes"

Note!make sure to replace [email protected] in the above command with the equivalent for your service account.

Confirm that impersonation has been granted to your service account:

Get-ManagementRoleAssignment -Role ApplicationImpersonation -GetEffectiveUsers

The above command will display a table of accounts assigned with impersonation. Please make sure that in the Role column the value is ApplicationImpersonation, and in that same row under the EffectiveUsername is the name of your service account. If so, that means the setup of the impersonation was successful.

Create resource accounts

A resource account or room mailbox is the calendar used to book the room via e.g. Outlook and the calendar Evoko Liso/Home will synchronize meeting data with. Oneresource account per Evoko Liso is necessary unless you want two or more Evoko Liso synchronizing with the same calendar.

Note!If you already have all resource accounts properly setup you can proceed to the next section.

In the Exchange Management Console navigate to "Recipient Configuration">"Mailbox".

In the right menu, click on "New Mailbox".

Select "Room Mailbox".

Select "New User".

Enter the name of the resource account and select the Organizational Unit (OU) where you want the resource account to be placed. Enter First and Last name of the resource account, then click Next.

Add an Alias for your resource account and click "Next".

Enter your Archiving settings, however in this guide were skipping it. click "Next".

Your resource account is ready to be created. click "New".

Your resource account is now created, click Finish.

We recommend you configure the resource account with the below cmdlet using the Exchange Management Shell:

Set-CalendarProcessing [email protected] -AutomateProcessing AutoAccept -AddOrganizerToSubject $False -DeleteComments $False -DeleteSubject $False -RemovePrivateProperty $false

Note!to create several resource accounts simply repeat above steps in this section.

Create room lists using the Exchange Management Shell (Optional)

Room lists help you to organize your rooms. If your company has several buildings with rooms that can be booked for meetings, it might help to create a room lists per building or even per floor.

Room lists are specially marked distribution groups that you can use the same way you use distribution groups. In Evoko Home you can import room lists which makes it a convenient way to add your rooms.

The below commands will help you to create a single room list and then add rooms, or create a single room list that holds all existing rooms in one go using the Exchange Management Shell:

Creates a new room list named My Rooms:

New-DistributionGroup -Name "My Rooms" RoomList

Adds a resource account ([email protected]) to an existing room list (My Rooms):

Add-DistributionGroupMember -Identity "My Rooms" -Member [email protected]

Fetches all resources (room mailboxes) and puts them in a single new room list named My Rooms:

$RoomAlias = Get-Mailbox -RecipientTypeDetails RoomMailbox | select -ExpandProperty Alias New-DistributionGroup -RoomList -Name "My Rooms" -Members $RoomAlias

Displays a table of all room lists in your Office 365 environment:

Get-DistributionGroup | Where { $_.RecipientTypeDetails -eq "RoomList" } | Format-Table DisplayName, Identity, PrimarySmtpAddress

Once done preparing Exchange 2010 move on to Step 3: Evoko Home installation

Step 2d: Google G Suite

Coming shortly.. check the following article for Google G Suite during the meantime.

Once done preparing Google G Suite move on to Step 3: Evoko Home installation

Step 2e: IBM Domino

This part will go through the necessary preparations needed in IBM Domino to integrate Evoko Liso.

Domino Prerequisites

Install the Evoko database

Setup mail file access

Verify installation

Domino prerequisites

Domino 8.5.3 or above.

Domino server running the Calendar, Scheduling and HTTP tasks.

Resources and one administrator account to manage the room resource calendars (in this guide we use a user named "Roommate Evoko/Evoko" as example).

Resource calendars.

Install the Evoko database

Create a user, in our examples called "Roommate Evoko/Evoko" with necessary rights to create databases and rights to sign or run restricted LotusScript /Java agents (you can also use an existing account if preferred).

Create or use an existing mailbox for Remote Management and statistics.

Check/specify the User ID in the Programmability Restrictions section of the Current Server Document.Current Server Document > Security > Programmability Restrictions

Make sure that the Evoko database template downloaded from https://www.evoko.se/downloads is available in your local Notes data directory.

Start your Notes client.

Create a new database.

Choose Evoko Room Manager template as template from Server local.

Select your server where to install Evoko Room Manager.

Enter database Title.

Type evoko\evoko.nsf in the filename field and click OK.

Sign the new database with an ID with sufficient rights to execute agents (switch user ID before if necessary).

From a Domino Administration workstation, launch the Domino Administrator.

Click the Files tab for the server containing the Evoko Liso database.

Select the evoko\evoko.nsf database by right clicking on it and choose sign.

Sign All design documents and click OK.

Setup mail file access

Give the Evoko Room Manager user minimum Reader rights to a mail file that will be used for statistics.

Open evoko\evoko.nsf on the server and fill in the fields:

Username Roommate Evoko/Evoko (user with the rights to access resources and agents).

Remote Manager MailFile where the statistics and updates is sent.

Rooms and Resources reservation database.

Hide Subject on reservations leave unchecked unless you want to disable Evoko Room Manager access to meeting Subjects.

Disable confirmation mail leave unchecked unless you want to disable confirmation mails when booking reservations.

Debug leave unchecked unless Evoko support have asked you to enable this for troubleshooting or testing.

Verify installation

To test if the web service responds, type the following URL in a web browser:

https://yourdominoserver.tld/evoko/evoko.nsf/ResourceReservation?OpenWebService

If you get a response like shown below then the web service works:

Domino( wsdl ). GETCURRENTTIME GETAPPOINTMENT CREATEAPPOINTMENT UPDATEAPPOINMENT SHOWALLAPPOINTMENTTODAY SHOWALLAPPOINTMENTDATES SENDMESSAGE RMUPDATE RETRIEVEMAILS GETATTACHMENT RMMARKREAD RMDELETEMONITOREMAILS GETROOMS GETROOM GETUSERS GETUSER

Once done preparing IBM Domino move on to

Version v2.1 of Evoko Home introduces a basic LDAP integration in order to make it easier for system administrators to import users from their existing environment to Evoko Home.

The integration requires a LDAP v3 compliant directory and currently has been tested withMicrosoft Active Directory and Apache DS.

Import users via LDAP

Under the Users tab in Evoko Home press Import followed by Import from LDAP. submitting a request

This should prompt a form which contains the below values.

Field

Comment

LDAP Server

Domain name or IP address to the LDAP server.

Port

Server port to connect on. 636 is the default for use with TLS (LDAPS) and port 389 for use without TLS (LDAP).

Disable TLS

Checkbox to disable the use of TLS e.g. for non-secure LDAP connections on port 389.

Username

LDAP user (e.g. [email protected]) to be used for authentication.

Password

Password for the above mentioned LDAP user.

LDAP Search Base

Defines the directory base from which the LDAP search begins, for example ou=finance,dc=domain,dc=tldor ou=finance,o=organisation etc.

LDAP Search Filter

A search filter which will be applied within the defined LDAP search Base. The defaultvalue is (objectClass=organizationalperson) but can be changed to better fit your search.

Once the form is filled out press Import to initiate.

If successful a prompt with results should be displayed, otherwise it should throw an error.

Future of Evoko Home LDAP integration

We recognize that a simple manual import may be a bit too basic for most use cases and the need for easy user sync/management is out there. Therefore we want to let you know that we do intend to keep adding to the LDAP integration, starting with scheduled sync, deletion of users along with support for RFID fields.

We're interested in hearing your feedback on the LDAP integration going forward and better understand the major challenges that exists out there, feel free to let us know by.

As usual, please find downloads at https://www.evoko.se/downloads/

Fixed: Issue with remote upgrade not working properly in 8.0.7.5.

Fixed:Issue with needing to reboot the Room Manager or exit the application before an update uploaded via USB took effect.

Fixed: Issue withremote upgrade giving an error message about the Remote Management account not working even though the account checks out.

Fixed: An issue with an error message being presented when attempting to connect to Google G Suite.

Fixed: Issue with the Evoko Control Panel closing when adding a room (Step by step) under the tab "Dashboard" to an existing group.

Fixed:Issue with the "Admin credentials" and "Dashboard" tabs in the Evoko Control Panel being disabled when opening an existing configuration.

Fixed:Issue with the configured NTP server not properly updating in the Evoko Control Panel on change.

Microsoft Exchange will only allow a certain number of concurrent connections over EWS (Exchange Web Services) to a single account. If that limit is exceeded, new connections are denied until some of the existing connections have been closed.

For best performance, we strongly recommend not exceeding the admin account to room account ratio in the table below.

Important! If these values is exceeded, your Room Managers are likely to experience intermittent disconnection issues, the more the limit is exceeded the more frequent you should expect these disconnection issues.

Booking system

EWSMaxConcurrency

Room accounts per Room admin account

Office 365

27

26

Exchange 2016

10

9

Exchange 2013

27

26

Exchange 2010

10

9

Exchange 2007

19

Note! These are default values. The maximum number of concurrent connections (EWSMaxConcurrency) can be changed for Exchange 2010, 2013 and 2016, but not for Exchange Online/Office365.

For more information on EWS throttling in Exchange, please see EWS throttling in Exchange on Microsoft Office Dev Center.

For information on how to add more room administrator accounts to Evoko Control Panel and assign rooms to each admin account, please see the Setup Guide for your booking system.

Currently there is no way to change the Evoko Home SSL/TLS certificate via the web interface once Evoko Home is installed and configured. However, updating the certificate is easily done via the file system of the server.

To change the certificate that Evoko Home use, simply replace the certificate (server.crt) and key (server.key) files. Their default storage location is:

Windows: C:\Program Files\Evoko\EvokoHome\liso_files\certificates\

Linux:~/Evoko Home/liso_files/certificates/

Note! Before replacing your existing certificate and key make sure that you have a backup copy so you can revert back in case of issues.

Note! Make sure that you use the exact same file names (i.e. server.crt and server.key), otherwise Evoko Home won't recognize the files.

Once the new certificate and key files are in place, restart the Evoko Home service to load the new certificate:

Windows: restart the ERM Service under services.msc

Linux: runsudo supervisorctl restart evoko_home

After restarting the Evoko Home service make sure you can access it via http (e.g. http://localhost:3000 ) and it should, if successful, redirect you to https (e.g. https://localhost:3002 ).

Important!The following instructions applies to the Evoko Room Manager (ERM1001) andNOTits successor, the Evoko Liso (ERM2001).

Introduction

Create a Room Admin account

Create a Remote Management account (If youre going to use the EVO functionality)

Create and configure Room accounts

Configuration via the Evoko Control Panel

Introduction

The Evoko Room Manager is a system for booking and managing rooms. The Evoko Room Manager is mounted outside the room and display the booking status on beautiful touch-sensitive screens, the red or green background illumination of the screen allows you to see at a distance whether or not the room is free. You book meetings just as you have always done in MS Outlook. The Evoko Room Manager also makes it possible to create and manage bookings directly on the touch-sensitive screen.

Account use

Account type

No. of accounts

Comment

Room admin account(1)

User Mailbox

1 + x/9

This account is used to manage the Room accounts(3) and is needed since resource accounts can't manage themselves. Up to 9 resources per room admin account is what we recommend and this is due to Microsofts default throttling policy of concurrent connections.

Remote Management account(2)

User Mailbox

1

This account is used for the EVO features (Remote Upgrade / Monitoring / Statistics). Since a large number of emails are processed through this account it is important that it is a dedicated account only used for this purpose.

Room account(3)

Room Mailbox

x

The email addresses for these accounts is what will be used to book the meeting rooms. Resource accountsdon'thave any passwords and cannot exist on their own. The Room admin account(1) has to be granted Send on behalf and Full access permissions to its belonging Room accounts(3) to synchronize meeting data.

Note! Please make sure that no security functions or programs block or restrict a direct https (443) connection between Office 365 and the Evoko Room Manager (e.g. domain control, firewalls, proxies, network logins etc.)

Create a Room Admin account

Go to the Office 365 Admin center and login with your Office 365 admin account.

In the Office 365 admin center press Add a user under Users. website

Enter the information for your Room admin account(1)and continue by pressing "Add".

Once the account is created, chose if you want to email the password or not and press Close.

Create aRemote Management account(If youre going to use the EVO functionality)

In the Office 365 admin center press Add a user under Users.

Enter the information for your Remote Management account(2)and continue by pressing "Add".

Once the account is created, chose if you want to email the password or not and press Close.

Create and configure Room accounts

A Room account(3) or room mailbox or resource is the calendar that will be used for booking the room via e.g. Outlook and the calendar the Room Manager will synchronize meeting data with. OneRoom account(3) per Room Manager is necessary unless you want two or more Room Managers synchronizing meeting information with the same Room account(3)calendar.

Note!If you already have all the Room accounts(3) setup for your organisation you can proceed to step 5 in this chapter with granting your Room admin account(1) the necessary permissions.

Go to https://outlook.office365.com/ecp/ and login with your Office 365 admin account.

Navigate to Recipients> Resources.

Press the + and select Room mailbox.

Enter the Room name and specify the Room accounts(3) Email address.Optionally add a Location and enter the Capacity and continue by pressing Save.

Your Room account(3)should now appear in the list of resources. Double click on the Room account, OR highlight it and press edit.

Go to "mailbox delegation".

Under the section "Send on Behalf", press add.

Add your Room admin account(1), then press "ok".

Under the section "Full Access", press add.

Add your Room admin account(1), then press "ok".

Configuration via the Evoko Control Panel

Download and install the Evoko Control Panel. The software is available at our.

Launch the Evoko Control Panel.

Choose Office 365 as your mail server, enable EVO functionality if you would like to use the EVO features (remote upgrade, monitoring, statistics) and have setup a Remote Management account(1).

Click on Continue to connectivity settings in the bottom right corner to continue.

Fill in your Office 365 server address (default outlook.office365.com). If you are unsure which address to use to use you could try the Autodiscover feature.

Optional: Test your accounts for functionality.

Exchange user - Fill in your Room Admin account(1).

Exchange password Fill in your Room Admin account(1) password.

Mailbox owner Fill in the email-address for your Room account(3).

Click on System properties in the bottom right corner to continue.

Choose your Time format.

Choose the language which will be displayed on the Evoko Room Manager.

Optional setting: Enter the name of your Organization.

Enter the email-address to your System Administrator.

Choose a system Admin PIN code, the code is used to access the Admin menu on the Room Manager.

Add one or two email-addresses to the Facility manager.

Choose a Facility manager PIN code, the code is used to access the Facility manager menu on the Evoko Room Manager.

Fill in your Remote Management account(3).

Remote Management user Fill in your Remote Manager account user(2).

Remote Management password Fill in the password for your Remote Manager account(2).

Remote Management email Fill in the email-address to your Remote Manager account(2).

Remote monitor update duration - (This sets how often each Room Manager send email- reports for the monitoring feature).

Add a unique Security key (Max 16 characters).

Choose if you want the Evoko Room Manager always on or set by time.

Choose your Time zone at the Evoko Room Manager unit location.

Optional Setting: Assign one or multiple NTP-servers, separate the servers with a comma.e.g. 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org

Click on Admin credential in the bottom right corner to continue.

Click on button Add users.

Add your Room Admin account(s)(1).

Click on Room dashboard in the bottom right corner to continue.

Click on Add group to create a group.

Choose method to add a room, for this guide well go with Quickly.

Fill in Room Name, Office 365 Room Admin account(1)and Office 365 Resource account email(3).

Fill in the amount of seats in the room and choose the room facilities.

Enable the optional features that you would like to configure your Evoko Room Manager with.

Book meeting - Enables the user to book a meeting on the Evoko Room Manager.

Extend meeting - Enables the user to extend a meeting on the Evoko Room Manager.

End meeting Enables the user to end a meeting on the Evoko Room Manager.

Report issue Enables the user to report any of the chosen facilities. When reporting any of the chosen facilities a email is generated to the assigned facility manager(s).

Display Subject Enables the subject of the meeting to be displayed on the Room Manager.

Display Organizer Enables the organizer of the meeting to be displayed on the Evoko Room Manager.

Confirm Meeting (5-30min) Enables a check in feature which will trigger a confirm/check-in button that will popup on the Evoko Room Manager 10 min prior to the meeting start and will be displayed 5-30 min post to the meeting start. If the confirm buttonisn'tpressed within the selected timeframe the meeting room will be released.

Confirm Reminder Enables a reminder-email which will be sent to the organizer of the meeting. This email is triggered 5 minutes before the confirm time expires and is only sent out if the room hasnt already been confirmed/checked in.

Note!To add several Rooms to your configuration simply repeat step 6.25-6.28.

Insert an empty USB-stick in your computer (4 GB or less and FAT-formatted is recommended).

Click on Export to USB in the bottom right corner to export your configuration.

Now that youre done with the configuration, to proceed simply upload the configuration to the Evoko Room Manager via the USB-stick and follow the instructions on the screen.

Evoko Home can be installed in Default mode on both Windows and Linux (Debian based) servers. The installation procedur depending on Operating system therefore please select the type of operating system which you will install Evoko Home.

Step 3a: Windows (Default mode)

Step 3b: Linux (Default mode)

Step 3a: Windows (Default mode)

This part will go through how to install Evoko Home in Default mode on a Windows server.

Windows server prerequisites

A server running Windows Server 2008 R2 (or later).

A static IPv4 address (the Evoko Liso units will point to this IP).

Two free and accessible application ports (default HTTP port 3000 and HTTPS port 3002)

Access to booking system (e.g. Office 365) over HTTP (port 80) or HTTPS (port 443).

Access to NTP server over NTP (port 123 UDP).

Install Evoko Home on a Windows server

This part will go through how to install Evoko Home in Default mode on a Windows server.

Download the latest version of Evoko Home for Windows to the server. Step 4: Connect Evoko Home to booking system

Extract the downloaded installation packageEvokoHome.zip

Run the executable setup.exe

This will trigger the "single installer" which will help you install correct versions of additional software (e.g. Node.js, MongoDB etc) required to run Evoko Home. This might take a while and involve pressing Accept/Nexta few times so we suggest you prepare with some .

During the installation of Evoko Home you have the option to set your own MongoDB credentials, if you do make sure to document them.

Once the installation is complete, verify that the service is running underservices.msc.

Look for a service named ERM Service and make sure its status isRunning.

If the service is running and no firewall blocking, access Evoko Home via http://localhost:3000

Once Evoko Home is installed move on to Step 4: Connect Evoko Home to booking system

Step 3b: Linux (Default mode)

This part will go through how to install Evoko Home in Default mode on a Linux server.

Linux server prerequisites

A server running a 64-bit Debian baseddistribution(Ubuntu Server 16.04/18.04 LTS recommended).

A static IPv4 address (the Evoko Liso units will point to this IP).

Two free and accessible application ports (default HTTP port 3000 and HTTPS port 3002)

A user with sudo permission

Access to booking system (e.g. Office 365) over HTTP (port 80) or HTTPS (port 443).

Access to NTP server over NTP (port 123 UDP).

Access to the internet during installation to download dependencies.

Install Evoko Home on a Linux server

In this guide we will use Ubuntu Server 16.04 LTS as our operating system which we connect to via SSH.

To ensure all basic build packages exist to run the installation script we recommend running:

sudo apt install -y build-essential

sudo apt update

sudo apt upgrade

Download the latest version of Evoko Home for Linux and put the installation package on the server.

Extract the downloaded installation package:

tar -xzf installation_v2.*.tar.gz

A directory v2.x.yz should now have been extracted, you can check this by running ls.

Change directory to the newly extracted directory and run the installation script:

cd v2.* && sudo bash install.sh

The installation script will automatically recognize the necessary tools/prerequisites required to run Evoko Home. To continue and install, select Yes by typing 1 and pressing Enter.

Next up is to create credentials for the Mongo database. It's in this database meetings, users and Evoko Home settings will be stored. Set a username (e.g. evoko_user) and press Enter. Then set a password (e.g evoko_pass) which you repeat twice, pressing Enter in between.

Type the HTTP application port (default 3000) and press Enter.

Set a memory limit for Evoko Home by typing the amount e.g.2048followed by pressingEnter.

Below should be prompted if setup is successfully completed, you may remove the installation files:

cd .. && sudo rm -r installation_v2.*.tar.gz v2.*

You should now be able to access Evoko Home via a web browser on the configured HTTP application port (default 3000).

Once Evoko Home is installed move on to

To get error messages when troubleshooting the Appconnector or Overview Screen server you can attempt to run the service from the command line on both Windows or Linux servers.

A common cause for issues with the Appconnector or Overview Screen is usually related to invalid details entered in the configuration file (which can be found in /etc/evoko/config.toml on Linux or C:\ProgramData\Evoko\config.toml on Windows). Attempting to run the service via the command line can give you some hints to what the issue may be or if it's is seemingly working fine.

The process vary slightly for Windows and Linux so please see the appropriate section for you below:

On Windows servers

On Linux servers

On Windows servers

Make sure the service you want to troubleshoot (i.e.Evoko Overview Screen or Evoko App Connector) is stopped underservices.msc.

Next open the start menu and press Start in foreground for the appropriate application.

For the Overview Screen (2.0.3 and above):

For the Appconnector (2.0.2 and above):

In case of errors starting the service it should be output in the shell otherwiseit should continue to run as long as the window stays open and the command isn't aborted (e.g. ctrl + c). Below is an example for wrong Evoko Home admin credentials being entered in the configuration.

On Linux servers

Make sure the service you want to troubleshoot is stopped.

For the Overview Screen run:

sudo service evoko-overview-screen stop

For the Appconnector run:

sudo service evoko-appconnector stop

Then attempt to start the service.

For the Overview Screen run:

sudo evoko-overview start

For the Appconnector run:

sudo appconnector start

In case of errors starting the service it should be output in the shell otherwiseit should continue to run as long as the window stays open and the start command (i.e. sudo evoko-overview startor sudo appconnector start) is not aborted (e.g.ctrl + c).Below is an example for wrong Evoko Home admin credentials being entered in the configuration file.

This issue is usually due to the configuration of the resource account (room mailbox) in Office 365 / Exchange which adds the meeting organizers name to the subject hence it being displayed doubled.

To address this we suggest running the following command in PowerShell / Exchange Management Shell.

Set-CalendarProcessing [email protected] -AddOrganizerToSubject $False-DeleteSubject $False

Note!Replace [email protected] with the equivalent of your resource account (room mailbox).

The issue which generates the following error messageon the Room Manager is often due to different software versions listed in the exported configuration files. factory reset

To resolve this issue we suggest clearing the temporary files for the Evoko Control Panel and export a new set of configuration files.

Make sure that you saved the configuration file ("MeetingRoomConf.xml") from the "Evoko Room Manager" folder somewhere on the PC (since this file contains your configuration).

Close the Evoko control panel.

Remove the following folder from the Windows PC:%appdata%\Evoko Room Manager

Launch the Evoko control panel and press the button "Import" under the tab "Start" and select the "MeetingRoomConf.xml" file which you previously backed up.

Navigate to the tab "Dashboard" and export a new set of files to your USB.

Upload your configuration to your Room Manager (a would be preferred to perform prior to uploading the newly exported configuration files).

The following error message usually indicates that something is wrong with the exported configuration files on the USB or the USB itself.

Please make sure that the configuration has been properly exported from the Evoko Control Panel. If properly exported your USB should have a folder named "Evoko Room Manager" in the root directory which should contain around20 files.

In case the "Evoko Room Manager" folder only contains a single "MeetingRoomConf.xml" file that means that something when wrong during export.

If the issue continues to occur then please try a different USB (4GB or less, FAT-formatted is recommended).

Important!following instructions applies to the Room Manager (ERM1001) andNOTits successor, the Liso (ERM2001).

Introduction

Create users in Active Directory

Create a Room Admin account

Create a Remote Management account (If youre going to use the EVO functionality)

Create and configure Room accounts

Configuration via Evoko Control Panel

Introduction

The Evoko Room Manager is a system for booking and managing rooms. The Evoko Room Manager is mounted outside the room and display the booking status on beautiful touch-sensitive screens, the red or green background illumination of the screen allows you to see at a distance whether or not the room is free. You book meetings just as you have always done in MS Outlook. The Evoko Room Manager also makes it possible to create and manage bookings directly on the touch-sensitive screen.

Account reference

Account type

No. of accounts

Comment

Room admin account(1)

User Mailbox

1 + x/26

The Room admin account(1)is needed to manage the Room accounts(3).Up to26resources per room admin account is what we recommend and this is due to Microsofts default throttling policy of concurrent connections.

Remote Management account(2)

User Mailbox

1

This account is used for the EVO features (Remote Upgrade / Monitoring / Statistics). Since a large number of emails are processed through this account we recommend a dedicated account for this purpose.

Room account(3)

Room Mailbox

x

Resource accounts or room mailboxesdon'thave any passwords and cannot be manged on their own. The Room admin account(1)has to be granted Send on behalf and Full access permissions to its belonging Room accounts(3)to synchronize meeting data.

Note! Please make sure that no security functions or programs block or restrict a direct http/https (80/443) connection between Exchange and the Evoko Room Manager (e.g. domain control, firewalls, proxies, network logins etc.)

Create users in Active Directory

In most organisations running Exchange, users are first created in Active Directory before created in Exchange. For our installation in this guide we have already setup the following accounts in our Active Directory:

Account reference

Display name

E-mail

Room admin account(1)

Room Admin 1

[email protected]

Remote Management account(2)

Remote Manager

[email protected]

Note! The accounts stated above are examples and you can use other account names if you wish. Furthermore several Room Admin accounts(1)might be necessary depending on the number of Room accounts(3)and the configured EWSMaxConcurrency for your Exchange 2013 environment.

Createa Room Admin account

Go to https://<servername>/ecp and login with your Exchange Admin account. website

Go to Recipients > Mailboxes.

Press the + and select User mailbox.

Fill in the alias of the Room Admin account(1)and select the user in Active Directory, then press save.

Your Room Admin account(1) should now appear in the list of mailboxes.

Create aRemote Management account (If youre going to use the EVO functionality)

In the Exchange admin center go to Recipients > Mailboxes.

Press the + and select User mailbox.

Fill in the alias of the Room Management account(2)and select the user in Active Directory, then press save.

Your Remote Management account(2)should now appear in the list of mailboxes.

Create and configure Room accounts

A Room account(3) or room mailbox is the calendar that will be used for booking the room via e.g. Outlook and the calendar the Room Manager will synchronize meeting data with. OneRoom account(3) per Room Manager is necessary unless you want two or more Room Managers synchronizing meeting information with the same Room account(3)calendar.

Note!If you already have all the Room accounts(3) setup for your organisation you can proceed to step 4 in this chapter with granting your Room admin account(1) the necessary permissions.

In the Exchange admin centergo to Recipients> Resources.

Press the + and select Room mailbox.

Enter the name of the Room account(3), specify the email address of the account and select the Organizational Unit (OU) where you want the Room account(3) to be placed.

Your Room account(3) should now appear in the list of resources. Double click on the Room account, OR highlight it and press edit.

Go to "mailbox delegation".

Under the section "Send on Behalf", press add.

Add your Room admin account(1), then press "ok".

Under the section "Full Access", press add.

Add your Room admin account(1), then press "ok".

Note! If you would like to setup several Room accounts(3)simply repeat above steps in this chapter.

Configuration via the Evoko Control Panel

Download and install the Evoko Control Panel. The software is available at our.

Launch the Evoko Control Panel.

Choose Exchange 2013 as your mail server, enable EVO if you would like to use the EVO features (remote upgrade, monitoring, statistics) and if you have set up a Remote Management account.

Click on Continue to connectivity settings in the bottom right corner to continue.

Fill in your Exchange 2013 mail server address. If you are unsure which address to use to use you could try the Autodiscover feature.

Optional: Test your accounts for functionality.

Exchange user - Fill in your Room Admin account(1).

Exchange password Fill in your Room Admin account(1) password.

Mailbox owner Fill in the email-address for your Room account(3).

Click on System properties in the bottom right corner to continue.

Choose your Time format.

Choose the language which will be displayed on the Evoko Room Manager.

Optional setting: Enter the name of your Organization.

Enter the email-address to your System Administrator.

Choose a system Admin PIN code, the code is used to access the Admin menu on the Room Manager.

Add one or two email-addresses to the Facility manager.

Choose a Facility manager PIN code, the code is used to access the Facility manager menu on the Evoko Room Manager.

Fill in your Remote Management account(3).

Remote Management user Fill in your Remote Manager account user(2).

Remote Management password Fill in the password for your Remote Manager account(2).

Remote Management email Fill in the email-address to your Remote Manager account(2).

Remote monitor update duration - (This sets how often each Room Manager send email- reports for the monitoring feature).

Add a unique Security key (Max 16 characters).

Choose if you want the Evoko Room Manager always on or set by time.

Choose your Time zone at the Evoko Room Manager unit location.

Optional Setting: Assign one or multiple NTP-servers, separate the servers with a comma. e.g. 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org

Click on Admin credential in the bottom right corner to continue.

Click on button Add users.

Add your Room Admin account(s)(1).

Click on Room dashboard in the bottom right corner to continue.

Click on Add group to create a group.

Choose method to add a room, for this guide well go with Quickly.

Fill in Room Name, Exchange User (Room Admin account(1)) and Mailbox owner (Room account(3)).

Fill in the amount of seats in the room and choose the room facilities.

Enable the optional features that you would like to configure your Evoko Room Manager with.

Book meeting - Enables the user to book a meeting on the Evoko Room Manager.

Extend meeting - Enables the user to extend a meeting on the Evoko Room Manager.

End meeting Enables the user to end a meeting on the Evoko Room Manager.

Report issue Enables the user to report any of the chosen facilities. When reporting any of the chosen facilities a email is generated to the assigned facility manager(s).

Display Subject Enables the subject of the meeting to be displayed on the Room Manager.

Display Organizer Enables the organizer of the meeting to be displayed on the Evoko Room Manager.

Confirm Meeting (5-30min) Enables a check in feature which will trigger a confirm/check-in button that will popup on the Evoko Room Manager 10 min prior to the meeting start and will be displayed 5-30 min post to the meeting start. If the confirm buttonisn'tpressed within the selected timeframe the meeting room will be released.

Confirm Reminder Enables a reminder-email which will be sent to the organizer of the meeting. This email is triggered 5 minutes before the confirm time expires and is only sent out if the room hasnt already been confirmed/checked in.

Note!To add several Rooms to your configuration simply repeat step 6.25-6.28.

Insert an empty USB-stick in your computer (4 GB or less and FAT-formatted is recommended).

Click on Export to USB in the bottom right corner to export your configuration.

Now that youre done with the configuration, to proceed simply upload the configuration to the Evoko Room Manager via your USB-stick and follow the instructions on the screen.

Evoko offers a standard 2-year warranty for all products from the date of purchase free of charge.

It is possible to extend the warranty period with up to 3 additional years at a cost, making the maximum total warranty period 5 years from the date of purchase.

The warranty can be extended for several years at a time, or year-by-year, as long as the standard or extended warranty has not expired.

More detailed information and Terms & Conditions for Standard and Extended Warranty are available in the document below.

Note! Extended warranty is not available for the Evoko Groupie

This support document explains the differences between different accounts and account types used by the Evoko Liso system.

tl;dr The most common misunderstanding when it comes to accounts is that the booking system service account and the Evoko Home admin account are the same account. They are not, even though they have the same username/email address. The credentials for logging into Evoko Home will be different from the service account credentials.For more information, please continue reading.

Booking system accounts

These accounts are created, maintained and edited in the booking system admin interface, e.g. Office 365 admin portal or Google Admin. They need to be created in the booking system first, then entered into Evoko Home so it can connect to the booking system. For instructions on how to do this, please see the Booking System Preparation chapter for your booking system.

Service account

Used by Evoko Home to connect to the booking system. All communication between Evoko Home and the booking system is done over this account. If the service account password is changed or expired, or if the Service account is locked or has had its mailbox or license removed, Evoko Home will not function properly until the issue is fixed. If the service account password is reset, it also needs to be updated in the Evoko Home global settings. Please note that resetting the service account password does not affect the Evoko Home login password.

Admin account

Used by Evoko Home when connecting to Google G Suite only. The Admin account needs to be a super admin account and be subscribed to the resource calendars. Similar to, but different from the service account - both are required when using Google G Suite.

Important! If Evoko Home is not able to access the booking system it will not be possible to reset Evoko Home account passwords, since Evoko Home sends the reset password email via the booking system. Attempting to reset the Evoko Home global admin account password while Evoko Home is disconnected from the booking system will effectively lock that account. If you are in this situation, please submit a support ticket request and we will do our best to help.

Evoko Home account types

Global Admin

The global admin can administer and configure the entire Evoko Home and Liso environment. The first global admin account is usually created during initial configuration of Evoko Home, sharing the username (email address) with the service account.

Please note! Evoko Home has its own user database and user credentials can be different from those in the booking system, even if they share the user name. This means that when you change the service account password in the booking system, the Evoko Home global admin account credentials do not change.

We recommend having more than one global admin account in Evoko Home to avoid being accidentally locked out.

Local Admin

An admin account in Evoko Home that can be limited to administer a subset of rooms.

User

The normal user account in Evoko Home. Does not have a password, thus cannot log on to Evoko Home. Used only to identify and authorize users when creating, modifying or deleting meetings directly on the Liso screen.

If Evoko Booking is used, the User type accounts will be redirected to the Evoko Bookings web interface when trying to access Evoko Home.

Statistics User

A user that can view and export statistics data in Evoko Home.

PINs and Passwords

A note on PINs vs Passwords Passwords are used to log on to Evoko Home. The PIN is only used for identification/verification on the Liso. PINs cannot be used to log on to Evoko Home.

The Evoko Liso system is compatible with the popular RFID technology, which makes handling your meetings on the Liso a lot quicker. Just present the card in front of the Liso instead of using your PIN.

Prerequisites and compatibility

Evoko Home RFID Settings

RFID Enrollment settings

Video demonstration

Prerequisites and compatibility

Evoko Home > v1.26

Evoko Liso firmware > v1.26

System running in default mode (Limited mode is not supported).

The Evoko Liso is can be used with 13.56 MHz cards compatible with ISO/IEC 14443A/B, for example theMIFARE classic 4K/1K card.

ISO/IEC 15693 or MIFARE Ultralight C cards are not compatible.

Evoko Home RFID Settings

To enable RFID authentication, open Evoko Home in a web browser and head to the Global Settings. On the left hand side, you will see the options for RFID:

This sets whether users are able to identify themselves using PIN only or PIN and RFID. To enable RFID, set this option to "PIN or RFID".

RFID Enrollment settings

This option controls how users can enroll their RFID into Evoko Home.

Auto - This means a user can present their RFID to a Liso at any time, then enter their PIN to associate the RFID with their Evoko Home user account.

Admin - This means the admin must import or enter the RFID into Evoko Home. No enrollment from the Liso.

Requested - This option is like Auto but with the addition that an Evoko Home admin must aprove the RFID in Evoko Home. This is shown by a red exclamation mark in the users list. When the admin edits the user a request to replace the RFID is shown.

Video demonstration

Please see the video below for a demonstration on how to enroll an RFID card.

Contents

Instructions for Evoko Home/Liso v1.x

Instructions for Evoko Home/Liso v2.x

Prerequisites

Evoko Home version 1.33 or above

Evoko Liso firmware version1.33 or above

Instructions for Evoko Home/Liso v1.x

This is how to enable 802.1x authentication on Evoko Home v1.x. Note that we recommend that the Liso(s) are on the same version number as Evoko Home.

Make sure both Evoko Home and the Evoko Lisos are running v1.33 or higher and that the Liso device is successfully connected to Evoko Home on an unmanaged port.

Enable 802.1x in Evoko Home global settings. wpa_supplicant.conf

Go to the monitoring tab in Evoko Home and click on the Liso you would like to configure

Click Request CSR

Wait for the CSR to be generated, then download the CSR.

Use the CSR to request a certificate for this device.

The Liso certificate should be named cert.crt.

The root certificate should be named root_cert.crt

If you use a Windows Certificate Server just download the certificates as base64 and rename the files.

Download and save the file wpa_supplicant.conf

Click Browse and Upload for each of the three files to upload them to Evoko Home.

Click the "Send Certificate to Liso" link to upload the files to the Liso device.

After the upload is done, reboot the Liso and move it to the managed network.

Repeat steps 3-10 for each Liso.

Instructions for Evoko Home/Liso v2.x

This is how to enable 802.1x authentication on Evoko Home v2.x. Note that we recommend that the Liso(s) are on the same version number as Evoko Home.

Make sure both Evoko Home and the Evoko Lisos are running v2.0 or higher and that the Liso device is successfully connected to Evoko Home on an unmanaged port.

Enable 802.1x in Evoko Home global settings and click the save button to save the settings.

Go to the Rooms tab in Evoko Home and expand the room list. Select the Liso you would like to configure and click the Device tab.

Click Request CSR from Liso

Wait for the CSR to be generated, then download the CSR.

Use the CSR to request a certificate for this device.

The Liso certificate should be named cert.crt.

The root certificate should be named root_cert.crt

If you use a Windows Certificate Server just download the certificates as base64 and rename the files.

Download and save the file

Click Browse for each of the three files to upload them to Evoko Home.

Click the "Send Certificate to Liso" link to upload the files to the Liso device.

After the upload is done, reboot the Liso and move it to the managed network.

Repeat steps 3-10 for each Liso.

Enable extended logging in the Evoko Control Panel

Extract logs using the Diagnostics tool

Enable extended logging in the Evoko Control Panel

Extended logging can be activated on the Room manager by enabling the feature under the tab "Support" in the Evoko Control Panel. website.

Important! You need to export the updated configuration to your USB and upload the updated configuration with extended logging enabled to the Room manager(s) in order for extended logging to be applied.

Extract logs using the Diagnostics tool

Download the latest Factory Reset/OS-update software from our

Extract the downloaded factory reset files in the root of a USB flash drive (4GB or less, FAT-Formatted is recommended).

Insert the USB-stick into the Room manager and reboot the device.

Wait until the Diagnostics tool is launched and then press "Collect log files".

Once done the logs should have been copied to a folder namedCollectedLogs on the USB.

Note! In order to collect logs of some significance please leave the Room Manager running for at least 30 minutes and try to reproduce the issue.

The process of updating the OS on a Room Manager is similar to performing a factory reset in the sense that it utilizes the same tool. Please follow the instructions below.

Download the latest Factory Reset/OS update software from our website.

Extract the downloaded factory reset files in the root of a USB-stick (4GB or less, FAT-Formatted is recommended).

Insert the USB-stick into the Room Manager and reboot the device.

Wait until "ERM Diagnostics" is launched and press "OS update".

On the prompt "Are you sure...", press "Yes".

Press "Start".

"Please restart your device" will be displayed once the OS update is finished, press "OK" and reboot the device bydisconnecting the powerto complete the OS update.

Important! The device needs to be power cycled for the OS update to be completed. If you perform a software initiated reboot, the OS will remain the same version until the device has been power cycled.

The reason for this most likely due to the configuration for the Room account (resource/room mailbox) in Office 365/Exchange.The following PowerShell command defines that any private flag of the appointment is not removed on the Room account which means that private flagged appointments subject should no longer be displayed on the Room Manager once the command is executed.

Set-CalendarProcessing [email protected] -RemovePrivateProperty $false

Note!Replace "[email protected]" with the equivalent for your Room account in the above command.

If your Pusco Unit for some reason doesn't work as it should, select below category and follow the directions:

Picture has frozen

Display is grey (sleep mode) + lights are on

Display is working but lights are off

Neither display nor lights are working

Picture is frozen

The display may freeze from time to time and must therefore be restarted. This can be done either in the software, Pusco Manager or by doing a hard switch on the unit. The restart takes a couple of minutes.

Restart using Pusco Manager

Go to tab My Pusco Units, hoover over the unit you would like to restart and press Show/Edit Unit info. Press Restart. The Pusco Unit will now do a restart and in a couple of minutes it will be up and running.

[email protected]

Restart by doing a hard switch on the unit

Turn off power by using the hard switch in the bottom of the brainbox. Wait 30 seconds and then turn power on again.

Display is grey (sleep mode) + lights are on

If the display is sleeping and the lights are on, the unit is probably in energy saving mode. This setting can be adjusted for every unit.

Go to My Pusco Units, hover over the unit you and press Show/edit Unit info. Mark what days and between what times the unit should be activated.

If you would like to wake the display you can do this manually by either using a remote control or the display menu. The display menu is accessed by opening the upper service hatch on the back of the unit. Press any button to wake the display.

Display is working but lights are off

If the display is working as usual but the lights are off, do following:

Pusco Floor:

Start with switching the unit OFF and remove power cord and ethernet cable from unit.

Loosen the two screws on the lower hatch (allen key size 5). Remove the hatch by pulling it down.

Make sure all four cables are attached properly.

Put back the service hatch, power cord and ethernet cable. Switch unit ON.

If above didn't help, please contact Evoko Support.

Pusco Wall

Start with switching the unit OFF and remove power cord and ethernet cable from unit.

Loosen the two side screws and lift the unit of the wall bracket. Place the unit on something soft to avoid scratches.

Make sure all four cables are attached properly.

Put the unit back on the wall bracket and connect power cord and ethernet cable. Switch unit ON

If above didn't help, please contact Evoko Support.

Neither display nor lights are working

If neither display or lights are working follow below steps:

Pusco Floor

Check if hard switch is on

Check if power cord and ethernet cable are properly attached.

Open Upper Service hatch and control hdmi + power cables are properly attached

Remove lower service hatch and control all cables are attached properly

Start with switching the unit OFF and remove power cord and ethernet cable from unit.

Loosen the two screws on the lower hatch (allen key size 5). Remove the hatch by pulling it down.

Make sure all four cables are attached properly.

Attach lower service hatch, power cord and ethernet cable. Switch unit ON

If above doesnt solve the problem, the brainbox or Pusco unit needs further investigation. Contact [email protected] for further information.

Pusco Wall

Check if hard switch is on

Check if power cord is properly attached (bottom of unit)

Remove unit from wall bracket to control cables

Loosen the two side screws and lift the unit of the wall bracket. Place the unit on something soft to avoid scratches.

Make sure all four cables are attached properly.

Put the unit back on the wall bracket and connect power cord and ethernet cable. Switch unit ON

If above doesnt solve the problem, the brainbox or Pusco unit needs further investigation. Contact for further information.