System Galaxy Install Charts

These tables cover the System Galaxy component distribution on each computer, based on the computer's role in the system  - i.e. whether it is a Database Server, Communication/Event Server, or Client Workstation (for monitoring, enrollment/badging, etc.). The charts have assistive install notes for convenience.

  • The Databases must be installed first and must online so that other computers and can connect to the database during their installation.
  • The Database and Communication/Event server (GCS Services) can be installed on the same computer or separate computers as needed.
  • If the main Communication/Event Server is installed on a MS Server OS, then the SG software is supported for administrative or diagnostic purposes only. Client Workstations are supported for card enrollment, biometric enrollment, badging, or monitoring. Some 3rd Party peripheral devices/drivers may not be compatible with a server OS.
  • When the main Comm/Event Server is installed, Galaxy will automatically open the ports that Galaxy uses, including the GCS WebAPI Service port. If you are not using one of the features that depend on the GCS WebAPI Service, you should disable the service and close the port exceptions .
  • The following features depend on the API service: idProducer Badging, Invixium Biometrics, SG LaunchPoint Web Client, Galaxy DoorPoint and PersonPoint mobile apps.

System Galaxy Current Release Version Chart

This table shows the currently released versions for the System Galaxy enterprise software version and Controller Flash Code.

System Components

Current Release Version

System Galaxy  ACS - Enterprise Software

 

 

SG 11.7.0

S28 11.0.7 - 635/600-series Flash

See Release Version Chart in the Hardware Guide for all versions.

 

  • IMPORTANT: All 635/600-series Panels must be flashed to the correct flash version that comes with your System Galaxy software.
  • WARNING: Be aware that the Factory Flash on a new or replacement board may not match the field system's SG software version. Therefore you will need to field-flash on all boards (CPU/Daughter) to match the software version you are installing or upgrading to. You only need to flash boards that do not match. In the case of a system upgrade, the flash version at all panels must be updated to match the new version of software. This is why you must always verify your panel's flash version.
  • WARNING: if you are upgrading a system that has flash older than S28 5.04 CPU Flash, then contact Authorized Tech Support for the appropriate stepped upgrade path.

See Flash Release Version Chart in the 635 Hardware Install Guide

500i-series Flash

500 Panels are no longer supported.

 

 

 

 

 

 

 

 

S28 v8.20e - 500i/508i/502i series flash

  • IMPORTANT: All 500/500i-series Panels must be flashed to the correct flash version that comes with your System Galaxy software.
  • IMPORTANT: Be aware that the Factory Flash on a new or replacement board may not match the field system's SG software version. Therefore you will need to field-flash on all boards (CPU/Daughter) to match the software version you are installing or upgrading to. You only need to flash boards that do not match. In the case of a system upgrade, the flash version at all panels must be updated to match the new version of software. This is why you must always verify your panel's flash version.

WARNING: older 500 Panels are not supported. You will need to contact authorized technical support for assistance with an upgrade path for older panels and hardware.

See 635 Hardware Guide for more details on the Release Version Chart.

 

Basic Installation Steps - Outlined

This chart outlines the Basic Steps to performing any SG installation.

  • There are 3 Steps to the SG installation.
  • All install three steps must be run in sequential order on each Galaxy computer.
  • The role of the computer will determine which option you will choose during each step - i.e. "role" means database server, event server, client workstation, etc.

System Galaxy Install media (USB/OSI)

INSTRUCTIONS:

Step-1 ) Prerequisite Components

Requirements:

  • you must run Step-1 on every computer /ever role
    i.e. DB Server, Comm Server and all Client Workstations
  • run Step-1 if doing an upgrade to an existing system.

Also See...

  • Step-1 Readme for important info before you start installing. The read-me (html) will open your default browser.
  • System Specification Guide (pdf) to see specifications for PC/Server, OS, Database, Network, as well as other compatibility and scalability guidelines.

 

This part takes only a few minutes.

 

  1. Click Step-1 Prerequisites link to begin the install if all requirements are satisfied . This install includes the .NET Framework & other components.

  2. Restart computer when you are finished.

 

Step-2 ) Database Components

  • When installing a new database, allow generous time to complete the entire process. Step-2 often takes 30 to 40 minutes - it could take longer.
  • UPGRADE WARNING: always back up your databases to and other assets to a separate and secure location before you start the upgrade. Notice: During Step-2, there is a backup-link in the database install screen that can run a backup on-the-fly before you proceed with the database upgrade. Always back up both the SysGal and SysGalArc databases.
  • The database installer will run a prerequisite validation to confirm all system components are present. The installer will display a list of pass/fail notifications. You may need to correct flagged issues before the Database can commence. Be aware that it will always notify you if IIS Server is not installed. However the IIS Server will not really impede the Database install. See IIS Exception notice below.
  • You must choose the SQL Client Component option on all client workstations that are not hosting Databases.

IIS Exception Notice: the IIS Server will not impede or impair the MSSQL or Database installation. If this is the only missing/flagged component, you can proceed with the Step-2 installation. However, be aware that IIS is required for certain Galaxy features (i.e. idProducer Badging, SG LaunchPoint, Galaxy Mobile Apps, Invixium IXM-WEB App and Video Plugins for Video Surveillance (VMS/NVRs).

IIS Install Notice: If you need the IIS Server to support WebAPI Service/API-dependent features*, you must use the IIS Install Helper Utility to get the correct IIS options enabled. The IIS Install Utility is launched from the Galaxy Installation splash-screen (usb/iso media).

Step-2 provides two install choices (Database SQL Server with Databases -or- SQL Connection Components. You must run the appropriate choice on each Galaxy computer.

  • See Step-2 Readme for important inf before you start installing Part-2. The read-me opens in a browser.
  • Restart the computer when the Part-2 install is finished if prompted or for best practice.

UPGRADE WARNING: BACK UP YOUR DATABASES BEFORE YOU UPGRADE! There is a link to perform the backups within Part-2 of the install program. Back-up both the SysGal and SysGalArc.

  1. Install MSSQL Server & Databases: run this only on your Database Server!
    This option will install (or upgrade) a SQL Server and databases. The SQL Installer will run a pre-install checklist to verify that certain components are installed and that the PC has enough space and resources before embarking on the actual SQL Server Install. Correct flagged issues as appropriate.
  2. Install SQL Client Components
    This option only installs the SQL Client Components. Choose this option if you are installing or upgrading client workstations

NOTICE: SG 11 does not support Windows 7 | XP.

NOTICE: SG 11.7.0 comes with MS-SQL Server 2019 (64bit). The 32-bit version is available on separate disk by request.

Step-3 ) System Galaxy Software

  • If you are installing a database server, you do not have to run Step-3 on the database server, although you can run Step-3 if you choose as follows ...
    1. You can run Step-3B on the database server just to get the GCS services installed on the server OS.
    2. You could optionally chose to run Step 3A on the server, but be aware that the SG Software is supported on a Server OS for diagnostic purposes only*. A client license seat is used.
  • Optionally, Step-3 can be installed on a separate computer (Server or Windows OS) that serves as the 'main Communication Server', and does not reside on the same computer with the database.
    1. You can run Step-3B on the database server just to get the GCS services installed
    2. You could optionally chose to run Step 3A on the server, but be aware that the SG Software is supported on a Server OS for diagnostic purposes only*. A client license seat is used.
  • or Step-3 can be installed on a separate computer (Windows OS) that serves as a Client Workstation.

ABOUT SERVICES: The "core services" , including the Web API service, are installed for automatic start-up. Other non-essential services are installed as "manual start-up". You only need to configure the non-essential services for auto-start if you are using a feature that relies on them. See the Step-3A Component Placement (SG Main Communication Server) .

Step-3 offers the following options...

Choose only one option on each computer.

  1. Full Install of Main Communication Server
    (software, apps, utilities, and services)
  2. Install only GCS Services
    (no client software)
  3. Client Workstation
    (no services, includes badging if purchased)
  4. Ancillary Communication Server
    (Comm Service & Event Service)

Restart the computer when the Part-3 install is finished.

 

 

IMPORTANT NOTICE: SG Software is supported on Server OS for diagnostic purposes only - which simply means you can use SG to register and configure the system and for system diagnostics, but not as an operational client workstation for real-time monitoring or badging / credential enrollment. Server OS may not support certain drivers or features in their intended optimal performance for monitoring, alarm reporting, or enrollment due to higher security settings.

 

 

SG Component Placement (per Server / Workstation Role)

Step-3A Component Placement (SG Main Communication Server)

Breakdown of component placement for Step-3A of SG Install.

Main Communication Server

Step 3A of the SG Install

System Galaxy Access Control System - Enterprise Software

Choose this for a full install of Comm Server or a Standalone Server.

GCS "Core Services"

GCS Client Gateway

GCS Comm Service

GCS Event Service

GCS DBWriter Service

GCS Web API Service

IMPORTANT: You must install Step-1 Prerequisites, and Step-2 Client Components before Step-3.

Core services support the communication between the Galaxy hardware and System Galaxy software (Comm server, Database server, and client workstations).

  • Services are already installed to “start automatically”.
  • Encryption is supported.
  • Firewall ports are automatically opened by SG Install.
  • Virus/Mal-ware exceptions must be manually created for these services to run unimpeded.

 

ABOUT THE "GCS.WebAPI.Service"

idProducer Badging Solution

Galaxy Mobile Apps

Assa DSR Manager App

Kone Manager App

Video API Plugins such as Lensec

 

As of SG 11.X the Web API Service is installed to start automatically.

IMPORTANT: if you are not using the API service you should plan on configuring it to start-up type = "manual" and you may need to close any unused ports.

  • May need port configuration if not using default port.
  • Encryption is supported.
  • May need SSL Certificate if you are running an SSL encrypted connection ( this is required with Mobile Apps). 

 

ABOUT Additional GCS Services

Additional services support special features like Event Alerts by Email/Text/File, Data Loading, Alarm Panel notifications, etc. 

  • Must be manually configured to “start automatically”.
  • Encryption is supported.
  • You must create Firewall, Virus/Mal-ware exceptions for optional services to run unimpeded.

 

ABOUT GCS Services Manager

Allows operator to view, start, and stop only Galaxy services without going into the control panel.

ABOUT GCS Service Monitor

Allows operator to view, start, and stop only Galaxy services without going into the control panel – also supports viewing connections and logging.

ABOUT Apps & Utilities

Apps and Utilities folders are located in the C:\\GCS\System Galaxy folder. This includes SG Card/Cardholder Import Utility, Assa DSR Manager, Kone App and others utilities. Typically apps and utilities do not require an additional installer. Consult appropriate documentation for the appropriate apps.

ABOUT Manuals

PDF documents are installed in the C:\\GCS\System Galaxy folder.

ABOUT Badging Software

(*included if purchased) The location of the badging software may vary based on which version of SG you have purchased. Reference the Badging Guide in the Manuals folder.

NOTICE: Some enrollment devices are not supported on a Server OS.

 

Step-3B Component Placement (GCS Services only)

Breakdown of component placement for Step-3B of SG Install.

Distributed Comm Server 

Step 3B of the SG Install

(no software)

Choose this for a distributed comm server (services only)

GCS Core Services

GCS Client Gateway

GCS Comm Service

GCS Event Service

GCS DBWriter Service

GCS Web API Service

IMPORTANT: You must install Step-1 Prerequisites and Step-2 Client Components before Step-3.

Core services support the communication between the Galaxy hardware & System Galaxy software (Comm server, Database server, and client workstations).

  • Services are already installed to “start automatically”.
  • Encryption is supported.
  • Firewall ports are automatically opened by SG Install.
  • Virus/Mal-ware exceptions must be manually created for these services to run unimpeded.

 

ABOUT THE "GCS.WebAPI.Service"

idProducer Badging Solution

Galaxy Mobile Apps

Assa DSR Manager App

Kone Manager App

Video API Plugins such as Lensec

 

As of SG 11.X the Web API Service is installed to start automatically.

IMPORTANT: if you are not using the API service you should plan on configuring it to start-up type = "manual" and you may need to close any unused ports.

  • May need port configuration if not using default port.
  • Encryption is supported.
  • May need SSL Certificate if you are running an SSL encrypted connection ( this is required with Mobile Apps). 

 

Additional GCS Services

Additional services support special features like Event Alerts by Email/Text/File, Data Loading, Alarm Panel notifications, etc. 

  • Must be manually configured to “start automatically”.
  • Encryption is supported.
  • You must create Firewall, Virus/Mal-ware exceptions for optional services to run unimpeded.

 

GCS Services Manager

Allows operator to view, start, and stop only Galaxy services without going into the control panel.

GCS Service Monitor

Allows operator to view, start, and stop only Galaxy services without going into the control panel – also supports viewing connections and logging.

 

 

Step-3C Components (SG Client Workstation)

Breakdown of component placement for Step-3C of SG Install.

Client Workstation 

Step 3C of the SG Install

System Galaxy enterprise software

Choose this for Enrollment Station, Badging Station, or Monitoring Station

   

Monitoring is an inherent feature of SG.

Badging Software*

Biometric Enrollment Software*

*Included if purchased.

 

IMPORTANT: You must install
Step-1 Prerequisites
, and Step-2 Client Components before Step-3.

The SG Client installs with the full inherent features.

Biometric Solutions are provided with the installation (if purchased) and can be installed by following the instructions in the correlating Installation Guide for that product.

  • Invixium Biometric Solution
  • MorphoManager Solution

 

Badging Solutions are provided with the installation (if purchased) and can be installed by following the instructions in the correlating Installation Guide for that product.

  • idProducer Web Badging Solution
  • Card Exchange Badging Solution

 

All manuals are installed in the C:\\GCS\System Galaxy folder and are also included on Disk2 of the GalSuite Disk Set.

NOTICE: Some enrollment devices are not supported on a Server OS.

 

 

Step-3D Component Placement (Ancillary Communication Server)

Breakdown of component placement for Step-3D of SG Install.

Ancillary Comm Server 

Step 3D of the SG Install

(no software)

Choose this for an ancillary Comm / Event Server

Comm & Event Services

GCS Comm Service

GCS Event Service

IMPORTANT: You must install Step-1 Prerequisites and Step-2 Client Components before Step-3.

An Ancillary Server supports communication & events from loops/clusters connected to the SG Ancillary Server. The Ancillary server transmits the event logging and communications to the Main Comm Server & SG Database Server.  

After you install the Ancillary Server, you must manually configure the Ancillary Comm Service to connect to the GCS ClientGW Service which will be running on the Main SG Comm Server.

  • Comm & Event services are installed to “start automatically”.
  • Encryption is supported.
  • Firewall ports are automatically opened by the SG Install.
  • Virus/Mal-ware exceptions must be manually created for these services to run unimpeded.

 

NOTICE: There can be only one ClientGW Service running system-wide.

NOTICE: There can be only one DBWriter Service running system-wide.