The problem seen at a school however means proving a strong case to the board of directors or whoever runs it that a better program is needed. Simply coming from any student however wouldn't be enough to convince them that any change was needed however. You simply have to take your own precautions from the beginning.
That's it Night Hawk, I brought it to their attention several times, since one of the classes was right down the hall from the server room. I usually got a lame reply of some kind like "We're looking into it".
I finally told them "You've been looking into it for 3 months now & everyone is still getting infected!" They didn't like that....
It was a regular occurrence to go to your class and sometimes your PC wouldn't be working because the virus hosed it....
Maybe I should sneak into the server room & put MSE on it....:sarc:
Oh yeah...another casualty of McCrappy....I ran a SFC a week before this happened...I ran it after the debacle and look what I found:
{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = , Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-08-10 12:20:45, Info CSI 0000010f [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = , Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-08-10 12:20:45, Info CSI 00000110 [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7600.16385.WindowsFoundationDelivery"
2010-08-10 12:20:45, Info CSI 00000113 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
Thanx McAfee!