Hi,

I seem to remember something called rc.exe in the NT reskit. I never
actually used it, but I was under the impression you could use it to run
a command on a remote machine?

I had a look at the Win2k reskit today, and it's not there! I then
started looking at the docs, and the options they offer for remote CMD
appear to require installation of a horrible client on EVERY machine!

I then had a look at WMI, and there's a "Win32_Process" object with a
"Create" method, but it says it's only for XP?

Even if any of this worked, the issue remains as to what security
context the CMD will be running in? It's not much use if it's Local
system or whatever, as it won't be able to access the files I'm trying
to deploy. I believe SysInternals have a util to solve the above issues,
but I'd be interested to know if there's a way of doing it using only
what's built into Win2k or the reskit...

--
Gerry Hickman (London UK)

Gerry,

Check your email, I just sent you PSEXEC, which I've had
success using. You must have local administrator rights
on the target system.

Jerry
>-----Original Message-----
>Hi,
>
>I seem to remember something called rc.exe in the NT
reskit. I never
>actually used it, but I was under the impression you
could use it to run
>a command on a remote machine?
>
>I had a look at the Win2k reskit today, and it's not
there! I then
>started looking at the docs, and the options they offer
for remote CMD
>appear to require installation of a horrible client on
EVERY machine!
>
>I then had a look at WMI, and there's a "Win32_Process"
object with a
>"Create" method, but it says it's only for XP?
>
>Even if any of this worked, the issue remains as to what
security
>context the CMD will be running in? It's not much use if
it's Local
>system or whatever, as it won't be able to access the
files I'm trying
>to deploy. I believe SysInternals have a util to solve
the above issues,
>but I'd be interested to know if there's a way of doing
it using only
>what's built into Win2k or the reskit...
>
>--
>Gerry Hickman (London UK)
>
>.
>

Jerry wrote:

> Check your email, I just sent you PSEXEC, which I've had
> success using. You must have local administrator rights
> on the target system.

OK, thanks.

--
Gerry Hickman (London UK)

Brendon Rogers wrote:
> Perhaps you are thinking of rclient which is in the Reskit. Look for rsetup.

Yes, but it's not much use if you have to first install it on every
machine...

--
Gerry Hickman (London UK)

Hi Brendon,

I had a look at this today, but couldn't make any sense of the docs, it
was talking about video memory, which I didn't like the sound of. I
didn't find out how to deploy it to 600 machines, and I also fail to
understand why Microsoft's solution requires a client when SysInternals
does not?

The SysInternals solution is one tiny file, no messing with clients, and
it takes care of starting sessions using domain accounts.

One thing I missed completely was the "AT" command, according to the
docs to can schedule it on a remote machine. I have not tried this yet,
but surely it's too simple, or everyone would just use that instead.

Brendon Rogers wrote:
> It can be installed to the client from the server and is extremely easy to
> script.
>
>
> "Gerry Hickman" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>Brendon Rogers wrote:
>>
>>>Perhaps you are thinking of rclient which is in the Reskit. Look for
>
> rsetup.
>
>>Yes, but it's not much use if you have to first install it on every
>>machine...
>>
>>--
>>Gerry Hickman (London UK)
>>
>
>
>


--
Gerry Hickman (London UK)