Example Answer File
The following is an example answer file that could be used when silently installing VShell.
# Value file for VanDyke Software VShell installer.
# Run the installer (e.g., vshell-x86.exe) with the following
# command-line options to make use of this file:
# /v"ANSWERFILE=Full_Path_To_This_File"
# For example:
# vshell-x86.exe /s /v"/qn ANSWERFILE=c:\temp\myValuesFile.txt"
#
# With a silent installation (include the /s /v"/qn" command-line option
# when launching the vshell-x86.exe installer), no dialogs are
# displayed and the options specified here will be used in place of the
# default installation options.
#
# With an interactive installation, the default values presented
# in the interactive dialogs of the installer will be replaced with
# any corresponding values defined within this file.
#
# Install Options
# -------------------------
# INSTALL_DIR: Full path to where the product should be installed.
# Environment variables are allowed here.
#
# Note that the value should not contain " (double
# quote) characters, even if there are spaces in the
# path.
#
INSTALL_DIR=C:\Program Files\VanDyke Software\VShell
# INSTALL_IN_FIPS_MODE: VShell can be installed in FIPS mode,
# which means that connections to VShell will only be allowed
# to use FIPS-approved algorithms. Enabling FIPS mode is recommended
# for organizations that need to comply with Federal security
# guidelines such as FIPS 140-2 or NIST 800-53.
#
INSTALL_IN_FIPS_MODE=NO
# Valid values for these options include YES | NO
#
CREATE_PROGRAM_GROUP=YES
CREATE_CTRL_PANEL_SHORTCUT=NO
START_VSHELL_SERVICE=YES
START_FTPS_SERVICE=YES
START_CONTROL_PANEL_APPLICATION=YES
# INSTALL_PUBLIC_KEY_ONLY: Public-key-only authentication under
# Windows requires installing an LSA module in the System32
# directory and will require a reboot.
# WARNING: If /NOREBOOT is specified on the command line, the value
# of INSTALL_PUBLIC_KEY_ONLY is ignored.
#
INSTALL_PUBLIC_KEY_ONLY=YES
# INSTALL_FTPS_SERVER: Installs the VShell FTPS server, which supports
# FTP secured with SSL.
#
INSTALL_FTPS_SERVER=YES
# Ignored if silent install.
#
DISPLAY_README=YES
DISPLAY_HISTORY=YES
SUBSCRIBE_NEWSLETTER=YES
# Post-install options
# --------------------
# Environment variables are allowed, but the Installer will
# attempt to evaluate them automatically unless you escape each %
# character.
# LICENSE_FILE: Full path to the file containing license
# information. The .lic file allows for registration of
# the product at install time. The .lic file must follow
# the format specified in the license letter you received
# when your licenses were purchased.
# The .lic file is copied to the installation folder and
# renamed according to the naming convention required by
# the application being installed.
# NOTE: The license file must exist on the destination
# machine (or be available via a network path using
# a mapped drive or UNC path) prior to installation.
#
# Environment variables are also allowed here, but require
# two % characters on each side of the variable name.
#
# Note that the value should not contain " (double
# quote) characters, even if there are spaces in the
# path.
#
#LICENSE_FILE=C:\temp\myvshell.lic
# REGISTRY_CONFIGURATION_FILE: Full path to the file containing
# configuration values that the installer will merge into the
# Registry. This file must be in the Registry format and end
# in .reg.
# NOTE: The registry file must exist on the destination
# machine (or be available via a network path using
# a mapped drive or UNC path) prior to installation.
#
# Environment variables are also allowed here, but require
# two % characters on each side of the variable name.
#
# CAUTION: This will change the Registry on the machine where
# VShell is being installed. Care should be taken
# when making any changes to the Registry.
#
# Note that the value should not contain " (double
# quote) characters, even if there are spaces in the
# path.
#
#REGISTRY_CONFIGURATION_FILE=C:\temp\vshell-test.reg
# AUTO_REBOOT: Tells the installer to reboot or not reboot at
# the end of the installation. If the value is NO, the
# installer will not reboot the machine at the end of the
# installation, even if a reboot is required to complete the
# installation. If the value is YES, the installer will
# reboot the machine at the end of the installation even if
# no reboot was necessary. If this value is unspecified,
# the installer will decide if a reboot is required.
# AUTO_REBOOT=NO
# AUTO_REBOOT=YES