Prev: sbs2003 page file size for 3GB RAM
Next: Exchange 2007 sp2 error
From: Mike Lemons on 9 Nov 2009 14:24
I have a client runnng SBS 2008 Standard with 12 client computers all running
XP Pro SP3. In the SBS Console, under Security, one computer appears with
the status shown in subject of this post. The computer in question is
running McAfee antivirus. I found problems on this computer, a couple
viruses and trojans. Had to uninstall and reinstall McAfee and then ran
scans which cleaned up and reenabled the antivirus. However, the status of
this comptuer remains the same. I installed the Group Policy Client Side
Extensions for XP and did the gpupdate /force, successfully. Security Center
service is running on the client. Don't see any problem with it's domain
account. Any suggestions on how to repair Security Center accessability for
this system would be appreciated.
--
Mike Lemons
From: Cliff Galiher on 9 Nov 2009 15:58
A/V products are very good at *detecting* issues, but the cleaning process
can (and usually does) leave the system in an unstable state. Deleted,
renamed, or mismatched dll's. Windows updates that the A/V wasn't aware of
that cause conflicts, all are regular symptoms.

Honestly? Re-install.

-Cliff


"Mike Lemons" <MikeLemons(a)discussions.microsoft.com> wrote in message
news:5EB6D59B-74EB-4CD6-9DCF-136C25989E31(a)microsoft.com...
> I have a client runnng SBS 2008 Standard with 12 client computers all
> running
> XP Pro SP3. In the SBS Console, under Security, one computer appears with
> the status shown in subject of this post. The computer in question is
> running McAfee antivirus. I found problems on this computer, a couple
> viruses and trojans. Had to uninstall and reinstall McAfee and then ran
> scans which cleaned up and reenabled the antivirus. However, the status
> of
> this comptuer remains the same. I installed the Group Policy Client Side
> Extensions for XP and did the gpupdate /force, successfully. Security
> Center
> service is running on the client. Don't see any problem with it's domain
> account. Any suggestions on how to repair Security Center accessability
> for
> this system would be appreciated.
> --
> Mike Lemons

 | 
Pages: 1
Prev: sbs2003 page file size for 3GB RAM
Next: Exchange 2007 sp2 error