SE_UTIL Deployment Utility

A. Introduction
B. Installing SE_UTIL
C. Updating the Server
D. Testing the Update Process
E. Novell NetWare Setup Considerations
F. NT Server Setup Considerations
G. Automating Win95/WinNT Updates
H. Automating DOS/Win3.1x Updates
I. Support
J. Common Questions

A. Introduction

SE_UTIL is an effective, easy to use deployment utility for Command AntiVirus™ with F-PROT Professional®. SE_UTIL can be used for either first-time deployment or updating existing installations in a multi-platform environment. The functionality of SE_UTIL is quite simple. The software to be installed or updated is stored on a server and the workstations are connected to this shared location via a mapped drive. Installations and updates are then accomplished via the login script.

[top]

1. Download the SE_UTIL.EXE file and place it in a directory (by itself) on the Administrator's workstation. Do not place this file on the server drive as errors could occur.

2. In the unique directory where SE_UTIL.EXE has been placed, type SE_UTIL.EXE [ENTER]. This is a self-extracting file that creates the following files:

   SETTUP.BAT
   installation batch file - requires destination drive letter

   CROSSPLT.EXE
   self-extracting PKzipped file - extracted by a batch file

   READ1ST.TXT
   an ASCII version of this file

   NEW.TXT
   features enhanced by this version of SE_UTIL

   SE_UTIL.DOC
   this file

3. Install the utility to the server. Type SETTUP.BAT S: [ENTER] where S: is the mapped drive specified for the SE_UTIL installation.

Behind the scenes:
SETTUP.BAT does the following:

• extracts the file CROSSPLT.EXE to the local directory
• expands recursed subdirectories named UPGRADE and UPDATE
• SETTUP.BAT creates the directory path \CSS\ANTIVIR at the server
• it copies the contents of the local UPDATE sub-directory to the file server
• SETTUP.BAT will modify the CHECK.BAT (now found in \CSS\ANTIVIR\ ) to indicate which drive is being used for the SE_UTIL utility. This is handled via an environment variable setting SET SERVDR=S: (or whatever drive letter is being used for the installation).
• SETTUP.BAT will create the product directories as well as the product installation directories. The product directory will contain definition file updates and the installation directories should contain the full product version of Command AntiVirus.

Hint: The file server must be a mapped drive letter to which users have access. Use the MAP ROOT command to create this mapping if security measures do not allow placing the server copy in the root of the available server drives.

[top]

Method 1: Using Diskette Set
Change into the UPGRADE directory on the Administrator's workstation and type:

UPGRADE {server} {source drive letter} [ENTER] 

EXAMPLE: UPGRADE S: A: [ENTER]

This will ask for the Command AntiVirus installation diskette(s). The command copies the appropriate files to the specified directory on the server.

Method 2: Using Product Downloads (FTP ,Web or BBS)
1. After downloading Command AntiVirus to the local machine, place the downloaded copy into a working directory, preferably one assigned to this task. Then, extract the file by typing its self-extracting file name. Note: if the file has a "zip" extension, you will need to use an unzipping utility such as PKunzip™ or WinZip™.

2. After extraction, locate the file named ONEDISK.BAT. This file is used for file placement into the specified directory on the file server. At the DOS command line, run the ONEDISK command as in ONEDISK S:\css\antivir\fpw95 [ENTER]. A table of platforms that you can substitute into the command line per operating system is listed below:

F:\CSS\ANTIVIR\FPW\SETUP
Command AntiVirus for DOS/Windows

F:\CSS\ANTIVIR\FPW95\SETUP
Command AntiVirus for Win95

For Windows NT platform, please see the section "G.2 Automating Windows NT Installations".

[top]

To test the updating procedure, change into the S:\CSS\ANTIVIR directory on the server and type:

CHECK.BAT [ENTER] 

This will examine your workstation and install the appropriate software. If this test works properly, the administrator can place this command in the Netware login script.
If you get an out of environment space error, try this command instead:

CHECK2.BAT [ENTER] 

This will "force" environment space to allow running the CHECK.BAT batch file. E. Novell NetWare Setup Considerations

The CHECK.BAT file is designed to run within a login script. To use it, place the following command in the login script (do not indent this line):

#COMMAND /E:1024 /C S:\CSS\ANTIVIR\CHECK.BAT 

If using NetWare Client32 to connect to a Novell NetWare 4.1 server, use the following syntax instead. Remember NOT to indent this line in the login script:

@COMMAND /E:1024 /C S:\CSS\ANTIVIR\CHECK.BAT 

If you have a mixed environment,

*THE FOLLOWING IS AN EXAMPLE OF
*CLIENT32 & VLM IMPLEMENTATION
*OF SE_UTIL IN A LOGIN SCRIPT
*
* OS_VERSION="V7.00" ARE NOT CLIENT32
* OS_VERSION="V4.00" ARE USING CLIENT32
IF OS_VERSION="V7.00" THEN BEGIN
* Do not indent this line!
#C:\COMMAND /E:1024 /C S:\CSS\ANTIVIR\CHECK.BAT
END 
IF OS_VERSION="V7.00" THEN BEGIN
GOTO DONEFP
ELSE
IF OS_VERSION="V4.00" THEN BEGIN
@C:\COMMAND /E:1024 /c S:\CSS\ANTIVIR\CHECK.BAT
END 
DONEFP:
*SUBROUTINE JUMP

[top]

SE_UTIL can also be implemented on an NT Network. SE_UTIL requires that a mapped server drive be used. Mapping can be accomplished using a command like the one below:

net use S: \\NTMAIN\NT40 �--

All workstations affected should have the same mapped drive prior to use of the SE_UTIL distribution utility. Once this mapping been established, the other properties involved fall into place.

Edit the NT login script to indicate the following syntax:

NET USE S: \\NTMAIN\NT40 �--

CD S:\CSS\ANTIVIR
CALL S:\CSS\ANTIVIR\CHECK2.BAT
CD S:\ 

Running the CHECK.BAT file through the NT login script has resulted in two reported anomalies:

1. If the user is already running a copy of Command AntiVirus for Windows, the user may get an error message stating that an existing version of F-AGENT is active. This is because Windows users already have DVP (Dynamic Virus Protection) running when they log in to the NT system. Unlike the Command AntiVirus setup program, CHECK.BAT does not turn off the DVP. Restarting Windows will eliminate this message.

2. If the user did not have a copy of Command AntiVirus running on the workstation, the user may get the error message that DVP could not be run as the device driver has not been loaded. As in the above instance, Windows is running when one logs on to the NT server. As a result, the system has already loaded the device drivers listed in SYSTEM.INI. CHECK.BAT adds the device line. However, an attempt to run DVP in the current Windows session would result in aforementioned error message. Again, a restart of Windows would eliminate the error message.

[top]

The Windows 95 and Windows NT installations are actually handled by the SETUP.EXE file within the \css\antivir\fpw95\setup and \css\antivir\fpwnt\setup directories. The SETUP.EXE file uses an initialization file called SETUP.INI. This file can be edited and the administrator can change some of the values registered to create customized installations using SE_UTIL techniques. Unless the .ini file is modified, a user-interactive installation will occur.

Here are suggestions of allowable modifications to the SETUP.INI file that will aid in a silent installation.

1. Modify value InstallSilent=YES original value NO
2. Modify value MakeRescueDisk=NO original value YES
3. Modify value LaunchReadme=NO original value YES
4. Modify value LaunchFPROT=NO original value YES

[top]

Placing the product Command AntiVirus for Windows NT on a server drive for deployment by SE_UTIL requires the use of SETUP NETADMIN instead of ONEDISK.BAT. The following steps outline the procedure to follow:

• Insert disk #1 of Command AntiVirus for Windows NT
• Select START > RUN (or FILE > RUN) A:\SETUP NETADMIN
• After the welcome screen, the Network Setup Configuration dialog box will open.
• In the first UNC entry box, enter the location on the network where you want to store the (shared) components of Command AntiVirus, in the event you wish to use a LAN installation later. In the second UNC entry box, enter the location of the install file set, in this case where ..\css\antivir\fpwnt\setup is
  Example:
  \\ntmain40\shared\css\antivir\fpwnt\shared
  \\ntmain40\shared\css\antivir\fpwnt\setup
• There is a check box which controls whether you want users to be able to scan network drives. If you clear this box, select Next (ignore the next two steps)
• Select Next.
• Scheduling a scan of the server requires a valid logon id: username - existing account must have access rights to network drives scanning requires the read right; disinfect, quarantine and delete requires the write right the account should be accessible for all userspassword should not expire; if password does expire, modify the password information in Command AntiVirus for Windows NT by selecting PREFERENCES > ADVANCED > SERVICE ACCOUNT
• Select Next, and insert disks for FNT as required.
• The Command AntiVirus config dialog box will open; fill in your name and company information.
• Select OPTIONS to view or modify the FNT capabilities; select or clear the choices and select either SAVE or CANCEL.

This will successfully place the Command AntiVirus for Windows NT files into the directory for use by SE_UTIL. SE_UTIL makes use of a batch file called LSILENT.BAT located in UNC path (second path) specified during SETUP NETADMIN process. In order to facilitate a smooth client install of Command AntiVirus over a previously installed version using the SILENT AND LSILENT batch files, the following setting must be added to the SETUP.INI located in the "InstallPath" directory after running "SETUP NETADMIN":

[Network Install]
InstallPath=\\ntmain40\shared\css\antivir\fpwnt\setup
SharedPath=\\ntmain40\shared\css\antivir\fpwnt\shared
ClientQuarantinePath=%SystemDrive%\Program Files\Command Software\F-protnt\Quarantine
EnableNetworkScans=0
DoNotReboot=1

If this line is not added, the setup launched by LSILENT will automatically reboot the machine in order to update the files after setup.

[top]

The Windows installations are handled by the SETUP.EXE file within the \css\antivir\fpw\setup directories. The SETUP.EXE file uses an initialization file called SETUP.INI. This file can be edited and the administrator can change some of the values registered to create customized installations using SE_UTIL techniques. Unless the .ini file is modified, a user-interactive installation will occur.

Here are suggestions of allowable modifications to the SETUP.INI file that will aid in a silent installation.

1. Modify value Silent=1 original value 0
2. Modify value FPSwitches=/Hard /Disinf /Today original value /Hard /Today

[top]