Sy st em Inst a lla t ion Pro ce du re | Cha pte r 2-4

E: Installing Software

Installation of System Galaxy Software is covered in the Software Installation Guide found on the System Galaxy Software CD. That document matches the Installation Program for your specific version of System Galaxy Chapter 4 of this manual includes an installation process overview and general instructions. The SG Software Installation Program typically runs in 3 parts: the Installer chooses which options to execute, depending on which server/client is being set up. Chapter 4 discusses how these options are chosen. Part 1: installs the appropriate SQL Database Engine /Native SQL ODBC driver Part 2: installs the Badging software and components Part 3: installs the System Galaxy Access Control software
All 3 parts must be run in order. The Native SQL driver must be installed on every computer.
The same Installation CD will be used for all installations: on every SG PC/Server (i.e. Database Server, Main SG-CommServer, Client Workstation) any type of installation being performed (i.e. Networked Server/Database or Standalone)
Install/Upgrade HELP: Galaxy Install CD #1 provides help instructions that guide the install process. Internet Explorer v7 browser is needed, internet connection is not needed to see the instructions. IMPORTANT| Installer should review the Software Setup Procedure found in Chapter 3. (Steps 1
and 2 specifically instruct/guide installer in identifying the type of system planned as well as where to expect components to be installed by the software installation program.) Installer will take into consideration the type of system and which PC/Server is being setup.
F: Registering the System and Workstation
Product Registration is covered in Chapter 5. Customer has a 14 day grace period to register software, after that the functions of the software and ability to use the system software is affected. Every workstation and the SG Communication Server must be registered.

G: Adding a Loop

Adding the first loop is covered in Chapter 5. The instructions guide user through setting up hardware using the Loop Wizard.

H: Connecting to a Loop

Connecting to loops is covered in Chapter 5. SG-8 connects to loops automatically through background services. Also see Chapter 11 of this manual for additional info on GCS Services.
Sy st em Inst a lla t ion Pro ce du re | Cha pte r 2-5

I: Load Flash

Loading Flash is covered in Chapter 5. See the appropriate (600 or 508i) Hardware Manual for important information.

J: Burn Flash

It is necessary to burn flash into memory. This is covered in Chapter 5.

K: Controller Reset

It may be recommended to force a cold reset from the Loop Diagnostics screen. See Chapter 5.

L: Loading Data

This load session sends the loop programming done in (step G) to the controllers. See Chapter 5.

Setup Templates are for recording site configuration. Templates help the installer know what to collect organize the setup information when its collected and make it easy to do the actual programming configuration. Additional copies of the Setup Templates are located in the Appendix for larger sites. Feel free to photocopy each/any template you find particularly useful. Once the tasks in this chapter are completed, the installer will have completed Step D in the main System Installation Procedure found in Chapter 2 and be ready to proceed with software installation.
Pre pa ri ng f o r S oft wa re In st a ll a t ion | Cha pt e r 3 -2

Software Setup Procedure

The following tasks are designed to be completed before running the software installation program so that the installation and programming (configuration) of the software will be a smooth as possible. IMPORTANT | ALWAYS BACK UP EXISTING DATABASE, DATABASE LOG, and BADGING AND GRAPHIC FILES BEFORE RUNNING THE SOFTWARE INSTALLATION PROGRAM for an upgrade site. See Step-3 for details.
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Also See

Objectives

Identify the Type of System (networked, standalone, etc) Identify the Database Conversion/Backup Needs Identify the location of Shared Files Identify need for Floor Plan Graphics (Alarm Graphic Monitoring) Identify Operators and Privileges Identify names & locations of Loops & Hardware Identify Department Names (if used) Identify Customer Name(s) (SG-WebModule only) Identify Area Names & Locations (if used) Identify Names & Setups of Schedules & Holidays (recommended) Identify Access Groups and Privileges (recommended) Identify Access Profiles and Settings (if used) Identify I/O Groups Names & Configuration (if used) Sample System Designs at end of this chapter.
Pre pa ri ng f o r S oft wa re In st a ll a t ion | Cha pt e r 3-3
Description of Software Setup Tasks
Step 1: Determine the Type of System and PC Installations
Objective: Determine what kind of system and installations the jobsite will require, and what upgrades are needed. Chapter 1 contains the PC Requirements.

Alarm inputs, I/O Groups

armed or on

unarmed/disarmed

Outputs
Schedules can drive relays, locks, lighting, heating, cooling, alarms, inputs, outputs, sensors, bells, etc.
Pre pa ri ng f o r S oft wa re In st a ll a t ion | Cha pt e r 3-15

Schedules

Schedule Name M-F, 8am-5pm, no holiday activity M-Sun, 5pm-8am Normally Active Hours M-F 8AM-5PM M-Sun, 5pm-8am Effect of Holiday Hours, if any INACTIVE ALL DAY Not affected by holidays

Holidays/Special Days

Date JULY 4th, 2001 Holiday Type Type 1 (Full Day) Descriptive Name INDEPENDENCE DAY
Pre pa ri ng f o r S oft wa re In st a ll a t ion | Cha pt e r 3 -16
Step 11: Identify Access Groups and Privileges
Objective: Determine the names of the Access Groups and what privileges each group has. It is recommended to use descriptive loop/controller/port names to ease programming of this and other functions. Schedules must be setup in order to link them in the Access Group Programming Screen. Access Groups must be set up in order to use them in the Card Programming Screen. Purpose | An Access Group is a function that manages a cardholders access privileges to doors (or elevator floors) based on schedules. An Access Group is assigned to one Loop and any combination of doors/ports and schedules. Doors/ports can have the same or different schedules. If a cardholder needs access to more than one Loop, the user needs to make a separate Access Group for each Loop. The system allows up to four (4) Access Groups to each Loop on a card. If a cardholder needs access to more than 4 Access Groups, the user can add multiple cards or use an Access Profile. (See the following step in this chapter for a description of Access Profiles. Refer to the Card Programming section for more information on setting up the cards.) TERM | Access Privileges are the rules of when and where access is granted. These privileges are housed in Access Groups. Assigning the Loop and Doors controls WHERE the access is granted. Assigning the schedule controls WHEN access is granted. Access Groups are created in the Access Group Programming Screen. Access Groups are assigned to an access card in the Loop Privileges tab of the Cardholder Programming Screen. Access Cards are not active until they are given valid access privileges by assigning a Loop and an Access Group (or Access Profile) in the Cardholder Programming Screen. The Access Group name should be descriptive to indicate how the access privileges apply. For example, Office Day Shift 8-5 indicates that a Day Shift employee has access to the office doors from 8am to 5pm. Any time outside those hours, the card will not work. NOTE | System Galaxy v8 allows up to 1500 Access Groups per Loop (One loop per group). There are two built in Access Groups. They are NO ACCESS and UNLIMITED ACCESS. The UNLIMITED ACCESS group gives a card access to all doors/readers at all times. The remaining 1498 groups are user-defined groups. IMPORTANT | The UNLIMITED ACCESS group supersedes all other privileges. This group is convenient for making a Test Card, which is used to walk test the system or for acceptance testing during hand-off to the customer. If you do not need 4 access groups on a card, then leave the rest of the fields unset (i.e. no access). See the section on Cardholders Loop Privileges for more details. CAUTION | Access Group names may be shared across loops, but not the access privileges. Those rules must be setup specifically per loop. Sharing Access Group names across loops should be carefully considered, since unsharing them can impact existing programming/system performance.

Start the Galaxy Install Program from My Computer
1. 2. 3. 4. 5. Place the Galaxy Install CD (disc-1) in the CD drive. Click on the Desktop icon for My Computer. Click the CD drive icon. Double-click on the file default.hta. The Installation Startup screen will open.
Start Galaxy Install Program from Windows Explorer
1. 2. 3. 4. 5. 6. 7. Place the Galaxy Install CD (disc-1) in the CD drive. Right-click on the Start button in the taskbar at the bottom of the screen. Click on the Explore menu option. Once Explorer opens, scroll down until the directory tree (left pane) shows the CD drive. Click the CD drive icon. Double click on the file default.hta. The Installation Startup screen will opens
Location of Database and Script files
Database files are found on disc-1 in the Data Files directory. The disk provides blank database for SQL 2005 database engine and older 2000 engines Database files are found in the appropriate DataFiles directory on disc-1 CD:\Components\Database\SQL Server\DataFiles\SQL2005 (for 2005 servers) CD:\Components\Database\SQL Server\DataFiles\MSDE_SQL2000 (for 2000 servers) Database scripts are found in the Scripts directory on disc-1 D:\Components\Database\SQL Server\Scripts
S oft wa re In st a l lat ion In st ruct i on s | Cha pt e r 4-5
Standard Installation Process
The system components (i.e. prerequisites, database, services and software) are installed based on the choices made during the installation process. The Installer must consider the type of system (network/standalone) and which Server or Workstation is being setup, in order to make these choices correctly. HELP / TIP: The Installation Instructions on the CD(1) provide Quick Step tables and detailed steps that guide installer through the choices for a database server, communication server, or workstation. Also a graphic Installation Flow Diagram is on the CD(1).
The Standard Installation occurs in 3 parts: These are run on each Server or Workstation in the system. See table below for planning:
Server/Workstation Install Models
Type of Server or Workstation
Run Parts 1, 2, and 3 of installation on this PC/Server: Standalone Server *Part-2 choose to install new/full SQL Database Server *Part-3 choose to install Full Software & Services Database Server Run Part 1 and Part 2 only (typical) *Part-2 choose to install new/full SQL Database Server Note: you can add software on DB server if purchased. Run Parts 1, 2, and 3 of installation on this PC/Server: Communication Server (main LCS)
*Part-2 choose to install the SQL Client Components only *Part-3 choose to install Full Software & Services Run Parts 1, 2, and 3 of installation on this PC
Client Workstation (as purchased)
*Part-2 choose to install the SQL Client Components only *Part-3 choose to install Workstation Software only Run Parts 1, 2, and 3 of installation on this PC/Server: *Part-2 choose to install the SQL Client Components only

The SQL Server 2005 Express Engine will also start automatically but there are no icons displayed. To confirm the MSSQL service is running, you can open the GCS Service Manager (Start>Programs>System Galaxy>Utilities>GCS Service Manager). Optionally you can open the computer Control Panel>Administrative Tools>Services to verify.
A green bulb indicates the service is running; red indicates the service is stopped.
First Tim e Start Up | Chapter 5-5
Verifying Services are running on Windows Vista
After the Main Communication Server is installed, the core GCS Services should automatically start/run, but are not interactive with desktop. This means they do not display on the System Tray. Also, the MSSQL Service should be running on the database server. The database may, or may not reside on the Communication Server, depending on how you installed the system. In either case, it is mandatory that the SysGal Database and the GCS Services be running, online (network), and able to connect, in order to register the System and each System Galaxy Workstation. 1. Provide the IP Address of the target computer* and click the [Fill List] button to populate the list of services (* check the [Local Computer] option to see services on the same machine you are on. 2. Select the Service name on the list and click the [Connect to Service] button* to connect to it. (* the Connect button changes states allowing user to disconnect from a service and to another service as needed). The list of Loops (508i) is available in the Comm Service; the list of 600-series panels is shown in the Event Service. 3. Additional tabbed-views are available for the selected service: a. incoming & outgoing Service Connections b. Connection Status Messages
First Tim e Start Up | Chapter 5-6
Starting System Galaxy Software
To start System Galaxy 8, double-click the System Galaxy icon (located on the

PCs desktop)

When SG starts up, it should automatically connect to the database, and read the IP Address and listening ports of the Client Gateway Service. Once this is done the software will make a connection to the Client Gateway Service, then use the port 5010 to retrieve the system ID. IF the software cannot connect to the database, the ODBC Settings Dialog will display allowing the installer to set up the DSN connection to the database. Once the ODBC settings are configured completed the software will retrieve the System ID from the Client Gateway.

Mandatory Field checkbox

Select List checkbox
Allow Employee ID editing check box Print Badge Always Shows Setup - check Move to Current Record after Edit check box Clear all fields when adding new records Checkbox Alert when similar name added Check box Assign Employee ID Range: text boxes
Orientat ion t o Sy stem Galaxy | Chapt er 6-16
Cardholder Path Options Tab
Setting Specify location of badging files Field Type text field Description This field is the location where System Galaxy will look to find the badging photo files that are assigned to users. To change this location, click the Browse button. All PCs in the system must point to the same location, so that all the badging photos can be viewed from any PC. See the chapter "Badging" for more information. This field is the location where System Galaxy will look to find the fingerprint files that are assigned to users. To change this location, click the Browse button. All PCs in the system must point to the same location, so that all the badging photos can be viewed from any PC. See the chapter "Badging" for more information.
Specify locations of Sagem finger files

Text field

Event Log Output Tab
Setting Send event data to text file Specify path and filename of event log file Status Group to send Field Type check box text field Description When checked, System Galaxy will begin sending a copy of every selected event to an ever-growing text file. This field specifies the location and name of the text file that will receive a copy of all the selected event messages. Click the Browse button (three dots) to select a location. Using this field, you can limit the events being sent to the text file based on the devices in a status group. See the chapter "Monitoring Events" for more information on device status. Click this button to arrange the order in which event data is sent to the text file. Place a check to include a data field in the text file. To rearrange the order of the data, highlight a data field and use the arrows to move the field up or down in the list. These options dictate which events are sent to the text file. "Alarm Events" limits the event messages to acknowledgeable alarms. "All Events" includes all events. "Selected Events Only" limits the event messages to those selected by clicking the "Select Events" button. "Selected Alarm Events" limits the event messages to those alarms selected by clicking the "Select Events" button. System Galaxy will begin sending a copy of every selected event to the selected output destination (Com Port or TCP/IP destination), which may be a printer or some other recording device. Using this field, you can limit the events being sent to the output destination based on the devices in a status group. See the chapter "Monitoring Events" for more information on device status.

Orientat ion t o Sy stem Galaxy | Chapt er 6-23

Timer Options

Timer Retry this option sets the time between retries when attempting to connect to a controller. If the Retry count is zero (see option below), this setting has no effect. Retry Count this option forces the Loader to reattempt a failed connection multiple times (as determined by the setting in the field). The time between retries is determined by the Timer Retry setting (see option above). Stop 500 load if NACK occurs - (checked by default) this option interrupts and aborts a Data load when the controller selected to return an ACK (acknowledgement) signal fails to do so. This option can be disengaged if it seems that the selected controller is malfunctioning and the rest of the system is believed to be loading correctly. Clicking the Datasource button will, by default, show Sysgal (or the current System Galaxy service name) as the datasource. If you want to use a different System Galaxy database, you can select a different datasource.

Datasource

Load Data Defaults
This list of check-boxes mirrors those listed on the Load Data tab. Checking or Unchecking these boxes sets the defaults for those check-boxes for the next time the GCS Loader is opened.
The Communication Server/Service
Prior versions of System Galaxy used Zlink Server to manage messages to and from the loops. SG-8 uses background services to connect the Communication Server to controllers. See Chapter 11 for information on how Services work. SG-7.02 (or higher): the software supports multiple Communication Servers. Prior versions of SG7 did not support multiple communication servers. See Chapter 1 for a diagram of the distribution of services for multiple Communication Servers. Also Chapter 4 contains diagrams, instructions and tables that describe the implementation of multiple Communication Servers. See Chapter 3 for system design and planning; including (Putting it all Together) for diagrams of sample systems. See Chapter 6 for orientation to the System Galaxy menus, toolbars and windows. See Chapter 11 for detailed information on GCS Services; how the function and how to manage them.
Also see Chapter 11 - Description of Services section for the About GCS Communication Service concerning multiple communication services. See Chapter 11 for instructions on using the GCS Service Manager Utility.
Orientat ion t o Sy stem Galaxy | Chapt er 6-24

7 Configuring the System

Chapter 7 Contents
Overview Quick Steps for System Configuration chapter overview fast-start mini-procedures for configuring the system holidays/special days time schedules access groups access profiles i/o groups areas departments Details on System Configuration detailed information on configuring the system holidays/special days time schedules access groups access profiles i/o groups areas departments

Configuring t he Sy stem | Chapt er 7-38

Create I/O group names

I/O Groups are used to link inputs and outputs together. Some of the uses of I/O groups include: Trigger outputs (relays) based on events in the system. Control groups of inputs by PC-issued commands, alarm cards, or PINs. Link doors to create Door Groups Link door alarms to outputs. Lock and Unlock doors based on alarms

To Communication Server

EXAMPLE
In the above diagram, Input 1 is linked to I/O Group A. When Input 1 generates an event, the event message is sent around the loop. If the Communications Server is connected, it also receives the event message. If it is not connected, the event message is buffered for later download. Any outputs that are also linked to I/O Group A (such as Output 2) will react to the message based on their programming. Any outputs not linked to I/O Group A (such as Output 1) will ignore the message.
When you are setting up additional loops, you can choose to share I/O groups between those loops. This process is explained in the Sharing Options section of Managing Loops. USE CAUTION WHEN SHARING BECAUSE ONLY THE NAME IS SHARED AND UNSHARING CAN IMPACT SYSTEM PERFORMANCE. Before Inputs and Outputs can be linked to an I/O group, you must create the name of the I/O groups you will be using. Those I/O group names will appear in a droplist where ever you can assign an input, output, door alarm, or other function to an I/O group.
C onf i gu rin g t he S y st em | Cha pt e r 7-39
Adding/Editing I/O Group names - Detailed Instructions
Adding or editing an I/O group name begins by opening the I/O Groups window. This window can be opened by following the menu selections Configure > Hardware > I/O Groups. Once the I/O Groups window is open, you can choose to add a new I/O Group or edit an existing I/O Group.

Adding an I/O Group Name

To add an I/O Group, begin by choosing the loop to which your new I/O Group will be added. Click on the loop name in the droplist by the label Loop. Click the Add New button (found in the upper right corner of the window). When Add New is clicked, the Name and Notes fields become enabled. In the Name field, type a descriptive name for the new I/O Group (max. length of 65 characters). In the optional Notes field, type any comments or information regarding the new I/O Group (max. length of 255 characters). Use the ARM Schedule droplist to select the schedule during which all the inputs associated with this I/O Group will be armed. (Note: In System Galaxy versions prior to version 6, inputs were assigned individual arm schedules. Since System Galaxy version 6, all inputs in an I/O Group are armed with the same schedule, making the system more consistent with other alarm-type systems.) Click the Apply button to save the new I/O Group. At this point user has created the I/O Group (Name). The linking of Inputs and Outputs for the I/O Group that has just been created will take place in the individual Inputs/Outputs properties screens.

Pro g ramm ing Lo ops | C ha pt e r 8 -7
The Card/Reader Options Tab
The Card/Reader Options tab has the following sections: ABA Options, Reader Disable Options, and the Crisis Mode I/O Groups. These sections are explained below.

ABA Options

If ABA format cards are being used, you may need to set up certain card options in order for the system to properly recognize the cards and accurately process the data. ABA format card readers include most magnetic stripe and barcode readers. The fields in the ABA section include Start and Stop digits, and Enable long codes. Start and Stop Digits The code on an ABA format card may contain up to 60 digits, while an access code may only be several digits long. The rest of the digits on the card are therefore not actually part of the access code, and should not be read by the system. If there are more digits on the card than just those that make up the access code, the software must be told what set of digits are actually part of the access code. This information is set using start and stop positions. Once the start and stop position of the digits in the access code are set in the software, then the system will only read the digits from the start to the stop positions (including the start and stop digits). By default, the start digit is set at 1 (one) and the stop digit is set at 60 (the last position on standard magnetic stripe cards). If the default settings are used, the system will use the first non-zero digit as the start of the code, and the last digit as the end. If, for example, the defaults are changed to make the start digit 5 and the stop digit 17, the system will begin reading the access code at digit 5, and stop reading the access code after digit 17. To change the default start and stop digits, enter the position of the start digit in the Start Digit field, and the position of the stop digit in the Stop Digit field. Enable Long Codes Enabling long codes allows System Galaxy to read more than 14 digits of a single access code. If the Enable long codes option is not selected (unchecked), the system will not process more than fourteen (14) digits of a single access code - regardless of where the access code starts on the card. This means that if the start and stop digits are left at the default 1 and 60, and the first digit is a nonzero number, the system will only read digits 1-14. If the start and stop digits are changed to 7 and 43, the system will only read digits 721. If the Enable long codes option is selected (checked), the system will convert any access code longer than fourteen digits into a shorter, encrypted code that is usable. Due to the encryption, however, the converted code will not look the same as what is actually encoded on the card.

Working Online from a Client Workstation
Working online from a Client varies from working online with a Communications Server in that a Client depends on two connections to be online: the connection between the loop hardware and the Communications Server, and the connection between the Communications Server and the Client. The GCS Communication Service, GCS DBWriter Service, and GCS ClientGW Service MUST be running and connected to loops in order for a Client Workstation to connect to the loops. Establishing a connection from a Client As stated above, the GCS Services must be running and connected to the loops for the Client Workstation to connect / monitor / load data. Double-click the SG-8 Software icon and log in to System Galaxy to start. o Full Event Monitoring: The Event Window will open and event/alarm messages will be sent from the Communications Server (via the GCS ClientGW Service) to this client PC. Use this option for monitoring stations. System Programming Only: Events and alarms are not sent to this client PC. Use this option for dedicated badging or card-management stations that do not participate in monitoring.
Click the Hide button to hide the Communications Control window. It can be reopened from the Configure Menu using the Communications Controls selection From the main menu-bar, select Configure > Options > Client Gateway In the Connection Settings dialog enter the external IP Address of the PC where the GCS Client GW Service runs. To find out what the IP Address should be, user can run a ipconfig command at the DOS Prompt of the PC that hosts the GCS Client GW Service. The IP Port should be set to 4002 Click OK to save When you work online, any changes that are made to the system through the software are loaded to the hardware immediately when you click [Apply] to save. Exceptions to this immediate load are changes to I/O devices (which may require recalibration before they take effect), some scheduling changes (which take effect at the top of the next minute), new controllers, and changes to port definitions. New controllers and port definitions must be loaded before they will take effect.
Pro g ramm ing Lo ops | Chapt e r 8 -17
Working Offline from a Loop Client
Working Offline means that there is either no active connection between the Client and Communications Server, or between the Communications Server and the Primary Controller of the loop. When you work offline on a Client, the changes you make are still captured in the database for the loop. However, the changes are not loaded to the loop because there is no active connection to the loop. For example, new cards that are created offline will not be active in the controller, and will not be functional until the card information is loaded to the loop. User must manually load offline changes to the loop using the GCS Loader screen/Load Data tab. Follow the instructions in previous sections about starting Services and auto-connecting to the loops. Also see the Chapter on Managing Services.

Department Filters supersede Editing Privileges. If you exclude a department from an operator, then he/she will not be able to see or edit cardholders that are associated with that department. To grant privileges to a department you must move the department into the Included list using the arrow button. CHANGE DEPARTMENT FILTERS: 1. Select the operator name and click the EDIT button. 2. Select the Department Filters tab if the page is not already showing. 3. To grant privilege, select a department in the Excluded list (left pane) click the arrow to move it to the included list (right pane). To deny privilege move the department to Excluded list. 4. Click Apply to save changes NOTE: the department must already be programmed in the system in order to add it to the Included list. If you made your operator before you programmed your departments, you will need to go back and add the departments to the included list as appropriate.
Creat ing the Operators | Chapt er 10-15
Setting Operator Cardholder Options
These filters supersede (further limit) the Editing Privileges granted in the earlier section. This screen has two sections. On the left is a list of every field in the Cardholder Programming screen. On the right is a list of each tabbed subscreen in the Cardholder Programming screen. CHANGE CARDHOLDER OPTIONS: 1. Select the operator name and click the EDIT button. 2. select the Cardholder Options tab if the page is not already showing. 3. set the options in the screen as desired. 4. click Apply to save changes In the Cardholder Field list you can select an individual field and use the checkboxes at the bottom to make that field [view only] or [hide data] in the field from the operator. EXAMPLE: if your operator has full editing privileges, but you want to limit the ability to change the last name, you could set the last name field to view only. Also field hidden (you may use a miscellaneous field for the social security number and use the hide option here to make that data hidden from operators. In the Cardholder Tab list you can select a tabbed subscreen and check the box to allow the tabbed screen to display or uncheck the box to hide the entire tabbed screen from the operator. EXAMPLE: if your operator has full editing privileges, but you want to protect personal information, you could simply turn off (uncheck) the Personal tab.
Creat ing the Operators | Chapt er 10-16

The Diagnostic Commands

The following commands are available in the drop-down list for the Command Selection field:

Activate Crisis Mode

This command activates a Crisis Mode for the selected controllers, as though the mode had been triggered by the Crisis Mode I/O Group. TERM: Crisis Mode is a condition set to be triggered by an Alarm event on a selected I/O Group (the Crisis Mode I/O Group, as set in the Loop Properties).
In Crisis Mode, Access Groups are automatically remapped in reaction to the mode. Note: Crisis Mode can create conflicts with anti-passback measures if the crisis mode settings would force some cardholders to use doors in a way that would generate a passback violation. Check your settings to determine if a conflict exists. In a Crisis Mode, Access Group privileges are altered according to their Crisis Mode settings. They can be set to be upgraded to wider access, or downgraded to lower access. Crisis Mode is a Latching setting that will continue even after the triggering condition has ceased. It must be turned off by a command from the PC, or by resetting the affected controllers.

Clear Logging Buffer

Each controller records and retains the most recent 10,340 events in a buffer inside the controller. By choosing to clear this buffer, all the stored events will be totally deleted. This command is useful if you do not wish to retain the information in the buffers, such as messages generated during the testing of a newly set-up system or messages generated during an extended period of off-line activity. Upon clicking the Execute button, you will receive a warning: If you proceed with this command, YOU WILL DELETE all log event information from the selected controllers memory! You WILL NOT be able to recover the information! Do you wish to proceed? When you receive this warning, click the Yes button to proceed, the No button to Cancel.
Mon it o ring E vent s | Cha pt e r 14-14

Delete All Cards

When a card is added to the System Galaxy database, the cards information is loaded to the loop. Each controller in that loop the stores the cards access information to determine which entry attempts will receive Valid Access, Invalid Access, and Not in Database messages. By choosing to Delete All Cards, the card/access information in the controllers memory will be deleted NOT the cards in the System Galaxy database. This command is useful if you wish to clear out the existing card information before reloading the controller with updated information. Upon clicking the Execute button, you will receive a warning: If you proceed with this command, YOU WILL DELETE all card information from the selected controllers memory! Are you sure you want to delete all cards from the controller(s) memory? When you receive this warning, click the Yes button to proceed, the No button to Cancel.

Integrated Ba dgin g | C h a pt e r 17-28
Setting-up your card printer encoder:
Verify that the software is not currently in Edit Mode, and that the card record which is currently displayed is assigned a badge design. Select Printer Encoder Setup from the Card menu. Verify that the printer with the magnetic encoder is showing in the Printer Name field. If it is not showing, please see the Troubleshooting Printer/Encoder Setup section ( 17-29) for more information. In the Magstripe tab, select "Magstripe Printer Encoder". Click the Setup button. In the Setup for Magstripe Printer Encoder window, click the Importbutton. If you receive the message "Are you sure you want to overwrite the current encoder definition?" you already have an encoder set up for the printer. It is probably a good idea to overwrite the old definition with a known good definition. The Open window will appear, with a list of encoder definition files. Highlight the file which contains the definition for your printer, and click Open. If you do not see any files, you may need to browse to the correct folder. The encoder definition should now be imported. Click OK to save the encoder definition. Click OK to close the window.
Troubleshooting Printer/Encoder Setup
The following chart documents some common printing/encoding errors and their solutions. Problem Message "The page layout will not fit on the currently selected printer. Use this layout anyway?" Solution This means that the printer assigned to the badge design was changed, and the badge design is too large for the new printer. Either change the printer assigned to the badge design back to the original, or change the badge design in GuardDraw. This can occur if the printer with the magnetic encoder is not the one assigned to the badge. You should change the badge design to use the printer with the encoder. Three possible causes: 1. The software is not registered for magnetic encoding. 2. The user whose record is currently being displayed has no badge assigned. 3. The software is in Edit Mode
When setting-up magnetic encoding, the printer which appears in the Printer Name field is not the printer with the magnetic encoder. I am attempting to set up magnetic encoding, but the option is grayed out.
Integrated Ba dgin g | C h a pt e r 17-29

Sy st em Re qui rem ent Gu i de |System Galaxy 8
Galaxy System Recommendations Guide for SG 8.3

Installers Guide

Information in this document is subject to change without notice. Therefore, no claims are made as to the accuracy or completeness of this document. This document is not intended to supersede recommendations or specifications for integrated applications/technologies. This manual can be viewed in comparison or addition to recommendations from 3rd party or integrated applications/technologies. 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. Reproduction, cribbing or adapting any contents of this document, with or without the consent of Galaxy Control Systems, is not deemed as reliable or liable information. System specifications, OS Recommendations, Client and PC recommendations may vary depending on your framework and individual application needs.

third edition Feb. 2009

Copyright 2009

Galaxy Control Systems

All rights reserved
Copyright protection claims include all forms and matters of copyrighted material and information, including but not limited to, material generated from the software programs that are displayed on the screen such as icons, look and feel, etc. Trademarks
Microsoft, Windows, Windows NT, MSDE and SQL Server are registered trademarks of Microsoft Corporation in the U.S. and other countries. DbaMgr2k may or may not be a registered trademark in the U.S. and other countries. Card Exchange, CEInside, are tradema`rks of ExchangeIT Solutions. EPIBuilder is a trademark of ImageWare Systems, Inc. Genesis or GENESISSQL may be a trademark of Time America, Inc. STOPware & PassagePoint are trademarks of STOPware, Inc. and its owners. PELCO is a registered trademark of Pelco. Ademco, RapidEyeTM Multi-Media are trademarks of Honeywell. General Solutions, DVTel, Kalatel, Integral, Loronix, Sagem, ExeedID, Farpointe, HID, BOSCH, and Cypress may be registered trademarks or service marks of their respective companies in the U.S. or other countries. Adobe, Acrobat are registered trademarks of Adobe Systems Inc. Graphics/illustrations are for the sole purpose of edification and are subject to copyright.
3 North Main Street Walkersville MD 21793 800-445-5560

www. galaxysys. com

Sy st em Recomm endat ion s | page 2

Table of Contents

Introduction..... 4
System Galaxy 8.3 General Installation Requirements..5
General PC Hardware Requirements:....6 System Galaxy Hardware S28 Flash and Boards...6
Integrated Applications & 3rd Party Technologies.. 7
Important Genesis Time & Attendance Notes...7 Important Sagem Interface Notes...7 Important Schlage Interface Notes...8 Known Requirements for SQL Server 2005 Express...8
System Galaxy IT Requirements.... 9
System Galaxy Security Notes...9 PC Firewall Exceptions Table...10

SG Client & Workstation Recommendations... 11
Minimum Recommendations for a Stand-Alone Solution..12 Minimum Recommendations for Distributed Solutions...13
Database Server Minimum Recommendations - Distributed Solution..13 Communication Server Minimum Recommendations - Distributed Solution.14 Client Workstation Minimum Recommendations - Distributed Solution..15
Sy st em Recomm endat ion s | page 3

Introduction

This document provides base recommendations and requirements for System Galaxy (SG). The information herein addresses operating system considerations for running System Galaxy (SG). It includes Installation Requirements, Security Notes, PC Com Port and Firewall Requirements, and TCP/IP Client considerations for System Galaxy. The later sections cover base recommendations for each System Galaxy computer where used in either a Standalone or Networked system. NOTICE: This document may include recommendations for integrated applications or 3rd party or technologies based on application or system needs of System Galaxy. Galaxy makes every effort to include pertinent specifications in this document and in documents written for the installation and setup of integrated applications for typical expectations. There may be scenarios, systems, or environments that require different or additional specifications than the ones noted here-in. Please consult Technical Support if you have an unusual or exceptional situation.
IMPORTANT: System specifications, OS Recommendations/Compatibilities, Client/PC specifications may vary depending on your individual system or application needs. This document does not necessarily supersede any recommendations or specifications for integrated applications/technologies. This manual can be viewed in comparison with, or addition to, recommendations from 3rd party or integrated applications/technologies.
IMPORTANT: If you planning a large-scale system or are installing an integrated application or encounter a unique site situation, please be careful to read all associated materials to confirm you specific needs. Contact Galaxy Control Systems with any questions you cannot resolve.
Sy st em Recomm endat ion s | page 4
System Galaxy 8.3 General Installation Requirements
System Galaxy install, System Galaxy client software, GCS Client Services, and SG Web Module are Microsoft.NET Framework-based. System Galaxy requires administrative rights on the computer to properly install the system. System Galaxy operators need power-user rights to operate the system. System Galaxy 8.3 software & GCS Services are compatible with the following operating systems

Windows Vista Ultimate & Business | Windows XP Pro | Windows 2000 Pro Windows Server 2000/2003 IMPORTANT: Some integrated applications or 3rd party technologies are not supported or recommended on a server platform. See the section on Integrated Applications. SG 8.3 is designed to use SQL 2005 Native Client (ODBC driver) for database connections. The Microsoft Native Client components are included in the GalSuite Install Part 2. The SQL Client components must be installed on every computer running System Galaxy Software or GCS Services. SG 8.3 comes with MS SQL Server 2005 Express Database Software. This includes Management Studio Express. NOTE: System Galaxy 8 is also compatible with existing SQL Server 2000/2005 Database Software. SG 8 offers Product Levels for System Registration. Customer product level is labeled on the Software Install CD and available through Galaxy Customer Service department. NOTE: Core features are available by default on all product levels. Certain features or integrated applications are available based on purchased product levels and options. NOTE: Customers upgrading from SG v6 may need to consider hardware upgrades. The 500 non-i-series hardware must be replaced with 600-series or 500i-series hardware. System Galaxy database size is the inherent size of the database engine you choose. SQL Server 2005 Express has a 4GB max. size limit (imposed by Microsoft). If you are using SQL Server 2000/2005, please consult the Microsoft specifications that came with your software.
Sy st em Recomm endat ion s | page 5
General PC Hardware Requirements:
See other sections for Operating System and Service Pack Requirements. IBM Compatible PC with Intel Pentium IV processor (2.8 GHz or higher) or better 2 GB of RAM Standard graphics card capable of 24-bit color at 1024x768 resolution. 17 Monitor (or larger) Standard CD ROM Drive (required for installing system) Standard Parallel Port (printing) COM (RS-232 serial) Ports as needed:
1 COM port for HyperTerminal connection (to configure controllers) 1 COM port per 508i Loop* (if using direct connect; 508i also supports TCP/IP connection) 1 COM port for RS-232 Galaxy enrollment reader (dedicated port, if used) 1 COM port for a serial-port UPS (if using a serial-port UPS)
Serial-Port UPS (recommended) Windows compatible printer 1 NIC card Microsoft Internet Explorer v7 or later
System Galaxy Hardware S28 Flash and Boards
Flash code must be confirmed. A new install should verify the flash version on the boards matches the software version. An upgrade or repair situation requires the boards to be flashed to the correct version of flash. IF you are running SG 8.3 you should have the following flash: 600-series Controller S28 Flash file v 2.30e

CPU board: 2.30e DPI board (Reader): 171d DIO board (Input/Output): 161b DSI board (Serial RS485): 2.31f Output Relay board: no flash on board, Relay board used for Elevator or Output Relay control.
508i-series Controller S28 Flash file v8.20c Subordinate boards and peripheral modules do not contain flash code.
IMPORTANT: See the 600-series Hardware Installation Manual, 508i-series Installation Addendum, and 500-series Hardware Manual for specifications on installing and operating System Galaxy hardware.
Sy st em Recomm endat ion s | page 6
Integrated Applications & 3rd Party Technologies
This section covers the high-level requirements for integrated applications and interfacing technologies. Please compare these recommendations with the requirements published by the manufacturer of the 3rd party applications / technologies where appropriate. Also see the specific requirements printed in the related System Galaxy Interface Guide. Since operating environments can vary from customer to customer, it is important to remember that requirements may vary depending on the applications needs in a given environment. Technical support may be based on these recommendations. These recommendations do not supersede any requirements imposed by maker for applications or technologies not manufactured by Galaxy Control Systems.
Important Genesis Time & Attendance Notes
Genesis SQL (GENSQL) is compatible with MS SQL Server 2000, but not MSDE. If using a shared server connection, System Galaxy 8.1 (or later) is compatible with SQL Server 2000. However, you must manually copy and attach the SG databases and manually create the SG database logins. If using a linked server connection, System Galaxy 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 integrated application.
Important Sagem Interface Notes
Sagem MSO Optical Fingerprint Enrollment devices and drivers may NOT be compatible with Windows Server operating systems. Please plan on using a compatible workstation operating system for the computer running the Sagem Enrollment Interface. See the Galaxy Interface Guide for Sagem MA520 or Sagem MA110 for requirements specific to Sagem Enrollment application integration.
Important Schlage Interface Notes
Schlage Wyreless interface for the PIM-485 is mainly a hardware interface. Some limitations are inherent to the nature of wireless technology and need to be considered.
Microsoft Java msjavx86.exe must be installed on your PC in order to operate the CDT software. This is found on the Galaxy Install CD (Disc 2) in the Schlage folder at the root of the CD. Microsoft IE 6.0 browser is needed to run the CDT software (MS-IE 8 may not work). The Internet Explorer configuration interactive option for Sun Java must be unchecked and the option for Microsoft Java must be checked. The CDT v1.7 (Configuration Demo Tool) from Schlage in order to program the WAPM devices/doors. This installs on the C-drive in a typical directory path c > Program Files > WirelessDemoTool > WyrelessDemo.html. This tool is found on the Galaxy Install CD (Disc 2) in the Schlage folder at the root of the CD.

See the See Galaxy Interface Guide for Schlage PIM-ODT-485-RS for requirements specific to the integration to System Galaxy. Also see Schlage/IR documentation for product information.
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. Operating Systems: Galaxy Control Systems suggests meeting the recommended requirements for each computer in the type of system (standalone or distributed) that you are installing. SQL Server 2005 Express is known to be compatible with the following operating systems. However, you should consult the last section in this manual to determine which operating system fits your system needs. Microsoft Windows 2000 with Service Pack 4 Microsoft Windows XP with Service Pack 2 Microsoft Windows Vista (Ultimate or Business) Service Pack 1 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) MDAC 2.8 SP1 for Windows 2000 (GalSuite CD installs this automatically during Part 1)) the presence of Internet Explorer 6 with Service Pack 1 (this is not installed by GalSuite Install) See Microsoft SQL Server product documentation requirements specific to your product.
Sy st em Recomm endat ion s | page 8
System Galaxy IT Requirements
This section covers the IT and Security information concerning System Galaxy.
System Galaxy Security Notes
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 full chart in Section 5.0. The GalSuite Install program may automatically open 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: you must manually open the required ports for any 3rd party firewall applications or port blocking applications. REMEMBER: port 3001 is used 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 Ports 135 and 6000 to 6050 are designated for DTC service on both the SG database server and the Time & Attendance database server. Note that the DTC authentication settings must match on both servers. If you are running Windows 2000, then both servers will have to use NONE as the authentication setting. TIP: A.reg file is included on the GalSuite CD that opens the T&A ports on both database servers if a linked server is used. 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 needed DTC configuration. The.reg file can be viewed in notepad.
Sy st em Recomm endat ion s | page 9
PC Firewall Exceptions Table
The table below lists default ports and program exceptions that System Galaxy requires to operate. If these ports are not available on your customers network, then you will need to work with their IT Professional to configure the ports.
Allow/Open sqlservr.exe sqlbrowser.exe 5010
Who uses it 2005 SQL Express Server 2005 SQL Server Browser GCS Event Service GCS Comm Service GCS DBWriter Service GCS Gateway Service GCS Event Service GCS Alarm Panel Service GCS Gateway Service
Where to open it On the computer running the 2005 Express Server if other computers need to make ODBC connections On the computer running the 2005 Express Server if other computers need to make ODBC connections On any computer running the GCS Event Service On any computer running GCS Comm Service On the computer running the GCS DBWriter Service On the computer running the GCS Gateway Service On any computer running the GCS Event Service On the computer running the GCS Alarm Panel Service On the computer running the GCS Gateway Service
The following exceptions are used for Genesis Time and Attendance on Linked SQL Servers TCP thru 6050 MSDTC Service MSDTC Service On both the Genesis and Galaxy Database Servers 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 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.

Sy st em Recomm endat ion s | page 10
SG Client & Workstation Recommendations
System Galaxy supports a wide variety of configurations that range from small professional to corporate or enterprise. System Galaxy is also designed to meet the future needs for system expansion. System Galaxy is designed to support a networked architecture. The 600-series and 500i-series hardware uses TCP/IP connectivity. The System Galaxy software and databases can be installed on a single computer (standalone) for very small systems, or in a distributed solution (multiple computers) using TCP/IP connectivity. As computers and hardware have advanced in capabilities and cost-effectiveness, many sites will use a distributed solution.
There are two types of networked architectures: A standalone solution with one computer and the hardware using TCP/IP connectivity A distributed solution with multiple computers and hardware using TCP/IP connectivity.
Dedicated Computer: in the context of this document, the term dedicated computer means that the computer (client or server) is solely devoted to running the System Galaxy integrated access control applications and services for the purposes of monitoring and controlling access and other System Galaxy features such as card enrollment. The specifications in this document do not cover shared applications/uses. Minimum Recommendations: in the context of this document, the term minimum recommendations means that the computer (client or server) running System Galaxy should, at a minimum, meet stated specifications. However, there may be reasons to increase certain specifications. Because systems vary, minimum recommendations may need adjusting. Distributed Solution: in the context of this document, the term distributed installation means that the entire System Galaxy software system (SG Access Control software, GCS Services, and database) will be installed on several separate computers. This is the most commonly needed solution. Standalone Solution: in the context of this document, the term standalone installation means that the entire System Galaxy software system (SG Access Control software, GCS Services, DB engine, & databases) will be installed on one computer. The hardware will connect to this computer by TCP/IP.
IMPORTANT: If you are specifying requirements for a system that will need to expand (grow) or share resources with other applications (email, web browsers, programs, etc), you should take these goals into consideration also. Shared applications may cause conflicts or could require you to adjust your system specifications
Sy st em Recomm endat ion s | page 11

Minimum Recommendations for a Stand-Alone Solution
A Standalone Solution is described as having all the software components (databases, database engine, services, and SG software application) running on a single computer which is also responsible for connecting to the hardware loop/controllers. IMPORTANT: The following assumptions are made for all system recommendations:
It is assumed that all connected loops will utilize TCP/IP connections to the networked Communication Server PC (or Standalone PC). It is assumed that no other software is running on any workstation where System Galaxy is installed/operating. Be aware that any additional programs must be taken into account when configuring a multi-use computer system.
It is important to remember that these are minimum recommendations with examples given. If you are specifying requirements for a system that will need to expand (grow), you should take those goals into consideration.
<< This diagram depicts a Standalone PC with hardware connectivity. As you can see, the SG Software Application, GCS Services, Database Engine and both the main database and archive database will reside on the one computer.
Worksheet for a Standalone System
Computer Description OS Compatibility Windows 2000 Pro or XP Pro Windows 2000 server or Windows 2003 server Minimum Hardware Recommendations 2.8 GHz Pentium processor 2.0 GB RAM or greater 40 GB HD or greater
All System Galaxy components running on the same computer with no additional SG client workstations connected.
IMPORTANT: Some integrated applications or technologies may not be supported on Server OS, while other integrated applications may impose specifications for a Server OS. See the Integrated Applications section in this manual and the related System Galaxy Interface Guide for details.
Sy st em Recomm endat ion s | page 12
Minimum Recommendations for Distributed Solutions
Database Server Minimum Recommendations - Distributed Solution
A Database Server is described as housing the main SysGal and Archive databases and hosting the Database Engine in a Networked System. In a networked system, the software components are distributed among more than one PC. IMPORTANT: The following assumptions are made for all system recommendations:
<< This diagram depicts a Database Server connecting to a Communication Server and Client Workstation in a Distributed Solution. As you can see, this is one example of a distributed solution. See the worksheet below for details. Contact System Galaxy Technical support for assistance for more complex needs.
Worksheet for a Database Server in a Distributed System

Computer Description Computer running DB engine, System Galaxy Client software and GCS Services ( with up to 2 additional System Galaxy client workstations connected) Computer only running DB engine, and GCS services (not SG Client Software). ( with 3 or more additional System Galaxy client workstations connected) Database Server OS Min. Recommendations Windows 2000 Pro | XP Pro Windows Vista Ult. | Bus. Minimum Hardware Recommendations 2.8 GHz Pentium proc. 2.0 GB RAM 40 GB HD Windows Server 2000 | 2003
Sy st em Recomm endat ion s | page 13
Communication Server Minimum Recommendations - Distributed Solution
A Communication Server (or Loop Communication Server, LCS) is the PC/Server that handles the communication to the Loops/controllers in a Networked System. In a networked system, the software components can be distributed among more than one PC. Thus, the database may or may not reside on the Communication Server. IMPORTANT: The following assumptions are made for all system recommendations:
<< This diagram depicts a Communication Server connecting to a separate Database Server in a Distributed Solution. As you can see, this is one example of a distributed solution. See the worksheet below for details. Contact System Galaxy Technical support for assistance for more complex needs.
Worksheet for a Communication Server in a Distributed System
Computer Description Computer running System Galaxy Client software and GCS Services ( with the DB engine on separate computer and up to 3 additional SG Workstations connected) Computer running System Galaxy Client software and GCS Services ( with the DB engine on separate computer & 4 or more additional SG Workstations connected) Communication Server OS Min. Recommendations Windows 2000 Pro | XP Pro Windows Vista Ult. | Bus. Minimum Hardware Recommendations
Windows Server 2000 | 2003
2.8 GHz Pentium processor 2.0 GB RAM or greater 40 GB HD or greater
Sy st em Recomm endat ion s | page 14
Client Workstation Minimum Recommendations - Distributed Solution
A Client Workstation is described the additional workstation that runs the System Galaxy software for monitoring or badging purposes. This additional client will operate in a Networked environment and make TCP/IP connections to both the Database Server and the SG CommServer. IMPORTANT: The following assumptions are made for all system recommendations:
It is assumed that no other software is running on any workstation where System Galaxy is installed/operating. Be aware that any additional programs must be taken into account when configuring a multi-use computer system.

<< This diagram depicts a Client Workstation connected to the Communication Server and the Database Server in a Distributed Solution. As you can see, this is one example of a distributed solution. See the worksheet below for details. Contact System Galaxy Technical support for assistance for more complex needs.
Worksheet for a Client Workstation in a Distributed System

Computer Description

Workstation Running System Galaxy Client software for monitoring or badging, but not running the GCS Services. Additional Client Workstation Minimum Recommendations Windows 2000 Pro | XP Pro Windows Vista Ult. | Bus. Minimum Hardware Recommendations 2.8 GHz Pentium processor 1 GB RAM or greater 40 GB HD or greater
Sy st em Recomm endat ion s | page 15