PWB and PSEXEC

[GregP]

I'm just wondering if anyone has experience (good or bad) using psexec?

I've got a .bat file setup to display a timer using Javascript in PWB. It works great. However when the situation becomes a bit more complicated things fall over.

1) Batch file running locally off shellbar. Work Great.

2) Batch file executed remotely as domain admin with
"psexec \\public32 -s -i -d "c:\timer\15min.bat".
Works Great.

3) When I try to schedule the remote execution with the AT command it falls into a steaming pile of poo. :(

I gather...
psexec uses system account on the remote PC if I use the -s switch, but this won't work when run from the AT command (because AT does not run as a domain admin, like when I execute it manually).

So I changed the -s switch to use "-u LIBRARY\public32" (or a few other users with varying privileges), to force the execution to occur using a particular account, but then PWB crashes on the remote computer with a runtime error.

I know that the batch files starts, because it is this that calls PWB before it crashes. Can anyone with more experience using PSEXEC see something obviously wrong?

The other thing I had considered is the issue may be in the relationship between PWB and the access privileges of the user who executes it, however I wouldn't have thought PWB needed any particular security privilege to start. Would I be right?

I would like to avoid using "at \\public32" if possible.

I'm running WinNT4.0Sp6 IE6 and using PWBv2 as the shell.

I can't believe I'm tearing my hair out over a relatively little part of our system. :(

[Scott]

PWB does not need special security privileges to execute. Of course the user account has to have at least read and execute privileges on the PWB folder and files.

What is the run time error PWB is having? You should be able to look in Event Viewer to gain some incite.

--Scott

[Guest]

The account has read and execute privileges.

The runtime error is a MS Visual C++ error:
"Runtime Error!

Program C:\pwb\PWB.exe

This application has requested the runtime to terminate it anunusual way. Please contact the application's support team for more information."

(That's out of my notebook, if I wrote it down wrong the other day I can check again)

I'll take a look at the Event Viewer today.

[GregP]

Took me a while....

I'm sure I'm not the only one with 4 million things that needed to be done Yesterday. :)

The event viewer has nothing unusual, in particular nothing from PWB or PSEXEC.

At the moment I'm using 'AT \\public32' but I want the actual scheduling to occur on our admin PC, not on the users PC.

Does the run-time error help at all? Or is it too vague?

Ta,
Greg