Getting NOD32 Clients To Update

[dhicks]

Have you added all of the recommended exceptions for the active scanning?

 

Yes:

 

 

All the machines in the Senior IT suite are now up-to-date with Windows updates, ensured by manually running Windows Update until it reported no more updates left to install. That's not all updates - there's still a bunch of Microsoft Updates to install, mostly to do with MS Office, but for some reason WSUS is randomly deciding it won't install those.

 

The machines are still freezing. Therefore, I figure Windows and / or NOD32 doesn't work and the proper solution is to wipe to whole mess off and install Ubuntu on the lot...

 

--

David Hicks

[cookie_monster]

Yes:

 

 

All the machines in the Senior IT suite are now up-to-date with Windows updates, ensured by manually running Windows Update until it reported no more updates left to install. That's not all updates - there's still a bunch of Microsoft Updates to install, mostly to do with MS Office, but for some reason WSUS is randomly deciding it won't install those.

 

The machines are still freezing. Therefore, I figure Windows and / or NOD32 doesn't work and the proper solution is to wipe to whole mess off and install Ubuntu on the lot...

 

--

David Hicks

 

 

 

What version are you running on the desktops?

 

A few ideas.

 

1. Can you try a clean install of windows and install NOD32 and see if it's the same?

2. Have you turned off active scanning to see if that solves the issue?

3. Check that NOD32 is set to NOT scan network drives.

[dhicks]

What version are you running on the desktops?

 

I've tried 3.0.672 and 4.0.474. Same results.

 

Can you try a clean install of windows and install NOD32 and see if it's the same?

 

Yes, I have one recently re-imaged machine in the IT suite that seems to have no problems. Thing is, I can't think what it wouldn't have installed that the other machines would.

 

Have you turned off active scanning to see if that solves the issue?

 

No, any idea how I do that?

 

Check that NOD32 is set to NOT scan network drives.

 

There are no network drives mounted on startup, which is when the machines are freezing - drives are mounted as users log in.

 

--

David Hicks

[cookie_monster]

Interesting that this should come up, I was wondering the same thing when ESET support were giving me recommended exclusions. If I was a virus writer i'd be very interested in this advice.

 

Microsoft AV advice may aid attackers, researcher warns ? The Register

[dhicks]

If I was a virus writer i'd be very interested in this advice.

 

Made me wonder, too, as I was typing the exceptions list in - I originally thought "Why not simply exclude C:\WINDOWS\security\*.*?", but then realised that would exclude executable files from being scanned. I think the list above should avoid excluding anything executable, and I think Windows still relies on file extension for executable status (unlike Unix, which relies on explicit executable permissions). A virus could, of course, store whatever data it wanted in a location excluded by the list, but it would still have to get on your system in the first place anyway, at which point you've already lost, so I don't think this list of exclusions is actually a problem.

 

--

David Hicks