Runwait and ProcesswaitClose doesn't work!

[Wolfteeth]

Very Interest in the topic problems, I am writing a program which need to promote the permission via LSrunase.exe program and below is my sample script.

for $i =1 to 5
  $rpath = "C:\Temp\"
  $strcommand = "notepad.exe"
  $strrun=$rpath & "lsrunase.exe /user:adminTemp /password:****** /domain:MYDOMAIN /command:" & """" & $strcommand & """" & " /runpath:" & $rpath
  $pid = Run($strrun)
  ProcessWaitClose($pid)
Next

Runwait absolutely doesn't work and refer to the manual that I used ProcessWaitClose, but it still not works.

as my thought that the notepad.exe should be opened once I close the last one, but it didn't, it just run and run with no wait. because the running user name is not the the one who login the machine.

anyone who has experience on this?

[Aarstad]

The processwaitclose variable which is a run execution. Change it with a processname and it will work.

[careca]

What you could also do is set the variable $strcommand to the process close instruction, and remove the $pid variable alltogether

Run($strrun)
  ProcessWaitClose($strcommand)
Next

[Wolfteeth]

The processwaitclose variable which is a run execution. Change it with a processname and it will work.

it doens't work even use the "program name", it seems if run on different crendation, the processwaitclose can't recognize the token and doens't work.

[Wolfteeth]

What you could also do is set the variable $strcommand to the process close instruction, and remove the $pid variable alltogether

Run($strrun)
ProcessWaitClose($strcommand)
Next

this is what I did at the first time.. but it doens't work.

[careca]

Try this way. If i got your problem right, this should work.

For $i = 1 To 5
$rpath = "C:Temp"
$strrun=$rpath & "lsrunase.exe /user:adminTemp /password:****** /domain:MYDOMAIN /command:" & """" & "C:\Windows\System32\notepad.exe" & """" & " /runpath:" & $rpath
MsgBox (4096, "info", $strrun)
If Not ProcessExists("notepad.exe") Then
ShellExecuteWait("C:\Windows\System32\notepad.exe")
EndIf
Next

[Wolfteeth]

Not..the root cause I found that it is because of the "Program" is running on the prompted authentication session via "LSrunase.exe", thus, the user session is different, which caused ProcessList cannot see the "Program" even its running on task manager and got the proceessID, but our Procssexist("Program") cannot return the PID to autoit... sucks...I am still checking to see...

what I am doing now is to try:

for $i =1 to 5
$rpath = "C:Temp"
$strcommand = "notepad.exe"
$strrun=$rpath & "lsrunase.exe /user:adminTemp /password:****** /domain:MYDOMAIN /command:" & """" & $strcommand & """" & " /runpath:" & $rpath
Run(@ComSpec & " /k " & $strrun)
Next

this does works but the new opened @ComSpec window will not be terminated....still thinking...

Edited October 25, 2012 by Wolfteeth

[Wolfteeth]

Try this way. If i got your problem right, this should work.

For $i = 1 To 5
$rpath = "C:Temp"
$strrun=$rpath & "lsrunase.exe /user:adminTemp /password:****** /domain:MYDOMAIN /command:" & """" & "C:\Windows\System32\notepad.exe" & """" & " /runpath:" & $rpath
MsgBox (4096, "info", $strrun)
If Not ProcessExists("notepad.exe") Then
ShellExecuteWait("C:\Windows\System32\notepad.exe")
EndIf
Next

sorry, it's wrong.

[Wolfteeth]

still not found good ideas...

.the root cause I found that it is because of the "Program" is running on the prompted authentication session via "LSrunase.exe", thus, the user session is different, which caused ProcessList cannot see the "Program" even its running on task manager and got the proceessID, but our Procssexist("Program") cannot return the PID to autoit... sucks...I am still checking to see...

[UEZ]

FYI: my experience with ProcesswaitClose() was that it caused a high cpu usage whereas Runwait() worked properly.

Br,

UEZ

[JLogan3o13]

I would agree with JohnOne, RunWait is usually a better alternative. Also, I would suggest taking LSrunase out of the mix; it's pupose is to allow you to run an install as another account, but you can do the same natively with RunAsWait. Even if your goal is to use the encryption methods in LSrunase, I would try it without, just to help narrow down the problem.

[Wolfteeth]

it is a quite good article to have a test to use LSrunase instead of RunAsWait, sometimes, especial for enterprise user, the encrypted pwd is very important. and should not be plain text always.

besides, our AutoIT.exe still is able to be cracked...sigh...

Edited October 29, 2012 by Wolfteeth