NAV Corp 7.6 server sched scan won't stop running

[bfessenden]

We still are running NAV Corporate 7.6 on our AD network.

The scheduled scan that was running once a week on the Windows 2000 AD Server was taking days to run, so I deleted it. It still runs.

So I deleted all scheduled scans for all servers and clients. It still runs.

I have checked the registry keys mentioned in this forum and at Symantec for scheduled scans and can't find anywhere where it is still set to run.

Even stopping and starting the NAV service, and rebooting the server cannot stop it from running. It justs starts up again as soon as the server has started.

What am I missing here?

Thanks.

Bret

 

[oggywan]

Does the scan start after a system restart or when you login as an administrator? Have you searched whether there are any virussweeps active? If you ensured that all scans are gone from the registry then all that is left are user based scans (I forget whether 7.6 had the feature) and virus sweeps.

http://service1.symantec.com/SUPPOR...200551b64?OpenDocument&src=bar_sch_nam&seg=ag

 

[bfessenden]

Actually, I'm not sure how to check if it runs before I login.

I am logging in as administrator.

You bring up a question, though, and my apologies if this is a stupid one, but - what's the difference between a virus sweep and a scheduled scan of all server groups or clients?

That link that you provided is very useful though. For some reason I missed those registry locations.

Thanks!

Bret

 

[LawnBoy]

They accomplish the same thing, but a sweep is done on-demand rather than scheduled.

 

[oggywan]

The virus sweep is a feature that you can use at the server group level to quickly initiate a scan on all servers and clients within the group. It can be rather useful during a virus outbreak, but the virus sweep is unfortunately rather hard to remove. If you search for virus sweep in the Symantec knowledgebase, you may find some additional information.

 

[bfessenden]

I don't think I've ever started a virus sweep myself, but I haven't has a spare minute to check those registry entries yet to see what their values are.

I know I have removed all client and server scheduled scans, so I'll get back to this thread when I have time to check the registry.

This has been very helpful, so far. Thanks again!

Bret

 

[bfessenden]

Ok. I finally had time to remove all the virus sweep registry entries, made sure I still had to scheduled scans, rebooted the server, and it started scanning again.

I did notice something I had not noticed before that may give another clue: I have another domain controller that is really doing nothing right now, but is in the same server group in MAV Corporate, and I checked all it's registry keys, rebooted it also, and it starts scanning after I log into it as well.

So the only two servers I have both start scanning after I have removed all scheduled scans and removed registry entries for virus sweeps.

Any other suggestions? Coulod I just uninstall the parents, or would that screw up all the clients?

Thanks!

Bret

 

[oggywan]

You can uninstall/reinstall those parents without any problem as long as you put the product back on the same machines with the same NETBIOS name and IP-address.
Clients should check in with that servers and re-appear in the SSC over time.

 

[bfessenden]

Thanks. I guess I'll give that a try.

Bret

 

[m4ilm4n]

I found that older clients (7.5/7.6) version of LiveUpdate will cause the rtvscan.exe service to occupy 50-100% of CPU, especially on reboot. Updating LiveUpdate manually fixed it.