System Tool virus

Added note:
I've seen several posts on this and most are on stand-alone machines.
Is the approach the same for a client-server environment?  What is the best approach to fixing this?
Thanks for your prompt reply.

Signed,
Desparately Seeking Solutions

Isn't that what they always say?  Anyways loaded is right, they can come from anywhere.  Do they have email, could be junk mail.  Do they have outside internet access, could have went to a bad site or opened up a popup (did you check their browsing history). That being said I have symantec endpoint on all my customers and they still get spyware, you won't find a program that stops everything.  IF you are looking for some tools to get rid of this I find that malwarebytes does a good job, also combofix (THough i wouldn't use this on a server).   Sorry i'm not more help....

hi csaroli,
I ran malwarebytes and it found nothing.

what is the name of the fake av tool that has infected the machine, maybe a screen shot?

the screen shot can be seen here:
http://www.symantec.com/connect/forums/system-tool-malware-or-spyware

However, I found a suspicious file at %AppData%\[randomstring.exe].  It was create around the time the problem was reported and the user was listed in the Permissions....so I bit the bullet and deleted it.
I logged in as the user and it hasn't popped up....(yet).  I plan to run more scans, install all updates,etc. while I can?  If it seems to good to be true it probably is... my guard is still way up... the thing could be morphing into something else...or be deeply embedded somewhere else...

I welcome your feedback...

If you are an advanced IT tech, one thing you can do is use Knoppix or Unbuntu boot cd.  You can do a google search since it is a freeware Linux OS and burn a cd.

It will load the complete OS off the cd and allow you to explore the hard drive...keeping your hard drive OS and data files intact.  Click on the hard drive and change the read/write settings so you can make changes to the hard drive on the trouble virus files that are loading.  Set the view for details and search for the date around the virus incident.  Look under the hidden system folders, Local Settings and Application data especially the Startup items.  After you're done, just click turn off and restart.  Repeat if the virus persists.

This variant of malware is one of the few that require a "Safe Mode" boot (with networking) to clean with Malwarebytes.

Please review the detailed instructions here:
http://www.bleepingcomputer.com/virus-removal/remove-system-tool 
********************

This is actually a pretty nasty piece of malware.
We have had a couple of questions about this variant over the past few days - here is one example:
https://www.experts-exchange.com/questions/26833850/Infected-by-a-program-called-System-Tool.html
********************

yes, bleeping computer forums is a good resource for malware, and i agree with younghv, try malwarebytes in safemode.  I might also suggest turninf off system restore

You may as well run these in case a rootkit is also present. Post logs if needed
TdssKiller and Hitmanpro.
http://support.kaspersky.com/viruses/solutions?qid=208280684
http://www.surfright.nl/en/hitmanpro

@optoma,
The malware has already been identified as "System Tool".

Neither of your recommendations are called for - or needed.

optoma,
There is nothing 'professional' about offering improper advice.
Anyone can do Google Searches and find a wide variety of links to anti-malware products - then post them here.

The simple fact is that NO ONE should be recommending extraneous advice about running additional applications - when the actual solution has already been provided.

If - and only if - the symptoms do not go away should we recommend further actions.

Those of us who actual repair infected systems for a living understand that malware needs to be approached "one step at a time" and throwing multiple suggestions at a known and verified solution is not the kind of advice that should be posted.

I do not intend to be unprofessional, but I also will not stand by and allow improper advice to be posted.

@ Younghv .
" different strokes for different folks " 

BTW, I deal with repairs  of all kinds on a working basis.

Thus far, deleting the file seemed to be the solution.
 
Just a final comment:  the issue resided on my win2k3 server on one particular profile.

Thanks for all feeback!