Many years back I had to use PSEXEC, today I would use powershell or something else.
You can still have Remedy start as System if you perform runas or download the Runas.exe utility. Here is an example for reference: ProgramLauncher.bat: ################## rem Usage: RunAs <user> <password> [/V] [/B] [/I] <program name> [parameters] e:\progra~1\arsyst~1\scripts\RunAs <domain account> <passwd> /I e:\progra~1\arsyst~1\scripts\DoStuff1.bat %1 %2 %3 e:\progra~1\arsyst~1\scripts\RunAs <domain account> <passwd> /I e:\progra~1\arsyst~1\scripts\DoStuff2.bat %2 DoStuff1.bat: ################## e:\progra~1\arsyst~1\scripts\psexec \\<IP Address> -u <domain account> -p <passwd> -s cmd /c e:\progra~1\arsyst~1\scripts\MySpecialStuff1.bat %1 %2 %3 MySpecialStuff1.bat: ################## e:\Perl\bin\Perl.exe e:\progra~1\arsyst~1\scripts\PerlFun1.pl %1 %2 %3 Patrick Dill Dean of Medicine Information Technology UW School of Medicine From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of jham36 Sent: Friday, March 20, 2015 8:42 AM To: [email protected] Subject: Re: Running PSEXEC from Remedy ** Our Remedy service is starting as System. That service runs armonitor, which I guess runs all the other related remedy processes including ARserver. Since I am working on DEV, I can try and have that startup as a named generic account that we use to login to the remedy server with. Thanks, James On Friday, March 20, 2015 at 11:08:30 AM UTC-4, LJ LongWing wrote: ** James, One problem that most people end up experiencing at one point or another is that their Remedy server is not running as the same user they are using to 'test' when remoted in. If Remedy is not 'running as' the user that you are remoted into the server as, then it's not running with the same permissions/environment. So, if not already doing so, have the Remedy service run as the same user you are testing with and you may find that the problems go away. On Fri, Mar 20, 2015 at 8:49 AM, jham36 <[email protected]<javascript:>> wrote: ** Hello all. I am trying to execute a set fields action with a process command. We have built a console in remedy for our users to be able to execute some remote automation that they normally would not have access to. Currently this works fine when the controlling process is run on our Remedy server. My problem is that I do not want this process running on the remedy server. In some cases it runs for an hour, in others it can run for days depending on what the automation is doing. I want to offload this process to another server. I have successfully tested this by using a few vbscripts that write a file out to the remote server that gets picked up by another process and executes the command and writes out the results to another file to be picked up and returned to remedy. With the set fields command, I am not always expecting a return value for the process. If the command is to get the status, or to see if a vm is available to run the process, I want a return value. When running the automation, I don't need a return value. That all may be a bit confusing but isn't really too important with regards to my issue. Besides my working test with writing out text files and multiple vbscripts, I am also exploring using psexec which would require one vbscript to execute since i need to write out a text file in order to get the stdout. Another option is a program called paexec, which is almost identical to psexec, except that the stdout is returned without needing to write out a text file. My issue is that when I have the Process command run from remedy, it runs my vbscript on my remedy server, but the paexec does not seem to run. When I try with psexec, it executes, but hangs and does not connect to the remote machine. Executing my vbscript from a command line works fine for both psexec and paexec. If I replace the paexec or psexec command in my vbscript with "hostname", it returns the hostname of my server to remedy. I'm thinking that the psexec or paexec are not getting network access when remedy is running the vbscript that calls these programs. I was also considering trying to call the paexec program directly in the Process command, but remedy throws an error. $PROCESS$ @@:D:\QCInt\Test\paexec.exe \\remotesrvname<file:///\\remotesrvname> C:\User\QCInt\RunTestSet\RunTestSet.exe "-ss Process2Run" Any ideas on the programs seemingly not having network access when remedy executes the vbscript or remedy throwing an error when I forgo the script and run the command directly? Thanks, James _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
