There are tools available that allow you to run programs on a remote machine, for example if you have ssh available you can fire off a command line program. And I think for windows sysinternals.com has a remote execution tool.

Doug is correct. For security reasons there is no direct method of executing a command on a remote machine without using something like SSH or a tool such as PsExec. You can also use remote scripting. If you have proper permissions on the remote machine, you can run scripts from your current machine that execute on the remote machine.

Here's how it works. You run a script on your local machine that uses the FileSystemObject to copy a prewritten script file to a remote machine on your network. You'll need it's UNC path and proper credentials. Then, using WMI you can run the script (or any other command line for that matter) by starting a process on the target machine. A pure scripting example looks something like this.

First, thank you Doug and Nilpo for helping me!
I’m not a programmer, I’m just trying to make my life easier by automating some processes on the machines I’m working with. Basically I’m pulling evt logs and processing them. I found and modified a script for that. It stores decompressed EVT logs as a text file to the “host” and now I want to “call” my EVT.vbs script “from the host machine", I have all the credentials and I’ll try Nilpo’s script during weekend.
I do not want to “schedule” my EVT.vbs script on my local machines, I want to “cal it” from the “host”.
Thank you guys again. Vl123456

My bad!
Actually my EVT.vbs script does not store decompressed EVT.txt to the “host”. It stores locally in the “home” folder and then I’m using XCOPY batch file that pulls the EVT.text file from the “local” machines to the “host”.
Sorry about this, VL123456

You're just reading event logs? Windows provides a tool for that. WMI (Windows Management Instrumentation) is capable of reading events and is designed to work on remote machines. That's the technology my script above is using to launch a process on the remote machine. From what it sounds like, WMI can do the whole process for you by design. Can you provide more details about what you're trying to find?

Thank you for your help Nilpo!
I'm pulling out "System" even logs (from the systems on LAN) then using special .exe and a .bat that decompresses the event logs and gives me only the events I'm interested in and stores them in the home dir on each machine as a TXT file. Then using Perl (I'm comfortable with Perl) I'm sorting/processing the EVTs and sending them to the server. The only missing part was the way to get these TXT files from locals to the host com.
I got VBS script (thanks to Google) to pull the EVT logs, I also modified it so it pulls EVTs, decompresses and stores it to the home dir on each local machine. I was thinking to use a VBS script to get the TXT files from the local machines. Actually today, I managed to transfer the TXT files from the local comps with Perl.

Code:

my $cmd = "copy C:\\fromhere C:\\tothere \/y";
system ("$cmd") ;

I cannot use Perl on these local machines - not allowed.That is why I wanted to use VBS that I know nothing about.

I guess what I'm getting at is that you don't need to do anything on the remote machines at all. You can do all of this from one location. A WMI script can poll remote machines for only the event information you want and store it locally...any way you want. Then you can use Perl or whatever you wish to crunch the data. For instance, let say I wanted to check every computer on my network for bluescreens and improper shutdowns. I could do something like this.

Yes, as you can see I'm kind of using CMD (from Perl) to pull out my logs from each local machine.
I'm OK with that for now but I was wondering how I could call "my VBS" script on each machine from the host. I'm using Perl to manipulate the logs.