Network Deployment Installation

A network deployment provides an efficient way to install and license the CivilGEO software on multiple computers. A number of commercial and open source software utilities are available that can be used as deployment solutions across one or many computers (simultaneously) on the network.

Software Deployment Best Practices

Remember to follow these best practices when creating a software deployment:

Create the deployment from a workstation rather than a server
This helps to eliminate the need for the same computer to run the installation, read the media, and write the files. The combination of these tasks can greatly increase the amount of time necessary to complete the software deployment and can even cause corruption in the process. It is better to create the deployment on a shared network location from an administrative workstation.
Do not create deployments over a WAN or VPN
Network connections using a WAN or VPN are generally slow and can cause file I/O errors during the deployment creation. Running the deployment over a WAN or VPN can also result in missing or corrupt files.
Disable antivirus software
Running antivirus software while creating the software deployment may cause issues. The antivirus software scans every file being written and read in real time, which will add time to the process and may introduce other complications. For example, the antivirus software might block certain files from being written or may modify the files and result in software corruption.
Use a shared directory
Before creating the software deployment, create a shared directory on either the server or on a workstation. Keep the share name short and simple. Do not include spaces in the share name. Do not nest the shared directory too deeply on the drive.
Use a separate folder for each deployment image
Creating multiple software deployments within the same shared directory can cause corrupt installations and other problems.
Create and store deployments on NTFS file systems only
Other file systems, such as LINUX, UNIX, DFS, NFS, AIX and others can cause unforeseen issues with software deployments, including file systems used on network attached storage (NAS) devices.
Users should have full read/write access
The users creating the software deployments should have full read/write access to the network share where the software deployments are to be stored.
Use UNC (Uniform Naming Convention) for network paths
When specifying network paths, use a uniform naming convention (UNC) rather than mapped drive letters. For example, use \\servername\share\folder instead of S:\folder. Not all networked computers share the same mapped drive letters and the use of UNC network paths eliminates these types of problems.
Avoid modifying a deployment once it has been created
Instead of modifying an existing software deployment, it is better to create a new deployment for each modification that you make.
Avoid moving deployments between servers
It is not recommended to move software deployments between servers. If you must do this, you may need to modify the deployment to insert its current location into the deployment structure.

Creating a Silent Installation

Our software products use InstallShield software for installation. Using the installation software provided; you can easily create a silent install that allows deployment of the software to multiple computers on your network. This makes it much easier to install the software without having to babysit the installation for each computer.

To manually perform a silent installation, the following steps can be placed in a batch file or script file to automate the installation operation:

Launch the Command Prompt with the Run as Administrator option in the directory where the SETUP.EXE product installation program resides.
Execute the below command to install the product in silent mode (on one line):

SETUP.EXE /s /v/qn /v"USERNAME=\"[End_User]\"" /v"INSTALLDIR=\"[Target_Path]\"" /v"COMPANYNAME=\"[Your_Company]\""

The installation program options shown above are detailed as follows:

1. Silent Mode:
  The /s parameter informs the installation program to install the software in a silent mode.
2. Without MSI installer User Interface:
  The /v/qn parameter will pass the /qn parameter on to the embedded MSI installer. The /qn is an msiexec (i.e., Windows Installer) switch indicating to run with no UI.
3. USERNAME (Optional):
  The “USERNAME=[End_User]” option is used to specify the user name. Replace [End_User] with the end user name.
4. COMPANYNAME (Optional):
  The “COMPANYNAME=[Your_Company]” option is used to specify the company name. Replace [Your_Company] with the name of your company.
5. INSTALLDIR (Optional):
  The “INSTALLDIR=[Target_Path]” option is used to define the UNC or drive letter and absolute path to the location where the software is to be installed. It is not recommended that the software be installed on a network drive, but on the target computer hard drive. If this parameter is not defined, the software will be installed in the default directory:
  C:\Program Files\CivilGEO\ProductName

Automated Software Installation and License Deployment

When performing a software deployment on an enterprise network that has a floating network license, it can be very time consuming to visit every computer in the network and manually install the software and register the license. For each workstation, CivilGEO software requires that the License Server IP Address and Port be manually specified.

Fortunately, the CivilGEO software and network licensing process can be deployed using a command line. This can save time and effort when using automation deployment software, such as PDQ Deploy.

Launch the Command Prompt with the Run as Administrator option in the directory where the SETUP.EXE product installation program resides.

For Floating Network License (on one line):

SETUP.EXE /s /v/qn /v"FLOATING_SERVER_IP=[Server_IP]" /v"FLOATING_SERVER_PORT=[Server_Port]"

For Cloud License:

SETUP.EXE /s /v/qn /v"CLOUD_SERVER_ID=[Server_ID]"

The CivilGEO installation program options shown above should be on one line, and are as follows:

Silent Mode:
The /s parameter informs the CivilGEO installation program to install the software in a silent mode.
Without MSI installer User Interface:
The /v/qn parameter will pass the /qn parameter on to the embedded MSI installer. The /qn is an msiexec (i.e., Windows Installer) switch indicating to run with no UI.
FLOATING_SERVER_IP:
The /vFLOATING_SERVER_IP=[Server_IP] option is used to specify the Network License Server IP. Replace [Server_IP] with the IP of the Network License Server. For example:
```
/vFLOATING_SERVER_IP=192.168.20.1
```
FLOATING_SERVER_PORT:
The /vFLOATING_SERVER_PORT=[Server_Port] option is used to specify the Network License Server port. Replace [Server_Port] with the port of the Network License Server. Typical ports would be 8081, 8082, etc. For example:
```
/vFLOATING_SERVER_PORT=8081
```
Cloud_Server_ID:
The /vCLOUD_SERVER_ID=[Cloud_Server_ID] option is used to specify the Cloud License Server ID. Replace [Cloud_Server_ID] with the license server ID of the Cloud License. For example:
```
/vCLOUD_SERVER_ID=9ABCD9E9F9GH
```

This weblink provides additional information on the command line parameters supported by the installation program. If you have difficulty getting this to work, please contact our technical support staff. Our technical support team will be glad to assist you.

Additional Installation Options

The installation software provides the following additional options:

Display Options

Options to control the display of the installation process:

/quiet
Quiet mode, no user interaction

/passive
Unattended mode – progress bar only

/q[n|b|r|f]
Sets user interface level
n – No UI
b – Basic UI
r – Reduced UI
f – Full UI (default)

Example to execute in quiet mode:

SETUP.EXE /s /v/qn

Logging Options

Options to control the logging of the installation process:

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i – Status messages
w – Nonfatal warnings
e – All error messages
a – Start up of actions
r – Action-specific records
u – User requests
c – Initial UI parameters
m – Out-of-memory or fatal exit information
o – Out-of-disk-space messages
p – Terminal properties
v – Verbose output
x – Extra debugging information
+ – Append to existing log file
! – Flush each line to the log
* – Log all information, except for v and x options

Example to log the verbose output (on one line):

SETUP.EXE /s /v/qn /v"USERNAME=\"CEM\"" /v"COMPANYNAME=\"ABC, Inc.\"" /v"INSTALLDIR=\"C:\Program Files\CivilGEO\"" /v"/lv \"C:\temp\InstallLog.txt\""

Restart Options

Options to control the restarting of the computer after installation:

/norestart
Do not restart after the installation is complete

/promptrestart
Prompts the user for restart if necessary

/forcerestart
Always restart the computer after installation

Example to control restarting of the computer (on one line):

SETUP.EXE /s /v/qn /v"USERNAME=\"CEM\"" /v"COMPANYNAME=\"ABC, Inc.\"" /v"INSTALLDIR=\"C:\Program Files\CivilGEO\"" /v"/lv \"C:\temp\InstallLog.txt\"" /v/norestart