SEER for Software Installation Guide

Transcription

Technical Installation Guide
SEER for Software
GALORATH INCORPORATED
2016
Authored by: Galorath Incorporated
Contents
INTRODUCTION ............................................................................................................... 2
SEER FOR SOFTWARE PRODUCT LINE .................................................................................... 2
EDITION INSTALLATION ORDER ........................................................................................ 3
WHAT YOU NEED ........................................................................................................ 4
MINIMUM SYSTEM REQUIREMENTS......................................................................................... 4
GENERAL INSTALLATION OPTIONS......................................................................................... 6
LOCAL ...................................................................................................................... 6
SERVER ...................................................................................................................... 7
CLIENT ...................................................................................................................... 8
PRE-INSTALLATION CONFIGURATION OPTIONS ......................................................................... 9
DOCUMENT FILES ......................................................................................................... 9
HELP FILES ................................................................................................................. 10
APPDATA .................................................................................................................. 10
LOCAL INSTALLATIONS ..................................................................................................... 11
QUICK INSTALL PROCESS .......................................................................................... 11
DETAILED INFORMATION ............................................................................................... 11
DEFAULT INSTALLATION CONFIGURATION ....................................................................... 12
APPLICATION DATA AND DOCUMENT DATA FILES .............................................................. 12
FIRST TIME INITIALIZATION ......................................................................................... 13
CONFIGURE SEER SO ALL LOCAL USERS SHARE A COMMON DATA SET ................................ 14
SERVER INSTALLATIONS..................................................................................................... 15
SERVER APPLICATION DATA AND DOCUMENT DATA FILES .................................................... 16
SEER-SEM SETTINGS.INI CLIENT CONFIGURATION ............................................................ 17
CRYSTAL REPORTS COMPATIBILITY FOR WINDOWS SERVER & CITRIX ....................................... 17
CLIENT INSTALLATIONS ..................................................................................................... 18
CLIENT/REMOTE USER FIRST TIME INITIALIZATION ............................................................ 19
SILENT INSTALLATIONS ..................................................................................................... 19
OTHER TECHNICAL INSTALLATION DETAILS ............................................................................ 20
REGISTRY SETTINGS ...................................................................................................... 20
START MENU SHORT CUTS ............................................................................................. 21
ODBC SETTINGS ......................................................................................................... 21
CRYSTAL REPORT DLLS ................................................................................................. 21
DISC SPACE SIZING........................................................................................................... 22
REPAIR/REMOVE INSTALLATION .......................................................................................... 23
Technical Installation Guide | 3/31/2016
UPGRADE INSTALLATION ................................................................................................... 23
MINOR UPGRADES ....................................................................................................... 23
MAJOR UPGRADES ....................................................................................................... 24
INSTALLATION FAQ ......................................................................................................... 25
APPENDIX – SEER-SEM 8.2 FILE MANIFEST ............................................................................. 28
APPENDIX – COMMAND LINE INSTALLATION............................................................................ 40
1
Technical Installation Guide
SEER for Software
Introduction
This installation guide describes the available options for installing the SEER for Software application. It includes
topics such as basic system requirements, general installation options, and technical installation details.
It is intended to guide the reader through the process of installing and maintaining SEER for Software (SEER-SEM) on
the following operating systems:

Windows 7 SP1, Windows 8, Windows 8.1, or Windows 10

Windows 2008R2, 2012, or 2012R2 Servers
Icons are used throughout the installation guide to highlight important points in the installation, configuration, and
deployment process. Below is a list of the icons you will encounter:
Hints
Useful Information
Caution
Warning
Good practice
Bad practice
SEER for Software Product Line
The software products you receive depend on your SEER for Software Edition.
Estimator
Edition
Project
Manager
Studio
Edition
SEER for Software Core (SEER-SEM)



SEER-SEM Standard Configuration



Estimating Program
Essentials Essentials


SEER-SEM Commercial Configuration


SEER-SEM Browser Interface*


Estimate by Comparison*

Estimate by Comparison Pro*







Microsoft Project Integration




Project Monitoring & Control


Metrics Analysis & Benchmarking



SEER For Software
2
SEER For Software
Estimator
Edition
Project
Manager
Studio
Edition
ProjectMiner

ISBSG Database

Enterprise Shared Database
Estimating Program
Essentials Essentials
*
*
*
*
SEER-HD (both Access and SQL)*





SEER-HDA *





* Installation details provided in separate guides.
* Installing the Enterprise Shared Database is optional. The current release of Enterprise Shared Database has been
tested for use with Microsoft SQL Server (2005, 2008, 2008R2, & 2012) and Microsoft SQL Server Express. If you
would like more information on the installation and configuration of Enterprise Shared Database, please contact
Galorath to request a SEER Database Admin Guide.
Edition Installation Order
Installing a complete SEER edition typically requires that you follow a specific installation order. Assuming you have
the SEER Edition installation files on your computer, the installation order is described below.
1)
Install SEER-SEM - Run the 'Setup.exe' in the SEER-SEM folder. Once the SEER-SEM installation is
complete, proceed to install SEER_Compare.
2)
Install Estimate By Comparison (SEER_Compare) – Run the 'Setup.exe' in the SEER_Compare folder. The
SEER-HD installation should automatically start during the installation of Estimate By Comparison; if it does
not, you can manually begin the process after the Estimate By Comparison installation is complete.
SEER Estimate by Comparison requires Microsoft .NET Framework runtime version 2.0 to run. You
will be prompted during installation if you need to install it.
For detailed installation information please review the SEER_Compare installation guide.
3)
3
Install SEER-HD – if installation did not begin during the SEER-SEM/SEER_Compare installation, you can
manually start the process by running the 'Setup.exe' in the SEER-HD folder
For detailed installation information please review the SEER-HD installation guide.
4)
(OPTIONAL) Install SEER-HDA – Run the ‘Setup.exe’ located in “SEER-HD\SEER-HDA” subfolder.
For detailed installation information please review the SEER-HDA installation guide.
What you Need

Administrative Privileges

Minimum System Requirements

The SEER for SEM installation files; usually downloaded from www.SEERbyGalorath.com/oss8/users, or
supplied on a CD-ROM
A valid SEER license file that is typically sent to users via email with an attached SEER License Utility.exe
file, or supplied on a CD-ROM with installation files.

Minimum System Requirements
Item
SEER-SEM Standard/Commercial Configuration
Disk Space
Server Installation: 130 MB
Local Installation: 130 MB minimum, up to 190 MB
Memory
256 MB minimum, >512 MB preferable
Operating System
Windows 10, 8.1, 8, 7 SP1, and Server (2008R2, 2012, 2012R2)
Microsoft .NET Framework 4.0
Microsoft Visual C++ Redistributable for Visual Studio 2013 (x86)
(i.e., Microsoft Visual C++ 2013 Redistributable - x86 12.0.30501)
Optional
MS Project 2000 or higher (for exporting projects to MS Project)
SQL Server (2005, 2008, 2008R2, 2012, 2014) for the Enterprise Shared Database
(refer to the SEER Database Admin Guide for details)
Item
MSP Integration
Disk Space
106 MB
Memory
Operating System
Microsoft .NET Framework 4.0
Microsoft Visual C++ Redistributable for Visual Studio 2013
(i.e., Microsoft Visual C++ 2013 Redistributable - x86 12.0.30501 or
Microsoft Visual C++ 2013 Redistributable – x64 12.0.30501)
Software
MS Project 2000 or higher

Non-English versions of Project 2K and above can be accommodated, but
special configuration is required
SEER-SEM
Note: SEER Metrics is included in this estimate
4
5
Item
SEER Compare
Disk Space
50 MB
Memory
Operating System
Item
SEER-HD & SEER-HD Upgrader
Disk Space
2 MB
Memory
Operating System
Item
SEER-HDA
Disk Space
8 MB
Memory
Operating System
Item
SEER-CriticalMass
Disk Space
16 MB
Memory
Operating System
Windows XP
General Installation Options
Choosing the best configuration for your organization will depend on several factors. For example, the number of
users, requirement for shared data, integration with other systems, and organizational IT policies may influence the
decision. As you begin the installation process, you will be required to choose one of the following installation
options.
Options
Description
Local
All files are installed to the local PC. All the work is done on the local PC.
Server
All files are installed onto the Server. The SEER application is then typically executed
from a remote computer either through a Client install (see below), or through a thin
client application such as Citrix.
Client
Individual user settings, shortcuts and links to the networked server are setup on the
local machine. The SEER executable, knowledge bases, project files, etc. remain on a
networked server.
Local
The local install option installs all aspects of the solution to the local machine.
Product
User Settings
Knowledge Bases
Project Files
If you plan to have a small number of local install users, or a small number of users running SEER on a single
machine, Galorath recommends configuring the product so that knowledge bases and project files are stored in a
common area on the machine or on a network server.
SEE ALSO:
LOCAL INSTALLATIONS
CONFIGURE SEER SO ALL LOCAL USERS SHARE A COMMON DATA SET
The default configuration of a local installation places the Sample Projects, Tools, Knowledge Bases, and Flexible
Export Templates (classified as Document files) on each user machine.
6
Server
In this option, all aspects of the main product are installed on a networked server. A server installation is generally
done for one of two reasons:
1. To support a networked/client configuration (see next option)
2. To run the SEER product as a “server” to other applications
The product, user settings, project files, and knowledge bases are installed on a shared server location. This option is
equally valid for one user or multiple users. A fully remote installation means that no setup or full installation of the
SEER product is needed on local machines; only Client installs are needed on the local machines (see next section).
Product
User Settings
Knowledge Base
Sample Files etc.
This option allows for uniform knowledge bases, project files, and export templates among a large group of users
(Clients). During maintenance upgrades, only the Server copy of SEER requires updating making maintenance easier
when there are multiple users.
be considered.
SEE ALSO:
SERVER INSTALLATIONS
7
Issues related to read / write access (for connected clients), and security need to
Client
In this option, it is assumed that the main SEER product already exists and is installed on a remote machine, typically
a networked server (see previous section). If not, the Client cannot complete the installation. This installation sets up
a user area on the local machine to manage client specific user settings. The client install registers the location of the
remote server installation on the client machine, so SEER can be invoked as an automation call from the remote
computer.
The remote installation is referenced and used for execution on the local PC. This “Client” install is not true
server/client architecture. The executable is read from the remote computer, but is loaded and executed from the
memory of the local PC. This isolates the CPU load to the local PC, minimizing the demands on the server. This
option is equally valid for one user or multiple users.
SEE ALSO:
CLIENT INSTALLATIONS
User Settings
User Settings
Product
Knowledge Base
Project Files
8
Pre-Installation Configuration Options
Before starting installation, there are some setup options you may wish to consider. You can configure how
Document files (Knowledge Bases, templates, project files, tools files, etc.) are installed, and configure the default
program paths and other settings.
Note. This type of customization is typically done before distributing SEER out to a group of
users.
Document Files
The default installation configuration will install a complete set of Document files into the chosen installation
directory. If you have additional and/ or custom document files that you would like to include with the new
installation, you may copy them into the respective Document folders before installation:
[INSTALLATION FILES PATH] Comments
\DOCUMENTS\EXPORT TEMPLATES
Copy custom Export Template files into the Export Templates Folder.
\DOCUMENTS\KBASES
Copy custom KBase files into the Kbases Folder.
\DOCUMENTS\PROJECTS
Copy custom Project files into the Sample Projects Folder.
\DOCUMENTS\SCENARIOS
Copy custom Scenario files into the Scenarios Folder.
\DOCUMENTS\TOOLS
Copy custom Tools files into the Tools Folder.
You can modify the [INSTALLER FILES PATH]\SETUP.INI file to customize how custom document files are to be
installed.
SETUP.INI
Options
CustomAppData
ON = Will only install files from the AppData folder, no additional Application
Data files will be installed from the Data1.CAB file.
OFF [default setting] = Will install files from the Data1.CAB file, and any additional
files in AppData folder.
9
CustomExportTemplates
ON = Will only install files from the Documents\Export Templates folder, no
additional Export Template files will be installed from the Data1.CAB file.
files in Documents\Export Templates folder.
CustomKbases
ON = Will only install files from the Documents\Kbases folder, no additional
KBase repository files will be installed from the Data1.CAB file.
files in the Documents\Kbases folder.
CustomProjects
ON = Will only install files from the Documents\Projects folder, no additional
Sample Project files will be installed from the Data1.CAB file.
files in Documents\Projects folder.
CustomScenarios
ON = Will only install files from the Documents\Scenarios folder, no additional
Scenario files will be installed from the Data1.CAB file.
files in Documents\Scenarios folder.
CustomUtilities
ON = Will only install files from the Documents\Tools folder, no additional Tools
files will be installed from the Data1.CAB file.
files in Documents\Tools folder.
Caution. It is essential to keep track of your installation type and options, especially for future upgrades. Any
time the default settings are used in an install, the latest Data1.CAB files will always be installed. Hence, if
you wish to maintain only a subset of your custom files in these document folders, you need to always set the
Custom settings ON.
Help Files
The default installation configuration will install a complete set of Help files into the chosen installation directory. If
you have custom html help files that you would like to be installed, you may copy the html help files into the
respective Help and/or ParameterHelp folders. Your custom help files will overwrite the default SEER help html
files.
\HELP
Copy custom Help files into the Help folder.
\PARAMETERHELP
Copy custom Parameter Help files into the ParameterHelp folder.
AppData
The default installation configuration will install the default SEER-SEM SETTINGS.INI from the DATA1.CAB file. If
you want to configure the SEER-SEM SETTINGS.INI before installation you need to:
a) Modify the [INSTALLER FILES PATH]\SETUP.INI by changing the CustomAppData flag to ON.
b) Modify the SEER-SEM SETTINGS.INI in the [INSTALLER FILES PATH]\APPDATA folder.
Caution. If you set [FIRST-TIME-INIT-AND-UPGRADES] conditions, be sure they match the type of
install you plan on using. For Local installs, all options are typically set to 1. For Server and Client installs,
all options are typically set to 0.
[INSTALLATION FILES PATH] Comments
10
Local Installations
Choose this option to install all aspects of SEER-SEM onto a single machine.
Quick Install Process
1.
2.
3.
4.
Start the SETUP.EXE file
Choose the Local option
Choose an installation directory (default = c:\Program Files\SEER\SEER-SEM X.X)
The installation package manages the entire process, once completed you can begin using SEER.
Detailed Information
During the installation process, the installer installs all the necessary application files, configures ODBC connections,
writes registry settings, and creates start menu short cuts. The following details explain the entire installation
process, and what happens during first time initialization of the SEER application.
SEE ALSO:
OTHER TECHNICAL INSTALLATION DETAILS
11
Default Installation Configuration
The default configuration of a local installation is to install all files into the chosen installation directory. When a user
logs onto the machine and runs SEER, SEER will copy a complete set of Application Data and Document Data files to
the user’s local profile.
Each user that runs SEER on the machine will get their own set/copy of Application Data and Document Data
files during first time initialization. By default each user will use his own set of Application and Document data. This
may or may not be preferable. Administrators can configure the SEER application so that all users share a common set
of Application Data and Document Data files (see details below).
Galorath recommend that multiple users share a common set of Application Data and Document Data files to
promote consistency when developing estimates and sharing models.
SEE ALSO:
APPENDIX – SEER-SEM 8.2 FILE MANIFEST
Application Data and Document Data Files
Application and Document Data are files that the application and/or users configure or write too. By default,
SEER insures that each user gets a set of these files copied to a user writable location.
Application Data and Document Data files are installed in the chosen installation directory in the respective AppData
and Documents directories i.e.
[installation directory]\SEER\SEER-SEM X.X\AppData\
[installation directory]\SEER\SEER-SEM X.X\Documents\
Projects
Scenarios
Tools
Export Templates
KBases
SEER-SEM Sample Projects to learn from
SEER-SEM Sample Scenarios to learn from
Extra Utilities, PDF copies of release notes, user guide etc.
Flexible Export Templates
SEER-SEM Knowledge Bases
Document Data includes the following Directories and files.
Item
Files
12
Application Data files include the following files.
Files
Notes
SEER-SEM Data.INI
SEER-SEM Settings.INI
User Settings file. This is a unique file for each user. It is used to store user
application preferences (e.g., font sizes, project parameter settings, paths, etc.)
SEER-SEM Tags.INI
SEM-ACTNAMES.INI
SEM-LABCATNAMES.INI
SEM-LANGTABLE.INI
views.ini
First Time Initialization
During first time initialization of SEER, SEER creates a local user profile, and copies the Application Data and
Document Data from the installation directory to the Local User SEER profile. This insures all users have full read
and write privileges to SEER related files.
Note. The installing user can configure the installed SEER-SEM Settings.INI file to change the default first time
initialization behavior (see Configuring SEER before first time initialization below).
Document Files are copied from the installation directory to the following location during first time initialization:
OS
Default Local User Document Files Path
7SP1/8/8.1/10
\Users\[USER NAME]\Documents\SEER\SEER-SEM X.X\
Application Data Files are copied from the installation directory to the following location during first time
initialization:
13
OS
Default Local User Application Data Files Path
7SP1/8/8.1/10
\Users\[USER NAME]\AppData\Local\SEER\SEER-SEM X.X\
Configure SEER so all Local Users Share a Common Data Set
If there are multiple local users, or multiple users on a single machine, the SEER-SEM SETTINGS.INI file can be
configured to point to a shared set of Application Data and Document files.
Configuring SEER before installation
See Pre-Installation Configuration Options.
Configuring SEER before first time initialization
Remember, during first time initialization, the SEER-SEM SETTINGS.INI file is copied from the installation directory
to the local user application data folder. If it is configured before first time initialization, then all users that later run
SEER, will start with the same exact configuration.
1. Copy Document and Application Data files from the installation directory to a location that all future users
will have read and write access to.
Note. Application Data files must be treated as a set and stored in the same folder location.
2. Configure the [PATHS] section of the installed SEER-SEM SETTINGS.INI file to point to the new application
data and document locations.
3. Configure the [FIRST-TIME-INIT-AND-UPGRADES] section of the installed SEER-SEM SETTINGS.INI file.
Configuring SEER after first time initialization
1. Admin should copy the Document and Application Data files from the installation directory to a location
that all users have read and write access to.
2. Each local user then needs to configure their [PATHS] section of the SEER-SEM SETTINGS.INI file to point
to the new application data and document locations, this is most easily accomplished through the SEER
application:
a. From the SEER Options menu, select ‘Set Paths’ – browse to the shared Application Data and
Document data.
b. From the SEER Options menu, select ‘Save Configuration’ to store the path information in the
local user SEER-SEM SETTINGS.INI file.
14
Server Installations
All files are installed onto the Server. The SEER application is then typically executed from a remote computer either
through a Client install (see below), or through a thin client application such as Citrix.
1.
2.
3.
4.
5.
6.
Choose the Server option
Choose an installation directory (default = c:\Program Files\SEER\SEER-SEM X.X)
The installation package manages the entire process
Provide Write access to the AppData and Document data folders
Distribute the SEER Client installer
During the installation process, the installer installs all the necessary SEER application files, configures ODBC
connections, writes registry settings, and creates start menu short cuts on the server. The following details explain
the entire installation process, and what happens during first time initialization of the SEER application.
SEE ALSO:
OTHER TECHNICAL INSTALLATION DETAILS,
Start
Setup.EXE
Choose Server
Choose Server
Installation
Directory
15
Files Installed
ODBC
Connections
Registry Settings
Start Menu
Short Cuts
[OPTIONAL]
Admin
Configures SEER
for Clients
The default configuration of a SERVER INSTALLATION is to install all files into the chosen installation directory. If you
run the SEER application on the server, then it will operate just the same as a local installation (see Local Installations
above).
By default, a Server install is configured such that all Client/Remote SEER users connecting through a network or via
a thin client interface such as CITRIX will get a unique copy of the SEER-SEM SETTINGS.INI file.
The SEER-SEM SETTINGS.INI file is a unique file for each user. It is used to store user application preferences e.g.
font sizes, colors, project parameter settings, paths etc.
The SEER-SEM SETTINGS.INI file is installed on the server in the following location:
[server installation directory]\SEER\SEER-SEM X.X\AppData\SEER-SEM Settings.INI
During first time initialization of SEER, SEER copies the SEER-SEM SETTINGS.INI file from the server to the
following location for each Client/Remote user:
SEE ALSO:
CLIENT INSTALLATIONS
OS
Client User Application Data Files Path
7SP1/8/8.1/10 \Users\[USER NAME]\AppData\Roaming\SEER\SEER-SEM X.X\
For client/server configurations, the Roaming user application data location is used. This insures that the SEERSEM SETTINGS.INI file will roam with the user if required to do so.
Server Application Data and Document Data Files
By default, all Client/Remote users point to and use the Application Data files and Document Data files installed on
the server.
Administrators should insure that CLIENT USERS HAVE WRITE ACCESS to the Application Data and Document Data
folder on the Server.
These locations may be configured via the SEER-SEM Settings.INI. See next section for details.
The Application Data and Document folders are installed on the server in the following locations:
[server installation directory]\SEER\SEER-SEM X.X\Documents\
By default, Client/Remote users will not get copies of Application Data or Document files copied to their
machine or any user profiles on the server. Administrators may choose to reconfigure this via the SEER-SEM
SETTINGS.INI. See next section for details.
[server installation directory]\SEER\SEER-SEM X.X\AppData\
16
SEER-SEM Settings.INI Client Configuration
The SEER-SEM SETTINGS.INI file is a unique file that gets copied to each user’s roaming profile during first time
initialization of SEER. It is used to store user application preferences e.g., font sizes, colors, project parameter
settings, paths etc.
Configuration of the SEER-SEM SETTINGS.INI file should be completed before remote/client first time
initialization of SEER.
1. Copy Document and Application Data files from the installation directory to a location that all
Client/Remote users will have write access.
2. Configure the [PATHS] section of the SEER-SEM SETTINGS.INI file to point to copies of the Application data
and Document data in another location on the server, or networked drive. You can use a drive letter path,
or a UNC path.
Insure that paths end with a back slash.
3. [OPTIONAL] Configure the [DEFAULT-PATHS-AND-UPGRADES] table with respect which data you
would like SEER to copy for each Client/Remote user (default is set to not copy data).
Crystal Reports Compatibility for Windows Server & Citrix
The version of Crystal Reports that is included with SEER-SEM is not compatible with Windows Server and Citrix.
If you are installing SEER-SEM on either of these operating systems, then you need to upgrade to Crystal Reports XI.
The Crystal Reports XI setup is available for download from our Internet Distribution site. Please contact technical
support for download information.
1. Run CrystalReportsXI_RuntimeSetup.msi.
2. Depending on the SEER-SEM installation type, replace the crpe32.dll file with the one installed during the
Crystal Reports XI setup. For a Server installation, replace the crpe32.dll file in the SEER-SEM program
directory. If the default location was selected, this would be C:\Program Files\SEER\SEER-SEM X.X.
17
Client Installations
Individual user settings, shortcuts and links to the networked server are setup on the local machine. The SEER
executable, export templates, knowledge bases, project files, etc. remain are on a networked server.
Start
Setup.EXE
Choose Client
Choose Server
Installation
Directory
ODBC
Connections
Registry Settings
Start Menu
Short Cuts
Run SEER
SEER copies SEER-SEM
Settings.INI from
Server
Server
Installation
Start First Time
Initialization
Settings.INI
copied to User
Roaming App
Data
1.
2.
3.
4.
Choose the Client option
Link to SEER-SEM installed on a Networked Server
The installation package manages the entire process, once complete you can begin using SEER.
During the installation process, the installer configures ODBC connections, writes registry settings, and creates start
menu short cuts. The following details explain the entire installation process, and what happens during first time
initialization of the SEER application.
SEE ALSO:
OTHER TECHNICAL INSTALLATION DETAILS,
18
The default configuration of a Client installation is to configure ODBC connections, set registry values, and create a
start menu shortcut. When the Client first runs SEER, SEER is configured to only copy the SEER-SEM SETTINGS.INI
file to the Client roaming application data location.
Client/Remote User First Time Initialization
During first time initialization of SEER, SEER creates a user profile, and copies the SEER-SEM SETTINGS.INI file to
this profile. This insures all Client users have a unique file for setting the SEER application interface in a way that suits
them e.g., font sizes, colors, default reports etc.
The SEER-SEM SETTINGS.INI file is copied by SEER to the following location:
OS
Client User Application Data Files Path
7SP1/8/8.1/10 \Users\[USER NAME]\AppData\Roaming\SEER\SEER-SEM X.X\
Silent Installations
An advanced command line installation option is available. For details about command line installations, including
SEER-SEM specific Configuration Properties, see the Command Line Installation section in the Appendix.
If your installer does not include a license file because you are between renewals or you downloaded the installer
from the Internet Distribution site, you must put a copy of the most current license in the installer directory in order
for a silent installation to work. During a regular installation, the installer will ask for the location of the license if
one is not found with the installer. During a silent installation, the installer silently aborts if no license is found in the
installer directory.
From the RUN COMMAND DIALOG:
Default Local Installation
No Properties need to be set to do a default Local installation:
"<path to installer directory>\setup.exe" /s /v/qn
19
/s is the silent switch for setup.exe. It suppresses setup.exe’s splash screens. /v is the MSI switch for setup.exe,
which passes the /qn MSI silent switch to the “SEER-SEM X.X.msi” installation session.
Since no Properties are being defined in the /v switch, the installer will install SEER-SEM in “C:\<Program
Files>\SEER\SEER-SEM X.X”. The setup type will be “Local” rather than “Server” or “Client”.
Client Installation
The two critical Properties to set for a Client installation are SETUPTYPE and NETWORKPATH.
"<path to installer directory>\setup.exe" /s /v"SETUPTYPE=Client
NETWORKPATH=\"\\SERVER\SEER-SEM\" /qn”
Note: Administrators who are “pushing” a Client installation to numerous other users’ computers will want to use the
UNC (universal naming convention) path in order to avoid conflicts that may result from different users mapping the
network share to different drive letters. Since the directory in the Network install example above has been shared as
“\\SERVER\ SEER-SEM”, Client installation can set
NETWORKPATH=\"\\SERVER\SEER-SEM\"
For more details and installation options, see the Command Line Installation section in the Appendix.
Other Technical Installation Details
Registry Settings
During installation modifications are made to the computer registry settings. The settings vary slightly depending on
the installation type and are noted below.
32 bit Operating Systems:
Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Galorath\SEER-SEM
Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Galorath\SEER-SEM
Name
Data
Path
If a LOCAL/SERVER INSTALL, this will point to the installation directory specified.
If a CLIENT INSTALL, this will point to the Server location of SEER.
ProjectMinerDBPath
If the ProjectMiner option is included in the Edition, this will point to the location of
the Estimating Library database.
Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Galorath\SEER-SEM\X.X
Where X.X is used denote the product version.
Name
Data
InstallDir
This will point to the installation directory specified
InstallerVersion
X.X.X
NetworkPath
IF LOCAL/SERVER INSTALL, this will point to the installation directory specified.
IF CLIENT INSTALL, this will point to the networked server location of SEER-SEM.
Path
IF LOCAL/SERVER INSTALL, this will point to the installation directory specified.
IF CLIENT INSTALL, this will point to the networked server location of SEER-SEM.
Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Galorath\SEER-SEM\X.X
20
ReleaseName
SEER-SEM Configuration (General or Commercial)
SetupType
IF Local Install = Local
IF Client Install = Client
IF Server Install = Network
Start Menu Short Cuts
The installer creates a Start Menu short cut to the SEER application. The shortcut is installed in the following
location:
OS
Installed Start Menu Shortcuts
7SP1/8/8.1/10 \ProgramData\Microsoft\Windows\Start Menu\Programs\SEER\SEER for
Software\SEER for Software X.X\SEER for Software X.X
For Client installations, the start menu shortcut will point to the SEER application installed on the server.
In a Windows Terminal Server environment, where users have roaming profiles, administrators may need to
create or add to any user log on scripts. The script should copy the SEER start menu shortcuts and merge them into
the user roaming profile as they log onto the server.
ODBC Settings
During installation several System DSN connections are created. Each of these is described in the table below.
ODBC Location: C:\Windows\system32\odbcad32.exe
ODBC Location: C:\Windows\SysWOW64\odbcad32.exe
21
System DSN Name Type
Description
PUBLDATA
Used with the Publish/Export Report features in SEER. Each time this
feature is used, a PUBLDAT#.TXT file is created/modified in the
Local or Roaming user application data folder (see Local and Server
installations above).
Microsoft Text
Driver (*.txt;
*.csv)
Crystal Report DLLs
During Installation, SEER uses a crystal report merge module to install files needed to run crystal report features. A
list of the files and versions of these files are described below:
For Server installations, a copy of crystal report dll files are also installed in the SEER installation directory. This
set is installed to insure that Clients/Remote users can successfully use the crystal report features within SEER.
Filename
Path
Version
Notes
crpe32.dll
exlate32.dll
implode.dll
MSVCRT20.DLL
odbc32.dll
odbccp32.dll
odbcint.dll
p2sodbc.dll
pg32.dll
crxf_pdf.dll
u2ddisk.dll
u2dmapi.dll
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\System32
\Windows\Crystal\
\Windows\Crystal\
\Windows\Crystal\
8.5.0.217
8.5.0.217
1.0.0.1
2.12.000
3.520.4403.2
3.520.4403.2
3.520.4403.2
8.5.0.72
1.0.011
8.5.0.37
8.5.0.1
8.0.0.0
u2dpost.dll
\Windows\Crystal\
8.5.0.61
8.5.0.77
5.0.0.0
8.5.0.98
8.5.0.92
8.5.0.99
8.5.0.144
Interface to crystal report engine
Misc
32-bit required runtime file
MFC Runtime library
MS ODBC Driver Manager
MS ODBC Installer
MS ODBC Resource DLL
CR Physical Server DLL for ODBC
Presentation Graphics
Export to PDF Format
Export Destination - Disk File
Export Destination - MAPI (MS Mail, MS
Exchange)
Export Destination - (MS Exchange Public
Folders)
Export Format - HTML
Export Format - Rich Text
Export Format - Text
Export Format - MS Word
Export Format - MS Excel
Special Installation
8.5.0.35
Special Installation
u2fhtml.dll
u2frtf.dll
u2ftext.dll
u2fwordw.dll
u2fxls.dll
crtslv.dll
\Windows\Crystal\
\Windows\Crystal\
\Windows\Crystal\
\Windows\Crystal\
\Windows\Crystal\
\Program Files\Seagate
Software\Shared\
ExportModeller.dll \Program Files\Seagate
Software\Shared\
Disc Space Sizing
As a rough sizing guide we provide the following example. This can be used to help plan what project file storage
space is required either on your PC or on a Server.
Storage requirements for SEER-SEM can be measured by the number of projects that will be planned with SEERSEM. Given the following scenario:
Typical project size = 100 elements
SEER-SEM element size ≈ 70K
Number of projects per year = 1000
Disc Space Required = 100 * 70K * 1000 = 7,000,000K ≈ (6836MB)
Of course, these assumptions can be fine tuned to your organization.
Disc space sizing varies enormously with the amount of users, the amount of files created, and the type of data used to
create files.
22
Repair/Remove Installation
You can invoke the Repair/Remove installation dialog via the operating system Control Panel:
Programs and Features option in 7SP1/8/8.1/10
Options
Description
Repair
Choosing this option will proceed to reconfigure ODBC connections, registry settings,
Start Menu Short cuts, and reinstall AppData and Document data files in the original
installation directory.
Note. This will not update individual user copies of AppData and Document
data which were copied by SEER during first time initialization.
Remove
Choosing this option shall proceed to




remove all files that were installed by the installer.
remove ODBC connections set by the installer.
remove registry entries set by the installer.
remove start menu short cuts.
Note. This will not remove individual user copies of AppData and Document
data which were copied by SEER during first time initialization.
The remove option will cycle through all user profiles on the machine where SEER
was installed and remove the SEER-SEM SETTINGS.INI file. This insures that should the
installer be rerun, each user will get a new SEER-SEM SETTINGS.INI file.
The remove option will not remove SEER-SEM SETTINGS.INI files from Roaming
profiles.
Upgrade Installation
Periodically you will receive information about a new version of SEER, along with information on how to get the
latest installation files. Upgrades may be minor or major depending on the content of the update.
23
Minor Upgrades
Minor upgrades occur more frequently than major upgrades. Typically the program will contain updates to exiting
processes and/or program features. To begin the upgrade process:
1. Log on with administrative privileges
2. Locate and Start the SEER-SEM SETUP.EXE file
3. The installation package manages the entire process, once complete you can begin using SEER.
The minor upgrade installation process assumes all settings of the initial/previous installation.
After upgrade installation is complete, and the next time SEER is run, SEER begins an upgrade initialization process.
During this process, SEER copies updated document files (such as release notes) from the installation directory to the
local user document location. SEER upgrades/copies files according to the settings defined in the [FIRST-TIMEINIT-AND-UPGRADES] table of the installed SEER-SEM Settings.INI file.
During upgrade initialization user copies of Application Data files are preserved. Thus, all/any customizations in
the application data files are retained.
Major Upgrades
Major upgrades occur less frequently than minor upgrades. Major upgrade versions may be installed along side
existing installations of SEER. Thus, users can if they wish, have multiple major versions of SEER installed on a single
machine. A major install is a completely new install so all of the available installation options described in this guide
are available to choose from.
You can begin a major upgrade and use a currently installed license from another major installation. During the
installation process, you will be asked to point to the location of your currently installed SEER version. The installer
will make a copy and use this license file for the major upgrade.
24
Installation FAQ
Q:
What is involved in installing and maintaining SEER Applications on a Server?
A:
The SEER applications are end-user business applications that require a Wintel-standard PC running on
Microsoft Windows (i.e. Windows 7SP1, Windows 8). The applications are distributed as a collection of
executable files (.exe) and dynamic link libraries (.dll) and other supporting data and user files.
Installation involves a standard process that places program and data files in the appropriate places, sets up
user program menus, and takes care of program registration. Removing the program involves a similar
uninstall process.
Use of SEER-SEM results in the creation of one or more project files, which can be accessed locally or
shared across a network. With respect to network resources, the SEER applications resemble spreadsheet or
word processing applications rather than large client-server or transaction processing applications. They can
be run from an application server or as standalone applications on a client machine.
25
Q:
Do the SEER applications require any unique or extreme resources from the network or user
workstations?
A:
No. We make every effort to ensure that SEER applications conform to the general guidelines and
recommendations specified by Microsoft. Each application will run well in under 256 MB of RAM. At least
96 MB of disk space and 256 MB of RAM are required. For optimal use, at 512 MB of RAM or higher is
recommended.
Q:
As a network administrator, what are my choices when deploying SEER applications?
A:
You have a great deal of flexibility as to how your organization uses SEER applications. Install a single copy
of each application on each workstation for the ultimate in performance and total elimination of network
traffic. If you want to centralize administration and maintenance of the applications, you can install them on
an application/file server. For network installations, a workstation setup routine must be run from each
client machine to install required system files to the local workstation.
Q:
My organization has offices throughout the world. What type of configuration would you suggest?
A:
To achieve a balance between having to keep track of multiple copies of the applications and having to rely
on wide area communication links, we suggest that you install one copy of SEER at each office location, and
let the users run the program from the local area network. If you have 10 locations, then install on the 10
different sites and let the users run locally.
Q:
What about upgrades and maintenance? What should we expect with respect to having to redeploy bug fixes and upgrade releases?
A:
To minimize the overhead involved in upgrading and re-deploying our applications, Galorath has adopted
the following strategies:
Project files from previous versions of SEER are now automatically upgradeable. That means that users will
be able to preserve their custom settings, presentations.
An upgrade installation of a SEER application requires that you have that SEER application installed with a
current license. Depending on the type of upgrade, the install process will do one of two things.
For minor updates, the installer automatically detects the existing installation and updates it.
For major upgrades, the installer will ask you for the location of the previous version of SEER and use
license information contained in the earlier SEER version. After you have installed the new version, you
may uninstall the earlier version.
Updates can be downloaded from our web site support area.
Q:
As a network administrator, will I be getting a lot of support calls about use and functionality of
the SEER applications?
A:
The SEER applications feature on-line help and built in links to the Galorath web site (www.galorath.com)
as well as the ability to e-mail support staff at Galorath. In addition to the normal telephone support and inclass training Galorath provides, these features should go a long way in directing users to take advantage of
the proper resources at Galorath. A link to the help list of Frequently Asked Questions is also built into the
SEER applications.
If you want to contact Galorath Incorporated for technical support or any other reason, we can be reached
at:
Phone: (310) 414-3222
(310) 414-3220
Email: [email protected]
WWW: http://www.galorath.com
http://support.galorath.com (password required, registration is free)
Please have your serial number ready for technical support. This serial number is found in the Help / About
dialog box.
A Technical Notes library found on our web site reflects ongoing research and program development, and
provides more detailed and theoretical explanations of various aspects of the program. Individual articles are
available upon request, without charge.
FAX:
26
27
Q:
What about sharing of files?
A:
The SEER applications allow you to email project files to other users or to store them on a network
directory. If you are building custom knowledge bases, it is recommended that they are stored in a common
area accessible to all users. Users may specify the location of the knowledge base files in the program under
Options/Set Paths. Project files may be shared in a similar way.
Q:
What kind of Setup program do you employ?
A:
All of the Setup programs we use were developed with InstallShield, so they have a very common look and
feel for users, and work well with the various file systems and configurations in existence today.
Q:
Do your programs work with Windows 8 / 8.1 / 10?
A:
Yes, all of our applications are tested on 7SP1/8/8.1/10.
Q:
Do your programs work with older operating systems such as NT and 2000?
A:
All of our applications were built from the ground up on Windows NT and 2000 under a network
environment. However, we are no longer developing or testing on these operating systems.
Appendix – SEER-SEM 8.2 File Manifest
During Local and Server installs, the following files are installed into the chosen installation directory.
AppData
Documents
Help
ParameterHelp
Activity.rpt
ACTUALS.DAT
ADDFROMREPOSITORYLib.dll
BasicEst.rpt
Converter.exe
converter.mpt
CopyConfig.CDB
CostbyLb.rpt
CostFYD.rpt
CostFYM.rpt
Custom1.crf
Custom1.exe
Custom1.rpt
Custom2.crf
Custom2.exe
Custom2.rpt
Custom3.crf
Custom3.exe
Custom3.rpt
Custom4.crf
Custom4.exe
Custom4.rpt
Defaults.txt
DevCostM.rpt
DevHrsM.rpt
DtlStafM.rpt
ETC.rpt
FLDDEFS.DAT
Gsw32.exe
Notes
Folder contains all APPDATA files (see below for list of
AppData files)
Folder contains all DOCUMENT folders and files (see below
for list of all Document files)
Folder contains all help files
Folder contains all parameter dialog help files
[Installation Path]\SEER\ SEER-SEM 8.2\
Filename
28
29
Gswag32.dll
Gswdll32.dll
IDToHtmMap.xml
InpNote.rpt
Interop.SEER_SEM.1.1.dll
License_SEER-SEM.lic
LTCLR13n.dll
LTDIS13n.dll
ltefx13n.dll
ltfil13n.DLL
ltimg13n.dll
ltkrn13n.dll
LVKRN13N.DLL
normprob.db
OUT_0000.FLX
OUT_0001.FLX
OUT_0002.FLX
OUT_0003.FLX
OUT_0004.FLX
OUT_0005.FLX
OUT_0006.FLX
OUT_0007.FLX
OUT_0008.FLX
OUT_0009.FLX
OUT_0010.FLX
OUT_0011.FLX
OUT_0012.FLX
OUT_0013.FLX
OUT_0014.FLX
OUT_0015.FLX
OUT_0016.FLX
OUT_0017.FLX
OUT_0018.FLX
OUT_0019.FLX
OUT_0020.FLX
OUT_0021.FLX
OUT_0022.FLX
OUT_0023.FLX
OUT_0024.FLX
OUT_0025.FLX
OUT_0026.FLX
OUT_0027.FLX
OUT_0028.FLX
OUT_0029.FLX
OUT_0030.FLX
OUT_0031.FLX
OUT_0032.FLX
OUT_0033.FLX
OUT_0034.FLX
OUT_0035.flx
OUT_0036.flx
OUT_0037.flx
OUTDEFS.DAT
PerHrsLb.rpt
PerMonLb.rpt
ProjectMiner.dll
ProjectMiner.udl
PUB_CW1.FLX
PUB_CW2.FLX
PUB_EP1.FLX
PUB_EP2.FLX
PUB_FALA_NAMES_CW.FLX
PUB_FALA_NAMES_EP.FLX
PUB_FALA_NAMES_SW.FLX
PUB_INCC.FLX
PUB_INCO.FLX
PUB_INCP.FLX
PUB_INCU.FLX
PUB_INEC.FLX
PUB_INEO.FLX
PUB_INEP.FLX
PUB_INEU.FLX
PUB_INSC.FLX
PUB_INSO.FLX
PUB_INSP.FLX
PUB_INSU.FLX
PUB_MC1.FLX
PUB_ME1.FLX
PUB_MONTECARLO_CW.flx
PUB_MONTECARLO_EP.flx
30
31
PUB_MONTECARLO_SW.flx
PUB_MS1.FLX
PUB_SW1.FLX
PUB_SW2.FLX
PUB_YC1.FLX
PUB_YC2.FLX
PUB_YE1.FLX
PUB_YE2.FLX
PUB_YS1.FLX
PUB_YS2.FLX
QuickEst.rpt
RDRisk.rpt
RMRisk.rpt
RSRisk.rpt
SampleIn.txt
schema.ini
SEER.Common.dll
SEER.Common.dll.config
SEER.DAC.ClrWrappers.SeerDb.dll
SEER.DAC.CppEmulators.DataAccessors.dll
SEER.DAC.CppEmulators.Entities.dll
SEER.DAC.CppWrappers.Entities.dll
SEER.DAC.DataAccessors.dll
SEER.DAC.DataAccessors.dll.config
SEER.DAC.Entities.dll
SEER.DAC.Entities.dll.config
SEER.DAC.Errors.dll
SEER.DAC.Errors.dll.config
SEER.DAC.Security.dll
SEER.DAC.UI.dll
SEER.DAC.UI.dll.config
seer_rnk.dll
SeerDataObjects.dll
SeerDb.dll
SeerDbDll.dll
SEER-SEM Properties.INI
SEERSEM.exe
seer_sem.tlb
SEM_32 DLL.dll
SEM_32 DLL_SA.dll
SEMProjectAssistant.dll
SEMProjectAssistantLegacy.dll
SizeMetricGenerator.exe
StatComp.dll
ZedGraph.dll
[Installation Path]\SEER\ SEER-SEM 8.2\AppData
Filename
Notes
SEER-SEM Data.INI
SEER-SEM Settings.INI
SEER-SEM TAGS.INI
SEM-ACTNAMES.INI
SEM-LABCATNAMES.INI
SEM-LANGTABLE.INI
views.ini
Activity Cost By Fiscal Year - COSTS.flx
Activity Cost By Fiscal Year - DATES.flx
actvhour.flx
actvsch.flx
BASICEST.FLX
COPYFORSEERIT.FLX
COPYFORSEERITWITHINSERT.FLX
COSTBYFY.FLX
Defects.FLX
details.flx
ENTERPRI.FLX
ETC.FLX
FBSINPUT.FLX
fpcntnew.flx
fpcount.flx
Goals.FLX
inp-tech.flx
INPUTS.FLX
laborcst.flx
laborhrs.flx
[Installation Path]\SEER\ SEER-SEM 8.2\Documents\Export Templates\
Filename
Notes
32
33
Maintenance Effort By Year.FLX
Maintenance.FLX
MANT-CST.FLX
MANT-HRS.FLX
MSProj Basic.FLX
msproj.flx
PARAMSUM.FLX
PMC_Outputs.FLX
prjsched.flx
Properties.FLX
QUICKEST.FLX
Risk Analysis all elements.flx
Risk Analysis.FLX
RISKDATA.FLX
SEI.FLX
size-all.flx
sizeline.flx
size-ufp.flx
SoftwareMetrics.FLX
STAFFDET.FLX
STAFFTOT.FLX
sumbasic.flx
sumcost.flx
V_CostSummary.FLX
V_CostSummaryReport.FLX
V_KbaseSelections.FLX
V_LaborHoursByActivity.FLX
V_Project Properties.FLX
V_ProjectHoursByActivity.FLX
V_ProjectQuickEstimate.FLX
V_ReqsSummary.FLX
V_SeiDrivers.FLX
V_SysITSummary.FLX
[Installation Path]\SEER\ SEER-SEM 8.2\Documents\PROJECTS\
Filename
Notes
Agile Sample - OTB
eHandicapper.PRJ
Building an Agile Estimate.PRJ
COTS and Custom Sample - CIPU
Custom Apps and Package
Customizations.PRJ
COTS Samples.PRJ
Data Warehouse Sample - Marketing
Analytics Package.prj
ERP Example.PRJ
Illinois Outreach.PRJ
OUTSIDE.PRJ
SAP BPC Implementation.PRJ
TACTICAL.PRJ
TaxSystemAccountReporting.PRJ
trading.prj
WATCHER.PRJ
Web Development Sample Customer Facing Web Portal.prj
Not included in SEER-SEM Commercial Configuration
Spacecraft Sample.cdx
Spacecraft Sample.dbf
Spacecraft Sample.fpt
Spacecraft Sample.PRJ
Tactical Simulation Template.cdx
Tactical Simulation Template.dbf
Tactical Simulation Template.fpt
Tactical Simulation Template.PRJ
Trading Regions.cdx
Trading Regions.dbf
Trading Regions.fpt
Trading Regions.PRJ
Web Server.cdx
Web Server.dbf
Web Server.fpt
Web Server.PRJ
[Installation Path]\SEER\ SEER-SEM 8.2\Documents\Tools\
Filename
Notes
Activity Cost By Fiscal Year Report.xlsm
[Installation Path]\SEER\ SEER-SEM 8.2\Documents\SCENARIOS\
Filename
Notes
34
Class Knowledge Base Definitions.doc
CompPHPM.xls
Data Collection Form.xls
Parametric Project Monitoring and Control
Users Guide.pdf
PARAMSUM.XLS
PMC Reuse Efficiency Worksheet.xlsx
PMC Worksheets.xls
ProjectMiner Users Manual.pdf
Proxy Definitions.doc
SEER for Software User Guide.pdf
SEER for Software 8.2 Release Notes.pdf
SEER-SEM Detailed Reference.pdf
SEER-SEM Estimate to Complete.xls
SEER-SEM Input worksheet.xls
SEER-SEM Rework Percentages.xls
SEER-SEM Server Mode Details.xls
SEER-SEM View Creator Template.xls
SEER-SEM Worksheets.doc
SEER-SEM Worksheets.pdf
SEMacros.xls
[Installation Path]\SEER\ SEER-SEM 8.2\Documents\KBases\
Filename
Notes
35
!NOKNOWL.APP
!NOKNOWL.CLS
!NOKNOWL.cot
!NOKNOWL.END
!NOKNOWL.MET
!NOKNOWL.PLT
!NOKNOWL.STD
_Des thru Tst Only.END
_Req Only.END
_System Test Only.END
~GENERAL.END
~NEW.END
1679IV-V.STD
2167A.STD
2167AFUL.STD
2167AMIN.STD
498-BUSI.STD
498-SUPP.STD
498-WEAP.STD
80Percent.CLS
ADADEV.MET
ADAFULL.MET
ADAINC.MET
ada-oo.met
AGILEFULL.MET
AGILENOVICE.MET
AI.APP
applet.app
applicat.cot
AVIONICS.PLT
Baseclasses.PRX
BasicAppComps.PRX
BUILD23.END
BusiMissCrit.PLT
BUSINESS.PLT
busitool.app
CAD.APP
casefull.met
CatalogueInventoryManagement.APP
classlib.COT
client.plt
CLIENTSR.PLT
Cloud.PLT
CMRCL-HI.STD
CMRCL-LO.STD
CODEGEN.MET
COMMAND.APP
COMMERSL.STD
CommonCriteriaEAL0.STD
COMMUNIC.APP
compmnt.cot
concept.END
CONVAUTO.END
36
37
CONVMANL.END
COSMIC.PRX
COSMIC_DM.PRX
COTSI&T.MET
CustomerRelationshipManagement.AP
P
DATABASE.APP
database.cot
DataConversion.END
DatabaseSystem.APP
datamine.app
dataware.app
DecisionSupportSystem.APP
desgnreu.END
DIAGNOST.APP
DO178BLevelA.STD
DO178BLevelB.STD
DO178BLevelC.STD
DO178BLevelD.STD
DO178BLevelE.STD
DO178CLevelA.STD
DO178CLevelB.STD
DO178CLevelC.STD
DO178CLevelD.STD
DO178CPDIF.PRX
DocumentManagement.APP
DOD7935.STD
driver.app
DWBI_Components.PRX
Early_Quick_FPs_BFC.PRX
Early_Quick_FPs_UBFC.PRX
electrnc.app
ElectronicDataInterchange.APP
Embedded.PLT
erp.plt
Euro Based Costing.CLS
EVOLVE.MET
ExecutiveInformationSystem.APP
FAA.STD
FBS.PRX
FINACIAL.APP
FINAPROC.PLT
FLIGHT.APP
FPCOUNT.PRX
framewrk.cot
GBP Based Costing.CLS
gencode.END
GRAPHICS.APP
GROUND.PLT
GrouSystNonCrit.PLT
GUI.APP
IEEE.STD
IEEE-EIA 12207.STD
IEEEFUL.STD
INCREMNT.MET
Industrial.PLT
int-asis.END
intconfg.END
INTERNET.PLT
isformal.std
ISO9001.STD
is-relax.std
j-016ful.std
j-016min.std
j-016nom.std
Japanese Yen Based Costing.CLS
legacy.cot
Logistics.APP
Mainframe.PLT
MAINTFUL.END
maintfulNewSys.END
MAINTMIN.END
maintminNewSys.END
MANNED.PLT
MATH.APP
mbd.END
MIS.APP
MIS-HI.STD
MIS-LO.STD
MISSILE.PLT
38
39
MISSPLAN.APP
MKIIFPA.PRX
Mobile Device.PLT
MOBILE.PLT
Modification.END
MOD-MAJ.END
MOD-MIN.END
MSGSWICH.APP
MULTIMED.APP
NetworkManagement.APP
NONE.MET
None.prx
NONE.STD
Object.prx
OFFICE.APP
OO-ALL.MET
OOD-OOP.MET
OPSYSTEM.APP
PROCESS.APP
proclibr.cot
PROTOTYP.MET
PURCHASE.MET
rad.met
RADAR.APP
REDOC.END
REENGMAJ.END
REENGMIN.END
REPTGEN.APP
ReverseEngineering.END
RHOSTMAJ.END
RHOSTMIN.END
RICEF.PRX
ROBOTICS.APP
RUPFull.MET
RUPLite.MET
salesforce.END
salesforce.plt
salvage.END
sap.plt
server.plt
No part of this document may be duplicated and/or made public by printing, photocopying, microfilm, audio, electronically or by any other means, and may not
be stored in a retrieval system without written permission of Galorath Inc
Although this document is produced with great care, Galorath Inc. may not be held responsible for any damage caused by mistakes or imperfections within.
Galorath Inc. reserves the right to make changes/modify this document from time to time.
Appendix – Command Line Installation
See next page.
SHIPBORD.PLT
SIGPROC.APP
SIMULATE.APP
SLOC.prx
SPICE.STD
SPIRAL.MET
storypoints.PRX
TELECOMM.PLT
TEST.APP
TOOLS.APP
Topclasses.PRX
TRAINING.APP
transact.app
TRIGGER.PRX
TRUST3.MET
Ufpcount.prx
UNMANNED.PLT
Use Case Points Summary.PRX
Use Case Points.PRX
Usecases.PRX
UTILITY.APP
VoiceProvisioning.APP
WATERFAL.MET
WEB-SITE.MET
WEBSITE.PRX
Workflow.APP
XPERTSYS.APP
40
Installing SEER-SEM 8.2
The SEER-SEM 8.2 installer is an InstallShield 2014 Basic MSI installer that uses Windows Installer
technology and the InstallScript language to perform custom installation actions.
Product Code:
Upgrade Code:
{B16471CC-AE45-4FB7-82CB-D2D32E9574D9}
{65DF4CC4-3B3A-4A5E-B58F-64C1BDFC01FB}
SEER-SEM comes in “edition” configurations that implement increasing complexity of the features
included. Activation of specific features is handled by your encrypted "License_SEER-SEM.lic" file. If
features you expect are not active, first check that you have the latest license file installed. Your license
file is downloaded separately from the installer as an archive file used to extract your license into your
SEER-SEM installer folder.
I. Basic Installation
A. Setup Requirements
SEER-SEM requires .NET 4.0, Microsoft Data Access Components (MDAC) 2.8, and Microsoft
Visual C++ 2013 Redistributable - x86 12.0.30501.0 in order to run correctly. If the SEER-SEM
installer detects that any of these items are not installed, it will first attempt to install them before
continuing with the SEER-SEM installation. These requirements are contained in executables in your
installer media that may also be run separately.
B. Initial Setup
Initial installation of SEER-SEM may be launched with its full user interface by clicking on either the
SETUP.EXE file or the SEER-SEM 8.2.MSI file in your installer media. Or you may launch initial
installation from the following command lines:
Setup.exe
"<installer directory path>\setup.exe"
Msiexec.exe
msiexec /i "<installer directory path>\seer-sem 8.2.msi"
Quotation marks are necessary when there are any spaces in paths or filenames.
The installation wizard will lead you through the process of installing SEER-SEM 8.2.
SEER Metrics Analysis & Benchmarking
Since all SEER-SEM editions contain SEER Metrics, SEER-HD (SEER Historical Database) will need
to be installed. SEER-HD is a database repository used by SEER Metrics and other SEER applications
like Estimate by Comparison and Microsoft Project Integration. If you are running the SEER-SEM
installer in fully visible graphic mode from your installer, the SEER-SEM installer should launch the
SEER-HD installer when it is through installing SEER-SEM.
If you are running the SEER-SEM installer silently, you will need to set "RunSEERHD=No" in the
installer's setup.ini and launch the SEER-HD installer separately.
Windows 7 and above OS Versions
In order to run silent installation on a Windows 7 and above
operating system, you need to run the DOS command prompt
with elevated Administrator privileges in order to prevent the
UAC (User Access Control) dialog from appearing.
Normally Systems Administrators perform silent installation,
but if you wish to run silent installation on your local
machine, you can browse to All Programs  Accessories on
your Start Menu, right click on the DOS Command Prompt
and select “Run as Administrator,” and then enter the silent
command line.
Note: You should always run an MSI installer on the
machine on which you are installing the particular program.
Windows Installer makes extensive registry entries, and it is
problematic to have those installation records on a different
machine than the installed software.
C. Upgrade
Setup.exe
No special action needs to be taken when you are upgrading SEER-SEM 8.2 using Setup.exe in full
user mode. The installer will update your program’s files, shortcuts, etc. It will NOT, however,
change the setup type (Local, Client, or Network) or automatically install features that you deselected
at the time of first installation. In order to change setup type, you must uninstall and reinstall the
program. In order to reconfigure features, you must use the installer's command line (see below).
"<installer directory path>\setup.exe"
Msiexec.exe
MSI databases (“SEER-SEM 8.2.msi”) require special command line settings for upgrading. Hence
we normally recommend using Setup.exe as the easiest upgrade option for basic installations.
msiexec /i "<installer directory path>\seer-sem 8.2.msi" REINSTALL="ALL"
REINSTALLMODE="vomus"
For further explanation of reinstall mode, see upgrade topics under the advanced section below.
D. Uninstall
SEER-SEM 8.2 may be uninstalled from its user interface by selecting the Control Panel’s
Add/Remove Program applet’s “SEER-SEM 8.2” entry and clicking the “Uninstall” button.
From the command line, SEER-SEM 8.2 may be uninstalled using the /x switch of either Setup.exe or
Msiexec.exe:
Setup.exe
“<installer directory path>\setup.exe” /x
Msiexec.exe has two options:
msiexec /x “<installer directory path>\seer-sem 8.2.msi”
msiexec /x}{B16471CC-AE45-4FB7-82CB-D2D32E9574D9}
{B16471CC-AE45-4FB7-82CB-D2D32E9574D9}is the SEER-SEM 8.2 “product code,” a unique GUID
that MSI uses to store and retrieve all information about the program installation in your computer’s
registry. The nice thing about using it is that you need to have no other information to uninstall, but it is
very difficult to remember. The product code may be used with command line switches only if the product
is already installed.
I. Advanced Command Line Installation
Installer Media Files
The following list of files in the installer media is intended to help you understand the various files in the
installer media and their functions. Standard practice, nevertheless, would be to keep all of these files
together in the same installer directory.
File name
Description
0x0409.ini
Setup.exe English language initialization file. Required to run
Setup.exe. English is the only language currently supported.
Not required if you are running the installer using
Msiexec.exe.
CD automatic launcher for setup.exe. Effective only if the
installer is in the root of a CD. Launches Setup.exe in full
user mode with no special configuration. Not required.
SEER-SEM 8.2 cabinet file. Required for running Setup.exe
and "SEER-SEM 8.2.msi". This file contains all the source
files for installing SEER-SEM, with the exception of
license.dat. It does not contain any installation logic.
Data1.cab must be in the same directory as “SEER-SEM
8.2.msi”.
CD text license. Not required for running the installer.
Windows Installer 3.0. Run this if your Windows installer is
out of date.
This folder contains "Microsoft Data Access Components
(MDAC) 2.8" and "Microsoft Visual C++ 2013
Redistributable - x86 12.0.30501.0", and
autorun.inf
Data1.cab
eula.txt
WindowsInstaller-KB893803-x86.exe
ISSetupPrerequisites FOLDER
File name
License_SEER-SEM.lic*
Section 508 Evaluation Information.pdf
SEER-SEM 8.2.msi
Setup.bmp
Setup.exe
Setup.ini
Description
dotNetFx40_Full_setup.exe file which is .NET 4.0 installation
package. All of these are Windows requirements for running
SEER-SEM. If they are not already installed, the SEER-SEM
installer will ask you to install them before proceeding. You
may also run them separately before running the SEER-SEM
installer.
SEER-SEM license file. The installer copies this over to your
SEER-SEM Program Files directory. Hence it MUST be kept
in the same directory as SEER-SEM 8.2.msi. See note below.
Section 508 software information. Not required for running
the installer.
Main SEER-SEM MSI installer database. This contains all of
the core logic and files for installing SEER-SEM. This file
may be run from the MSIEXEC command line in lieu of
using setup.exe.
Setup.exe splash screen. Not required if you are running the
installer silently. Not required if you are running the installer
using Msiexec.exe.
Setup launcher. Not required if you are running the installer
using Msiexec.exe.
Setup.exe initialization file. Required to run setup.exe. Not
required if you are running the installer using Msiexec.exe.
* License_SEER-SEM.lic WARNING. License_SEER-SEM.lic is downloaded separately from your
installer. You extract the license into your SEER-SEM installer folder, then run the installer. If your
installer is distributed without a license because you are between renewals, you MUST put a copy of your
most current license into the installer directory in order for silent or minimal user interface installation to
work. During regular installation the installer asks the user for the location of any previous license if one is
not found with the installer folder. During silent install it silently aborts if no license is found in the
installer directory.
Setup.exe Behavior
Setup.exe will detect whether you have an existing installation of SEER-SEM 8.2 and run in upgrade
mode to update the installation. If you do not have an installation, it will run in initial installation
mode.
1. Setup.ini Configuration
A. User File Configuration
SEER-SEM 8.2 and above allow users to customize their SEER-SEM configuration files and to
add Projects, Kbases, Export Templates, Scenarios, and other user files to their installation by
setting flags in the installer Setup.ini and placing custom files in folders in the SEER-SEM
installer media. The following feature flags are available:
Setup.ini
[Startup]
CustomAppData = OFF/ON
CustomExportTemplates = OFF/ON
CustomKbases = OFF/ON
CustomProjects = OFF/ON
CORRESPONDING MEDIA FOLDER
<Installer>\AppData
<Installer>\documents\Export Templates
<Installer>\documents\Kbases
<Installer>\documents\Projects
CustomScenarios = OFF/ON
CustomUtilities = OFF/ON
CustomHelp = OFF/ON
CustomParameterHelp = OFF/ON
<Installer>\documents\Scenarios
<Installer>\documents\Tools
<Installer>\Help
<Installer>\ParameterHelp
ON = Default file installation. The SEER-SEM installer will install default Galorathconfigured files contained in the installer's Data1.cab file archive. It will also look in the
appropriate installer media directory and copy over any extra files that have been included
there. This allows you to install the standard default SEER-SEM files and ADD IN any files
of your own by including them in the media folder.
OFF = The SEER-SEM installer will install ONLY the files contained in the features media
folder. This option SUPPRESSES installation of default files from the Data1.cab. It enables
more choice of what is installed but requires that you be responsible for ALL the files you
wish to include or exclude.
When the installer reads in the setup.ini settings values for custom user file installation, it sets
an internal MSI property to the boolean value of 0 or 1 (for OFF/ON). These values may be
used on the MSI command line if the installer is being run directly from the "SEER-SEM
8.2.msi" file without the "setup.ini" file present.
SETUP.INI
CustomAppData
CustomExportTemplates
CustomKbases
CustomProjects
CustomScenarios
OFF
Installs SEER-SEM
initialization and
configuration files
from the installer
Data1.cab
Installs Export
Templates from
Data1.cab and adds in
any Export Templates
found in the Media
folder
"<Installer>\document
s\Export Templates".
Installs Kbases from
any Kbases found in
the Media folder
s\Kbases".
Installs SEER-SEM
Project files from
any Project files found
in the Media folder
s\Projects".
Installs Scenarios from
any Scenarios found in
the Media folder
s\Scenarios".
ON
Checks for
customized
initialization files -SEE BELOW
MSI PROPERTY
B_CUSTOM_APPDAT
A_FILES
Installs ONLY files
found in the
"<Installer>\documen
ts\Export Templates"
folder
B_CUSTOM_EXPORT
_TEMPLATES
Installs ONLY files
found in the
ts\Kbases" folder
B_CUSTOM_KBASES
Installs ONLY files
found in the
ts\Projects" folder
B_CUSTOM_PROJEC
TS
Installs ONLY files
found in the
ts\Scenarios" folder
B_CUSTOM_SCENAR
IOS
CustomUtilities
CustomHelp
CustomParameterHelp
Installs Tools or
Utilities files from
any files found in the
Media folder
s\Tools".
Installs SEER-SEM
Help files from the
installer Data1.cab and
adds in any Help files
found in the Media
folder
"<Installer>\Help
Installs SEER-SEM
Parameter Help files
from the installer
any Parameter Help
files found in the
Media folder
"<Installer>\Parameter
help
Installs ONLY files
found in the
ts\Tools" folder
B_CUSTOM_UTILITIE
S
Not implemented Same as ON
B_CUSTOM_HELP
Not implemented Same as ON
B_CUSTOM_PARAME
TERHELP
APPDATA FILE GROUP
The "AppData" file group (SEER-SEM initialization and configuration files) behaves
differently than other user file goups.
OFF = Installs preconfigured INI and other configuration files from Data1.cab.
Nothing is written to these files by the installer except the version of the SEER-SEM program.
You or your system administrator are responsible for resetting the values of all other INI
values that need to be reset.
ON = The installer checks for each and every SEER-SEM "AppData" configuration file. If
the file exists in the Installer Media "AppData" folder, the installer installs it. If the file is
NOT found in the folder, the installer installs the default Data1.cab version of the file.
The installer does NOT reinstall (copy) or reconfigure INI or other configuration files during
update, since overwriting user INI file settings that have been made manually is considered
bad practice. In other words, AppData files are copied and configured only during first
installation.
These properties may NOT be set in the Setup.ini file. File status is detected by the installer.
0 indicates that a file is absent. 1 indicates that a custom file is present.
FILE
Custom1.rpt
Custom2.rpt
Custom3.rpt
Custom4.rpt
SEER-SEM Data.ini
SEER-SEM
Settings.INI
MSI PROPERTY
B_CUSTOM_CUSTOM1_RPT
B_CUSTOM_SEER_SEM_DATA_INI
B_CUSTOM_SEER_SEM_SETTINGS_INI
Values Set
0/1
0/1
0/1
0/1
0/1
0/1
SEER-SEM
TAGS.INI
SEMACTNAMES.INI
SEMLABCATNAMES.INI
SEMLANGTABLE.INI
views.ini
B_CUSTOM_SEER_SEM_TAGS_INI
0/1
B_CUSTOM_SEM_ACTNAMES_INI
0/1
B_CUSTOM_SEM_LABCATNAMES_INI
0/1
B_CUSTOM_SEM_LANGTABLE_INI
0/1
B_CUSTOM_VIEWS_INI
0/1
UPGRADE
Custom user file configuration settings may be set during UPGRADE as well as initial installation.
However, changing settings can result in unexpected outcomes and should at the very least be
pretested.
The SEER-SEM installer, for example, will not automatically alter feature group configuration
during upgrade just because you switch a custom file group INI setting. If you have chosen NOT
to install "Sample_Projects," for example, and then reset "CustomProjects = OFF" to "
"CustomProjects = ON" in the setup.ini during upgrade, the installer will NOT uninstall Project
files (in other words, while "CustomProjects = ON" will SUPPRESS installation of Projects, it
will not UNINSTALL them later on during update if they have been previously installed).
We recommend that if you wish to reconfigure the installation or removal of features (groups of
user files), you do so from the command line before or after your upgrade.
MsiExec.exe /i{B16471CC-AE45-4FB7-82CB-D2D32E9574D9}}
ADDLOCAL="Sample_Projects"
will add "Sample_Projects" files into your installation from the installer Data1.cab.
MsiExec.exe /i{B16471CC-AE45-4FB7-82CB-D2D32E9574D9}
REMOVE="Sample_Projects"
will remove installed .CAB Project files.
B. SEER Historical Database Configuration
The SEER-SEM installer automatically attempts to launch the installer for SEER Historical
Database (SEER-HD). If you do not wish to the installer to launch SEER-HD, or you are running
the SEER-SEM installer silently, you will need to set "RunSEERHD" from its default value of
"Yes" to "No."
Setup.ini
[startup]
RunSEERHD=No
2. Setup.exe Command Line Switches
Normally most of the Setup.exe switches are not needed if you keep your installer media files
intact on the CD or you copy them over to a single directory on your computer. The default
installer configuration is to keep all files in the same directory as Setup.exe. The two critical
switches are /v and /s.
/s
Hides initialization dialog. For basic Silent default installation, use
/s /v/qn This will perform a default Local installation of SEER-SEM
8.2 on your computer. See below.
Performs an administrative installation – or installation of the
installer, normally to a network directory. Unpacks the .CAB file to a
directory and places an .MSI file in the top level of the directory.
Passes parameters to msiexec.exe. The /v switch is normally quoted,
since it usually contains spaces: /v"one very long MSI command line
string". See below for special remarks on using this setup.exe switch
to configure silent installations.
/a
/v
For more complete information about other Setup.exe switches, see InstallShield help, available
on the web at:
http://helpnet.flexerasoftware.com/installshield21helplib/installshield21helplib.ht
m#StartTopic=helplibrary/IHelpSetup_EXECmdLine.htm
Note the distinction between “InstallScript”, “InstallScript MSI,” and “Basic MSI” or “Windows
Installer” installers. Setup.exe switches that apply to the first two types of installer do not apply to
the SEER-SEM 8.2 installer, which is a “Basic MSI” or “Windows Installer” installer.
2. Silent Installation
/S is the silent switch for setup.exe. It suppresses setup.exe’s splash screens. /V is the MSI switch
for setup.exe, which passes the /qn MSI silent switch to the “SEER-SEM 8.2.msi” installation
session.
3. Configuration Properties
Since silent installation does not have the advantage of a user interface for setting installation
configuration variables, these need to be passed on the command line using the Setup.exe /v
switch. “Public Properties” are the MSI equivalent of global variables. Below is a list of basic
configuration properties that can be used on both the Setup.exe and Msiexec.exe command lines.
They must be spelled ALL CAPS and their values must be spelled precisely in the upper
case/lower case form indicated in the table (with the exception of paths, which are case insensitive
on the Microsoft Windows operating system).
Properties (these must be
Values
spelled ALL CAP)
Custom MSI Properties – SEER-SEM-specific
SETUPTYPE
Local
Client
Network
NETWORKPATH
<UNC path to a
network installation
of SEER-SEM 8.2>
Description
-- “Local” installs all files on the user’s
local machine. Local is the default.
-- “Network” installs all files on a
network computer so that a user
“Client” installation may be connected
to it.
-- “Client” installs a minimal subset of
SEER-SEM files that will run SEERSEM from a network installation
(previously installed).
If SETUPTYPE is “Client”,
NETWORKPATH must be defined. If
SETUPTYPE is “Local” or “Network”,
NETWORKPATH has no effect.
Standard MSI Properties
INSTALLDIR
<Path to the
installation directory
of SEER-SEM on the
local machine>
This is a standard MSI property. It
determines the main program files
directory for the SEER-SEM
installation. If not set, the default is
“<ProgramFiles>
\SEER\SEER-SEM 8.2”. On most
machines, the Environment variable for
<ProgramFiles> translates to
“C:\Program Files\”. Hence on most
machines, the default INSTALLDIR is
“C:\Program Files\SEER\SEER-SEM
8.2”.
4. Feature Configuration Properties
The feature configuration properties ADDLOCAL, REINSTALL, and REMOVE are discussed in
the “Msiexec.exe Behavior” section below in order to avoid overcomplicating the discussion of
Setup.exe. The main difference is that using them with Setup.exe requires including them in the
command line string passed by the Setup.exe /v switch.
5. Setup Types (Local, Network, Client)
A. Local Installation with the Setup.exe command line
No Properties need to be set to do a default Local installation. The example is a silent installation:
Since no Properties are being defined in the /v switch, the installer will install SEER-SEM in
“C:\<Program Files>\SEER\SEER-SEM 8.2”. The setup type will be “Local” rather than
“Network” or “Client”.
Non-Default Local Installation
If you want to install SEER-SEM Local in another directory than “C:\Program Files\SEER\SEERSEM 8.2”, you have to set the INSTALLDIR property. Since “Local” is the default setup type,
SETUPTYPE does not need to be defined on the command line.
"<path to installer directory>\setup.exe" /s /v"INSTALLDIR=\"c:\my sem
directory\" /qn"
Note that the /v switch now requires quotation marks and escape characters, since the command
line sent to Msiexec.exe has spaces and internal quote marks in it. If the property value does not
contain spaces,it does not need to be quoted. Follow the standard program procedure of escaping
quotes within quotes using the backward slash (\").
Note also that the MSI /qn switch for silent install is inside the long MSI command line string
passed by the setup.exe /v switch.
B. Network Installation with the Setup.exe command line
Network installation installs SEER-SEM 8.2 to a network computer shared directory so that Client
user’s on other machines may connect to it.
The two critical Properties to set for a Network installation are SETUPTYPE and INSTALLDIR.
It is unlikely that administrators will want to install SEER-SEM 8.2 in the default directory
“C:\Program Files\SEER\SEER-SEM 8.2”.
"<path to installer directory>\setup.exe" /s /v"SETUPTYPE=Network
INSTALLDIR=\"C:\SEER-SEM 8.2\" /qn"
NETWORKPATH is NOT actually used for a Network installation. It is used by Client
installation (see below) to connect to an already existing Network installation.
Make sure that you share SEER-SEM's Network folder so that others can connect to it. For
example, the directory above can be shared as “\\SERVER\SEER-SEM”.
C. Client Installation with the Setup.exe command line
Client installation connects to an already existing installation of SEER-SEM on another (network)
computer in a shared directory. Before running a Client installation, the Network version should
be updated to the same version as the Client installer.
The two critical Properties to set for a Client installation are SETUPTYPE and
NETWORKPATH.
"<path to installer directory>\setup.exe" /s /v"SETUPTYPE=Client
NETWORKPATH=\"\\SERVER\SEER-SEM\" /qn”
Note: Administrators who are “pushing” a Client installation to numerous other users’ computers
will want to use the UNC (universal naming convention) path in order to avoid conflicts that may
result from different users mapping the network share to different drive letters. Since the directory
in the Network install example above has been shared as “\\SERVER\ SEER-SEM”, Client
installation can set
NETWORKPATH=\"\\SERVER\SEER-SEM\"
6. Upgrade
Upgrade will update existing program files, shortcuts, ODBC connections and the like in your
exiting installation.
SETUPTYPE and NETWORKPATH
During upgrade, the installer will NOT update setup type or the network connection for Client
installation. In other words, defining SETUPTYPE or NETWORKPATH on the command line
will have no effect, since during upgrade the installer gets this information from your computer’s
registry.
If you wish to change the setup type or the location of SEER-SEM to which a Client installation
connects, you must first uninstall any previous SEER-SEM 8.2 and reinstall using the new
upgrade installer.
REINSTALL Property
We do NOT recommend that you try to finesse upgrade by defining a REINSTALL feature list,
since other factors are too complex. If your users have uninstalled any optional features, they may
reinstall the new ones by using Maintenance Modify. All optional features are listed in the
Maintenance dialog interface.
Moreover, you could easily reconfigure the installation after upgrade with a command line like the
following (you want the users to have help files but not scenarios):
"<path to installer directory>\setup.exe" /s /v"ADDLOCAL=\"Help_Files\"
REMOVE=\"Scenarios\" /qn"
7. Silent Uninstall
Silent Setup.exe uninstall uses the /x, /s, and /v switches. /X uninstalls. /S suppresses the setup
launcher’s splash screen, and /v passes the silent /qn switch to Msiexec.exe to suppress the user
interface in “SEER-SEM 8.2.msi”.
"<path to installer directory>\setup.exe" /x /s /v/qn
8. Administrative Installation
If you prefer not to use Administrative
installation, you can copy the CD installer
to a network directory and run it from
Msiexec.exe or from Setup.exe using
normal setup mode or command lines.
An Administrative Installation installs a
copy of the installer, normally in a
network directory so that it can be run by multiple users. Admin install
uncompresses the .CAB file and places files in an internal directory
structure (see far right). The top level directory (immediate right)
contains a “seer-sem 8.2.msi” that can be used to run a SEER-SEM
installation. After administrative installation, Setup.exe is no longer
available for running an installation from an administrative setup. It is
NOT copied to the administrative installer’s directory. You must use
the .MSI database in the admin directory and the MSIEXEC.EXE
command line.
Setup.exe
You must invoke administrative installation from the command line. The basic command line for
launching administrative installation uses the /a switch:
"<path to installer directory>\setup.exe" /a
With the /a switch alone, you will get the administrative install user interface, which will ask you
where you wish to put the installer.
If you wanted to do a silent install (there is little reason for it with Administrative installs, since
they are usually done once by one system administrator), you could also use the following. Note
that the Administrative installer uses the directory property TARGETDIR (rather than
INSTALLDIR) as the location of its installation:
"<path to installer directory>\setup.exe" /a /s
/v"TARGETDIR=\"\\SERVER\SEM_INSTALLER\" /qn"
Note about “license.dat”: If your shipped installer does not come with a license file (a rare case),
you need to put a copy of your most recent license in the administrative installation’s top-level
directory. If you do not, users will see a “Find License” dialog during the installation process
asking them for the location of their previous license, or, if running silent, the installer will abort
(since it can’t install a license). If your regular shipped installer has a license (the normal case), it
will automatically be moved over to the Administrative installer directory.
Note also that you would STILL have to perform a “Network” installation using either the regular
or the Administrative installer before the user could perform a Client installation. The
Administrative installer is an installation of the INSTALLER, not of a Network setup of SEERSEM. Let’s presume you installed Network SEER-SEM in “\\SERVER\\SEER-SEM”.
After you have installed Network SEER-SEM, a user could use the Administrative Installer to
install a Client version of SEER-SEM 8.2 Studio edition with an Msiexec.exe command line like
the following:
msiexec /i "\\SERVER\SEM_INSTALLER\seer-sem 8.2.msi" SETUPTYPE="Client"
NETWORKPATH="\\SERVER\SEER-SEM" /qn
9. Creating a LOG file
Creating a log file for the installation requires using the MSI /L command line switch. SEE MSI
help for a complete list of log flags for limited logging. In order to log ALL information (verbose
logging), use “/l*v <logfile.log>” as follows:
"<path to installer directory>\setup.exe" /s /v"/l*v \"c:\semlog.log\" /qn"
Note that there is a space before the log file name and that if you fail to specify a full path to the
log file, the log will be placed in the directory from which setup.exe is launched. This could be a
problem if you are launching from a CD (the file will not be created) or you are doing multiple
installs from a network directory (the file will be replaced for each install). The log file is a simple
text file, regardless of the extension you give it.
10. Setup.ini
If you are using setup.exe to install SEER-SEM, you may also use the “CmdLine” parameter in
the “Startup” section to set properties and FIX the installer as an installer of a particular type (the
installer will be fixed until you change the CmdLine parameter or redefine the properties on the
actual command line). This sort of configuration is optional, since all settings may be done on the
command line itself. SEER installers do not come with the CmdLine parameter preset.
Setup.ini file
[Startup]
CmdLine=
For example, if you have a Project Manager edition and know that you know that you will always
want to run Client setup, and have users connect to a specific networked SEER-SEM, you could
define the CmdLine parameter as follows:
CmdLine=SETUPTYPE="Client" NETWORKPATH="\\SERVER\SEER-SEM"
There are, of course, certain liabilities to fixing the installer:
You need to remember to change values in the INI file if you decide to change configuration.
If you were to set REINSTALL="ALL" REINSTALLMODE="vomus", you would be
permanently defining the installer as an UPGRADE installer. Any new user who tried to run
THAT installer would get NO installation, since the installer would find no existing features
to REINSTALL! In order to do a first time install, you would need to explicitly vacate these
properties on the actual command line! -- REINSTALL="" REINSTALLMODE=""
If you decide to leave certain properties flexible by not including them in the INI settings, you
will have to remember to include them on the command line.
Msiexec.exe Behavior
You can also run the SEER-SEM installer directly from Msiexec.exe, bypassing setup.exe. However,
there are a few differences.
Msiexec.exe does not automatically update Windows Installer on your computer. If you get a message
that Windows installer is out of date, you will need to run “Instmsiw.exe” from your installer media.
“Instmsiw.exe” installs Windows Installer 2.0 for Windows 2000 or Windows XP. SEER-SEM is no
longer supported on Windows 95, 98, ME, NT or Vista.
Most importantly, Msiexec.exe does not automatically detect that it should do an upgrade.
REINSTALL and REINSTALLMODE Properties need to be set on the command line to inform the
installer that it needs to go into upgrade mode. If you run the installer without them on a machine that
already has an earlier version of SEER-SEM 8.2, you will get the unenlightening message “Another
version of SEER-SEM 8.2 already exists on this machine.”
1. Msiexec.exe Command Line Switches:
MSI command line switches are particularly complex. The following are the ones most you are
most likely to use: In brief, they are:
/i
/x
/q
/l
/a
Install
Uninstall
User interface mode (silent install)
Logging
Administrative installation
For a more complete description of Windows Installer command line switches, see Microsoft
Windows Installer help on the web :
http://msdn.microsoft.com/en-us/library/windows/desktop/cc185688(v=vs.85).aspx
Feature Configuration
Normally you will not need to configure features during installation unless you want to remove items that
are in the standard configuration for a setup type. Setup types will install all required features and any
optional features that a user selects from the list of optional features. Or, if run in silent mode, SEER-SEM
8.2 installers will install ALL features appropriate to the setup type.
Feature Configuration Properties
The following Properties are used to configure features on the MSI command line:
Property (must be
ALL CAPS)
ADDLOCAL
REMOVE
REINSTALL
REINSTALLMODE
Values
Behavior
“ALL” or a list of
comma-delimited
features
comma-delimited
features
“ALL” installs the default features for a particular setup
type. A list installs the listed features except if they are
not in the specified setup type.
“ALL” removes all installed features. A list uninstalls
the listed features. (Note: using REMOVE=”ALL” with
the /i switch does not completely uninstall the program;
registry entries are still left. If you want to uninstall the
program, use the /x switch, which removes everything.)
“ALL” reinstalls the existing (already installed) features.
A list reinstalls any listed features that are already
installed.
REINSTALLMODE is used with REINSTALL to
configure how the installer updates or repairs. In order
to perform a complete upgrade, you must use the value
“vomus”. See below for more explanation.*
comma-delimited
features
“vomus” or another
string of acceptable
alphabetical flags
There is a strict hierarchy of precedence in the feature variables ADDLOCAL, REMOVE, and
REINSTALL. For example, if a feature specified in ADDLOCAL is also specified in REMOVE and
REINSTALL, REMOVE takes precedence over ADDLOCAL, and REINSTALL takes precedence over
REMOVE. So the installer will consequently attempt to REINSTALL the feature rather than to install it or
remove it. If the feature is not already installed, it will not be installed (even though you included it in
ADDLOCAL). Hence the clearest practice (if you are uncertain) is to make sure that if you use more than
one feature configuration property, no duplicates are in the lists, including the list implicit in “ALL”.
*REINSTALLMODE is a critical property used in conjunction with REINSTALL. In order to perform an
upgrade, you must use the value “vomus” for REINSTALLMODE. In fact, the standard properties for
performing a “minor upgrade” are the following:
REINSTALL="ALL" REINSTALLMODE="vomus"
This means, in effect, “reinstall all features that have been installed and re-cache the MSI database on the
user’s machine.” It updates everything. Any other definition of REINSTALLMODE would involve a
partial upgrade or repair. The particular letters guarantee that files, shortcuts, and other components are
updated. The “v” flag replaces the cached MSI database on the user’s machine, which is critical for
ensuring that Maintenance mode works properly. If the database is not replaced, the repair and modify
features of Maintenance will be repairing and modifying using the OLD database’s definitions.
Features
Feature names must be quotes exactly as listed below, with the same capitalization and use of underscores
for spacing (spaces are not allowed in feature names).
Feature
Description
Setup Type
AppData
Local
Network
CrystalReports85Feature
Installs various SEER-SEM initialization
files in the <ProgramFiles>AppData
folder cache. When your program
initializes, it makes copies of these files in
to your user profile. This allows multiple
users on one machine to customize the
program to their own specifications.
Covers all aerospace applications
(commercial and defense), weapons
systems, and ground-based mission
critical systems, etc. Optional knowledge
bases.
Covers all knowledge bases that are
common to both Commercial and
Aerospace. These are installed by default
although not required.
Covers business systems, commercial
mission critical applications, and
information systems, etc. Optional
knowledge bases.
Crystal Reports 8.5 files. Required.
CrystalReportsFeature
Crystal Reports 9.0 files. Required.
CrystalReportsODBC
ODBC connections necessary for
publishing reports with Crystal Reports.
Required.
Aerospace_Kbases
Both_Kbases
Commercial_Kbases
Export_Templates
Local
Network
Local
Network
Local
Network
Local
Network
Client
Local
Network
Client
Local
Network
Client
Local
Network
Local
Network
Help_Files
SEER-SEM Help files. Optional files.
Network_Crystal_Reports_Files
Crystal Reports DLLs installed in the
Network directory of SEER SEM for
Network installations of the program.
A complete Adobe Acrobat PDF version
of the SEER-SEM manual. Optional.
Network
Program executables, DLLs, and program
support files essential for running SEERSEM. Required except for Client
installation, where they are extraneous.
Sample SEER-SEM projects.
Local
Network
Installs SEER Metrics. If SEER Metrics is
not configured into the installer, this
feature will not install. Optional.
Scenario templates for generating variants
of standard projects. Optional feature.
Local
Network
Client
Local
Network
PDF_manual
Program_Files
Sample_Projects
SEERMetrics
Scenarios
Local
Network
Local
Network
Feature
Description
Setup Type
SEER_SEM_INI
SEER-SEM settings. Required for all
setup types. As of SEER-SEM 8.0 SEERSEM initialization files are contained in
the AppData feature.
Template and server mode script
generators, input worksheets, and other
items helpful for using SEER-SEM.
Optional feature.
Local
Network
Client
Utilities
Local
Network
Default Setup Types
By default, the three setup types include the following features. However, all features may not be enabled
for you to use unless you have license file for the edition that includes them.
Setup Type
Contains
Not Included
Local
AppData,Aerospace_Kbases,Both_Kbases,Commercial_Kb
ases,CrystalReports85Feature,CrystalReportsFeature,Crysta
lReportsODBC,Help_Files,PDF_manual,Program_Files,Sa
mple_Projects,SEERMetrics,Scenarios,SEER_SEM_INI,Ut
ilities
AppData,Aerospace_Kbases,Both_Kbases,Commercial_Kb
ases,CrystalReports85Feature,CrystalReportsFeature,Crysta
lReportsODBC,Help_Files,Network_Crystal_Reports_Files
,PDF_manual,Program_Files,Sample_Projects,SEERMetric
s,Scenarios,SEER_SEM_INI,Utilities
CrystalReports85Feature,CrystalReportsFeature,CrystalRep
ortsODBC, SEERMetrics,SEER_SEM_INI
Network_Crystal_Report
s_Files
Network
Client
AppData,Aerospace_Kba
ses,Both_Kbases,Comme
rcial_Kbases,Help_Files,
PDF_manual,Program_Fi
les,Sample_Projects,SEE
RMetrics,Scenarios,Utilit
ies
1. First Installation
A. Local Installation with the Msiexec.exe command line
No properties need to be defined to perform a default local installation:
msiexec /i "<path to installer>\seer-sem 8.2.msi" /qn
The silent switch has been added so that you can see how the msiexec.exe command line differs from
setup.exe.
Non-default Local Installation
Suppose you wish to silently install a Local setup type with no Commercial knowledge bases
(Commercial_Kbases), no PDF manual (PDF_manual), and no Scenarios (Scenarios). You can
perform such and installation by selecting all features EXCEPT these three the the ADDLOCAL
option. You must specify all the features that you want and none that you do not want, as well as not
omit any features that are REQUIRED for the program to operate.
msiexec /i "<path to installer>\seer-sem 8.2.msi" SETUPTYPE="Local"
ADDLOCAL="Aerospace_Kbases,Both_Kbases,CrystalReports85Feature,CrystalReportsFeature,
CrystalReportsODBC,Help_Files,Program_Files,Sample_Projects,SEERMetrics,SEER_SEM_INI
,Utilities" /qn
A simpler alternative, utilizing the fact that REMOVE has precedence over ADDLOCAL, would be
the following, which blocks the three undesired features from being installed:
msiexec /i "<path to installer>\seer-sem 8.2.msi" SETUPTYPE="Local" ADDLOCAL="ALL"
REMOVE="Commercial_Kbases,PDF_manual,Scenarios" /qn
Using REMOVE would not work with REINSTALL=”ALL”, however, since REINSTALL has
precedence over REMOVE. If the three features had already been installed, they would update rather
than be removed.
Follow the Features, Default Setup Type, and Releases tables above for help on what to include in your
custom setup.
B. Network Installation with the Msiexec.exe command line
Network installation installs SEER-SEM 8.2 to a network computer shared directory so that Client
user’s on other machines may connect to it.
As with Setup.exe, the critical properties to set are SETUPTYPE and INSTALLDIR.
msiexec /i "<path to installer>\seer-sem 8.2.msi" SETUPTYPE="Network"
INSTALLDIR="C:\SEER-SEM 8.2" /qn
Make sure that you share the directory to which you installed SEER-SEM so that a Client installation
can connect to it. For example, you could share “C:\SEER-SEM 8.2” as “\\<ServerName>\SEERSEM” where “ServerName” is the name of the network computer and “SEER-SEM” is the name of the
share.
C. Client Installation with the Msiexec.exe command line
2. Upgrade
Basic command line installation with Msiexec.exe requires using the REINSTALL and
REINSTALLMODE properties. REINSTALLMODE must be set to “vomus”. See
REINSTALLMODE in the “Feature Configuration Properties” section above.
msiexec /x "<installer directory path>\seer-sem 8.2.msi" REINSTALL="ALL"
REINSTALLMODE="vomus"
SEER-SEM installers are configured to automatically upgrade when the standard command line is
used.
For further information about upgrade logic, see the “Basic Installation” and “Setup.exe” installation
sections.
3. Uninstall
Uninstalling using the Msiexec.exe command line can be done two ways:
msiexec /x "<installer directory path>\seer-sem 8.2.msi"
msiexec /x {B16471CC-AE45-4FB7-82CB-D2D32E9574D9}
{B16471CC-AE45-4FB7-82CB-D2D32E9574D9}is the SEER-SEM 8.2 “product code,” a unique
GUID that MSI uses to store and retrieve all information about the program installation in your
computer’s registry. It can be used with command line switches only if the product is already
installed.
4. Logging
Logging for Msiexec.exe is the same as logging for Setup.exe, except that the command line is no
longer quoted within the Setup.exe /v switch.
msiexec /i "<path to installer>\seer-sem 8.2.msi" /l*v "c:\semlog.log"
If you specify only a filename, the log file will be placed in the installer directory. This could be
problematic if you are running from a CD (the file will not be written) or from a network directory
(each user will be overwriting the log file).
APPENDIX
InstallShield Setup.exe
For more complete information about other Setup.exe switches, see InstallShield help, available on the web
at:
http://helpnet.flexerasoftware.com/installshield21helplib/installshield21helplib.htm#Start
Topic=helplibrary/IHelpSetup_EXECmdLine.htm
Windows Installer and Windows Installer Switches
For more complete information, see Windows Installer help, available on the web at:
http://msdn.microsoft.com/en-us/library/cc185688.aspx
http://msdn.microsoft.com/en-us/library/aa367988.aspx

SEER for Software Installation Guide

Transcription

Similar documents

Atlantis Energy Systems Inc.

Regions CD Check Viewer Installation Guide

Chemcrest Installation Guide

Zonnestraal - English

KV “ANDENES” - KV “SENJA” - KV “NORDKAPP”

QuadraTec™ - Auralex Acoustics

Products_files/6 (catalogo DECO PROJECTS.EN)

1006 A Rochow St.

S kyline - Franz Viegener