David
Sat Jul 17 15:23:20 CDT 2004
psexec from sysinternals might work for you...
PsExec v1.43 - execute processes remotely
Copyright (C) 2001-2003 Mark Russinovich
www.sysinternals.com
PsExec executes a program on a remote system, where remotely executed
console
applications execute interactively.
Usage: psexec [\\computer][-u user [-p psswd]][-s|-e][-i][-c
[-f|-v]][-d][-<priority>][-a n,n,...] cmd [arguments]
computer Direct PsExec to run the application on the remote
computer. If you omit the computer name PsExec runs
the application on the local system.
-u Specifies optional user name for login to remote
computer.
-p Specifies optional password for user name. If you omit this
you will be prompted to enter a hidden password.
-s Run the remote process in the System account.
-e Loads the specified account's profile.
-i Run the program so that it interacts with the desktop on the
remote system.
-c Copy the specified program to the remote system for
execution. If you omit this option the application
must be in the system path on the remote system.
-f Copy the specified program even if the file already
exists on the remote system.
-v Copy the specified file only if it has a higher version
number
or is newer on than the one on the remote system.
-d Don't wait for process to terminate (non-interactive).
-priority Specifies -low, -belownormal, -abovenormal, -high or
-realtime to run the process at a different priority.
-a Separate processors on which the application can run with
commas where 1 is the lowest numbered CPU. For example,
to run the application on CPU 2 and CPU 4, enter:
"-a 2,4"
program Name of application to execute.
arguments Arguments to pass (note that file paths must be
absolute paths on the target system).
You can enclose applications that have spaces in their name with
quotation marks e.g. psexec \\marklap "c:\long name app.exe".
Input is only passed to the remote system when you press the enter
key, and typing Ctrl-C terminates the remote process.
If you omit a user name the process will run in the context of your
account on the remote system, but will not have access to network
resources (because it is impersonating). Specify a valid user name
in the Domain\User syntax if the remote process requires access
to network resources or to run in a different account. Note that
the password is transmitted in clear text to the remote system.
"Celler Dweller" <BillG@microsoft.com> wrote in message
news:e8wMC72aEHA.3012@tk2msftngp13.phx.gbl...
> Hi Guys,
> I have a remote site that we need to change some Network settings for. I
> do not want to have to send someone out there. I can copy the script to
> the remote computer, but my script will need to run with admin
> privileges. I do not wish to give the end (l)users the local admin
password.
> · I know I can specify a username and password for the Task Scheduler,
> GUI only, the AT command does not seem to support this
> · I found a news group article where Torgeir Bakken says, WMI
> does not support connecting to the same computer you are running
> the script from with another user credentials.
> I?d simply do this remotely but I am setting a static IP on these PCs
> among other network settings
> Can someone throw me a link or something?
> Thanks
>