Copy the text from the web page and paste it into notepad, saving it as "WMIProcessList.udf" - now you have the beginning of a UDF library.

I prefer to embed the UDFs in my code - so, you can paste it into your script, or you can put the UDF library folder on a network share and reference it in your script as
 Code:
Call '\\server\KixUdfLib\WMIProcessList.udf'
This will load the current copy each time the script runs. Put your Call statements near the top of your script. Embedded UDFs can occur anywhere, but we usually put them at the end.

As I said, I prefer embedding the UDFs in my scripts, as this insures that the script will continue to function if the library is unavailable or I make a change to the UDF that isn't compatible with that script.

There's a KixDev package on my site that includes KGen. This tool reviews your script for dependent UDFs, locates them in your UDF library, and generates a finished script with all dependencies included.

BTW - UDF means User Defined Function.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D