Re: Windows 2003 FSRM command options don't work

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks again. I have used PsExec for some things in the past. I'll
consider it and see if I can find an acceptable way to use it for this. Or
I'll use NET SEND, or I'll just live with it!

Geoff

"Francis Favorini" <francis.favorini@xxxxxxxxxxxxxx> wrote in message
news:%23bWMS$a4GHA.1544@xxxxxxxxxxxxxxxxxxxxxxx
In article <#YRJDsa4GHA.900@xxxxxxxxxxxxxxxxxxxx>,
geoff.varney@xxxxxxxxxxxxxxxxxxxxx says...
I don't like only having the message popup that access is denied.
[...]
The vbs was a popup that tells them they are not allowed to save
executables
to the folder. I don't know if it runs but stays on the server so the
user
will not see it on the local computer or what.

Bingo. The command runs on the server.

The batch file option works, it's simply a NET SEND %username% <Warning
message>.

Barring email, this is the only thing I can think of that will work "out
of
the box." I suppose you could use instant messaging (IM), but you'd need
to
have an IM client installed on all the machines.

You could also try PsExec from http://www.sysinternals.com to remotely run
your VBS file. You'd use the -i switch to "Run the program so that it
interacts with the desktop on the remote system". Note, there are security
issues with this. You'd need to figure out what credentials to use to run
the
remote process under. I think it uses LOCAL SERVICE by default. This would
probably work, but I haven't tried it. Don't use SYSTEM, which could be a
disaster if there are any bugs in your code. Be sure you understand the
implications of this method if you use it.

-Francis

P.S. Sorry about the ugly wrapping in my first post. I was trying to
insure
the commands didn't wrap. Oh well.



.

Relevant Pages

  • Re: Windows 2003 FSRM command options dont work
    ... The vbs was a popup that tells them they are not allowed to save executables ... I suppose you could use instant messaging, ... interacts with the desktop on the remote system". ...
    (microsoft.public.windows.server.general)
  • Re: Have user run a script with admin credentials
    ... psexec from sysinternals might work for you... ... PsExec v1.43 - execute processes remotely ... PsExec executes a program on a remote system, ...
    (microsoft.public.scripting.vbscript)
  • Re: remote machine execution
    ... The current problem in psexec is they cannot pass "=" sign over to remote ... machines. ... version of psexec. ... What happens when you execute the command line locally on machine ...
    (microsoft.public.windows.server.scripting)
  • RE: [Full-Disclosure] Psexec on *NIX
    ... The idea here is that he'd like to run commands on a remote windows box, ... but Psexec requires nothing more than a fresh windows ...
    (Full-Disclosure)
  • Re: remote machine execution
    ... i tried and it only pass the exe over the remote machine without the ... What happens when you execute the command line locally on machine nol-b0000586? ... you use any credentials to run the command via psexec, ... I suspect that the process spawned by psexec on the remote PC needs some network ...
    (microsoft.public.windows.server.scripting)