System Galaxy Installation Instructions: - Galaxy Control Systems

System Galaxy 8.1 Installation Guide 

System Galaxy 8.1 Installation Guide 

System Galaxy Software & Database 

Installations and Upgrades 

Page 1 of 29

Editions / Copyright 

System Galaxy 8.1 

Installation Guide 

Galaxy Control Systems 

3 North Main Street 

Walkersville MD 21793 

301-845-6600 

www.galaxysys.com 

Information in this document is subject to change without notice. 

No claims are made as to the accuracy or completeness of this document. 

Copyright © 2006 Galaxy Control Systems All rights reserved 

No part of this document may be reproduced, copied, adapted, or 

transmitted, in any form or by any means, electronic or mechanical, for 

any purpose, without the express written consent of Galaxy Control 

Systems. Copyright protection claims include all forms and matters of 

copyrighted material and information, including but not limited to, 

material generated from the software programs, which are displayed 

on the screen such as icons, look and feel, etc. 

Microsoft ® , Windows ® , MS-DOS ® , SQL Server , and Windows Server 

System ® , are trademarks or registered trademarks of the Microsoft 

Corporation in the U.S. and other countries. 

Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. 

Graphics, diagrams and designs are creations of the technical author. 

Page 2 of 29

Table of Contents 

Sections in this Manual Pg 

GalSuite Installation Diagram 4 

Introduction to the GalSuite Installation: 5 

Section 1.0 - Installation Requirements: 6 - 7 

Section 2.0 - Upgrade QUICK STEPS 

Page 3 of 29 

8 - 9 

Section 3.0 - New Install QUICK STEPS 10 

Section 4.0 - GalSuite Installation Instructions 12 – 26 

4.1 Start the GalSuite Install CD – pg. 12 

4.2 GalSuite Part 1) Prerequisites – pg. 13 

4.3 GalSuite Part 2) SQL Server Install for NEW INSTALLS & UPGRADES – pg. 14 

4.3.1 New Install: Database Server (or Standalone) with SQL Server 2005 Express – pg. 14 

4.3.2 New Install: Database Server (or Standalone) with existing MSDE/ SQL 2000 – pg. 16 

4.3.3 New Install: System Galaxy Communication Server or SG Client Workstation – pg. 17 

4.3.4 Upgrade: Database Server (or Standalone) using SQL Server 2005 Express – pg. 18 

4.3.5 Upgrade: Database Server (or Standalone) on MSDE2000/SQL 2000 Server – pg. 22 

4.3.6 Upgrade: System Galaxy Communication Server or SG Client Workstation – pg. 23 

4.4 Run GalSuite Part 3) System Galaxy – pg. 24 

Section 5.0 - Tips and Techniques: 27 - 29

Installation Diagram ~ SG V8.1 Install 

Page 4 of 29

About the SG 8.1 Installation: 

This Installation Guide provides Upgrade & Install Quick Step Procedures and Install Diagrams to help 

organize/support the installation effort. Use these tools to guide the installation of the GalSuite software. 

What’s New in the SG 8.1 Install? 

The SG 8.1 Install includes v2 .NET Framework, Windows Installer v3.1, and SQL Server 2005 Express 

database engine (royalty-free). MDAC 2.8 SP1 is only installed for systems on Windows ® 2000 OS. 

Also note that the Upgrade Results, and other Database scripts and batch files used to attach/detach 

databases and create logins are stored in the c:\Program Files\System Galaxy\DBscripts. 

What is SQL Server 2005 Express? 

SQL Server 2005 Express is Microsoft’s replacement for MSDE2000. System Galaxy 8.1 is designed to 

use the SQL Server 2005 Express database engine, but is compatible with SQL Server 2000 or MSDE. 

If an existing System Galaxy customer wants to upgrade to SG 8.1, they can: 

(recommended) upgrade databases & software and move to SQL Server 2005 Express 

or keep existing MSDE and upgrade the databases and software. 

IMPORTANT: A database server must be installed/present for each System Galaxy system and should be 

installed before any client workstations or communication servers are installed. 

NOTE: GalSuite Part 2: the New Install SQL Server 2005 Express also creates the database logins: 

• SA password = GCSsa5560 

• gcs_client = SysGal.5560 (notice the dot between SysGal and 5560) 

• gcs_web_client = SysGal.5560 

IMPORTANT: SQL 2005 Client Components must be installed on workstations that will need an ODBC 

connection to the database server. You must install this in GalSuite Part 2 (upgrades or new installs) before 

running Part 3 to install Galaxy Software. 

What’s in this Manual? 

Install Diagram (page 3) shows the flow of the install and main choices in a one-page diagram. It 

gives brief details about what is being installed in each part based on the choices. 

Section 1.0 Requirements for System Galaxy 8.1, Genesis T/A, and SQL Server 2005 Express. 

Section 2.0 Upgrade QUICK STEPS tables listing the major steps to do an upgrade on each computer 

in the Galaxy system, with choices based on the type of upgrade. 

Section 3.0 New Install QUICK STEPS tables listing the major steps to do a new install on each 

computer in the Galaxy system, with choices based on the type of install. 

Section 4.0 Instructions provides additional information about individual screens / how to use them. 

Section 5.0 Tips and Techniques provides useful info on tasks related to the installation process. 

Page 5 of 29

1.0 Installation Requirements: 

This section provides known requirements for System Galaxy 8.1 and for SQL Server 2005 Express. 

System Galaxy 8.1 Requirements: 

System Galaxy 8.1 Requirements are the same as previous releases of v8 / v7 with the following additions: 

SG 8.1 is compatible with Windows ® XP Pro; Windows ® 2003 Server; Windows ® 2000 

Server/Pro. 

SG 8.1 is designed to use SQL 2005 Native Client (ODBC driver) for database connections. 

The Microsoft SQL Client Components are installed in GalSuite Part 2. This must be installed before Part 3. 

SG 8.1 comes with SQL Server 2005 Express royalty free database engine. 

System Galaxy 8.1 is also compatible with existing SQL Server 2000 or MSDE 2000 for those 

customers that want to upgrade their software, but not migrate to SQL Server 2005 Express. 

SG 8.1 uses the product level registration method. Customers upgrading from SG v6 may need to 

consider hardware upgrades. SG 8 replaces 508 non-i-series hardware with 600-series (professional 

level) or 508i-series (corporate/enterprise levels). 

SG 8.1 will take a minimum of 600 MB for a simple installation. This value will increase by an 

unfixed amount if customer will be storing custom graphics, photo/badging and other credentialing 

files (i.e. fingerprints, signatures, etc). 

SG 8.1 Databases: the SysGal and SysGalArc database files are limited in size by the inherent 

limit of the database engine you choose. 

IMPORTANT SECURITY NOTE: 

The following ports/applications must be unblocked for System Galaxy: 

5010, 3001, 4000, 4001, 4002, 4003, 4004, and sqlservr.exe, sqlbrowser.exe for a networked 

system. See the chart in Section 5.0. 

The GalSuite Install program may automatically “open” these Windows ® Firewall Exceptions, 

depending on which installation choices are selected. IF you are doing a standalone install and no 

other clients will connect remotely to the SG Database/Comm. Server, then you will want to edit the 

firewall manually to use only those exceptions you truly need. 

! Remember that port 3001 is always required for communication to Galaxy hardware controllers. 

Also note that any network switches or routers must also meet port requirements. 

If using Time and Attendance with linked database servers: 

TCP Port 135 and ports 6000 through 6050 are used for MSDTC service on both servers. 

Note that the DTC authentication settings must match on both servers. If you are running 2000 

Operating System, then both servers will have to use “NONE” as the authentication setting. 

TIP: A “.reg” file is included on the GalSuite 8.1 CD that opens the T&A ports configures the DTC 

security settings. Be aware that you may need the IT personnel to approve running this or allow 

them to manually incorporate the needed DTC configuration. Use Notepad to view the .reg file. 

Page 6 of 29

1.0 Installation Requirements (continued): 

Known Requirements for SQL Server 2005 Express 

These requirements are abbreviated from the “Upgrading MSDE 2000 to SQL Server 2005 Express” 

document written/produced by Microsoft. The full documentation is found online with Microsoft. 

Hardware: Galaxy Control Systems recommends meeting the recommended requirements. 

• Processor: a 1-GHz processor is recommended. 

• RAM: 1 GB of RAM is recommended. 

• Disk Space: 1 GB of free disk space is recommended. 

Operating Systems: Galaxy Control Systems recommends meeting the recommended requirements. 

• Microsoft Windows 2000 with Service Pack 4 

• Microsoft Windows XP with Service Pack 2 

• Microsoft Windows Server 2003 Service Pack 1 

• Microsoft Windows Small Business Server 2003 Service Pack 1 

Prerequisites: for SQL Server 2005 Express 

• installation of v 2.0 .NET Framework (GalSuite CD installs v2.0 .NET Framework during Part 1) 

• the presence of Internet Explorer 6 with Service Pack 1 (this is not installed by the GalSuite Install) 

• MDAC 2.8 sp1 for Windows® 2000 (GalSuite CD installs this if needed) 

IMPORTANT GENESIS NOTE: 

Genesis SQL is compatible with MS SQL Server 2000, but not MSDE. 

If using a shared server connection, System Galaxy 8.1 is compatible with SQL Server 2000. 

However, you must manually copy and attach the SG 8.1 databases and manually create the SG 

database logins. 

If using a linked server connection, System Galaxy 8.1 can run on SQL Server 2005 Express. No 

claims are made or implied that Genesis is compatible with SQL Server 2005/ 2005 Express. 

See Galaxy Interface Guide for Genesis Time & Attendance for requirements specific to Time & 

Attendance. 

Page 7 of 29

2.0 Upgrade Quick Steps! 

Use the correct table to guide you through the upgrade of a Database or Standalone Server from SG v7.0 or 

higher. If you need to upgrade from v6 or older, contact Technical Support to have your database converted. 

NOTE: always make a backup database before upgrading! 

Upgrade DB Server (or Standalone PC) and install SQL 2005 Express 

TABLE 1: Upgrade Database Server (or Standalone PC) and install SQL 2005 Express 

Upgrade SG Database Server but move to SQL 2005 Express 

1 Stop ALL Galaxy software and services on all computers in the system. 

Back up existing databases !! (of SysGal and SysGalArc) and verify the database sizes are correct. 

GalSuite Part 1: Prerequisites (Mandatory) ~ reference Section 4.2 

2 Run GalSuite Part 1 to install v2 .NET Framework & Windows Installer 3.1 

GalSuite Part 2: SQL 2005 Express (Mandatory) ~ reference Section 4.3 

3 Run GalSuite Part 2: choose NEW INSTALL then Option 1 to install SQL Server 2005 Express 

4 Manually delete new blank databases from the 2005 Express engine 

5 Manually detach existing databases from old DB Engine 

6 

You must copy the SysGal & SysGalArc Database files and Log files 

to the newly created data folder for the SQL 2005 Express engine. 

Default MSDE directory 

c:\Program Files\Microsoft SQL Server\ MSSQL\ Data 

SysGal_Data.MDF 

SysGal_Log.LDF 

SysGalArc_Data.MDF 

SysGalArc_Log.LDF 

copy files to SQL Server 2005 directory 

Default MS SQL Server 2005 Express directory 

c:\Program Files\Microsoft SQL Server\MSSQL.1\ MSSQL\Data 

7 Manually attach existing SG databases to the 2005 Express engine (named SysGal and SysGalArc) 

8 If the previous system was v7.X or v8.0, you need to manually run the Login script (on the CD in the 

Components\Database\SQL Server\SQL2005\Scripts\ “CreateLoginsAndUsersSQL2005.sql”). 

9 Run GalSuite Part 2 click UPGRADE and choose Option 2 upgrade SysGal and SysGalArc. 

If you need to upgrade software on this machine (standalone PC), run GalSuite Part 3 below. 

GalSuite Part 3: System Galaxy (Conditional) ~ reference Section 4.4 

10 Run Part 3 only if upgrading System Galaxy software on this machine; 

choose Option A ) to upgrade a standalone server (i.e. software & services) 

Note: the install automatically detects/uninstalls the old version of SG from the System Galaxy directory. If 

SG was installed in a directory that is more than 2 tiers deep, you need to uninstall the old SG manually. 

Page 8 of 29

Upgrade DB Server (or Standalone PC) but keep MSDE/2000 

TABLE 2: Upgrade Database Server (or Standalone PC) but stay with existing MSDE or Server 2000 

Upgrade SG Database Server but keep MSDE or SQL Server 2000 

1 

2 

Stop ALL Galaxy software and services on all computers in the system. 

Back up existing databases !! (of SysGal and SysGalArc) and verify the database sizes are correct. 


Run GalSuite Part 1 to install v2 .NET Framework & Windows Installer 3.1 


3 Run GalSuite Part 2: choose UPGRADE and then Option 2 upgrade SysGal and SysGalArc 

NOTE: you will not need to install the SQL Server Express engine if the customer is staying with 

the existing MSDE 2000 engine. However, just as Microsoft increasingly limits it’s support of the 

MSDE product, Galaxy will be forced to eventually stop using MSDE in future releases. Your 

customer may wish to consider moving to SQL Server 2005 Express (explained in Table 1). 

If you need to upgrade software on this machine (standalone PC), then do the following steps. 

4 

5 

Run GalSuite Part 2, click UPGRADE and choose Option 1 to install SQL Client Components. 

GalSuite Part 3: System Galaxy (Conditional) ~ reference Section 4.4 

Run Part 3 only if upgrading System Galaxy software on this machine; 

choose Option A ) to upgrade a standalone server (i.e. software & services) 

Note: the install automatically detects/uninstalls the old version of SG from the System Galaxy directory. 

If SG was installed in a directory that is more than 2 tiers deep, you need to uninstall the old SG manually. 

Page 9 of 29

2.0 Upgrade Quick Steps! (continued) 

Use the following tables to guide you through upgrading a Main Communication Server or Client Workstation 

in a networked environment. 

Upgrade a Main Communication Server (database is not on this machine) 

IMPORTANT: your database server must be installed/upgraded first! 

TABLE 3: Upgrade a Main Communication Server (database not on this machine) 

Upgrade a Main Communication Server (databases are not on this machine) 


1 Run Part 1 of the GalSuite Install to install v2 .NET Framework & Windows Installer 3.1 


2 Run GalSuite Part 2 click UPGRADE and choose Option 1 to install SQL Client Components 

GalSuite Part 3: System Galaxy (Mandatory) ) ~ reference Section 4.4 

3 

Run GalSuite Part 3 to install the System Galaxy software: 

choose Option A) to upgrade a Main Communication Server (software & services, includes badging) 


SG was installed in a non-standard directory that is more than 2 tiers deep, you need to uninstall the old SG 

manually before running GalSuite Part-3. 

Upgrade a Client Workstation (database is not on this machine) 

TABLE 4: Upgrade a Client Workstation (database not on this machine) 

Upgrade a Client Workstation or Comm. Server (databases are not on this machine) 




2 Run GalSuite Part 2 click UPGRADE and choose Option 1 to install SQL Client Components 


3 

Run GalSuite Part 3 to install the System Galaxy software: 

choose Option C) to upgrade a Client Workstation (Galaxy software, includes badging) 


SG was installed in a non-standard directory that is more than 2 tiers deep, you need to uninstall the old SG 

manually before running GalSuite Part-3. 

Page 10 of 29

3.0 New Install Quick Steps! 

Use the appropriate tables to guide you through the new install process. NOTE: There must be a database 

server installed and it must be installed before System Galaxy software is installed. 

Go to section 2.0 if you are doing an upgrade. 

Install a New Database Server (or Standalone PC) with SQL Server 2005 Express 

TABLE 5: Install NEW Database Server (or Standalone PC) with SQL Server 2005 Express 

Install a New Database Server with SQL Server 2005 Express 




2 Run GalSuite Part 2, then NEW INSTALL and Option 1 to install SQL Server 2005 Express and 

the blank SysGal and SysGalArc databases (logins are also created) 

If you need to install software on this machine (standalone PC), run GalSuite Part 3 below. 

GalSuite Part 3: System Galaxy (Conditional) ) ~ reference Section 4.4 

3 

Run GalSuite Part 3 to install System Galaxy software on this machine: 

choose Option A) to install a main Communication Server (software & services, includes badging) 

Install a New Client Workstation or Communication Server (database is not on this machine) 

TABLE 6: Install a NEW Client Workstation or Comm. Server (database not on this machine) 

Install New Communication Server or Client Workstation (databases not on this PC) 

Note: your database server should already be installed, running and ready for connection. 




2 Run GalSuite Part 2, then NEW INSTALL and Option 2 to install SQL Client Component 

3 


Run GalSuite Part 3 to install the software: 

choose Option A) to install a main Communication Server (software & services, includes badging) 

choose Option C) to install a Client Workstation (Galaxy software, includes badging) 

Page 11 of 29

4.0 System Galaxy Installation Instructions: 

The GalSuite Installation Program (CD) provides a main Startup Screen (fig. 1) for users to run all parts of 

the install process. 

4.1 Start the GalSuite Install CD: 

The CD should auto-start and open the Starting screen (figure 1) when you load it in the CD drive. Also, 

you can use Windows ® file explorer to browse to the CD drive and double-click the GalSuite icon to start. 

The GalSuite 8.1 Install has three (3) parts outlined below: 

PART 1) Prerequisites: installs the v2 .NET Framework and v3.1Windows Installer program. This part will also 

install the MDAC 2.8 SP1 on Windows ® 2000 Server. This part of the install must be completed 

before installing any other parts. 

PART 2) SQL 2005 Express Server: gives the user choices to perform an upgrade or new install: 

either install a new SQL Server 2005 Express database engine with new Galaxy databases, 

or perform a database upgrade from System Galaxy v7.0 or later. Databases from v6 or earlier must 

be sent to GCS Tech Support to be converted/upgraded. 

or install the SQL Client Components for new or upgraded SG Client Workstation/Comm. Server 

IMPORTANT GENESIS NOTE: If the customer will be registered for Genesis Time & Attendance, and use 

a shared database server engine, you must use SQL Server 2000 engine (i.e. not MSDE). If you use a 

linked server connection (SG database is not on the same server engine as Genesis) then you can run 

System Galaxy on SQL Server 2005 Express or other compatible choice (see requirements section). 

PART 3) System Galaxy: installs the System Galaxy software and/or GCS Services as appropriate. This part 

must be done last and always requires on actions in Part 1 and 2 to be completed. Note: the install 

will detect and uninstall the older versions of SG. If SG was installed in a non-standard directory that 

is more than 2 tiers deep, you need to uninstall the old SG manually before running Part-3. 

Figure 1: the GalSuite Install User Interface – Start up Screen: 

Page 12 of 29

4.2 Run GalSuite - Part 1) Prerequisites 

Part-1 on the CD installs components that are required for the rest of the installation to complete. 

IMPORTANT! THIS PART MUST ALWAYS BE INSTALLED FIRST on every type of System 

Galaxy server or client (i.e. database server, communication server, client workstation). 

Note: Gal Suite will run hidden during the execution of this part of the install. 

1. On the GalSuite screen, select “Part-1 Prerequisites” and click [Install Now]. 

Dialog boxes will display with hourglasses while the components install. This part 

may take some time. 

The System Galaxy Prerequisites Setup window will display when the components are 

finished installing successfully. 

2. Click [Finish] to return to the GalSuite Install Program. 

Figure 2: Installing Prerequisite requirements: 

Page 13 of 29

4.3 Run GalSuite - Part 2) SQL Server 2005 Express 

During Part-2 you must choose from options based on whether you are doing an upgrade or new install and 

the type of Server/PC you are setting up (i.e. database server, comm server, workstation). You can use the 

Install Quick Step Tables (sections 2 and 3) for guidance. 

3. On the GalSuite screen, select “Part-2 SQL Server 2005 Express” and click [Install Now]. 

4. In the Choose Install Type screen, click appropriate option - [NEW INSTALL] or [UPGRADE] 

and go to the appropriate subsection below: 

4.3.1 NEW INSTALL Database Server w/ SQL Server 2005 Express (Quick Start Table 5) 

IMPORTANT SECURITY ALERT: This portion of the install will configure the firewall settings to 

allow “sqlservr.exe” and “sqlbrowser.exe” to run on this computer. You may want to change 

firewall settings after completing the install ONLY IF no other Galaxy computers will be installed to 

connect to this computer (i.e. if you are setting up a “stand-alone computer”). 

a) from the Choose Install Type screen: click option 1 "Install Complete Database Server" 

(see fig 3).: click option 1 “Install Complete Database Server”. This opens a screen where 

you can install the SQL 2005 engine or attach new databases. 

Figure 3: New Install > (OPTION 1) Microsoft SQL Server 2005 Express 

Page 14 of 29

) In the Installation Folder field you can see the default location for the database files 

(recommended) or you can browse to a different path by clicking [choose folder]. 

c) In the Instance Name field you can see the default name (GCSSQLEXPRESS) for the SQL 

2005 engine. Note the install will set the SA password to GCSsa5560. 

d) Click [Click Here to Install Now] to begin the install. GalSuite installs SQL 2005 Express, 

attaches SysGal/SysGalArc databases, creates DB logins: 


• gcs_client = SysGal.5560 


• also the result files will be saved on the hard drive (c:\Program Files\System 

Galaxy\DBscripts folder). this folder will also contain the batch files for 

detaching/attaching databases, creating logins, etc. 

Figure 4: New Install > Microsoft SQL Server 2005 Express 

e) IF you are installing a Database Server, you are finished. If you are installing a 

Standalone server (i.e. adding Software/Services), go to Section 4.4. 

Page 15 of 29

4.3.2 NEW INSTALL: Attach new databases to an existing SQL Server 2005 

Note: If GalSuite finds an existing instance of SQL Server 2005, it will display the bottom half of the 

screen so you can attach the new databases. In this case you will not need to install an engine. 

a) Select the GCSSQLEXPRESS (or appropriate instance name). 

b) The Connection Security fields will use the SQL Server Authentication by default. 

Provide the appropriate user name and password. If the existing engine was previously 

installed with GalSuite, the default SA password is GCSsa5560. 

c) In the Database File Folder field you will see the default path for the database files. 

GalSuite reads this from the computer registry for the instance you selected. 

d) In the Galaxy Scripts Folder field you will see the default path for the result files for 

attach and login scripts. You can change this location by clicking the [choose folder] button. 

e) Click [Copy & Attach to SQL Server] button to attach SysGal/SysGalArc. NOTE: this will 

NOT set the PC firewall exceptions (see Table 7 in Section 5.0 for necessary settings). 

Figure 5: New Install >Galaxy Databases on existing SQL Server 2005 instance 

f) If this is only a database server, you are finished. If this is a Standalone Server (i.e. 

adding software/services), go to Sect. 4.4. 

Page 16 of 29

4.3.3 NEW INSTALL: SG Workstation or Communication Server (Quick Start Table 6) 

a) If installing a System Galaxy Communication Server or SG Client Workstation: you will 

click option 2 “Install SQL Client Components”. This installs the Native SQL Client 

Components (ODBC Driver) that the SG software uses. This install is always mandatory for 

System Galaxy software. 

Figure 6: New Install > SQL Server 2005 Client Components (ODBC Driver) 

b) Click [OK] when the client components have finished installing 

c) Go to Section 4.4 to complete the Software installation. 

Page 17 of 29

4.3.4 UPGRADE Databases using SQL Server 2005 Express (Quick Start Table 1) 

NOTE: You should have already run GalSuite - Part 1 to install prerequisites. 

IMPORTANT: If you are not switching to SQL Server 2005 Express (i.e. you are keeping MSDE), go 

to the next section for upgrading while keeping MSDE. 

a) Back up your existing SysGal and SysGalArc databases and verify they are the same size 

as the working databases. 

b) If you are migrating away from MSDE/2000, Run GalSuite Part 2 SQL Server 2005 Express 

and click [NEW INSTALL] button. 

If installing the new SQL 2005 Express: click option 1 “Install Complete Database 

Server”. This opens a screen to install the SQL 2005 engine. 

In the Installation Folder field you can see the default location for the database files 


In the Instance Name field you can see the default name (GCSSQLEXPRESS) for the SQL 

2005 engine. Note the install will set the SA password to GCSsa5560. 

Click [Click Here to Install Now] to begin the install. 

Figure 7: Migrating to Microsoft SQL Server 2005 Express 

Page 18 of 29

c) DELETE THE NEW BLANK DATABASES ON THE SQL Server 2005 Express engine after the 

engine is installed successfully. 

d) Manually detach the customer’s existing databases from the existing engine 

e) Copy the database and log files to the SQL 2005 Data directory 

Figure 8: Copying Database Files to new SQL Data folder 

f) Manually attach databases to the new SQL 2005 Express instance (GCSSQLEXPRESS). 

IMPORTANT: Name them SysGal and SysGalArc so that the login and upgrade scripts can 

run against them without errors. 

g) If the previous system was v7.x or v8.0, you need to manually run the 

‘CreateLoginsAndUsersSQL2005.sql’ script on the databases (located on the GalSuite CD in the 

Components\Database\SQL Server\SQL2005\Scripts folder). 

Page 19 of 29

h) Now that the existing databases are attached to the new engine, Run GalSuite Part 2 again 

and click the [UPGRADE] button in Choose Install Type screen. 

i) In the Installation Folder field you can see the default location for the database files. 

j) click Option 2 Upgrade Existing Databases: 

Figure 9: Upgrade Galaxy Databases on the SQL Server. 

Page 20 of 29

k) When you click the [Execute Upgrade…] button, the Upgrade Databases screen will open. 

Figure 10: Executing Upgrades on Galaxy Databases. 

l) Select the SQL 2005 Instance name (should be GCSSQLEXPRESS if you used the default). 

m) Select correct authentication settings and click [Connect to Server] button (user name SA 

and password = GCSsa5560 by default if you used GalSuite to install the SQL 2005 Express). 

n) STOP ALL GALAXY GCS Services on this machine (and any other networked workstations). 

o) Pick the main database (SysGal) and click the [Execute Main Database Upgrade] button. 

Scripts are executed to upgrade database and add new logins. Note: Registration must be valid. 

p) Pick the archive database (SysGalArc) and click the [Execute Archive Database Upgrade] 

button. Scripts will be executed to update the database. 

q) If this is a standalone PC go to Section 4.4 after the scripts complete successfully. 

r) If this is only a database server, you are finished. 

Page 21 of 29

4.3.5 UPGRADE: Databases/keep existing engine MSDE/2000 (Table 2) 


a) Back up your existing SysGal and SysGalArc databases and verify they are the same size 

as the working databases. 

b) Run GalSuite Part 2 and click [UPGRADE] button in Choose Install Type screen. 

c) In the Installation Folder field you can see the default location for the database files 


d) click Option 2 Upgrade Existing Databases 

e) When you click the [Execute Upgrade…] button, the Upgrade Databases screen will open. 

Figure 11: Executing Upgrades on existing Galaxy Databases. 

f) Select the MSDE or 2000 Instance name as appropriate. 

g) Select appropriate authentication settings and click [Connect to Server] button. 

h) STOP ALL GALAXY GCS Services on this machine and any other networked workstations. 

i) Pick the main database (SysGal) and click the [Execute Main Database Upgrade] button. 

Scripts are executed to upgrade database, add the new logins. Note: Registration must be valid. 

j) Pick archive database (SysGalArc) and click [Execute Archive Database Upgrade] button. 

k) If this is only a database server, you are finished. 

l) If this is a standalone PC and you need to upgrade software: 

Run GalSuite Part 2, pick UPGRADE, choose Option 1-Install SQL Client Components. 

Go to Section 4.4 to install software. 

Page 22 of 29

4.3.6 UPGRADE: Client Workstation or Comm. Server (Table 3/4) 


a) Run GalSuite Part 2 and click [UPGRADE] button in Install Type screen. 

b) Select Option 1 – Install SQL Client Components. This installs the Native SQL 2005 Client 

Components, including ODBC driver that Galaxy will use to support the data source 

connections. The data source connections are created in GalSuite Part 3. 

If you are upgrading from v7.x or 8.0 you must run this step before adding software. 

c) Click [OK] when the client components have finished installing. Go to Section 4.4. 

Figure 12: Installing SQL Client Components for a Workstation of Comm. Server 

Page 23 of 29

4.4 Run GalSuite - Part 3) System Galaxy software & services 

IMPORTANT: You must have already run GalSuite - Part 1 to install the prerequisite software. If you 

have not run GalSuite Part 1, you must run it before you can install software. 

IMPORTANT: You must have run the appropriate GalSuite Part 2 for SQL Server Components. 

• If this is a new install of a standalone computer (database and software on the same machine), 

you should have already installed the SQL Server Engine and System Galaxy databases. 

• If this is an upgrade of an existing standalone computer, you should have already completed 

upgrading the databases and installing the SQL Client Components. You must complete Part 2 first. 

• If this is a new install or upgrade of a Database Server that does not need Galaxy software, you 

are done / don’t need to run GalSuite Part 3. 

• If this is a Communication Server, you must have installed the SQL Client Components from Part 2 

before software can be installed. Also the Database Server must already be installed/upgraded and 

online before running Part 3. 

• If this is a Galaxy Client Workstation or Badging Station, you must have installed the SQL Client 

Components from Part 2 before software can be installed. Also the Database Server must already be 

installed/upgraded and online before running Part 3. 

1. The Wise Installation Wizard dialog will display and extract and start installing. 

ALL UPGRADES: If the previous installation of System Galaxy was not installed in the standard 

location (c:\Program Files\System Galaxy) and is more than two directories deep, the Software will 

need to be uninstalled with the original uninstall feature or from the Control Panel. 

UPGRADES for 8.0 or earlier: if an existing instance of System Galaxy software is detected, the 

Uninstall Previous SG Software screen will display. Click the button to Uninstall. 

UPGRADES for v8.1 or later: if an existing instance of System Galaxy software is detected, the 

Application Maintenance screen will display. This allows user to choose to Remove the previous 

version of System Galaxy. Pick ‘Remove’ option and click NEXT to uninstall. 

Click FINISH when UN-install is complete. 

2. Run GalSuite Part-3 and click [Install Now]. 

3. The Install Wizard Welcome screen displays. Click NEXT to continue. 

4. The User Information screen displays. You can keep the default values or set the values as needed 

and click NEXT to continue. 

5. The Destination Folder for System Galaxy displays: Keep the default folder (recommended) or 

browse as needed and click NEXT when ready to continue. 

Page 24 of 29

6. The Specify Workstation Configuration screen displays. Select the appropriate Option (A, B, C, D) 

and click NEXT when ready to continue. 

a) Complete Install: (pick this to install a Main Communication Server with Software/Services) 

This puts down the System Galaxy and Badging software and all the services (with the 

core services set to run/start automatically). 

This configuration can be installed on a computer that will be networked to the Database 

Server or on the same computer as the Database Server (standalone). 

If you will not be using any 600-series hardware, you can manually remove the Event 

Service after the installation is complete through the Control Panel. 

b) Install Galaxy Services – Main Communication Server without Client: 

This puts down the all the services (with the core services set to run/start automatically). 

It does not install System Galaxy or Badging software. 



c) Install Client Software Only/no services: (this installs a typical workstation/ badging station) 

This puts down the System Galaxy and Badging software, but no services 

d) Install Ancillary Communication & Event Server only: (pick this for an additional Comm. 

Server if a Main Comm Server has already been installed). If you need client software, it is better 

to run Option A and manually remove Client Gateway and DBWriter services through Control Panel. 

This puts down the Comm and Event services (set to run/start automatically). It does 

not install System Galaxy or Badging software. 



Figure 13: Galaxy Specify Workstation Configuration screen 

Page 25 of 29

7. Select SQL Server: click the [choose an available SQL instance] button. A dialog box opens that 

lists the computers and instances of SQL Server. 

WARNING: IF UPGRADING and connecting to SQL Server 2005 Express: you must pick your 

Database Server Instance. The (local) connection from the previous MSDE install will not work with 

SQL Server 2005 Express. 

8. Highlight the desired SQL Server and click [continue]. 

Figure 14: Select SQL Server screens 

Do not use “local” if you are 

connecting to 

SQL Server 2005 Express 

9. Click [yes] to confirm your choice. 

10. The server\instance name is populated in the ‘Selected Server’ field. 

11. Click NEXT. 

12. Ready to Install Application: click NEXT to start the install. The progress bar will display. 

13. Click FINISH when the installation is successful. 

NOTE: the ODBC data sources are created during this part of the GalSuite install provided you 

properly installed GalSuite Part 2 and your Database Server\instance is online. 

Page 26 of 29

5.0 Tips and Techniques: 

What are the new Database Logins for SG 8.1: 

GalSuite Part 2: the New Install of SQL Server 2005 Express also creates the database logins: 


• gcs_client = SysGal.5560 (notice the dot between SysGal and 5560) 


In the case of a site upgrade, the databases will have the old logins to begin with. You must add 

the new users/logins. The ‘CreateLoginsAndUsersSQL2005.sql’ script (located on the GalSuite CD in 

the Components\Database\SQL Server\SQL2005\Scripts folder) creates the logins on the SysGal and 

SysGalArc. MAKE SURE that if you manually attach the databases to use the standard SysGal and 

SysGalArc for the database names. If the customer can’t use the standard name for some reason, the 

scripts must be edited to use the name chosen. 

Run the create login script before running the database upgrade. Reference Section 4.3. 

How to open the SQL Result files: 

Use Windows file explorer to browse to the c:\Program Files\System Galaxy\DBscripts directory, and 

Right-click the file name and choose to ‘open with’ Notepad. 

Optionally, you can open Notepad by clicking the windows [Start] button and select the Run option. Type 

“notepad” into the command line. Notepad should open blank. You can use the File menu option to 

Open/Browse to the c:\Program Files\System Galaxy\DBscripts directory and select the desired 

filename. 

Page 27 of 29

How to setup 2005 Express Server if installed manually (i.e. not by GalSuite): 

If you previously installed 2005 Express Server and did not use the GalSuite install to do it, you need to 

verify/configure certain parameters before you can remotely connect to the SQL Server from a 

Communication Server or Client Workstation. 

From the Start menu, choose Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server 

Configuration Manager. 

In the Configuration Manager, the object tree shows 3 entities in the left pane: 

SQL Server 2005 Services 

SQL Server 2005 Network Configuration 

SQL Native Client Configuration 

Under SQL Native Client Configuration select Client Protocols: 

In the right pane, right-click on TCP/IP and select “Enabled” from the shortcut menu. 

Under SQL Server 2005 Network Configuration select Protocols for GCSSQLEXPRESS: 

In the right pane, right-click on TCP/IP and select “Enabled” from the shortcut menu. 

Select SQL Server 2005 Services: 

In the right pane, right-click on SQL Server Browser and select Properties: 

• select the Service tab in the Properties window 

• set the Start Mode to “Automatic” and click [Apply] then [OK], 

• right-click the SQL Server Browser again and select “Start” to start it. 

In the right pane, right-click on SQL Server (GCSSQLEXPRESS) and select “Restart” to restart it. 

(this service should also have the Start Mode set to Automatic. 

Set the computer Firewall Exceptions to allow the “sqlservr.exe” and “sqlbrowser.exe” applications 

Page 28 of 29

How to manually configure the PC Firewall for Galaxy computers: 

From the Windows [Start] menu, pick Settings > Control Panel 

Double-click the Firewall Icon in the list 

In the Firewall window, click the Exceptions tab (the “sqlservr.exe” and “sqlbrowser.exe” must be 

added to the list and the check box checked). 

Click the [Add Program…] button to add the program. Browse to the installed location – whatever 

location you chose when you did the install to select the program. Click OK to add. 

Example: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe 

Example: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe 

Click the [Add Port] button to add ports manually – use the table below to add the appropriate ports. 

Type the port number in the Name field and type the port number in the Port Number field. And click 

OK to add the port. 

Table of System Galaxy PC Firewall exceptions 

TABLE 7: PC Firewall settings for System Galaxy computers 

Allow/Open Who uses it Where to open it 

sqlservr.exe 2005 SQL Express Server On the computer running the 2005 Express Server if 

other computers need to make ODBC connections 

sqlbrowser.exe 2005 SQL Server Browser On the computer running the 2005 Express Server if 

other computers need to make ODBC connections 

3001 GCS Event Service On any computer running the GCS Event Service 

This port is always required on any PC that connects to Galaxy hardware controllers. 

4000 GCS Comm Service On any computer running GCS Comm Service 

4001 GCS DBWriter Service On the computer running the GCS DBWriter Service 

4002 GCS Gateway Service On the computer running the GCS Gateway Service 

4003 GCS Event Service On any computer running the GCS Event Service 

4004 GCS Alarm Panel Service On the computer running the GCS Alarm Panel Service 

5010 GCS Gateway Service On the computer running the GCS Gateway Service 

The following exceptions are use for Genesis Time and Attendance on Linked SQL Servers 

TCP 135 MSDTC Service On both the Genesis and Galaxy Database Servers 

6000 thru 6050 MSDTC Service On both the Genesis and Galaxy Database Servers 

TIP: A “.reg” file is included on the GalSuite CD that opens the Time & Attendance ports if a linked 

servers are used. It must be run on both servers. 

BE AWARE that the .reg file will configure the DTC security settings, so you may want the IT personnel 

to approve running this or allow them to manually incorporate the DTC configuration. 

ALSO NOTE that the DTC authentication setting must match on both servers. IF running on 

Windows 2000, the authentication setting must be set to NONE. 

Page 29 of 29

System Galaxy Installation Instructions: - Galaxy Control Systems

Create successful ePaper yourself

Delete template?

Save as template?