Defender Nightly Scan Not Working

[Guest]

I read the other post on this, but I do not think I have same issue

I have had WD on my Windows 2000 Server since the first beta ...
It has worked fine until about a month ago ...
I have latest SP and updates ... for both server and WD

It is set to scan at 3:00am every morning ... it does not scan anymore
unless I do it manually ... I have changed times, full to quick, turned off
and saved and nothing gets it to scan ...

What services should I check to see if they are running to perform the
automatic scan and what else can I do .... I have reinstalled several times
as well ...

 

[Guest]

Hello Tony,

Beforhand, I don't have experience with Windows 2000 Server, but in XP Home,
I will check the Task Scheduler disabled under services? Microsoft
Antispyware
schedules as a hidden task using the Windows Scheduled tasks facility--so
Task Scheduler needs to be availªble.

The Windows Defender service depends on RPC--so be sure that RPC is not
disªbled.
Remote procedure Call (RPC)
Remote procedure Call (RPC) Locator

If you select the Process tab you should see MSASCui.exe (the user
interface), and MsMpEng.exe (the service executable) running.

In Windows Defender--real-time protection is done by a system service,
starting at boot time--that's the Windows Defender service, whose executable
is MsMpEng.exe.

MpCmdRun.exe monitors for the existence of new signatures and is responsible
initiating the updating process when new signatures are available.

I,m sure more knowledgable people will be along soon.

For the benefit of the community reading this post, please rate the pºst.

I hope this post is helpful.

Let us know how it works ºut.

Еиçеl

 

[Guest]

I checked and the RPC Locator Service was set to Mn\anual and it was not
started ... I set it to automatic and Started it ...

It still does not do a nightly scan ...

Anything more to try ?

 

[Guest]

Tony,

The problem you've experienced is one of several known to exist with
Defender running on Windows 2000 PRO/Server. It really doesn't matter,
however, since Windows 2000 is no longer supported by the released version of
Defender that came out recently and the version you have will stop working
entirely in late December.

The officially stated reason is that Windows 2000 ended Mainstream Support
in June of 2005, though I personally believe the real reason is both these
known issues and the fact that Defender can only effectively protect a PC
with Windows XP SP2, Vista or Win 2003 Server. This is due to fundamental
design differences in these OS versions that would require major changes to
Windows 2000, in effect upgrading it to XP SP2, to allow Defender to be
effective. Obviously there's little incentive for Microsoft to do this.

If I were you, I'd concentrate more on options to move to a newer OS, since
security issues are shortening the useful life of all MS OS versions.
Assuming that you can get a 5 year or greater useful life from an OS is risky
business today, though it's possible that the improvements in Vista will
allow a bit better lifetime for that OS, only time will tell.

Bitman