Vista - Scripting neophyte - why does this simple script not work?

Hi all

I know nothing at all about scripting, I've just copied this from a
website.

All I want to do is to kill a process which is running on several XP
PCs - let's call it "rogueprocess.exe". If I look at Task Manager on
the Processes tab "rogueprocess.exe" is running. And I want to kill it
stone dead.

Here's the script :


'****************************************************************************
Option Explicit
Dim objWMIService, objProcess, colProcess
Dim strComputer, strProcessKill
strComputer = "."
strProcessKill = "'rogueprocess.exe'"

Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\cimv2")

Set colProcess = objWMIService.ExecQuery _
("Select * from Win32_Process Where Name = " & strProcessKill )
For Each objProcess in colProcess
objProcess.Terminate()
Next
'**************************************************************************


If I run this script, it doesn't kill the process. What is wrong with
the script?

Thanks for any assistance.

Stephen

"Stephen Mulholland" <mulhollands@xxxxxx> wrote in message
news:4736d787-23ea-4ba4-834f-ef3b68eb6aac@xxxxxxInstead of running a script that is outside your field of experience, why
not use the traditional methods of killing the process?
a) Kill it from the Task Manager.
b) Kill it with this command: taskkill /f /im "RogueProcess.exe"

Note that some processes are not "killable". To test your script, use a
process that you know can be killed, e.g. "notepad.exe".

On Jan 12, 4:16*pm, "Pegasus \(MVP\)" <I....@xxxxxx> wrote:Good points, sir, and well made.

However, when I say the rogue process is running on "several XP PCs",
you might want to read "several XP PCs" as "over 1800 XP PCs".
Oops. Long story, but basically I messed up, not to put too fine a
point on it. I rolled out a program using SMS 2003, messed up the
program's command line and now the program can't finish. I need to
kill the process invisibly, so the plan is to convert the vb script to
an exe, roll it out with SMS, let it run and finish - rogue process
killed, problem solved.

Thanks

Stephen

Or save a step and just use pskill (also Sysinternals free utility)