Declined Remote Procedure Call

[Steve Fabian]

For those of us who have multiple systems with licensed copies of Take
Command it would be very useful to have an implementation of Remote
Procedure Call (RPC), allowing the local copy of TCC to initiate the
execution of a TCC command or batch file on a remote machine. While many
operations on the remote machine's file system are possible by simply
mapping one or more of its disk volumes into local drive letters, there are
even some file system operations not permitted in that manner, e.g.,
creation or deletion of file links (junctions, reparse points, hard links,
etc.) or modifying file time stamps. Of course, operations other than those
relating to the remote file system (e.g. anything relating to processes on
the remote system) cannot be done at all. While such things can be done
through other means, it would be useful to me, and I presume to many others,
esp. those who have system or network administrator positions, to be able to
perform such actions directly within the Take Command framework.
--
Steve

 

[rconn]

> For those of us who have multiple systems with licensed copies of Take
> Command it would be very useful to have an implementation of Remote
> Procedure Call (RPC), allowing the local copy of TCC to initiate the
> execution of a TCC command or batch file on a remote machine.

What's wrong with the existing REXEC and RSHELL?

Rex Conn
JP Software

 

[Steve Fabian]

| ---Quote---
|| For those of us who have multiple systems with licensed copies of
|| Take Command it would be very useful to have an implementation of
|| Remote Procedure Call (RPC), allowing the local copy of TCC to
|| initiate the execution of a TCC command or batch file on a remote
|| machine.
| ---End Quote---
| What's wrong with the existing REXEC and RSHELL?

The section of HELP topic rexec.htm (and the virtually identical one in
topic rshell.htm) which states:
"Note: Windows does not include the rexec service, so you will need to get
one from a third-party and install it on the remote system before executing
REXEC."

In other words, we need a TCMD implementation of the rexec and rshell
services to use REXEC and RSHELL to perform actions on the remote system.

--

Steve

 

[samintz]

Not to dismiss your request, but have you looked at Sysinternals PsExec
utility?

From their web site:
Utilities like Telnet and remote control programs like Symantec's PC
Anywhere let you execute programs on remote systems, but they can be a
pain to set up and require that you install client software on the remote
systems that you wish to access. PsExec is a light-weight
telnet-replacement that lets you execute processes on other systems,
complete with full interactivity for console applications, without having
to manually install client software. PsExec's most powerful uses include
launching interactive command-prompts on remote systems and
remote-enabling tools like IpConfig that otherwise do not have the ability
to show information about remote systems.

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

-Scott

Steve F$BaC(Bi$BaO(B <> wrote on 04/22/2010 08:49:31 AM:

> For those of us who have multiple systems with licensed copies of Take
> Command it would be very useful to have an implementation of Remote
> Procedure Call (RPC), allowing the local copy of TCC to initiate the
> execution of a TCC command or batch file on a remote machine. While many

> operations on the remote machine's file system are possible by simply
> mapping one or more of its disk volumes into local drive letters, there

are

> even some file system operations not permitted in that manner, e.g.,
> creation or deletion of file links (junctions, reparse points, hard

links,

> etc.) or modifying file time stamps. Of course, operations other than

those

> relating to the remote file system (e.g. anything relating to processes

on

> the remote system) cannot be done at all. While such things can be done
> through other means, it would be useful to me, and I presume to many

others,

> esp. those who have system or network administrator positions, to be

able to

> perform such actions directly within the Take Command framework.
> --
> Steve
>
>
>
>
>
>
>

 

[rconn]

> | ---Quote---
> || For those of us who have multiple systems with licensed copies of
> || Take Command it would be very useful to have an implementation of
> || Remote Procedure Call (RPC), allowing the local copy of TCC to
> || initiate the execution of a TCC command or batch file on a remote
> || machine.
> | ---End Quote---
> | What's wrong with the existing REXEC and RSHELL?
>
> The section of HELP topic rexec.htm (and the virtually identical one in
> topic rshell.htm) which states:
> "Note: Windows does not include the rexec service, so you will need to
> get one from a third-party and install it on the remote system before
> executing REXEC."
>
> In other words, we need a TCMD implementation of the rexec and rshell
> services to use REXEC and RSHELL to perform actions on the remote
> system.

Or, you can download one of the 10,000 free REXEC / RSHELL services, and
have it today.

Rex Conn
JP Software