Installing GainSeeker Client version 8.6

Transcription

1 Installing GainSeeker Client version 8.6 Before installing Copy the CD to the network (recommended) On some versions of the Windows operating system, Windows may need to perform a Change (repair) for the GainSeeker program each time a different Windows login first launches a GainSeeker program on that computer. When performing a Change (repair), Windows may need to access the GainSeeker installation CD to complete the repair. It will try to access the CD in the same location that was used to install GainSeeker on this computer. To avoid the need to insert your GainSeeker installation CD in the CD-ROM drive each time a Change (repair) is needed on any of your GainSeeker workstations, Hertzler Systems recommends the following strategy: 1. Copy the GainSeeker installation CD to a shared location on the network. This location should be on a network drive that will not change in the foreseeable future (for example, a mapped drive or UNC path that will remain the same even if the server gets switched out). You can copy the entire CD to this location, or you may copy only the \SPC\DISK1\ folder and its sub-folders. 2. Use this network copy of the CD instead of the physical CD when installing GainSeeker on your workstations. If you are upgrading from GainSeeker version 8.0 or later, you should eventually delete (or rename) all network copies of the CD except for the latest version particularly after you have upgraded all of the GainSeeker workstations to the latest version. This will prevent any workstations from erroneously installing or repairing GainSeeker from older versions of the CD. Where to install When installing GainSeeker on a traditional client/server network, you should install GainSeeker at all client workstations, not at the server itself. If you are upgrading from a previous version of GainSeeker, you should start by installing GainSeeker version 8 on a client workstation that already runs the previous GainSeeker version. When installing GainSeeker on a terminal server with Citrix or Terminal Services, you must run the GainSeeker installation at the terminal server. When installing GainSeeker on a web server or intranet server for use with GS Analyze or GainSeeker Mobile Web Service, you must run the GainSeeker installation at the web server or intranet server. Permissions on the computer To complete the GainSeeker installation, Windows requires you to log in with Administrative rights or to run the installation as an Administrator. Permissions on the network To complete the GainSeeker installation, you must have full permissions (all except Supervisory rights) to the Shared data folder a network file path where shared data files exist (or should be placed).

2 Permissions on the database To complete the GainSeeker installation, you must be able to access the GainSeeker database with the same permissions as other GainSeeker users. System Requirements Make any changes necessary to meet the System Requirements for installing and using GainSeeker. This includes ensuring that the Microsoft.Net Framework version 3.5 Service Pack 1 and version 4.0 are installed on all workstations, your terminal server, and/or your web server or intranet server. (Installing this version of the.net Framework will require a computer reboot.) Close all GainSeeker modules If GainSeeker data already exists on your network, you may need to have some or all network users exit all GainSeeker modules before you can successfully install this version of GainSeeker: When using GainSeeker on a Pervasive or Btrieve database, all GainSeeker users must close all GainSeeker modules before you install this version of GainSeeker. If any of the shared files on the network are locked when you try to install GainSeeker, the installation cannot be successfully completed. When using GainSeeker on terminal server with Citrix or Terminal Services, all GainSeeker users must close all GainSeeker modules before you install this version of GainSeeker. If any of the shared files on the terminal server are locked when you try to install GainSeeker, the installation cannot be successfully completed. When installing this version of GainSeeker on a workstation, you must close all GainSeeker modules before launching the installation. Performing the installation Launching the installation On a GainSeeker workstation To begin the installation, use one of the following methods: If you copied the GainSeeker installation CD (or a portion) to a shared location on the network, browse to this location and run the SETUP program. (Optionally, for Windows Vista (or later) operating systems, right-click Setup. Then select Run as Administrator.) Otherwise, insert the GainSeeker installation CD into your CD-ROM drive. On a terminal server The CD-ROM menu opens automatically and allows you to install GainSeeker on your system. If this is not the case, browse to your CD-ROM drive and run the SETUP program. Use Add or Remove Programs in Control Panel to launch the GainSeeker installation program (SETUP.EXE from the network copy of the GainSeeker installation CD or from the physical GainSeeker installation CD) in "install mode". If you are prompted to restart the computer to finish the installation, click Finish in Add or Remove Programs before accepting the prompt to restart the computer. After the server has been rebooted, log on as the same user so that the GainSeeker installation will finish properly. Alternately, you may be able to finish the installation after the server reboot by re-running the GainSeeker installation.

3 More information on installing programs on a terminal server is available from the Microsoft TechNet web site. On a web server or intranet server To begin the installation, use one of the following methods: If you copied the GainSeeker installation CD (or a portion) to a local drive, browse to this location and run the SETUP program. (Optionally, for Windows Vista (or later) operating systems, right-click Setup. Then select Run as Administrator.) Otherwise, insert the GainSeeker installation CD into your CD-ROM drive. The CD-ROM menu opens automatically and allows you to install GainSeeker on your system. If this is not the case, browse to your CD-ROM drive and run the SETUP program. Screens that may appear during the installation More work required to run Dynamic Reports When installing GainSeeker for a Pervasive or Btrieve database, the following message may be displayed at the beginning of the installation process: A similar message may also appear near the end of the installation process: The work being referenced by these messages is the conversion of your database from file mode to database mode that is required to use the current version of GainSeeker. Location of shared data Very Important: On this step, you should specify a network file path where shared data files exist (or should be placed). If the folder you specify does not exist, the installation program will attempt to create it for you. The path you specify will become the config_path= setting in Cms.ini on this workstation. If prompted to choose the Shared Data Folder (Config_Path), you must specify the network file path where shared data files exist. Do not use the default path provided on this step (C:\Data\), because it does not point to a shared folder on your network.

4 When upgrading a workstation from a previous version of GainSeeker, this prompt will not be displayed. Exception for Laptop users: If you are using a laptop or similar device that you plan to run while you are disconnected from the network, you may first want to use the default path while installing GainSeeker. Then, manually update the config_path= setting in Cms.ini for that device. You will also need to update the Redirect= setting in Settings.hsi. The config_path should be a mapped drive or a UNC that will not change. The installation stores this information and uses it for repairs. When GainSeeker is run, it verifies the existence of all files copied to that location. GainSeeker will attempt to repair itself if the drive is not mapped or the computer name in the UNC does not exist. Database settings For all databases except Pervasive or Btrieve, the installation program will prompt you to enter information for connecting to the GainSeeker database. For an Oracle database, the Database server you specify will actually be the Oracle Net Service Name you have set up on the workstation. After you enter the requested information and click Next, GainSeeker will automatically test these settings to make sure they successfully connect to the database before continuing with the installation. When upgrading a workstation from a previous version of GainSeeker, this prompt will not be displayed.

5 After you click Finish After you click the Finish button on the final step of the InstallShield Wizard, some additional tasks may be performed. Automatically apply minor changes to database If you are upgrading from a GainSeeker version prior to 8.0, the following changes may be automatically applied to your GainSeeker database: Create new table HSICFG and fill with settings from Create new database table HSIUC Create new table HSIRPT previous tables and files If you are upgrading from a GainSeeker version prior to 8.4, the following changes may be automatically applied to your GainSeeker database: Create new table HSISCRIPTS Create new table HSICT Create new table INSPECTIONUID Set initial login password The first time you install GainSeeker on your network, it will create a single user named SPC MANAGER which has full rights to all functions in the system. For security purposes, the installation will prompt you to set a login password for this user. When upgrading from a previous version of GainSeeker, this prompt will not be displayed. After the installation Finalizing database settings For all databases except Pervasive or Btrieve, you may need to update database connection settings in Cms.ini and/or in Settings.hsi. For more information, see the setup instructions for SQL Server, Oracle, MySQL or MariaDB. When upgrading a workstation from a previous version of GainSeeker, this step is not needed.

6 Installing a newer.net connector for MariaDB For the MariaDB database, you must install the MySQL.Net Connector version by running the UTILITY\Database updates\mysql\connectors\mysql-connector-net msi file on the GainSeeker installation CD. Pushing an automated installation package to client workstations Some IT departments routinely automate software installation to client workstations by "pushing" it over the network. To automate the GainSeeker installation on multiple workstations across your network, you can use a third-party application such as AdminStudio from Flexera Software to repackage the GainSeeker installation program with transforms that will automatically respond to the user prompts. Additional tasks for Citrix and Terminal Services In a multisession application hosting environment such as Citrix and Windows Terminal Services, it is not necessary to install GainSeeker on additional workstations. However, you may need to perform one or more of the following steps after installing GainSeeker on your terminal server: Set up a unique identifier for each computer or network user Map client COM ports to the terminal server Configure one or more GainSeeker shortcuts for PDA mode During installation on Windows Vista (or later), changes are made to the Cms.ini in the Virtual Store folder. These changes are not made to the Cms.ini in the Windows Folder. It is a best practice to copy the Cms.ini file from the Virtual Store folder to the Windows folder. When other Windows users log into that workstation to run GainSeeker, it uses the Cms.ini file in the Windows Folder as a base file, which copies to that user's Virtual Store folder. Ensuring backups After installing GainSeeker, ensure that your GainSeeker database and your shared data folder will be backed up regularly. Other steps: If upgrading from a previous version of GainSeeker: For each configuration that uses a different set of tables, you will probably want to update the table names for the HSIRPT table, the INSPECTIONUID table, and the HSICT table. Then use the Check for Tables button to automatically create the new table names. (Pervasive.SQL database only) If you have not already done so, convert your database from file mode to database mode. (optional) Install the sample data. On a Pervasive database, this feature is only available after converting from file mode to database mode. (optional) Install GS Analyze on your web server or intranet server. (optional) Install GainSeeker Mobile Web Service on your web server or intranet server. (optional) Install OPC components for PC Collect data entry. If upgrading from GainSeeker version 7: use the Password Check utility to update any login passwords from GainSeeker version 7 that had been entered with uppercase characters and/or with more than six characters.

7 If upgrading from GainSeeker version 7: launch the SPC Designer module and run the Syntax Checker. Repeat this step for each configuration that uses a different set of templates. If upgrading from GainSeeker version 7: all of the roles that were assigned to users in GainSeeker version 7 will be converted as customizable roles - even if they were pre-defined (non-customizable) roles in GainSeeker version 7. You may want to review these roles and customize any new settings that are available after installing GainSeeker version 8.