Symantec AntiVirus Corporate Edition v9 Scheduled Scan

[Michael G. Schneider]

I have Symantec AntiVirus Corporate Edition v9 installed on my Windows 2003
servers. It offers the possibility to schedule a LiveUpdate and a Automatic
Scan.

The scheduled LiveUpdate runs fine. It runs even if nobody is logged on to
the server. However, the Automatic Scan does not run. It only starts if
somebody is logged on to the server.

Have I done something wrong? Or won't Automatic Scans start in the
background?

Michael G. Schneider

 

[Ken]

In article <[email protected]>, mgs-AntiSpam@mgs-
software.de says...
You've done something wrong. You usually have a master server. The
other servers are then installed through the master. You then install
the desktops either from the sysvol share on the server that controls
the client, or from the interface on the server that will control the
client. You then set the global properties from the master server for
the domain and from the controlling servers for the clients it controls.

Because it is Symantec and they want you to pay for support, nothing is
intuitive. As a matter of fact, everything seems to be working opposite
to how it seems it should work. It isn't really hard to configure, but
it is really easy to screw it up. Good luck with their documentation
and KB.

 

[Michael G. Schneider]

software.de says...

Thank's a lot for the answer.

You've done something wrong.

But what?

You usually have a master server...

In my case there is no master server. There are several independent servers.
But this is not relevant for my question. Even with one server I would not
have succeeded in setting up an "Scheduled Scan, running unattended".

Because it is Symantec and they want you to pay for support,
nothing is intuitive. As a matter of fact, everything seems to be
working opposite to how it seems it should work.

I do not think so. For me, Symantec Antivirus Corporate Edition is
intuitive. The question is simply: will a scheduled scan run unattended, or
will it only run, if somebody is logged on to the server.

It isn't really hard to configure, but it is really easy to screw it up
Good luck with their documentation and KB.

Unfortunately neither documentation nor KB give an answer. Or at least, I
cannot find it.

Michael G. Schneider

 

[Ken]

Now I am starting to suspect this is not a domain, just a loose group of
machines connected by a wire or wireless. I guess I was fooled by the
use of Corporate edition, which is really designed for a domain. If
this is not the case, than everything depends on what and how you have
set things up and probably needs someone who can apply that personal
touch.

 

[Michael G. Schneider]

Now I am starting to suspect this is not a domain, just a loose
group of machines connected by a wire or wireless. I guess I
was fooled by the use of Corporate edition, which is really
designed for a domain. If this is not the case, than everything
depends on what and how you have set things up and probably
needs someone who can apply that personal touch.

Indeed, this is a domain of 3 Windows 2003 Servers, which I use for
development purpose.

Symantec Antirus Corporate is designed for usage on a Windows Server. The
consumer products (for example Norton Internet Security with Norton
AntiVirus) will not run on a Windows Server.

SAVCorp has features, which are used inside a network. These features can or
cannot be used. In my case, I do not use them. Nevertheless SAVCorp is the
prefered AntiVirus solution from Symantec.

Michael G. Schneider

 

[Jeff.D.Gillis]

Indeed, this is a domain of 3 Windows 2003 Servers, which I use for
development purpose.

Symantec Antirus Corporate is designed for usage on a Windows Server. The
consumer products (for example Norton Internet Security with Norton
AntiVirus) will not run on a Windows Server.

SAVCorp has features, which are used inside a network. These features can or
cannot be used. In my case, I do not use them. Nevertheless SAVCorp is the
prefered AntiVirus solution from Symantec.

Michael G. Schneider

Hi Michael,

The reason your scheduled scans do not run is because they depend upon
the users profile to get the rights to scan and writes the details of
the scan under the HKCU hive in the registry, so when you log off, the
scan goes with your profile. Normally, when you schedule a scan using
the Symantec System Center, it creates a Admin Scan which runs under
the system account and stores under the HKLM hive.
On the CD, in the <cdroot>\Tools\Nosuprt\VPSCAN folder their is a
utility to create scans that run as Admin scans which you can script
and schedule and another utility <cdroot>\Tools\Nosuprt\ConfigEd that
you can use to set the configuration on unmanaged clients (I assume you
are running the SAV Client component and not SAV Server component) if
you are unmanaged. Both utilities have .pdf instructions on their
usage.

 

[Michael G. Schneider]

Thank's a lot for the answer-

The reason your scheduled scans do not run is because they depend
upon the users profile to get the rights to scan and writes the details of
the scan under the HKCU hive in the registry, so when you log off, the
scan goes with your profile. Normally, when you schedule a scan using
the Symantec System Center, it creates a Admin Scan which runs under
the system account and stores under the HKLM hive.

I think the user interface gives the impression that a scan is also started,
when nobody is logged on. Both features "Scheduled LiveUpdate" and
"Scheduled Scan" are started from within the same user interface with almost
identical dialogs. But regarding this detail they do differ.

On the CD, in the <cdroot>\Tools\Nosuprt\VPSCAN folder their is a
utility to create scans that run as Admin scans which you can script
and schedule and another utility <cdroot>\Tools\Nosuprt\ConfigEd that
you can use to set the configuration on unmanaged clients (I assume you
are running the SAV Client component and not SAV Server component) if
you are unmanaged. Both utilities have .pdf instructions on their
usage.

I will have a look at these. Thank's for the suggestion.

Michael G. Schneider