by @Macarlo
Windows 2000 Professional Beta Tester
(Screenshots by Namo Capture)

 Hi All.
I just tested here on my Windows 2000 Professional, the Workstation of the a.k.a. operating system Windows NT 5.0, the new Norton AntiVirus for this platform, release 7.01. Normally, as you know, all anti virus consumed high CPU and sucks excessive physical memory; this new release is really an exception, because sucks not much RAM and consumes only 66 per cent of CPU of the obsolete Pentium 200 that I'm using here for tests.

 READ ALSO

Norton AntiVirus Runs Fine on Windows 2000 Beta 3 - FAT

Norton AntiVirus Fails on Windows 2000 Professional

As you can see in the photo above, NortonAntivirus 7.01 Enterprise Solution is a tool for a network in a corporate environment, but if you are a SOHO user you also can use it fine, because this fine piece of software offers several options for install. The only problem I saw is if you are a beginner you simply can't install this one, because you will judge complicated the install menu, that have some hermetic words for a inexperienced user. But if you have any experience this install is simple and intuitive.

I installed my 7.01 from his CD and at the same time I was surfing on the Net, seeking for news and uploading files. I encountered not problems and this soft installed just fine, in few minutes. I installed in first the Snap-ins Photo above), in second the Central Quarantine Locally (screenshot below) and in third the Norton AntiVirus Client Locally.

Note that when the install is running and when I'm surfing and updating sites my nice NamoCapture was capturing screenshots for this review. Norton AntiVirus for Windows 2000 is a giant pack, totalising 270 megabytes on his CD (!!!). Yeah, man, when I remember that an OS/2 Warp 3.0 runs just fine using 20 megabytes on a DX486 with 8MB RAM I said with me: Bob Dylan is really right, the times are changing!

Just I finished the install of this fine anti virus he connected the Symantec Server by itself in order to update files and ask me about this operation; I authorized and the soft started the upgrade, as you can see in the next three images below:

1

2

 3

In the next screenshot you can see the Norton AntiVirus graphical interface displayed on my Windows 2000 Professional. Note that the design follows the Win 2000 style:

Technical Information

Installation Issues

 * Microsoft Management Console progress bar screen
 * Installing MMC and SSC on Windows NT machines upgraded
   with Service Pack 6a
 * Rollout using NTREMOTE
 * VPTray.exe running at 99% CPU utilization
 * Lock client settings before rolling out to clients
 * Rolling out Norton AntiVirus to NetWare servers
 * SymEvent and migration from NAV 2000 TO NAV Corporate Edition
 * PACKAGE.EXE and silent install
 * Replacing SETUP.ISS for a silent, unmanaged package
 * Specifying a directory to which Norton AntiVirus
   Corporate Edition Client Packager for DOS files are extracted
 * Upgrading from Norton AntiVirus 4.X/5.0 to Norton AntiVirus
   Corporate Edition
 * Default password for product update
 * Installing Norton AntiVirus for Netware 7.01 to long file folder
   names
 * SSC Discovery Service stops during console migration on PDCs
 * Migration issues

Virus-definition File Updating Issues

 * Primary server assignment may affect virus definition updating
   on secondary servers
 * Update Virus Pattern File for Windows 3.x clients

Usage Issues

 * LiveUpdate Administration Utility update
 * Don't uninstall the AMS Server from Norton AntiVirus servers
 * Displaying infected computer name in an AMS2 alert
 * DBCS Characters in Lotus Notes
 * Address cache sharing for Symantec System Center console and
   Norton AntiVirus server
 * Finding Windows NT computers requires TCP/IP protocol
 * Console information gathering

Client and Server Issues

 * Help file for Norton AntiVirus server
 * CorporateFeatures registry value for Scan and Deliver
 * Quarantine forwarding from Microsoft Windows 95
 * Required IPX syntax for Quarantine Forwarding
 * Norton AntiVirus tray icon on Windows NT servers
 * Installing over Norton AntiVirus Corporate Edition 6.0
   server
 * VPLOGON and Window 98 client migration from version 6.0
 * Administering Win9X clients with IPX/SPX protocol only

Windows 3.x Client Issues

 * "Cannot find realtime scan VXD" message after Windows 3.x
    install
 * DOS window error message when installing Windows 3.x
   clients

International Issues

 * Do not install SSC console to DBCS directory
 * Required Diamond video driver update
 * Managing alerts with the Japanese version of Alert
   Management System2

Installation Issues

Microsoft Management Console progress bar screen

In the Microsoft Management Console (MMC) installation program,
the second screen after the license agreement is an installation
progress indicator. The progress indicator screen includes a Next
button in the lower right corner.  If you click Next before the
progress bar is allowed to finish and automatically close, the
Microsoft Management Console install will continue, but will not
successfully complete.

Installing MMC and SSC on Windows NT machines upgraded
with Service Pack 6a

When you first install Microsoft Management Console and Symantec
System Center to a Windows NT 4.0 Server or Workstation machine
that has been upgraded with Service Pack 6a, the machine may
hang at the end of the install process.  

To resolve this issue, uncheck the "Restart the computer" box
that appears on the final MMC setup screen.  When the MMC and SSC
installation is complete, the final SSC setup screen appears. By
default, the "Yes, I Want to Restart My Computer Now" radio
button is selected. Click Finish to restart the computer.

Rollout using NTREMOTE

Before performing a rollout using NTREMOTE, check the TEMP
directory  to verify that it is empty.  If the TEMP directory
contains install files, delete them. You can then roll
out successfully using NTREMOTE.

Also note that you cannot run NTREMOTE to roll out to the same
client twice without first rebooting the client.

VPTray.exe running at 99% CPU utilization

Windows NT 4.0 or Windows 2000 machines must be logged in before
you use the NT Client Install Utility (NTREMOTE) to roll out and
install clients.

If you roll out when a machine is not logged in, the VPTRAY.EXE
process may run at 99% CPU utilization. To verify CPU
utilization, log in and view the Processes tab of the
Windows Task Manager following the install.

You can reboot the machine to bring the CPU usage of
VPTRAY.EXE down to normal levels.

Lock Client Settings Before Rolling Out To Clients

Before you roll out to clients, verify that realtime
protection settings are locked. If settings are not
locked, changes made to unlocked client realtime protection
options from the console can be overwritten with settings
made on the client locally.

Rolling out Norton AntiVirus to NetWare servers

If you enter the incorrect user name and password during the
rollout of Norton AntiVirus Corporate Edition for NetWare
Servers, the installation program will accept them.  Later,
when Norton AntiVirus is loaded on the NetWare server, you
will be prompted to enter a valid admin name and password.  
At this point, you can provide the correct user name
and password. Norton AntiVirus will load properly.
However, the groups "nortonantivirususer" and
"nortonantivirusadmin" will not be assigned the proper
rights.  When you add users into the groups, they will
not be able to get Norton AntiVirus.  To resolve this
issue, you will need to manually assign Read and Scan
rights for the following two folders to users in the
group:

   SYS:NAV
   SYS:LOGIN\NAV

When you install Norton AntiVirus Corporate Edition for
NetWare Servers in two different volumes under the same
Organizational Unit, and then remove Norton AntiVirus
Corporate Edition for NetWare Servers from one volume,
the "nortonantivirususer" and "nortonantivirusadmin"
groups created during the install will be deleted.

To resolve this issue, you must create the
"nortonantivirususer" and "nortonantivirusadmin"
groups, then assign the appropriate rights
to them.

Slow scanning after migration from NAV 2000 TO NAV
Corporate Edition

When you migrate machines that have mapped network drives
from Norton AntiVirus 2000 to Norton AntiVirus Corporate
Edition, you may experience very slow scanning of the
boot sector. This occurs because the SymEvent component
has not been updated. To update the SymEvent
component, you must reboot the machines.

In summary, the logical order should be as follows:

1. Migrate from NAV 2000 to NAV Corporate Edition.
2. Restart.
   The updated version of SymEvent is then loaded.

PACKAGE.EXE and silent install

If you create a silent, managed install package from CD2,
you must modify the GRC.DAT file in the corresponding OS
folder (for example, WINNT for Windows NT/2000).

Complete the following steps:

 1. Copy the installation folder from the CD
    to the local machine.
 2. Open the copy of GRC.DAT with a text editor, such as
    Notepad, from the appropriate OS directory under
    \CLT-INST.
 3. Locate the line that beings with Parent=
 4. After the = sign, add the following:

    S<SERVERNAME>

    where <SERVERNAME> is the name of your Norton
    AntiVirus server. You must enter the name is ALL
    CAPS.

 5. Save and close the text file.

The GRC.DAT must be changed and saved before the
package is created in order for the silent install
to work for both the single executable file and for
the floppy disk set.  

This needs to be done for the appropriate platform
(for example, Windows NT/2000 or Windows 95/98) before
creating the silent package.

PACKAGE.EXE has been enhanced so that it can now read
switches specified in the CONFIG.INF file when creating
a silent install package. (A description of each switch
is included in the Config.inf file.)  To enable this
option, check "Accept Config.inf Options For Silent
Install" in the Norton AntiVirus Corporate Edition
Client Packager dialog box. Note that you will need
to modify the CONFIG.INF file in the corresponding
OS folder (for example, WINNT for Windows NT/2000)
before creating the package.

Specifying a directory to which Norton AntiVirus
Corporate Edition Client Packager for DOS files are
extracted

The Norton AntiVirus Corporate Edition Client Packager
extracts cabinet file contents to the current working
directory unless you specify a target directory on the
command line.  If you are running the Norton AntiVirus
Corporate Edition Client Packager from a floppy
disk, you must specify a target directory.  For
information about Packager command-line parameters,
use PACKAGE.EXE with the /? command line parameter.

Some conditions under which you may want to use this
variable:

- If you want the system to ignore the default temp
  variable
- If you are installing to a different location than
  the current working directory.

Replacing SETUP.ISS for a silent, unmanaged package

You must replace the SETUP.ISS file before creating a
silent, unmanaged package from CD2.

Before running PACKAGE.EXE to create a silent package,
copy the SETUP.ISS file from the UNMANAGE folder
and replace the existing SETUP.ISS in the appropriate
platform folder (for example, copy it to the WINNT
folder for a Windows NT package).

The installation folder must be copied locally in order
to save and make these changes.

PACKAGE.EXE has been enhanced so that it can now read
switches specified in the CONFIG.INF file when creating
a silent install package.

(A description of each switch is included in the
CONFIG.INF file.) To enable this option, check
"Accept Config.inf Options for Silent Install"
in the Norton AntiVirus Corporate Edition Client
Packager dialog box. Note that you will need to
modify the CONFIG.INF file in the corresponding
OS folder (for example, WINNT for Windows NT/2000)
before creating the package.

Upgrading from Norton AntiVirus 4.X/5.0 to Norton
AntiVirus Corporate Edition

To upgrade from Norton AntiVirus 4.x/5.0 to Norton
AntiVirus Corporate Edition, you must run the Install
rather than the Update program.

Default password for product update

When you upgrade to Norton AntiVirus Corporate Edition
7.0 server from a machine on which LANDesk Virus Protect
was installed, the Symantec default password overwrites
any LANDesk Virus Protect password during the
installation process.  

The default Symantec password is (all lower case):

   symantec

Installing Norton AntiVirus for Netware 7.01 to long
file folder names

Do not install Norton AntiVirus for Netware 7.01 to
a long filename folder (longer than 8 characters).

SSC Discovery Service stops during console migration
on PDCs

When the Symantec System Center Discovery Service
(NSCTop.EXE) is stopped while you are migrating to
a newer version of the console, NSCTop.EXE may terminate
abnormally on a PDC. The install process will abort.

To resolve this issue, simply rerun the install.

Norton AntiVirus Enterprise Solution Migration

Norton AntiVirus Corporate Edition 7.01 will upgrade
existing NAV Corporate Edition 7.00 machines while
preserving the settings. It is important to remember
the following:

* If the Norton AntiVirus Corporate Edition user
interface is open on a client, changes cannot be made
to "Client realtime protection options" if they are
"unlocked" because settings made at the console will
be overwritten with any settings made on the client.

* Server-distributed settings will be overwritten
with settings made on the client locally.

* Norton AntiVirus Corporate Edition 7.01 follows
the same steps for all other antivirus products as
listed in the documentation for Norton AntiVirus
Corporate Edition 7.00.

* Symantec System Center 4.01 follows the same
steps for all other products as listed in the
documentation for Symantec System Center 4.00.
If your console is on a Windows NT PDC, see the
previous topic, "SSC Discovery Service stops during
console migration on PDCs".

Virus-definition File Updating Issues

Primary server assignment may affect virus definition
updating on secondary servers

When you assign primary server status to a server
before other servers in the group have been discovered
by the console, the primary server will not be able
to update virus definitions files on the secondary
servers. This remains true even after the servers
are discovered.

Once all servers have been discovered by the console,
you can correct this issue by temporarily assigning
primary server status to a different server.

Complete the following procedure:

 1. Assign primary server status to a different server
    in the server group.

    All other servers will now look to this server for
    virus definition updates.

 2. Reassign primary server status to the original
    primary server in the server group.

    Now all secondary servers will correctly point to this
    server.

Update Virus Pattern File for Windows 3.x clients

TCP/IP must be installed on Windows 3.x clients to enable
the Update Virus Pattern File feature.  If TCP/IP is not
installed, an error message reports that "Norton AntiVirus
could not launch the Virus Pattern File Download utility."

Usage Issues

LiveUpdate Administration Utility update

Norton AntiVirus Corporate Edition 7.01 products may not
appear in the LiveUpdate Administration Utility listing
until the LiveUpdate Administration Utility itself is
updated.  To perform the update, choose Update LiveUpdate
Administration Utility from the Tools menu.

Don't uninstall the AMS Server from Norton AntiVirus servers

After installing Norton AntiVirus server with the AMS server,
do not uninstall the AMS server.  If you uninstall the AMS
server, the Intel PDS service is also uninstalled. This
service is required for communication with the Symantec System
Center console discovery service.

Reinstalling SSC (without AMS) will reinstall the PDS
service. It is not possible to reinstall AMS without
installing both SSC and AMS.

Displaying infected computer name in Alert Management System2
alert

When you configure an alert message, and click the Default
button to include default fields, the following fields
are included:

   Alert: <Alert Name>   (the name of the alert)
   Computer: <Host Name> (the name of the associated
                          primary server)
   Date: <Date>          (the current date)
   Time: <Time>          (the current time)
   Severity: <Severity>  (the level of severity)
   Source: <Source>      (the directory on the infected computer
                          where the infected file is located)

To add the name of the computer where the infected file is
located to the message, click the Computer alert parameter.

DBCS characters in Lotus Notes

DBCS characters in e-mail alerts will appear as invalid
characters in Lotus Notes.

Address cache sharing for Symantec System Center console
and Norton AntiVirus server

When the machine on which you run the Symantec System
Center console is also designated as a primary server,
the same address cache is used for the console and
the primary server.  

The primary server may not be able to report the address
of its secondary servers back to any Symantec System Center
console until that machine checks in again with the
primary server.

Finding Windows NT computers requires TCP/IP protocol

Using the Find Computer feature to find Windows NT computers
on which the Norton AntiVirus Corporate Edition is installed
requires the TCP/IP protocol. If you remove the TCP/IP protocol
from a Windows NT server, you will not be able to find
the computer.

Console information gathering
-
The amount of time required for the console to gather
information from a server group varies, based on factors
such as server group size and link speed.  While the
console is gathering information, it may appear
as if the console is not responding. Once the gathering
process completes, the information appears and console
control is restored.

Client and Server Issues

Help file for Norton AntiVirus server

The Norton AntiVirus Enterprise Solution includes Norton
AntiVirus server as well as client installations.  Because
both programs perform essentially the same functions, they
share one set of Help files.  Some features, however, are
unique to client installations.  These are Startup Scans,
Custom Scans, and Scheduled Scans.  Although references
to these scan types may appear in the online Help system,
these scan types are not supported by Norton AntiVirus Server.

CorporateFeatures registry value for Scan and Deliver

A registry key controls Scan and Deliver behavior for the Norton
AntiVirus client. The CorporateFeatures value determines whether
the Corporate information panel is displayed in Scan and Deliver
to permit sending more than one file per day to SARC.

To enable or disable this capability, set the following registry
key:

   HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Norton AntiVirus

   CorporateFeatures=0 Disable, allows only 1 file per day to be
   submitted to SARC

   CorporateFeatures=1 Enable, permits more than 1 file per day
   to be submitted to SARC

Quarantine forwarding from Microsoft Windows 95

If Quarantine forwarding from Windows 95 does not work properly,
download "Dial Up Networking 1.3 Performance &
Security Update" for Windows 95 from the Microsoft web site.

Required IPX syntax for quarantine forwarding

When specifying a central quarantine server that uses
IPX protocool  only, you must use IPX address rather
than the machine name.

When specifying the IPX address, use the
following syntax:

   <NetworkNumber>.<MacAddress>

For example:

   00000152.00a024a41fc7

Norton AntiVirus tray icon on Windows NT servers

The Norton AntiVirus tray icon does not appear after a Norton
AntiVirus Corporate Edition installation to a server until
the computer is restarted. Norton AntiVirus is, however,
installed and working properly.

Installing over Norton AntiVirus Corporate Edition 6.0 server

To migrate from Norton AntiVirus Corporate Edition version 6.0
server to version 7.01, choose Install, not Update.  If you
choose Update, the migration will indicate that it failed.
However, it is likely that it succeeded. If the server rollout
program lists multiple errors, then the update did fail.
If the only error message is "service has stopped
responding", it is very likely that the update succeeded.

VPLOGON and Window 98 client migration from version 6.0

The upgrade will fail if VPLOGON is used to migrate from Norton
AntiVirus Corporate Edition version 6.0 client to version 7.01.
However, the installation will succeed at the next login if
"Forced Update During Next Login" is checked in the Client
Login Scan and Installation task.

Administering Win9X clients with IPX/SPX protocol only

If the console has trouble administering Win9x clients with
only the IPX/SPX protocol (no TCP/IP), try specifying the
proper Ethernet frame type for your network instead of
using "Auto". This setting can be found under the advanced
IPX/SPX properties page in your client machine's network
settings.

Windows 3.x Client Issues

"Cannot find realtime scan VXD" message after Windows 3.x install

A spurious error message may appear when you start Norton
AntiVirus after installing to a Windows 3.x client. Click OK,
then start Norton AntiVirus again.

DOS window error message when installing Windows 3.x clients

A spurious error message stating that the install program
"cannot be run in DOS" may be displayed. Ignore the message.

Note that during install, the DOS window is maximized.

International Issues

Do not install SSC console to DBCS directory

You cannot install the Symantec System Center console to
a DBCS directory path. Install the Symantec System Center
console to a non-DBCS directory.

Managing alerts with the Japanese version of Alert Management
System2

Buttons are not enabled in the Japanese version of Alert
Management System2.  To set alert options, you must right-click
the selections.

Required Diamond video driver update

On Japanese machines, if you are using the Diamond video driver  
version # 4.00.138.0228, you must update to version 4.00.1381.0301.

Copyright (c) 1999, 2000 Symantec Corporation

@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited

[TOP] [HOME] [INDEX]