132
LogTag Analyzer User Guide (2.0)
Distributing software to
workstations
When using the software on many computers within a computer network, it is not always
efficient to visit and install the software and subsequent updates manually on each
computer workstation. The installation of the software does support zero administration
installation, whereby the installation package can be located on a central point, usually a
server, and have it install on each relevant workstation, without requiring user
intervention.
To distribute the software without user intervention is a two step process.
1
Create an installation script file that will provide the answers and actions to be
performed on each step of the installation process. To create an installation script, use
the following command line syntax, including the quotes as used:
\\myserver\my_apps_path\setup.exe /a /r /f1"\\myserver\my_apps_path\setup.iss"
2
Ensure that whenever a user installs the software the installation script is used. To
install the software using an installation script previously created use the following
command line:
\\myserver\my_apps_path\setup.exe /a /s /f1"\\myserver\my_apps_path\setup.iss"
Where,
a
"\\myserver\my_apps_path\" represents the network path to the folder containing the
installation of the LogTag Analyzer software.
b
"setup.exe" is the installation software.
As many different installation scripts as are suitable for your situation may be defined and
used.
LogTag Analyzer software is released on the LogTag Recorders Internet site using a
standard filename syntax, which is
[software_name][major_version][minor_version]r[release_version].exe. For example, if
the file name of the installation package was "logtag_analyzer10r24.exe" the name of the
software would be "LogTag Analyzer" version 1.0 Release 24.
The installation of the LogTag Analyzer software involves copying a number of files to the
destination folder, which can be chosen during the installation process, a file is installed in
the Windows System folder and some plug and play drivers to support the USB Interface
Cradle. Therefore, when deploying the software onto Windows NT
®
based operating
systems, like Windows NT
®
, Windows 2000
®
and Windows XP
®
, the user installing the
software will require local administrator privileges for the software to install correctly. It is
possible, to elevate a users permissions on a Windows NT
®
based server network for the
sole purpose of being able to install the software successfully through the use of a Group
Policy Object.
Summary of Contents for Analyzer
Page 1: ...2 0...
Page 23: ...Chapter 3 Quick Start Guide 23 Only flashes if no alert condition is present...
Page 170: ......