Release 3.4.9

Installation Guide

July 2019

Sateon Release 3.4.9 Installation Guide Issue 1.2, released July 2019

Disclaimer Copyright © 2017, Grosvenor Technology. All rights reserved. Sateon and the Sateon logo are trademarks or registered trademarks of Grosvenor Technology. All other brands, names, or trademarks appearing in this document are acknowledged as the trademarks of their respective owners. No part of this document may be reproduced in any form or by any means for any purpose without the written permission of Grosvenor Technology. Whilst we make every effort to ensure the accuracy of our publications, Grosvenor Technology assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.

www.grosvenortechnology.com

Sateon Release 3.4.9 2 Issue 1.2 Installation Guide July 2019

Contents

Preface ...... 5 About Sateon ...... 5 About this guide ...... 5 Related documents ...... 6 Technical support ...... 7

Before installation ...... 8 Server specification ...... 9 Hardware requirements ...... 9 Operating system support ...... 9 Server software requirements ...... 10 Client requirements ...... 11 Browser support and Silverlight...... 11 Screen resolution ...... 12 Installation options ...... 12 Express installation ...... 12 Custom installation ...... 12 Other installation options ...... 12 Licensing ...... 13

Express installation ...... 14 When to use the Express installation ...... 15 Installation steps ...... 15

Custom installation ...... 19 When to use the Custom installation ...... 20 Installation steps ...... 20

Advanced installation options ...... 29 Installing an additional Comms Engine...... 30 Exporting the Certificates from the Sateon server ...... 30

Sateon Release 3.4.9 3 Issue 1.2 Installation Guide July 2019

Installing and configuring the remote Comms Engine ...... 33 Installing a distributed system ...... 39 Checks on the SQL Server ...... 40 Installing Sateon on a distributed system ...... 41 Deploying the databases separately ...... 47 Before deploying databases...... 48 Deploying databases separately ...... 48 Installing remote printing ...... 53 Before starting ...... 54 Exporting the certificates from the Sateon server ...... 54 Installing and configuring the remote printing ...... 57 Modifying an installation ...... 62

After installation ...... 67 Sateon components installed ...... 68 File structure installed ...... 68 Databases and scripts ...... 69 Services created ...... 70 Message queues configured ...... 71 Websites configured ...... 71 Shortcuts ...... 72 Starting the system ...... 72 Licencing ...... 74 Installing a Sateon licence ...... 74 Validating the licence ...... 76 Running Quick Start ...... 77 Step 1: Run Quick Start and Log in to Sateon ...... 78 Step 2: Select defaults...... 79 Step 3: Discover controllers ...... 80 Step 4(a): Set IP addresses ...... 81 Step 4(b): Set up a 485 network ...... 81 Firmware Update ...... 84

Upgrading Sateon ...... 86 Before upgrading ...... 87 Versions...... 87 Back up database ...... 87 Obtain an upgraded licence ...... 87 Check files ...... 87 Running the Sateon upgrade ...... 87 After upgrading ...... 90

Sateon Release 3.4.9 4 Issue 1.2 Installation Guide July 2019

Clear browser cache...... 90 Upgrade the licence ...... 90 Uninstalling Sateon ...... 91 Uninstalling Sateon ...... 92

Ports used ...... 94

Preface

This document provides detailed information on installing Sateon, including details of requirements, advanced installation options and performing upgrades. This version of the document relates to Sateon Release 3.4.4. It may not include changes incorporated in later versions of the software. Date of latest update: March 2018.

About Sateon

Sateon Advance is a powerful yet easy-to-use browser-based access control system that allows users to manage and monitor physical access to sites. It integrates access control, alarm and incident monitoring, visitor management and reporting facilities. Sateon is installed on a central server, and can then be accessed from multiple locations via a browser-based interface.

Note: If you are using one of the Grosvenor Technology Mini-PCs, there is no need to install any software. The Mini-PCs come pre-loaded with Sateon already installed.

About this guide

This document describes how to install Sateon Advance Release 3.4.4. It is aimed at installers and support engineers. Express installations require no prior knowledge, but for advanced features a good knowledge of Windows systems is useful, particularly using Microsoft SQL Server and Internet Information Services (IIS). This guide includes the following information:

Sateon Release 3.4.9 5 Issue 1.2 Installation Guide July 2019

 Section 1 – Before installation. This section explains things you need to be aware of before installing Sateon, including specifications of the computers that you install Sateon on.  Section 2 – Express installation. This section explains the one-step installation process that installs Sateon and all required prerequisites on a single system.  Section 3 – Custom installation. This section details how to install Sateon when you want to use specific settings rather than the defaults.  Section 4 – Advanced installation options. This section explains advanced installation options including split-tier installations, installing parts of the system only and modifying the installation.  Section 5 – After installation. This section explains the first steps you need to take after installing Sateon.  Section 6 – Upgrading Sateon. This section explains how to upgrade an earlier version of Sateon to 3.4.4.  Appendix A – Ports used. Lists the TCP ports that Sateon may require, depending what features are configured.

Note: Representations of screens in this document are shown for general illustration only. There may be some differences in the screens you see, depending on the operating system and the computer configuration.

Related documents

The following documents, available from Grosvenor Technology, may also be useful:  The Sateon Personnel Module Guide. Explains how to set up the people who will use the system and the tokens they use to gain access to the site.  The Sateon Access Control Guide. Explains how to set up the data in the access control module of Sateon which includes access permissions, time patterns, areas and system hardware.  The Sateon Control Centre Guide. Explains the Sateon Control Centre, which allows security staff to view and monitor events, to deal with reported incidents and to manage or control specific elements of the system.  The Sateon System Administration Guide. Includes information about system administration, including licensing the software, setting up system users and user groups and defining their access to data. There are also a number of guides to optional features of Sateon, including interfaces to third-party systems such as fire panels and CCTV systems.

Sateon Release 3.4.9 6 Issue 1.2 Installation Guide July 2019

Technical support

For further assistance with Sateon Advance, please contact Grosvenor Technology Technical Support as follows: Email (EMEA): [email protected] Telephone: +44 (0)1279 838000 Website: www.grosvenortechnology.com

Sateon Release 3.4.9 7 Issue 1.2 Installation Guide July 2019

Section 1

Before installation

This section explains things you need to be aware of before installing Sateon. It includes the following:  The hardware requirements of the server on which Sateon is to be installed. See Server specification on page 9.  The requirements of the client machines from which the Sateon user interface is accessed. See Client requirements on page 10.  The licensing requirements of Sateon. See Licensing on page 13.  The options available for installation. See Installation options on page 12.

Note: If you are using a Grosvenor Technology Mini-PC, installation is not required since Sateon and all prerequisites are already installed. See After installation on page 67 for details of starting up the system.

Sateon Release 3.4.9 8 Issue 1.2 Installation Guide July 2019

Server specification

Hardware requirements – up to 100 readers Grosvenor Technology advises the following as the minimum specification of the main Sateon server:  Processor – 2 GHz or faster 64-bit (x64) processor is required. We recommend that the processor has at least two cores.  RAM – 8 GB RAM  Hard drive – 128 GB SSD – Please note that mechanical drives are not recommended. Larger systems may need higher specification systems to ensure optimum performance. NOTE: For systems larger than 100 readers, please contact our helpdesk for a consultation on a suitable spec.

Operating system support The following operating systems are supported:  Windows Server 2012 R2 (Standard and Datacentre versions)  Windows Server 2016 R2 (Standard and Datacentre versions)  Windows 8.1, 64-bit (Pro and Enterprise versions)  Windows 10, 64-bit (Pro, Enterprise, Enterprise Long Term Servicing Branch and Education versions)

Note: Microsoft has ceased mainstream support for older operating systems including Windows 7 64- bit and Windows 2008 R2; therefore, they are not recommended for new installations. Grosvenor Technology recognises that Windows 7 is still in widespread use and therefore has performed some testing of the Sateon installation and upgrade process. However due to the age of this platform customers may encounter unexpected issues. Note: Grosvenor Technology does not support 32-bit systems for either client or server machines.

We recommend that all relevant Service Packs and updates are installed, whichever operating system you are running.

Important notes: 1. Because of constraints within the installer, Sateon must be installed on a computer with an English operating system. This release of Sateon does not support non- English operating systems. (This restriction applies only to the Sateon server; client machines can be running any operating system, and the user interface can be displayed in other languages with the use of Language Packs.)

Sateon Release 3.4.9 9 Issue 1.2 Installation Guide July 2019

2. Sateon MUST NOT be installed on a server that is operating as a Domain Controller. Microsoft advises that a server used as a Domain Controller server should not be used for any other purpose.

Server software requirements If they are not already present, the pre-requisites for Sateon are installed as part of the standard installation. There is no need to pre-install any software. However, if you already have a suitable version of Microsoft SQL Server in your organisation, it can be used. Always ensure you install Sateon from the provided media, to ensure that all pre- requisites are available at the point of installation. Note the following particular points about specific software requirements.

Microsoft SQL Server The following versions of Microsoft SQL Server are supported:  Microsoft SQL Server 2016 – all editions including Express.  Microsoft SQL Server 2014 – all editions including Express.  Microsoft SQL Server 2012 – all editions including Express. Important notes: 1. Microsoft SQL Server 2008 is not recommended for new installations. Although it may operate, support for this version has been removed in line with Microsoft’s supported systems. They are not tested and the results of a Sateon install cannot therefore be guaranteed. 2. The Express Editions of SQL Server are intended for small-scale installations. There is a 10 GB size limit per database (not including log files) and SQL Server Express will only use a maximum of 1 GB regardless of the amount of memory available. The SQL Server 2016 Express Edition is the one that is installed by the Express installer. 3. Ensure that whichever edition you are running, all relevant Service Packs have been installed. 4. If you are installing SQL on the same server as the Sateon application, you should consider restricting the memory that is allocated to SQL Server. The default installation of SQL Server will use as much memory as possible, which may cause problems with other applications running, including Sateon. For a full explanation and details on how to manage the SQL Server memory usage, see the following Microsoft support article: http://support.microsoft.com/kb/321363. This does not apply to the Express edition, where the memory is already limited. If SQL is running on its own server you do not need to restrict the memory. 5. For a distributed installation (using separate SQL Server and Application Server), the Comms Engine database and the ESS database (known as Local databases) are always installed on the Application Server, in order to reduce traffic between

Sateon Release 3.4.9 10 Issue 1.2 Installation Guide July 2019

systems and increase resilience. This means that a SQL instance will be required on the Application Server as well as the SQL Server.

Browser Support We recommend the following browser: • Microsoft Internet Explorer v7 and above. (Note that in v10 Microsoft introduced two variants of Internet Explorer. Only the Desktop version works with Sateon.)

The Sateon user interface uses Microsoft Silverlight technology, which requires a browser plug-in to be installed. If not already present, the user will be prompted to install this plug-in the first time that Sateon is run. Follow the browser installation details to ensure that the Silverlight plug-in is enabled. The minimum supported version of Silverlight is 5.1.50906.

Note: Google Chrome and Safari are no longer a supported browser for Sateon. This is because the latest versions of the browsers do not support NPAPI plug-ins, which means the Silverlight application cannot be run. Note: If you are using a Windows 10 system, the default browser is Microsoft Edge, which is not compatible with Sateon. This means that when you run Sateon from the icon on the desktop, Sateon will not run initially. Use the Search option to locate Internet Explorer and use it to access Sateon. Ensure you pin Internet Explorer to the Start menu or taskbar for future use.

Client requirements

Client machines can access the Sateon user interface via a web browser. No Sateon software needs to be installed on client computers, but users should be aware of the following points.

Browser support and Silverlight We recommend the following browser: • Microsoft Internet Explorer v7 and above. (Note that in v10 Microsoft introduced two variants of Internet Explorer. Only the Desktop version works with Sateon.) The Sateon user interface uses Microsoft Silverlight technology, which requires a browser plug-in to be installed. If not already present, the user will be prompted to install this plug-in the first time that Sateon is run. Follow the browser installation details to ensure that the Silverlight plug-in is enabled. The minimum supported version of Silverlight is 5.1.50906.

Note: Google Chrome and Safari are no longer a supported browser for Sateon. This is because the latest versions of the browsers do not support NPAPI plug-ins, which means the Silverlight application cannot be run.

Sateon Release 3.4.9 11 Issue 1.2 Installation Guide July 2019

Note: If you are using a Windows 10 system, the default browser is Microsoft Edge, which is not compatible with Sateon. This means that when you run Sateon from the icon on the desktop, Sateon will not run initially. Use the Search option to locate Internet Explorer and use it to access Sateon. Ensure you pin Internet Explorer to the Start menu or taskbar for future use.

Screen resolution The minimum recommended screen resolution for Sateon is 1280 x 800.

Installation options

The Sateon installer supports various installation options.

Express installation For small-scale installations, the Express installation is recommended which installs everything required to run Sateon, including pre-requisite software, on a single system. All the core Sateon features are installed, but no integrations or other optional features. Default values are assumed for database names, install locations and user accounts. The version of SQL Server installed is Microsoft SQL Server 2016 (Express Edition with Tools). For details, see Express installation on page 14.

Custom installation If you need to modify the standard installation in any way, or use settings other than the defaults, you should use the Custom installation. For example, use the Custom installation if you want to install any of the optional features, or if you already have a version of SQL Server installed that you want to use. For details, see Custom installation on page 19.

Other installation options The Sateon installer permits various other installation and configuration options, including the following:  Installing an additional Comms Engine, for example to support a remote site.  Setting up distributed (split-tier) installations, which have a separate Application Server (for the Sateon services, websites and utilities) and SQL Server (for the databases).  Deploying just the databases on a remote server.  Configuring printing services on a remote server.

Sateon Release 3.4.9 12 Issue 1.2 Installation Guide July 2019

 Modifying an existing installation, for example, adding additional features or removing features. For details, see Advanced installation options on page 29.

Licensing

Your licence file is specific to your Sateon installation and details the options and features that are supported in the software. All Sateon installations require a valid licence.

Note: If you are upgrading from an earlier Sateon version you will need to upgrade your licence.

Applying a licence is a two-stage process:  You need to load a suitable licence as soon as possible after installation. The licence can be provided in file format or as encrypted data included in a document or email.  The licence then needs to be validated within 30 days by calling Grosvenor Technology Technical Support. For details, see Installing a licence on page 74.

Note: If you do not have a licence file yet, contact Grosvenor Technology Technical Support as soon as possible.

Sateon Release 3.4.9 13 Issue 1.2 Installation Guide July 2019

Section 2

Express installation

This section explains the Express installation which installs the Sateon system and all required prerequisites on a single server. It includes the following:  A summary of when the Express installation is suitable. See When to use the Express installation on page 15.  Details of the process to follow. See Installation steps on page 15.

Sateon Release 3.4.9 14 Issue 1.2 Installation Guide July 2019

When to use the Express installation

The Express Sateon installation process sets up any required prerequisites and then installs the Sateon system on a single system. Note the following:  All the core Sateon features are installed, but no optional features or integrations. (Note that these can be added later if required.)  Default values are assumed for file locations, database names and user accounts.  The Express installation is intended for standalone systems that do not have an existing version of Microsoft SQL Server. It installs SQL Server 2016 Service Pack 1 – Express Edition with Tools. The Express installation is not recommended in the following situations:  If you already have a version of SQL Server installed that you intend to use for the Sateon database.  If you want to install any of the optional third-party integrations.  If you only want to install certain parts of the system on the selected machine, for example if you plan to install the databases on a separate SQL server, or install an additional Comms Engine on a remote site.  If you want to use different SQL database instances rather than the defaults.  If you wish to use a specific user account to run Sateon. The Express installation uses the Local Service account, which has access restrictions and is not suitable in some circumstances. In these situations, use the Custom installation which permits fully flexible configuration options. See Custom installation on page 19.

Note: The Express Editions of SQL Server are intended for small-scale installations. There is a 10 GB size limit per database (not including log files) and regardless of the amount of memory available, SQL Server Express will only use a maximum of 1 GB.

Installation steps

Before running the install process, ensure you are logged on to an Administrator account on the server, with full permissions.

To run the express installer 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. 2. The following dialog appears:

Sateon Release 3.4.9 15 Issue 1.2 Installation Guide July 2019

3. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions. The following page appears:

Sateon Release 3.4.9 16 Issue 1.2 Installation Guide July 2019

4. Click Express to start the Express installation.

Note: A User Account Control dialog may appear. This must be accepted in order to continue.

5. A dialog is displayed while the installation is in progress, for example:

Note: The entire process is indicated by the central progress bar. Installation may take some time, especially if all prerequisites need to be installed.

6. Depending on the prerequisites installed, you may be prompted to restart your computer in order to complete the installation.

Click OK. Once the computer has restarted, the Sateon installation will continue automatically as soon as you log on. 7. When the installation is complete, the following dialog appears.

Sateon Release 3.4.9 17 Issue 1.2 Installation Guide July 2019

8. Click Close. After installation, we recommend that you start up the Sateon user interface to apply the licence. See After installation on page 67.

Sateon Release 3.4.9 18 Issue 1.2 Installation Guide July 2019

Section 3

Custom installation

This section explains the Custom installation, which allows you to install Sateon using settings and options other than the defaults. It includes the following:  A summary of when the custom installation should be used. See When to use the Custom installation on page 20.  Details of the process to follow. See Installation steps on page 20.

Sateon Release 3.4.9 19 Issue 1.2 Installation Guide July 2019

When to use the Custom installation

If you want to use any settings other than the defaults, you should use the Custom installation. For example, use the Custom installation in the following circumstances:  If you want to install any of the optional third-party integrations (Elevators, Galaxy, IndigoVision, PSIM/BACnet, Simplex or offline locks).  If you already have a version of SQL Server installed that you intend to use for the Sateon databases or if you intend to use any version of SQL Server other than SQL Server 2016 Express Edition with Tools.  If you only want to install certain parts of the system on the selected machine, for example if you are setting up a separate SQL server.  If you want to use a different installation location rather than the default location (C:\Program Files x86)\Grosvenor Technology Ltd).  If you want to use different database instances rather than the default values.  If you wish to use a specific user account to run Sateon. The Express installation uses the Local Service account, which has access restrictions and is not suitable for distributed installations.

Installation steps

Before running the install process, ensure you are logged on to an Administrator account on the server, with full permissions.

To install Sateon using customised settings 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. The following dialog appears:

Sateon Release 3.4.9 20 Issue 1.2 Installation Guide July 2019

2. After reading the terms of the licence agreement, select the checkbox to accept the terms and conditions. The following dialog appears:

Sateon Release 3.4.9 21 Issue 1.2 Installation Guide July 2019

3. Click the Customise button. The following dialog appears:

By default, the essential features of Sateon are selected for installation: Sateon Core, Comms Engine, Logging, Event Gateway and Report Printing. To change these, click Install for any additional features, integrations and utilities you want to install. Click Skip for any selected features that you do not want to install.

Note: There is no need to select the Quick Start application separately as it is always included as part of Sateon Core.

4. Click Next. The Install Location dialog appears:

Sateon Release 3.4.9 22 Issue 1.2 Installation Guide July 2019

5. The default installation location is C:\Program Files (x86)\Grosvenor Technology Ltd. To select an alternative, overwrite or click Change and navigate to the preferred location. 6. Click Next. The following is displayed:

Sateon Release 3.4.9 23 Issue 1.2 Installation Guide July 2019

7. On this page you need to configure the account under which Sateon is run. This is used to run the Windows services and is also added to SQL when the Sateon databases are deployed.  By default, the installation uses the built-in LOCAL SERVICE account. This is an account with minimum privileges and no network access. It does not require a password. Since it does not include network access, we do not recommend it for use in distributed installations or when you need to configure automatic printing to a network printer (for example when producing muster reports).  The built-in SYSTEM account has high privileges including network access. It does not require a password. We do not recommend this in operational situations for security reasons.  Alternatively, you can select User Account and specify an existing name and password. This can be a local account, entered in the format computername\account, or a domain account, entered in the format domain\account. A domain account that has been set up specifically for Sateon is the recommended option if network access is required.

Note: We recommend that in all operational situations you use a dedicated user account – with a strong password – created specifically for use by Sateon. Where appropriate, consult in-house IT staff about suitable accounts and password policies.

For a user account, click Validate. The validation process checks whether the account/password combination exists; you cannot proceed with the installation until a valid account and password are provided.

Sateon Release 3.4.9 24 Issue 1.2 Installation Guide July 2019

8. Click Next.

Sateon Release 3.4.9 25 Issue 1.2 Installation Guide July 2019

All communication between server and client in Sateon 2.10 is encrypted using TLS, with authentication provided by digital certificates. The default settings (Create New TLS Certificate and Create New Auth Certificate) are suitable if your organisation does not have its own certificates. Both the Sateon TLS and Auth certificates will be generated and installed. If your organisation has its own certificates, click the Select Existing TLS Certificate buttons, then click the Select button to display a list of available certificates and choose the correct one. You should always select Create New Auth Certificate. 9. Click Next. The following dialog appears:

On this dialog, you need to specify the location of both the LOCAL SQL databases (the Comms Engine database and the ESS database) and the GLOBAL SQL databases (all other databases). Both locations default to the current machine name with a Sateon instance.  If you are installing all options on a single machine, these will both be the current server; no changes are required.  If you are installing a distributed system from the Application Server, you must edit the GLOBAL setting to ensure it refers to your remote SQL Server. The LOCAL setting refers to the local Application Server. For more details of installing a distributed system, see Installing a distributed system on page 39. Note that if you already have SQL Server installed and you are not using a Sateon instance you can overwrite the default details with the appropriate Server\Instance.

Sateon Release 3.4.9 26 Issue 1.2 Installation Guide July 2019

By default, the Deploy global database and Deploy local database checkboxes are selected, meaning that all databases for selected features are fully installed and deployed. For both options, you can clear these checkboxes if you do not want to deploy the databases during this installation; for example, if access to the SQL server is restricted. For a new installation (rather than an upgrade) if you are not deploying the databases you must also deselect the Register features checkbox. If this is left selected, the installation process will attempt to write to the SQL databases during installation. Errors will result if the databases are not present. In both cases the information icons provide additional explanation. 10. If you are deploying any databases, you must test the database connection before the Next button is activated. Click the Validate button. An error message is displayed if a connection to the specified SQL database instance cannot be made. If SQL is not already present on the server and a local location has been specified, the following icon will appear, indicating that Sateon has been unable to reach the specified database:

This is a warning only – no action is required as SQL Server 2016 will be installed on the local server. 11. Click Next. The following confirmation dialog appears, listing the installation settings and features to be installed:

Sateon Release 3.4.9 27 Issue 1.2 Installation Guide July 2019

12. Click Install to start the installation of the requested features. A User Account Control dialog may be displayed; you will need to accept this in order to continue.

Note: The entire Sateon installation can take some time, particularly if SQL Server needs to be installed. Depending on the prerequisites installed, you may be prompted to restart your computer in order to complete the installation. In this case, as soon as the computer has restarted, the installation will continue automatically when you log on.

13. Click Close when the completion dialog appears.

Note: If any errors are encountered during the installation, the installation will be cancelled, and any changes made by the installer will be rolled back.

After installation, we recommend that you log in to Sateon to change the default password and to apply the licence. After that, you should run Quick Start to discover and set up the controllers. See After installation on page 67.

Sateon Release 3.4.9 28 Issue 1.2 Installation Guide July 2019

Section 4

Advanced installation options

This section explains various other Sateon installation and configuration options:  For an explanation of how to install an additional remote Comms Engine, see Installing an additional Comms Engine on page 30.  For details of installing the application and SQL databases on different servers, see Installing a distributed system on page 39.  If you need to deploy the databases separately on a remote machine, see Deploying the databases on page 47.  If you need to configure remote printing, see Installing remote printing on page 53.  For details about adding or removing components from a Sateon installation, see Modifying an installation on page 62.

Sateon Release 3.4.9 29 Issue 1.2 Installation Guide July 2019

Installing an additional Comms Engine

An additional Comms Engine may be required for various reasons: to support remote sites, to improve system performance by load-sharing, or to avoid a single point of failure. The installer makes it easy to install an additional Comms Engine on another server and ensure it is communicating with the main system. Before starting, it is assumed that the main Sateon system is installed, using the Express or the Custom installation and that the licence has been applied. The steps you need to take are as follows:  On the main Sateon server, export certificates for use on the remote system.  On the remote server, you need to run the installer to install the Comms Engine package only. The installer will ensure all elements are present and all prerequisites are installed. As part of the process the certificates are imported.

Exporting the Certificates from the Sateon server The following steps are required on the main Sateon server. 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions. 2. Select the Advanced tab. The following dialog appears:

Sateon Release 3.4.9 30 Issue 1.2 Installation Guide July 2019

3. Select the Export Certificates button. The Certificate Export wizard opens:

4. Click Next. The Services dialog allows you to select the features that will be run on the remote machine. Select Comms Engine.

5. Click Next. The TLS Options dialog will be shown because the Comms Engine require a server (TLS) certificate. Enter the name of the server that the remote Comms Engine will be installed on.

Sateon Release 3.4.9 31 Issue 1.2 Installation Guide July 2019

Note: If you are using your own certificate rather than the supplied Sateon one, select the Skip checkbox and omit this step.

6. Click Next. On the Location dialog select the Browse button and select the destination directory for the certificates.

Note: Select an external drive or an easy to find location so you can retrieve the certificates easily from the remote system.

Sateon Release 3.4.9 32 Issue 1.2 Installation Guide July 2019

7. Select the Next button. The required certificates are exported and written to a file called Sateon-Certificates.zip in the specified directory.

Installing and configuring the remote Comms Engine 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions. 2. On the first dialog, select the Remote Comms Engine option.

3. The default installation location is C:\Program Files (x86)\Grosvenor Technology Ltd. To select an alternative, click Change and navigate to the preferred location. 4. Select the Next button.

Sateon Release 3.4.9 33 Issue 1.2 Installation Guide July 2019

5. On this page, you need to configure the account under which Sateon is run. This is used to run the Windows services and is also added to SQL when databases are deployed. For a user account, click Validate. The validation process checks whether the account\password combination exists; you cannot proceed with the installation until a valid account and password are specified. 6. Select the Next button.

Sateon Release 3.4.9 34 Issue 1.2 Installation Guide July 2019

7. On this dialog, select the Import Certificates button. A Windows File Open dialog is displayed; navigate to the Sateon-Certificates.zip file and select it. 8. An Import Certificates dialog appears with all the certificates listed and selected:

9. Click OK. The selected certificates will be imported. On the next dialog, enter the location of the Sateon service locator: the name of the machine hosting the main Sateon installation. It should be a fully-qualified domain name.

Sateon Release 3.4.9 35 Issue 1.2 Installation Guide July 2019

10. Click Validate to ensure it is correct.

Note: If the installation of Sateon running on the main server is not yet licenced, this step will fail.

11. Click Next.

Sateon Release 3.4.9 36 Issue 1.2 Installation Guide July 2019

12. Initially the GLOBAL SQL Server\Instance text box is empty and the LOCAL SQL Server\Instance text box is populated with the current machine name (the Comms Engine server). 13. Click the Validate button. The installer will complete the Global SQL Server settings and will check that the database can be reached:

Sateon Release 3.4.9 37 Issue 1.2 Installation Guide July 2019

Note: A warning icon will appear for the LOCAL SQL Server\Instance if SQL is not yet present on the server. No action is necessary as the installer will set up and configure SQL Server 2014 Service Pack (Express Edition with Tools).

14. Select Next. 15. The following confirmation dialog appears, listing the installation settings:

Sateon Release 3.4.9 38 Issue 1.2 Installation Guide July 2019

16. Select the Install button. The install will start.

Note: You will need to restart the server during the installation if SQL is installed. Once the computer has restarted, the installation will continue automatically.

17. Click Close when the completion dialog appears.

Installing a distributed system

Some larger Sateon installations will require a separate Application Server and Database Server.  The Application Server is used for the Sateon application and web server.  The Database Server (also known as the SQL Server) is used for the main SQL databases. A suitable SQL version must already be present on this server. The installation process for a distributed system can be entirely run from the Application Server.

Sateon Release 3.4.9 39 Issue 1.2 Installation Guide July 2019

The Sateon installer will handle the installation of the elements of Sateon as well as the prerequisites involved if necessary. However it is assumed that the Database Server will have a suitable version of SQL Server installed. You should also check that the SQL server permits remote connections, that the firewall policy does not prevent access and ensure that you have a suitable user configured.

Note: For a distributed installation (using separate SQL Server and Application Server), the Comms Engine database and the ESS database (known as Local databases) are always installed on the Application Server, in order to reduce traffic between systems. This means that a SQL instance will be required on the Application Server as well as the SQL Server.

Checks on the SQL Server We recommend the following checks on the SQL server are performed installation:  Check DTC settings as follows  Choose Control Panel > Administrative Tools > Component Services)  Expand Component Services and select Computers > My Computer > Distributed Transaction Coordinator  Right click Local DTC and choose Properties.  Select the Security tab. Ensure settings are as follows:

Sateon Release 3.4.9 40 Issue 1.2 Installation Guide July 2019

Once these checks are completed, we recommend that you start up the Sateon user interface and apply the licence. See After installation on page 67.

Installing Sateon on a distributed system 1. On the Application Server, open the installation media, typically a USB device, and locate and run SateonSetup.exe. The following dialog appears:

2. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions. The following page appears:

Sateon Release 3.4.9 41 Issue 1.2 Installation Guide July 2019

3. Choose Customise. The following page is displayed:

Sateon Release 3.4.9 42 Issue 1.2 Installation Guide July 2019

By default the essential features of Sateon are selected for installation: Sateon Core, Comms Engine, Logging, Event Gateway and Report Printing. To include any additional features, integrations and utilities you want to install, click the Install button next to the feature. 4. Click Next.

5. The default installation location for Sateon is C:\Program Files (x86)\Grosvenor Technology Ltd. To select an alternative, overwrite or click Change and navigate to the preferred location. Click Next.

Sateon Release 3.4.9 43 Issue 1.2 Installation Guide July 2019

6. On this page you need to configure the account under which Sateon is run. This is used to run the Windows services and is also added to SQL when the databases are deployed. A User Account that has been set up specifically for Sateon is the preferred choice for distributed installations. Specify an existing name and password. We recommend a domain account, entered in the format domain\account.

Note: We strongly recommend that for distributed installations you use a dedicated domain account – with a strong password – created specifically for use by Sateon. Where possible we recommend that you consult in-house IT staff about suitable accounts and password policies.

For a user account, click Validate. The validation process checks whether the account\password combination exists; you cannot proceed with the installation until a valid account and password are specified. 7. Click Next.

Sateon Release 3.4.9 44 Issue 1.2 Installation Guide July 2019

8. Communication between server and client systems in Sateon 2.10 is encrypted using TLS. On a first install the certificates required are created. 9. Click Next. The following dialog appears:

10. This dialog is used to identify the location of the databases. Initially, both GLOBAL SQL Server\Instance and LOCAL SQL Server\Instance will default to the current computer. If you installing a distributed system from the Application Server,

Sateon Release 3.4.9 45 Issue 1.2 Installation Guide July 2019

overwrite the GLOBAL setting with the name of your Database server. The LOCAL SQL Server\Instance should not need to be changed. For example:

11. Click the Validate button to check that the databases can be reached. If SQL is not already present on the local server, a warning icon will appear, indicating that Sateon has been unable to reach the specified database:

In this situation no action is required as SQL Server Express will be installed as part of the installation.

Note: If the validation for the Global SQL Server fails, check the SQL Server is configured to permit access, and that the user that you are running the installer as has database creation rights. In some cases the firewall configuration may need to be changed.

12. Click Next. A confirmation dialog will be displayed listing the Sateon features that are to be installed.

Sateon Release 3.4.9 46 Issue 1.2 Installation Guide July 2019

13. Click Install. The installation process will start. A User Account Control dialog may be displayed which will need to be accepted in order to continue. Depending on the prerequisites installed, you may be prompted to restart your computer one or more times in order to complete the installation. Once the computer has restarted, the installation will continue automatically. 14. At the end of the installation process, click Close. Check that all databases have been installed correctly. Global databases, including any optional databases will be installed on the SQL Server. On the Application Server, the SateonAcs and SateonEss databases will be installed.

Deploying the databases separately

In some situations you may wish to deploy the databases on a target server without installing the rest of Sateon. The installation process can be entirely run from a remote machine; you do not have to log on to the database server machine.

Sateon Release 3.4.9 47 Issue 1.2 Installation Guide July 2019

Before deploying databases  The databases should be deployed before the Application Server.  The description here assumes that the database server has a suitable version of SQL Server installed (Microsoft SQL Server 2014 or SQL Server 2012).  You should check that the target SQL Server permits remote connections, that the firewall policy does not prevent access and that you have a dedicated user account configured that has permission to create databases on the SQL server.  Check DTC settings on the SQL server machine as follows  Choose Control Panel > Administrative Tools > Component Services)  Expand Component Services and select Computers > My Computer > Distributed Transaction Coordinator  Right click Local DTC and choose Properties.  Select the Security tab. Ensure settings are as follows:

Deploying databases separately Follow these steps on the local server: 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions.

Sateon Release 3.4.9 48 Issue 1.2 Installation Guide July 2019

2. Choose the Advanced tab:

3. Select Deploy or Update Databases. The Deploy Database wizard starts.

4. Click Next.

Sateon Release 3.4.9 49 Issue 1.2 Installation Guide July 2019

5. In Machine Name, enter the name of the SQL Server machine. If you want a different instance name, change the Database Instance. 6. Click the Validate button. The installer checks that the specified server and SQL instance can be reached.

7. Click Next. The Update Databases page appears.

On a first install, no databases exist to be updated, so this page is blank. 8. Click Next. The Deploy Database page appears:

Sateon Release 3.4.9 50 Issue 1.2 Installation Guide July 2019

9. Select the databases to be deployed. At a minimum the following should be selected:  Sateon  SateonAreas  SateonIncidents  SateonLogging  SateonTokens If any of the optional features such as integrations are required, the appropriate databases should be selected. Do not select SateonEss or SateonAcs: these Local databases need to be installed on the Local machine. 10. Click Validate. Green ticks should appear against all selected databases:

Sateon Release 3.4.9 51 Issue 1.2 Installation Guide July 2019

11. Click Next. The following page appears.

Select the login to be used. We strongly recommend that in all operational situations you use a dedicated User account – with a strong password – created specifically for use by Sateon. 12. Click Next. A confirmation page appears, listing the databases to be deployed:

Sateon Release 3.4.9 52 Issue 1.2 Installation Guide July 2019

13. Click Next. Database deployment starts. This can take some time. 14. At the end of the process, click Finish. Once installation is completed, we recommend that you start up the Sateon user interface and apply the licence. See After installation on page 67.

Installing remote printing

The default Sateon installation will set up printing on the main server. In situations where a separate print server is required, the Report Printing feature must be installed on it. The installer makes it easy to install an additional print server on another server, as described below. The steps you need to take are:  On the main Sateon server, export security certificates for use on the remote print server system.  On the print server, you need to run the installer to install the Remote Printer feature only. The installer will ensure all elements are present and all prerequisites are installed. As part of the process you will import the certificates.  On the print server, you need to make sure that a suitable printer is configured and accessible. These steps are described below.

Sateon Release 3.4.9 53 Issue 1.2 Installation Guide July 2019

Before starting  On the main server it is assumed that the main Sateon system has already been installed, using the Express or the Custom installation. Ensure the licence has been applied. You should also check that the main Sateon server permits remote connections, that the firewall policy does not prevent access and that that you have a configured a suitable user account.  On the print server you need to ensure that a printer has been installed and set as the default.  On the print server you need to ensure that Adobe Reader is installed. This is required in order to produce reports.

Exporting the certificates from the Sateon server The following steps are required on the main Sateon server. 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions. 2. Select the Advanced tab. The following dialog appears:

3. Select the Export Certificates button. The Certificate Export wizard opens:

Sateon Release 3.4.9 54 Issue 1.2 Installation Guide July 2019

4. Click Next. The Services dialog allows you to select the features that will be run on the remote machine. Select just Report Printing.

5. Click Next.

Note: The TLS Options dialog is omitted as a TLS certificate is not required for the report printing option.

Sateon Release 3.4.9 55 Issue 1.2 Installation Guide July 2019

6. On the Location dialog select the Browse button and locate the directory that the certificates will be written to. By default this file is called Sateon-Certificates.zip but you can overwrite it with an alternative name if you wish.

Note: Select an external drive or an easy to find location so you can retrieve the certificates easily from the remote system.

7. A summary dialog is displayed.

8. Click Finish to close the wizard.

Sateon Release 3.4.9 56 Issue 1.2 Installation Guide July 2019

Installing and configuring the remote printing The following steps are required on the print server: 1. Copy the Sateon-Certificates.zip file from the main Sateon server to the Print Server (or ensure it is available). 2. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions. 3. On the Install tab, select the Remote Printing option. 4. Click Next. On the Install Location dialog, accept the default location or click Change to select an alternative. 5. Click Next.

6. On this page you need to configure the account under which Sateon is run. This is used to run the Report Printing service. By default this is Local Service, but if you are using a networked printer you must change this to a user account with access to network resources. We recommend creating and using a specific account for the automated printing, so that the privileges can be managed. For a local account, enter it in the form computername\account. For a domain account, enter it in the form domain\account. Enter the account password.

Sateon Release 3.4.9 57 Issue 1.2 Installation Guide July 2019

Note: We strongly recommend that in all operational situations you use a dedicated domain user account – with a strong password – created specifically for use by Sateon. Where possible we recommend that you consult in-house IT staff about suitable accounts and password policies.

For a user account, click Validate. The validation process checks whether the account\password combination exists; you cannot proceed with the installation until a valid account and password are specified. 7. Click Next.

8. On this dialog, select the Import Certificates button. A Windows File Open dialog is displayed; navigate to the saved Sateon-Certificates.zip file, select it and click Open. 9. An Import Certificates dialog appears with the required certificates listed and selected, as follows:

Sateon Release 3.4.9 58 Issue 1.2 Installation Guide July 2019

10. Click OK to return to the installer dialog. 11. Click Next. Enter the location of the machine hosting the main Sateon installation. We recommend specifying a fully-qualified domain name.

12. Click Validate to ensure it can be reached.

Note: If the installation of Sateon running on the main server is not yet licenced, this step will fail.

Sateon Release 3.4.9 59 Issue 1.2 Installation Guide July 2019

13. Click Next.

Sateon Release 3.4.9 60 Issue 1.2 Installation Guide July 2019

Initially the GLOBAL SQL Server\Instance text box is empty and the LOCAL SQL Server\Instance text box is populated with the current machine name where the remote printing is being installed. 14. Click the Validate button. The installer will complete the Global SQL Server settings and will check that it can be reached:

15. Select Next. 16. A confirmation dialog will be displayed listing the Sateon features that are to be installed:

Sateon Release 3.4.9 61 Issue 1.2 Installation Guide July 2019

17. Select the Install button. The installation will complete.

Note: A User Account Control dialog may appear. This must be accepted in order to continue.

18. Click Close when the completion dialog appears. We recommend testing the printing service after installation.

Modifying an installation

It may be necessary to amend the installed version of Sateon, for example adding or removing specific features.

To modify an installation 1. Choose Uninstall or Change a Program from the Control Panel and locate the Sateon application. 2. Right-click and choose Change.

Note: Alternatively, if you have the original installation media, locate and run SateonSetup.exe.

3. The installer starts. Select the checkbox to confirm acceptance of the licence terms and conditions.

Sateon Release 3.4.9 62 Issue 1.2 Installation Guide July 2019

4. The system detects an existing installation so Uninstall, Modify and Close are the only available options. Select Modify to display the following dialog:

Sateon Release 3.4.9 63 Issue 1.2 Installation Guide July 2019

For features that are currently installed you can select the Remove button. For features that are not currently installed you can select the Install button.

Note: Take care when modifying an installed version of Sateon. If you delete core features Sateon may not work as intended.

5. Click Next/Modify. If the original installation was set up using a specific user account, you will be prompted to enter the account password.

Enter the password for the user account and click Validate.

Note: If a built-in account such as LOCAL SERVICE was used for the original installation a password will not be required and this dialog will not appear.

Sateon Release 3.4.9 64 Issue 1.2 Installation Guide July 2019

6. Click Next. A summary dialog appears listing the options to be installed and removed, for example:

7. Click Modify. The installer runs and makes the requested changes. The following completion dialog appears.

Sateon Release 3.4.9 65 Issue 1.2 Installation Guide July 2019

8. Click Close.

Note: If you have added additional features, you may need to update the licence.

Sateon Release 3.4.9 66 Issue 1.2 Installation Guide July 2019

Section 5

After installation

This section provides details of what is installed, and explains some important tasks that you need to do following installation.  For information about what is installed, see Sateon components installed on page 68.  For details of checking the system to make sure it is running correctly, see Starting the system on page 68.  For information on licensing the software, see Installing a licence on page 74.

Sateon Release 3.4.9 67 Issue 1.2 Installation Guide July 2019

Sateon components installed

Note: The exact details depend on the features that are installed. If certain options are not selected, the corresponding files, databases, etc. would not be present.

File structure installed The installed file structure is as follows. This assumes the default location (C:\Program Files (x86)\Grosvenor Technology\Sateon) is used:

Details are as follows:  Certificates folder. Contains the SateonRoot certificate.  Databases folder. Contains files related to the SQL databases including scripts and schema files. For details of installed databases, see Databases and scripts on page 69.  Manifests folder. Contains files used by Windows.  Services folder. Contains files related to the Sateon Windows services. For details of installed services, see Services created on page 70.  Utilities folder. Contains various utilities for use by installers and support engineers. The following are included in the Express installation:  Account Reset. This tool allows Grosvenor Support to reset the administrator account in case of lock-outs.  Comms Engine Diagnostics. This utility allows engineers to check the operation of the Comms Engines and to update the firmware.  eSeries Programmer. Can be used to discover controllers: note that in Sateon Advance this utility is not usually required; it has been replaced by Quick Start.

Sateon Release 3.4.9 68 Issue 1.2 Installation Guide July 2019

 Migration Utility. This tool is used when migrating legacy JANUS systems to Sateon.  Quick Start. This application is used to discover and configure the controllers on the network.  Real Time Diagnostics. This tool is aimed at systems administrators and support staff. It allows you to configure and view system logging.  Telerik Report Designer. This utility enables you to set up your own card designs for printing on a dedicated printer. The following additional options may be present if selected during installation.  Galaxy Panel Explorer. This tool is used with the Galaxy Panel third-party integration. It allows engineers to check and report on the operation of the Galaxy Panel interface.  JANUS Extractor. This tool is used when migrating legacy JANUS systems to Sateon.  Mifare Card Reader. This utility is uses to enrol tokens with RDR-SAT-USB- DESK.  Websites folder. Contains files related to the Sateon websites. See Websites configured on page 71 for details.

Databases and scripts The following Sateon databases may be installed in the specified SQL instance. Local databases – always installed on the Application Server:  SateonAcs – this database holds the access control data.  SateonESS – holds data specific to event streaming. Core Global databases – always installed on the SQL Server:  Sateon – this is the main Sateon database, holding all data that is set up and managed from the user interface.  SateonAreas – holds data related to secure areas and the rules that apply to them.  SateonIncidents – holds data specific to incident status and reporting.  SateonLogging – holds data specific to data logging and auditing.  SateonTokens – holds data related to token usage. Optional Global databases – installed if selected:  SateonElevators – holds data specific to elevator system integrations.  SateonGalaxy – holds data specific to the Galaxy panel interface.  SateonIndigoVision – holds data specific to the IndigoVision controller interface.  SateonSalto – holds data specific to the Salto interface.  SateonSimplex – holds data specific to the Simplex panel interface.

Sateon Release 3.4.9 69 Issue 1.2 Installation Guide July 2019

Note: The Elevators, Galaxy, IndigoVision, Salto and Simplex databases are not installed unless specifically selected. However, even if they are installed, note that they cannot be used unless a suitable licence is present.

Services created The following are the core Windows services:  Sateon Areas – maintains and reports on information about secure areas and the rules that apply to them.  Sateon Comms Engine – communicates with and configures the panels controlling the doors and other hardware.  Sateon ESS (Event Streaming Service) – this service handles all events that are raised throughout the access control system.  Sateon Incident – handles the processing of high-priority events that require acknowledgement.  Sateon Legacy XML – this service provides an interface between Sateon and third- party applications using an XML protocol. Note that this is a separately licenced service.  Sateon Logging – writes details of events in the SateonLogging database, for use by reporting functions.  Sateon Report Printing – handles reporting functionality.  Sateon System Agent – this handles various aspects of the system including scheduling backups and reports, monitoring the status of other services and managing the Command Invoker, which executes commands automatically when certain events occur.  Sateon Tokens – maintains information about the use of tokens including token status and details of unauthorised use.  Sateon UI Gateway – handles data passed between the server and user interface. The following Windows services may be created if the appropriate integration options have been installed:  Sateon Aperio – this service manages the communication with wireless locks. Note that wireless lock support is a separately licensed option.  Sateon Elevators – this service communicates with external elevator control systems. Note that support for specific integrations are separately licensed options.  Sateon Event Gateway – this service provides a generic interface that can be used to send commands to various third-party systems, such as CCTV systems, with minimal configuration. The commands passed depend on the external system.  Sateon Galaxy – this service communicates with Galaxy intruder panels, where used. Note that Galaxy panel support is a separately licensed option.

Sateon Release 3.4.9 70 Issue 1.2 Installation Guide July 2019

 Sateon IndigoVision – this service communicates with the IndigoVision video controller. Note that IndigoVision support is a separately licensed option.  Sateon Psim – this service supports the PSIM integration. Note that PSIM support is a separately licenced option.  Sateon Salto – this service communicates with the Salto system. Note that Simplex panel support is a separately licensed option.  Sateon Simplex – this service communicates with Simplex fire panels, where used. Note that Simplex panel support is a separately licensed option.

Note: The Aperio, Elevators, Event Gateway, Galaxy, IndigoVision, Psim, Salto and Simplex services are not installed unless these functions are selected via the Custom installation. Even when present, note that these features cannot be used unless a suitable licence is installed.

All services (apart from the Sateon Legacy XML service, if present) should start automatically following installation. If necessary, you can start them and manage them from the Administrative Tools > Services dialog:

Message queues configured You can view the configured MSMQ queues from Administrative Tools > Computer Management > Services and Applications > Message Queuing > Private Queues.

Websites configured The Sateon websites are created beneath the Default Web Site in IIS. You will see the following in IIS Manager:

Sateon Release 3.4.9 71 Issue 1.2 Installation Guide July 2019

Shortcuts Shortcut to launch the Sateon user interface and the Quick Start are added to the Application Server desktop:

Starting the system

Following installation, we recommend that you start up the Sateon website on the server to ensure it works correctly.

To start Sateon 1. On the host server, you can select the Sateon icon on the desktop, or choose Sateon > Launch Sateon from Windows Start.

Note: If you are using a Windows 10 system, the default browser is Microsoft Edge, which is not compatible with Sateon. This means that if you run Sateon from the icon on the desktop, Sateon will not run. Use the Search option to locate Internet Explorer and use it to access Sateon, entering the URL https://hostname/sateon. Ensure you pin Internet Explorer to the Start menu or taskbar for future use.

Sateon Release 3.4.9 72 Issue 1.2 Installation Guide July 2019

2. The Sateon login page is displayed.

3. Log in using the default administrator ID and password: Username: admin Password: sateon Note that passwords are case-sensitive though usernames are not. 4. You will be prompted to change the password for the default account before continuing:

5. Enter a suitable New Password and enter it again for confirmation. Click Change Password.

Note: We recommend you copy the URL used to access Sateon and paste it to the client machines from which Sateon will be accessed.

Sateon Release 3.4.9 73 Issue 1.2 Installation Guide July 2019

Licencing

When Sateon is first started, it has no valid licence and the System Administration > Licence Info page is displayed:

The system requires a licence before any other pages can be viewed. Licensing is a two- stage process:  Load the new licence to access all licensed Sateon options.  Validate the licence within 30 days by calling Grosvenor Technical Support. Your licence file is specific to your installation. It will be provided on the USB stick under the \licence folder. The filename is in the format sateon.gtl

Note: If you do not have a licence file, contact Grosvenor Technical Support as soon as possible. See Technical support on page 7.

Installing a Sateon licence Follow these steps to install your licence: 1. On the Systems Administration > Licence Info page click the Add/Alter Licence button:

Sateon Release 3.4.9 74 Issue 1.2 Installation Guide July 2019

2. The following dialog appears:

3. Select Upload Licence. A file selection dialog appears. Navigate to the appropriate file (with the .gtl file extension) and click Open. The new licence file is installed.

Note: If you have the encrypted licence data, cut the entire string from the source email or document and paste it into the text box.

4. Click Save. 5. If the licence is successfully loaded, the following dialog box appears:

Click Finish. The log in dialog is redisplayed. 6. When you log back in, the main Sateon page appears. Additional options are available at the top of the main Sateon page. If you select System Configuration > System Administration > Licensing, details of the licence appear, for example:

Sateon Release 3.4.9 75 Issue 1.2 Installation Guide July 2019

At this point the licence is loaded but not validated. It will need to be validated within 30 days for Sateon to continue to work.

Validating the licence Following these steps to validate the licence: 1. Select System Configuration > System Administration > Licence Info to show details of the licence. If it has not been validated the status will appear as ADDED (Not Validated). 2. Click the Validate Licence button on the bottom of the page. A dialog will appear showing a validation code number:

Sateon Release 3.4.9 76 Issue 1.2 Installation Guide July 2019

3. Contact Grosvenor Technical Support (see Technical Support on page 7). You will need to provide the Licence ID number and the 16-digit Validation Code from this page. 4. Technical Support will give you a 16-digit code number. Enter it in the lower box and click Validate. The following dialog appears:

5. Click Finish. You will be logged out. When you log back in, select System Configuration > System Administration > Licence Info. The licence status will appear as follows:

Running Quick Start

The Sateon Quick Start application is intended to get Sateon controllers up and running as quickly as possible. It will discover the controllers connected to the network, and help users to set up IP addresses. It replaces the eSeries Programmer.

Sateon Release 3.4.9 77 Issue 1.2 Installation Guide July 2019

You should run Quick Start on all systems after Sateon has been installed and licenced (and after all controllers have been connected to the network). The application is installed as part of Sateon, in the Sateon/Utilities folder, and an icon will be present on the desktop.

Note: We recommend that you do not use the main Sateon user interface while running Quick Start. Ensure that any users are logged out.

Step 1: Run Quick Start and Log in to Sateon 1. Run Quick Start from the desktop icon or the application. The following dialog appears:

2. Enter the name of the server that Sateon is running on. It can be a fully-qualified name or a short form. Localhost can be used if you are running Quick Start on the server that Sateon is installed on. 3. Click Login to display the Login dialog.

Note: If no Sateon system is detected on the named server, or if you cannot log in to it, you can run Quick Start in Standalone Mode. In Standalone Mode, you can still discover controllers and set up their IP addresses, but you won’t be able to save controllers directly into Sateon.

Sateon Release 3.4.9 78 Issue 1.2 Installation Guide July 2019

4. Log in to Sateon using an Admin level username and password.

Note: If this is the first time you have logged into the Sateon UI, please use the default: Username: admin Password: sateon You will be prompted to reset the password, as described in Starting the system on page 72. Note that passwords are case-sensitive though usernames are not.

Step 2: Select defaults The first time you log in to the Sateon system, the Select Defaults dialog is displayed.

Sateon Release 3.4.9 79 Issue 1.2 Installation Guide July 2019

1. Choose the Reader/Token type used on your site, and click Continue. 2. Set the communication direction for the controller (if you are unsure, the default selection is ‘Outbound’).

Note: To change these defaults at a later stage, select the settings icon from the main screen.

Step 3: Discover controllers At this point, Quick Start will find all the controllers detected on the network and display their details as follows:

Each controller discovered will have a status:  New – The controller has been found but is not yet configured. The first step is to define its network settings so Sateon can connect to it.  Online – Sateon is already communicating with the controller. If it has door blades connected you can set up the door and reader configuration.  Offline – The controller is on the network but is not communicating with Sateon.  Unlicensed – The controller hardware doesn’t match the licence. Contact Grosvenor Technical Support. Each NEW controller discovered is identified by its unique serial number (this can be cross-referenced to the label on the controller itself). Advance controllers are reported as ADV1B (Single-Blade) or ADV4B (Multi-Blade). Legacy controllers are also discovered. Note that IPv6 must be enabled on the PC where Quick Start is running.

Sateon Release 3.4.9 80 Issue 1.2 Installation Guide July 2019

Step 4(a): Set IP addresses On each New controller, click the Install button to configure the controller. The following dialog appears:

1. Enter a name for the controller. We recommend using a name that identifies its location or purpose. 2. Select IP Only. 3. Choose Use DHCP if IP addresses are dynamically assigned, or choose Use Static IP Address to assign a static IP address. For static IP addresses you need to enter the full details: IP Address, Subnet and Gateway address. 4. Click OK. Sateon is then able to communicate with the controller. The status of the controller changes from New to Online.

Step 4(b): Set up a 485 network Up to 16 Advance controllers can be daisy-chained together. They can be any combination of Single-Blade or Multi-Blade controllers, with any number of Door or I/O Blades connected per controller. All controllers on one serial line must be Advance controllers; it is not possible to combine different types of controllers on one line. However, a single Sateon system can support multiple 485 lines, some of which can use legacy controllers. Hybrid networks using both IP-connected controllers and 485 lines are also permitted. One controller on each serial line must configured as a Relay Controller. This effectively acts as a line header, and requires an IP connection as well as a RS485 connection. It still functions as a normal controller and can have blades fitted. All other controllers in the chain are known as RS485 controllers. All controllers must initially be set up via an IP connection and configured via Quick Start.

Sateon Release 3.4.9 81 Issue 1.2 Installation Guide July 2019

Hardware connections

The maximum length of the line is 1.2 km. Note that the Relay Controller does not have to be at the bus end, it can be anywhere. Fit a 12 ohm termination resistor at either end of the RS485 bus:

Note that all Advance controllers require an Ethernet connection during the commissioning process. Once they are set up as the correct type and with the correct network settings, the Ethernet connection can be disconnected from RS485 controllers.

Note: Each controller needs to have an IP connection initially in order for Quick Start to discover and configure them. Either connect the controller via an Ethernet port or use a laptop with a USB cable connected to the USB port. This is only needed for the commissioning stage; once this is complete the controller can be located in its required position and connected to the 485 line.

To configure 485 connectivity 1. Run Quick Start to discover the controllers. 2. Select the controller and click Install. 3. Provide a name for the controller. 4. Select the appropriate connection mode:  Relay for a Relay Controller.  485 only for all other controllers in a 485 chain.

Sateon Release 3.4.9 82 Issue 1.2 Installation Guide July 2019

5. For a Relay controller, you need to set both the IP addressing and the baud rate for the 485 line:

For a 485-only controller, you need to select the Relay Controller acting as the line header and the baud rate (defaults to 19200 but can be changed if required):

Note: It is important to set the Baud rate correctly initially, as it cannot be changed without deleting and recreating the controller. Check with local IT staff where necessary.

Once Quick Start has run, the Sateon database is updated and additional information is available in the user interface.  For each Controller configured, a Controller record is set up in Sateon. For Relay controllers, the IP Address is shown and the 485 Relay Mode Active flag is set.

Sateon Release 3.4.9 83 Issue 1.2 Installation Guide July 2019

 For each Relay Controller configured, a 485 Field Network and a Port record are also created.

Firmware Update If a controller needs a new version of hardware, an Update Firmware button will appear. Pressing this will update the version of firmware running on the server. The Controller firmware cannot be updated over a 485 connection as the files are too large. If a firmware update is required while the controller has an IP connection the Update Firmware button will appear during Quick Start, enabling the process to be completed easily. If a firmware update is needed subsequently, the firmware can be updated locally using a USB stick. This is a FAT32 formatted USB stick with firmware/app files in a "firmware" directory in the root directory. Note that a controller’s current firmware version is shown in the Control Centre, when the Controller is selected on the Devices tab.

To update firmware 1. Open Sateon UI and select the Control Centre. 2. On the Devices tab, choose Controller and locate the correct controller to be updated. 3. Click Enable USB Firmware Update on the right of the screen:

Sateon Release 3.4.9 84 Issue 1.2 Installation Guide July 2019

4. When a confirmation message appears, select Yes 5. At this point, insert the USB stick into the controller.

Note: You must insert the USB stick within one hour of selecting the Enable USB Firmware Update option. Note that no messages appear in Sateon during this process.

6. While the firmware file is being downloaded, the controller LED will show a slow white flash. When it is complete the LED shows a fast, red flash. At this point you can remove the USB stick.

Note: If the USB stick is removed before the process is complete, the firmware will not be updated.

No messages are shown on the Sateon user interface. Once the firmware has been updated, you can check the firmware version shown in the Control Centre.

Sateon Release 3.4.9 85 Issue 1.2 Installation Guide July 2019

Section 6

Upgrading Sateon

This section explains the processes of upgrading and uninstalling Sateon where necessary.  Important points you need to check before running the upgrade are given in Before upgrading on page 87.  For instructions on how to upgrade Sateon, see Running the Sateon upgrade on page 87.  For details of tasks you need to do following a successful upgrade, see After upgrading on page 90.  If you just want to uninstall Sateon, see Uninstalling Sateon on page 91.

Sateon Release 3.4.9 86 Issue 1.2 Installation Guide July 2019

Before upgrading

Upgrading to version 3.4.4 is straightforward but there are a couple of important points you need to consider first.

Versions The earliest version of Sateon that can be upgraded is 2.6.0. If you have an earlier version, contact Grosvenor Technical Support. See Technical support on page 7.

Back up database Before upgrading, ensure you have taken a backup of the entire Sateon database. You can set up backups from System Configuration > System Administration > Backup Job.  If you have an existing backup job, select it and click the Trigger button:

 If you do not have an existing backup job, configure it using the Add button.

For full details, see the Sateon System Administration Guide.

Obtain an upgraded licence When you upgrade to Sateon 4 you need to upgrade the licence as well: your licence from earlier Sateon versions will not work. If you do not already have an upgraded licence, contact Grosvenor Technical Support.

Check files The upgrade process will remove everything from the Sateon folder on your file system. Ensure you move any files here that you want to keep, such as reports.

Running the Sateon upgrade

To upgrade Sateon to Release 3.4.4, you can run the installer in the same way as running a new install. The installer process will recognise that Sateon is being upgraded and will remove the earlier release and then install release 3.4.4. All data is preserved.

Note: For assistance with complex upgrades, please contact Technical Support.

To upgrade Sateon 1. Open the installation media, typically a USB device, and locate and run SateonSetup.exe. After reviewing the terms of the licence, select the checkbox to confirm acceptance of the terms and conditions.

Sateon Release 3.4.9 87 Issue 1.2 Installation Guide July 2019

2. The system detects an existing earlier installation, so Upgrade is the only available options. Select Upgrade to display the following dialog:

Sateon Release 3.4.9 88 Issue 1.2 Installation Guide July 2019

3. By default, all features already installed will be selected for Upgrade and elements not installed will be indicated by Skip. However if you wish, you can select additional items to be installed or select Remove for features that you do not need.

Note: Take care when modifying an installed version of Sateon. If you delete core features Sateon may not work as expected.

4. Click Next. The default installation location is C:\Program Files (x86)\Grosvenor Technology Ltd. To select an alternative, overwrite or click Change and navigate to the preferred location. 5. Click Next. On this page you need to configure the account under which Sateon is run. This is used to run the Windows services and is also added to SQL when databases are deployed. You should use the account selected when Sateon was first installed. 6. Click Next. The Certificates page is displayed. The default values are usually adequate as Sateon will recognise if a certificate is already present or not. However, if you are upgrading from a single server running 2.9.4 to a split tier running 2.10, a message appears on the Certificates page:

In this case, click the Repair button which will attempt to delete unwanted certificates. The dialog is then redisplayed. Select Create New … for both TLS and Auth certificates and click Next.

Sateon Release 3.4.9 89 Issue 1.2 Installation Guide July 2019

7. Click Next. On the SQL Server dialog accept the defaults and click Validate. 8. Click Next. The summary page is displayed listing the items to be upgraded. For example:

9. Click Finish when the completion dialog appears. Repeat this process on other servers if you have a distributed system.

After upgrading

Clear browser cache It is best practice after upgrading your Sateon system to clear the browser cache.

Upgrade the licence When you upgrade to Sateon 3.4.4 you need to upgrade the licence as well: your licence from earlier Sateon versions will not work. When you first start up Sateon, the following page appears, indicating that your licence needs updating.

Sateon Release 3.4.9 90 Issue 1.2 Installation Guide July 2019

Install the new licence as described in Installing a licence on page 74. Note that once installed it will need to be validated within 30 days for Sateon to continue to work. When you log in, a warning appears as follows:

For details, see Validating the licence on page 76.

Uninstalling Sateon

The Sateon installer enables you to uninstall Sateon if required.

Note: For details of uninstalling specific options and features, see Modifying an installation on page 62. There is no need to uninstall Sateon before installing a new version.

Sateon Release 3.4.9 91 Issue 1.2 Installation Guide July 2019

Uninstalling the entire application will remove the applications, services and files, but the SQL databases will be left in place. Any prerequisites that were installed as part of the one-step install will also be left in place. The process will remove everything from the Sateon folder (by default, C:\Program Files (x86)\Grosvenor Technology\Sateon); ensure you have moved any files here that you want to keep, such as reports or data backups.

Uninstalling Sateon 1. Choose Uninstall or Change a Program from the Control Panel and locate the Sateon application. 2. Right-click and choose Uninstall.

Note: Alternatively, if you have the original installation media, locate and run SateonSetup.exe.

3. The installer starts. Select the checkbox to confirm acceptance of the licence terms and conditions.

4. The system detects an existing installation. Select Uninstall; a dialog as follows in displayed to display the following dialog:

Sateon Release 3.4.9 92 Issue 1.2 Installation Guide July 2019

5. Click Uninstall to start the uninstall. A User Account Control dialog may be displayed which will need to be accepted in order to continue. At the end of the process, a confirmation screen appears. 6. Click Close to exit.

Sateon Release 3.4.9 93 Issue 1.2 Installation Guide July 2019

Appendix A

Ports used

The ports that Sateon requires depends on what features are configured. The following may be required.

Port Use Description 80 All HTTP traffic from Sateon HTTP port 443 All HTTPS traffic from Sateon HTTPS port, if running in secure mode. 4512 Silverlight, advanced graphics Used by the Silverlight plug-in to optimise the graphic performance. 9700 Cortech – XML Gateway Defined by XML Gateway. (Can be modified by customer.) 1801 MSMQ traffic Only used if Comms Engine is on a separate server. 3001 eSeries Programmer Used by XPort. 10005 Galaxy command port Galaxy interface only – used to send commands to panel. (This can be modified by customer.) 10002 Galaxy event port Galaxy interface only – used to send events to Sateon. (This can be modified by customer.) 10001 Simplex port Simplex only – used for commands and events from the Simplex panel. (This can be modified by customer.)

Sateon Release 3.4.9 94 Issue 1.2 Installation Guide July 2019