System Galaxy Upgrade Planning Procedure

This topic provides basic information about planning and implementing a system upgrade of System Galaxy software and hardware as well as the integrated 3rd Party solutions.

 

click to open PDF 

 

Introduction

The information in this guide may not apply to every system. Use the portions of the guide that do apply to your system.

 

If you have a scenario that is not covered in this guide, please contact your authorized technical support for assistance with planning your upgrade.

 

  Review the Important Backup Notices before you begin planning your upgrade.

 

 

 

TERMS

 

TERM "3rd Party Solutions" refers to the software and/or hardware that belongs to a third-party producer such as badging software, visitor management, biometrics, API interfaces, wireless readers, and peripheral devices - such as enrollment readers and finger capture devices, etc. 3rd Party

 

 

 

 

Important Backup Notices

 

Always back up all databases and all system assets, log files, reports. Failure to perform proper backups can lead to catastrophic data loss. See the related steps in the Software Upgrade Considerations for a preliminary list of things to consider

 

Always make and retain an extra set (duplicate copies) of your database backups. This way if the upgrade fails you still have a copy of your backups. Failure to make an extra copy of your backups can lead to loss of data.

 

For 3rd Party Solutions, consult the manufacturer's documentation concerning 'how to back up' associated assets - including badging, databases, data, templates, log files, config. files, drivers, tables, reports, physical assets, etc. biometrics, wireless readers, etc.

 

Create an Upgrade Plan and a Cut-over Plan that fits your system. Although this System Upgrade Planning Guide provides a guideline for upgrading System Galaxy and commonly integrated solutions, each system is unique, there are things to consider that might not be listed in this guide. The customer is responsible for identifying these system differences and for verifying the support and compatibility of any special customizations that are unique to their system.

 

Always backup all system assets for System Galaxy and each 3rd Party Solution and peripheral devices, before you begin your upgrade. Failure to do backups of assets can lead to data loss and the need to reconfigure or rebuild your assets or replace them, or permanent loss. See the related steps in the Software Upgrade Considerations for a preliminary list of assets to consider.

 

 

 

 

 

Software Upgrade Considerations

  1. Verify the existing Software Maintenance is current (paid for):

    1. Maintenance is current (paid for)

    2. Verify that the maintenance expiration date is a future date in your existing installation/system.

      WARNING: If the existing software does not have a valid maintenance date and registration code, the database upgrade will be prevented.

       

  2. System Requirements:

    1. Verify that all system computers (clients/server) meet the PC specifications and new software requirements for the new System Galaxy version that you are upgrading to.

    2. If you are upgrading Galaxy hardware, you will need to consider networking requirements.

      NOTICE: See the latest PDF https://www.galaxysys.com/sghelp/_docs/currdocs/IT-SG System Specification.pdf - or see the System Galaxy Specifications Online. Otherwise, if you are coming up to a recent version that is not the latest, see the System Specs Guide that corresponds with the version of System Galaxy you will be installing.

       

  3. Obtain the names and IP addresses of the new database server and new event server.

     

  4. Obtain the necessary access to the existing SG computers.

    1. This includes access to the physical server and client PCs, Computer Log In permissions with Administrative privileges, customer permission to reboot the PC when required during the upgrade.

    2. Determine if the database is being supported by the end user’s IT or the default installation was used.

      NOTE: If the Galaxy default values are not used, you will need the database server name, instance, database name, and login credentials.

    3. If remote assistance is desired, all PCs must be able to access Galaxy Control’s Remote Assistance website.

       

  5. Identify your Badging Software needs: The latest version of System Galaxy comes with the idProducer Badging Solution, although SG maintains compatibility with SG version of Card Exchange and the SG version of G & A GuardDraw. See the information for your brand of badging below.

     

    1. Upgrading for G&A Imaging Solution (Imageware/GuardDraw) ...

      1. You must back up all badging assets (photos, logos, etc.) before you begin the system upgrade. Do this whether you are keeping GuardDraw or migrating to idProducer.

        IMPORTANT: Save your badging assets to a different location (different computer) to avoid them being lost, deleted or overwritten - (i.e., photos, logos, icons, etc.).

         

      2. If you want to continue using GuardDraw, you must back up your badge templates to a separate location to prevent them being lost (overwritten).

        IMPORTANT: you must verify that your GuardDraw version will be compatible with the operating system you are planning to use. Galaxy’s version of GuardDraw is no longer supported by the original manufacturer. As a result, there will eventually be a point when this version of GuardDraw is no longer compatible with an operating system.

         

      3. If you are migrating to idProducer software, you must recreate new badge templates in idProducer after you register your idProducer license; however, you can keep/reuse your existing assets (photos, logos, etc.) if you back them up.

         

    2. Card Exchange Badging Solution ...

      1. Back-up all badging assets (photos, logos, etc.) before you begin the system upgrade. Do this whether you are keeping Card Exchange or migrating to idProducer.

      2. If you will continue using Card Exchange software, you must back up your badge templates - including templates on every badging client, as well as templates on a shared network.

      3. if you want to migrate to idProducer software, you will need to recreate your badge templates in the idProducer software. However, you can save and reuse your existing assets (photos, logos, etc.)

         

    3. idProducer Badging Solution ...

      1. Back-up all badging assets (photos, logos, etc.) before you begin the system upgrade.

        NOTICE: If you are migrating from Card Exchange or G&A GardDraw to Basic or Advanced idProducer, you will need to recreate all your badge templates.

        The new idProducer badge templates can use your existing badging assets (i.e, photos, logos, graphic files), so save those in a separate location until you are ready to use them. You will manually add those items to the badge templates when you create them in the idProducer Badge Designer. The new templates will be imported into System Galaxy once they are created.

        About idProducer License levels: idProducer is offered in two license levels - Basic license and Advanced license. The primary difference between the two license levels is that the Advanced License offers a subscription-based badging solution that supports creating subscriber-based badge templates for multiple Subscriber Accounts that are auto-synchronized to a corresponding SG Customer (i.e., linked SG Customers can have unique badges based on the linked idProducer Subscriber account. Cardholders badge templates are separated by the customer assignment). The Advanced license also supports multiple print servers per customer-subscription.  Contact authorized customer support for more information about idProducer to determine which license level is right for your system.

         

    .

  6. Biometric Solutions:

    1. Invixium Biometric Solutions ...

      1. You may continue using your existing solution, but you may need to upgrade your Biometric software or firmware.
      2. Contact Galaxy technical support for assistance with planning your upgrade.

    2. MorphoManager / BioBridge Biometric Solution ...

      1. You may continue using your existing solution, but you may need to upgrade your Biometric software or firmware.
      2. Contact Galaxy technical support for assistance with planning your upgrade.

    3. Sagem legacy biometrics or other custom applications: Contact Galaxy technical support for assistance with planning your upgrade.

  7. LaunchPoint web Client:

    1. See the Badging Solutions section for upgrade considerations.

    2. Back up any Reports you have exported in PDF or Excel to a separate location so they are not overwritten.

    3. Back up your company logo if you added that to the header logo space.

     

  8. Visitor Management: Contact Galaxy support for assistance with planning your upgrade.

    • StopWare/PassagePoint Visitor Management

    • EasyLobby Visitor Management

       

    1. Identify any Visitor Management integration with System Galaxy and determine what impact the upgrade will have on the integration.

    2. Testing the Visitor Management integration through a mock upgrade should be completed before a real upgrade is started.

      IMPORTANT: Testing both the upgrade and the continued operation of the Visitor Management interface is the responsibility of the system integrator and system owner.

       

  9. API Integrations: Contact Galaxy support for assistance with planning your API upgrade.

    1. Identify any API Integrations that are not provided by Galaxy and identify any API changes or other changes in the new SG Release that can impact API integrations.

    2. Contact the appropriate 3rd Party vendor who wrote the integration to ensure continued functionality after the upgrade.

    3. Testing the API integration(s) through a mock upgrade should be completed before a real upgrade is started.

      IMPORTANT: Testing both the upgrade and the continued operation of the API interface is the responsibility of the system integrator and system owner.

       

  10. Third-Party Custom Database Integrations: Contact Galaxy for assistance with planning your upgrade.     

    1. Identify 3rd Party Solutions for Time and Attendance - you need to work with the vendor/maker of the T&A solution to determine compatibility and how to move forward and whether you need to upgrade. Be sure to back up the databases and any stored procedures, triggers, scripts, data, assets, etc. that are associated with T&A

    2. Identify any elevator solutions or

    3. Identify 3rd party applications that were not provided by Galaxy (i.e., human resources, etc.)

    4. Back up any Stored Procedures - especially custom stored procedures that are associated with DB integrations.

    5. Contact the appropriate DB vendors/managers to ensure continued functionality after the upgrade. This includes importing and/or exporting data that may be impacted by any changes to the database schema.

    6. If your system uses the SG_Import program, you must also verify whether the import profile(s) need to be reconfigured to match up with the new database schema.

    7. Testing Database integration(s) through a mock upgrade should be completed before a real upgrade is started.

      IMPORTANT: Testing both the upgrade and the continued operation of the DB interface for importing and exporting data, as well as any 3rd party product dependency on exported data is the responsibility of the system integrator and system owner.

       

  11. Active Directory Solution: Contact Galaxy for assistance with planning your AD upgrade.

    1. Identify any Active Directory tool being used and determine if the system will continue using the existing AD implementation, or migrate to the newest AD Synch Tool.

    2. Contact the IS/IT Department for decisions regarding the choice and implementation of the Active Directory tool.

    3. Obtain any login/credentials or permissions to the AD Tools used.

    4. Back up any files associated with the AD Tool as appropriate on a separate location that is not being upgraded or replaced.

    5. Testing the AD integration through a mock upgrade should be completed before a real upgrade is started.

      IMPORTANT: Testing both the upgrade and the continued operation of the AD interface is the responsibility of the system integrator and system owner.

       

  12. Video Management Solution: Contact Galaxy for assistance with planning your AD upgrade.

    1. Identify any/all Video Management Systems being used and determine if the system will continue using the existing VMS system, or migrate to a new VMS solution.

    2. Obtain any VMS system logins needed to complete the backups, testing, and the upgrade.

    3. Back up any VMS reports, images, video clips, or system configurations or 3rd Party databases that are located on any computer that will be upgraded or replaced that are associated with the existing VMS. Store backups on a separate location that is not being upgraded or touched by the upgrade.

    4. Testing the VMS integration through a mock upgrade should be completed before a real upgrade is started.

      IMPORTANT: Testing both the upgrade and the continued operation of the VMS interface is the responsibility of the system integrator and system owner.

       

  13. Determine the location of all Galaxy and 3rd Party system assets and files to be backed up:

    1. Always create backups of all databases before you start your upgrade:

      This includes but is not limited to ...

      • backing-up SysGal and SysGalArc,

      • all 3rd Party Databases for integrated solutions such as biometrics, badging, visitor management, etc.

      • third-party or custom stored procedures, custom scripts/views/queries,

      • data conversion files (for imports or exports),

      • DB log files for SG and 3rd Party solutions

      Remember: 3rd Party solutions includes 3rd Party solutions provided by Galaxy or provided with System Galaxy as well as custom or separate 3rd party integrations not provided by Galaxy or provided by a separate vendor.

      IMPORTANT: It is the customer's responsibility to verify and test the compatibility and upgradability of separate systems and custom APIs.

       

    2. Always create backups of all system assets and discrete files  before you start your upgrade

      This includes but is not limited to ...

      • All biometric finger templates, badging design templates, photographs, signatures, logos, etc.

      • API Config. files - including API Integrations by private vendors that utilize Galaxy's API interface

      • All system reports, archived reports, and custom reports.

      • All icons, graphics, diagrams, floorplans.

      • All video files, audio files (.wav, .mp3/4 ...), image files (tif/.gif/.jpg/.png/.svg ...),

      • All integrated flash/firmware files, including peripheral hardware, readers, finger sensors, etc.

      • All drivers, including printers, enrollment devices, sensors, etc.

      • All your supporting 3rd Party documentation for hardware and peripheral devices or 3rd party integrations.

         

    3. All necessary credentials that you will need to complete the upgrade (logins, passwords, permissions, etc.)

    4. All necessary license keys or product codes that you need to maintain interrupted product use for System Galaxy and all 3rd Party integrations.

    IMPORTANT: Some assets may reside on a shared location on the customer’s network, or on a specific server or workstation. Be sure to identify all locations.

     

  14. Perform and Validate all backups of databases and appropriate sub-system files as noted above.

    IMPORTANT: Store the validated backups on a separate computer that is not being upgraded.

     

  15. Review the Database Upgrade section of this guide for important information about pre-scheduling database upgrades with Galaxy Control Systems.

 

 

Hardware Upgrade Considerations

Also see the 635/600 Hardware Installation Manual for board compatibility and flash upgrade information.

  1. Determine the version of the existing System Galaxy software, and existing 500/600 hardware and assess the hardware upgrade compatibility. If hardware is being added to an existing site, be sure it is compatible with the existing hardware.

    When upgrading from:

    1. Version 5x and earlier – Replace all 500 Series CPU boards with 500i CPU boards

    2. Version 6x – Replace all 500 Series CPU boards with 500i CPU boards

     

  2. SG Version 10.1 or higher is required to use 635 CPU boards.

     

  3. Upgrading Hardware: 500i and 600 architectures.

    1. 500i and 600 architectures are not inter-compatible. That is, you cannot replace a 500i architecture system with 600 hardware without major database reprogramming. If desired, the 500i architecture can be converted to 600 architecture using a built-in utility once the software has been upgraded to the latest version.

    2. Both 500i loops and 600 clusters can co-exist on a common System Galaxy server, sharing the same database, and be monitored from the same Galaxy interface.

    3. The two types of hardware must be on their own distinct architectures. They cannot communicate directly with each other, having I/O, door group, or anti-pass back interoperate between Loop and Cluster.

     

  4. In systems using 500i-series hardware, you should ...

    1. evaluate the health of the RS-422 loop that runs between each controller in the loop.

    2. The 500i CPUs will not need to be reflashed if they are already running 8.20 flash,

    3. they will need to be reloaded once the software upgrade is completed

    4. If the existing loop is experiencing any communication problems before the upgrade, then those issues should be resolved before starting the upgrade.

     

  5. Obtain a Factory Test Station Ribbon Cable (part # 81-0680-00) and familiarize yourself with using it on the 635 CPU.

    See the 635-FTS Factory Programming Guide (SG 10.4.9).pdf for complete instructions for how to utilize a 635 CPU as a Factory Test Station. These can be used to restore a board that fails to come back after a flash update.

     

  6. Review the Firmware Upgrade section in this document for important information on upgrading Galaxy access control panels (controllers).

     

  7. IMPORTANT: If you are upgrading a large system and has a lot of controllers/doors, or a large number of Cardholders, or has a lot of integrated systems, or has Biometric equipment, you should contact Galaxy at your earliest planning stages to ensure that the appropriate technical support and advice is provided.

 

 

Day of the Upgrade

Make sure you are prepared for the day of the upgrade before the upgrade day arrives.

 

  1. Schedule time to allow the system upgrade - including function testing time after the upgrade is performed.

     

  2. Keep in mind large scale sites where clients are scattered across the country may require your to deploy dealer technicians to multiple locations.

     

  3. When you begin the upgrade, you should be fully prepared for “down time”. This means mission critical doors will need to be propped, or otherwise made accessible, during any system down time.

     

  4. Organize the upgrade in such a fashion that the hardware can function offline while the software is upgraded, and then systematically upgrade one panel at a time if possible, to minimize end user inconvenience. Remember that upgrading a 508i/600 loop will require flashing the CPU, which if the CPU is a 600/635 will require updating its daughter boards. Depending on the starting version of firmware, this may require more than one step (see below). Always remember to cold start a CPU after flashing. This will clear any residual memory and eliminate possible Loading issues after an upgrade.

     

  5. Always work the upgrade in a logical order. It would be recommended to follow this sequence.

    1. Run the Database upgrade.

    2. Run the software/services upgrade at the Comm Server.

    3. Complete the System Registration from the Comm Server.

    4. Do the Hardware Flash version upgrade (doing controllers in steps if required).

    5. Cold start the Hardware Controller CPU’s.

    6. Load Data to the hardware controllers (Clusters) and perform the function tests.

    7. Upgrade any other client workstations, as needed.
      Note: Client registration is no longer needed in the latest release of System Galaxy.

     

 

About Database Upgrades

 

  1. Upgrading from SG v 8.1 or higher/newer: The database upgrade can be performed in one step using “Part 2- Database” on the GalSuite Installation Disk-1, unless there is a change in database engine. Upgrading the Database does not upgrade the database engine. Migrating your database to a newer SQL Engine may require Technical Support or a DBA technician with the knowledge. The Galaxy Learning Center has a video on how to move databases from one location to another: http://www.galaxysys.com/page-LearningCenter .

     

  2. Upgrading from SG v 8.04 or below/older: Contact Galaxy Tech Support. The database must be sent to Galaxy for conversion and upgrade. This process takes five (5) business days from the time we are notified of receipt.

     

  3. If faster turn-around time is needed because of customer requirement, any work done by Galaxy Technical must be pre-scheduled. If it is an on the spot decision to upgrade and they need the database upgraded “now” a fee will be charged.

     

  4. A Galaxy service technician may not be available to walk an on-site technician through a complete upgrade over the phone or through Remote Assistance. If such service is required, contact Galaxy technical to schedule an appointment.

     

  5. If non-standard database names are being used (this means anything other than SysGal and SysGalArc), consult Galaxy Technical Support department IN ADVANCE regarding upgrade script modifications.

 

 

About Firmware Upgrades

  1. Firmware on the CPU must be synchronized to the version of System Galaxy installed at the site. Determine the required version of flash by looking in Help>About>System Galaxy. Determine the version of flash for the new system by contacting technical support or obtaining a new Hardware Install Guide.

     

  2. Do not interrupt flashing: Do not interrupt power, do not disconnect the I2C data bus (the gray ribbon cable) or reset any of the boards connected to the ribbon cable during the update process. Interrupting the flash process will damage the board memory and require using the factory flash cable or factory repair to recover the board.

     

  3. When your controllers are running flash versions prior to 4.51, Galaxy strongly recommends disconnecting attached boards (DRM, DSI, etc) from the field devices they are controlling.

     

  4. When using Dual CPU configurations, disconnect the CPU boards from the I2C data bus (the gray ribbon cable) until both boards have been brought up to the desired version of flash. This is to prevent them from pushing competing versions of firmware to the attached boards.

     

  5. Disconnect 635 DSI boards from the ribbon cable before and while the rest of the boards in the controller can are being updated from firmware version 5.04 to 10.4x. Then update one 635 DSI at a time, while leaving the rest disconnected until they have been completed.

     

  6. Updating attached boards. Galaxy has made changes to the protocol on the data bus to improve communications. Boards running flash using the old protocol must be updated to one of the versions of flash running both protocols before being updated to the latest version that runs only the new protocol. This is because a CPU running the latest flash will not be able to recognize (talk to) a daughter board running the old protocol.

    • Prior to Flash 5.04 – only the old protocol
    • Flash 5.04 to 10.4.15 – has both protocols
    • Flash 10.4.17 and higher -- has the new protocol

     

  7. When upgrading from certain versions, it is necessary to update to an interim version before continuing to the desired end version. See the following charts:

     

    600 FLASH UPGRADES - for stepped version upgrade

    STARTING VERSION UPGRADE TO: (BEFORE CONTINUING)
    1.15 to 1.74 2.30e
    2.30e to 5.00

    5.04
    5.04

    10.4.15 – update attached boards
    10.4.15

    Latest Flash Version

     

    635 FLASH UPGRADES - for stepped version upgrade

    STARTING S28 VERSION UPGRADE TO S28 (BEFORE CONTINUING)
       
    4.77 to 5.00

    5.04
    5.04

    10.4.15 – update attached boards
    10.4.15

    Latest Flash Version