Distribution Through NetWare
You are advised to save this page
in HTM format, or print it with your online printer, for later reference.
The purpose of installing InVircible on a Novell server is
for its distribution to clients, only. DOS or Windows applications cannot run
under NetWare. Hence, InVircible will not run on the server itself. Before installing
InVircible to the server, InVircible should be installed to the administrator’s
client station first. Only then, the InVircible programs can be copied to the
distribution directory on the server.
Installation to the administrator
workstation
Install the complete InVircible package, including its network
management tools on the administrator workstation. Start the InVircible Setup
program, select “Custom installation”, and check the “Network
installation tools” option. The package will be installed to “C:\IV”,
on the administrator's console.
After installation is complete, restart the computer. InVircible
will check for viruses and automatically secure your program files. It is recommended
to check the administrator console for viruses at this time, before copying
the InVircible files to the distribution directory on the server.
Preparing InVircible for distribution
“FLAG F:\LOGIN\IV\ ROS”.
The License Templates
To complete the installation, copy your set of registration
templates to the distribution directory. Owners of a site license should have
three templates: User.txt, PwrUser.txt, and Admin.txt.
The presence of the administrator template, Admin.txt, is required
in the IV distribution directory, in order to set the distribution and configuration
parameters, described next.
Setting InVircible's working configuration
The following procedure will set which components of InVircible will be distributed
and installed to the clients workstations, as well as the settings of how InVircible
will work on these workstations. The default settings were selected for optimal
operation in most installations. Normally, there is no need to change these
default settings.
- Edit “ivb.ini” on the server, in the distribution directory to
add/remove files to be checked or skipped by IVB. See IV's online documentation
how to do this.
- Edit “ivx.ini” on the server to add/remove files to be checked
or skipped by IVX for macro viruses. See IV's online documentation how to
do this.
- Edit “iv.ini” on the server to configure the desired options for
the end-users (start IV.EXE from the distribution directory, then
press Alt + K to set and save the parameters stored in IV.INI).
- Create a configuration profile for Win32 users (Windows 95/98 and NT workstations).
This profile defines which components will be installed on end-user workstations,
and sets their working configuration:
- Start “IV configuration utility” from the InVircible
program group (Windows start menu).
- Determine the path and target directory for installing IV on the client's
workstations. "C:\IV" is recommended.
- Define if creating a program group is required on the workstation.
- Determine which components should be installed to workstations and their
working configuration.
- Save the configuration (INI) profile in the distribution directory.
Distribution through the System Login Script
Distribution takes place as part of the logon process. “IVLOGIN”
and “IVWLOGIN”, from the InVircible package take care of
installing and upgrading the DOS and Windows portions of InVircible, respectively.
Use your NetWare utilities: Syscon,
NwAdmin or NetAdmin to edit
the “System Login Script”. In NetWare 4.xx, edit the “Organization
Login Script” instead.
Add the following lines to the script. It's recommended that
you add them at the beginning of the script:
REM This command will distribute InVircible programs to workstations
.
MAP X:=SYS:\LOGIN\IV\
# X:IVLOGIN.EXE /FallBack /REG=reg_template /DIR=C:\IV
# X:IVWLOGIN /ForceOpt profile.ini
Script legend:
|
X:
|
A temporary logical drive required for running IVLOGIN.
Choose a not yet used letter for the temporary logical drive.
|
|
/FallBack
|
Directive to instruct IVLOGIN to run without graphic
display, for minimal workstation memory consumption.
|
|
Reg_template
|
Replace with the license template filename, to be used
on end-user workstations, e.g. user.txt.
|
|
/ForceOpt
|
Directive to force the settings contained in the Win32 profile file
to the logging workstation, whenever connecting to the server.
|
|
DIR=C:\IV
|
Directive to specify the target directory at the workstation
for installing IV.
|
|
profile.ini
|
Replace profile.ini with the filename of the
profile that defines the Win32 components for installation and settings.
|
Note: If running Novell Client32
then you are advised to replace the # (hash) command with the
@ ("at" mark). The hash command instructs
NetWare to execute the external command following the hash sign and wait
until execution is completed, before resuming execution of the next line in
the script. The at mark (@) instructs NetWare's Client32
to start executing the instruction after the @, and immediately resume execution
of the script, without waiting for the external command to
complete execution. The @ command is interpreted only
by Novell Client32 (there also exist a Microsoft version of Client32
to which the above does not apply) and may resolve problems encountered in earlier
NetWare scripts.
Daily operation
If you did all the above correctly, then InVircible should
now be set for automatic distribution and upgrading throughout the network.
As of now, any workstation that logs-on to the server will first execute the
login script. InVircible will install itself just once to every workstation.
On subsequent login, InVircible will compare the version number
on the server and on the workstation. If they differ, the copy on the workstation
will be upgraded to the same as on the server. All you need to do in order to
keep InVircible up-to-date throughout the organization, or to renew a license,
is to update the copy in the distribution directory on the server. The rest
will be done automatically, in the course of daily work, simply by logging in
to the server.
Last modified: May 15 2007 |
Site Map
