F
Filipe Bonjour
Hi,
I'm writing a series of scripts to be run on a Windows 2000 server to
control applications on a series of other Windows servers.
Most commands to control the application are network-transparent. But we
still need to launch from the controlling server some commands on the
running servers. For instance we need to run tlist.exe to gather
information on processes running remotely.
I tried to find both generic modules for launching commands remotely (e.g.
Net::Rsh) or more specific modules (e.g. Win32:rocess) but I haven't
found anything 100% satisfactory. I also thought of building a small
daemon running on the remote servers that would accepts requests, run
tlist.exe and return the reply. (I was thinking Net:aemon, because I
don't know enough about Windows to write a server in C).
Any thoughts would be appreciated!
TIA,
Filipe
I'm writing a series of scripts to be run on a Windows 2000 server to
control applications on a series of other Windows servers.
Most commands to control the application are network-transparent. But we
still need to launch from the controlling server some commands on the
running servers. For instance we need to run tlist.exe to gather
information on processes running remotely.
I tried to find both generic modules for launching commands remotely (e.g.
Net::Rsh) or more specific modules (e.g. Win32:rocess) but I haven't
found anything 100% satisfactory. I also thought of building a small
daemon running on the remote servers that would accepts requests, run
tlist.exe and return the reply. (I was thinking Net:aemon, because I
don't know enough about Windows to write a server in C).
Any thoughts would be appreciated!
TIA,
Filipe