I am trying to deploy a application through PSexec. This application will install a file filter driver on the target machine.

Command Line:
Psexec.exe \\Machine -c -f ToolBox.exe /s

I didn't get return code for a long time. So I check the target machine and find that the PSEXEC process hangs on running:

C:\WINDOWS\system32\rundll32.exe "C:\Program Files\Toolbox\USB Driver\CUsbInst.dll",_CUsbInstall@16 "C:\Program Files\Toolbox\USB Driver\Usb.inf"

After I kill the rundll32.exe process, the installation goes on and exit successfully.

Any suggestions to eliminate the hanging problem? Thanks in advance!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Is it applicable for you to igore exit code? if yes, use "-d" argument.

IMHO. Using psiexec is not managed solution. Better to use msi.
Answered 02/17/2011 by: itolutions
Orange Senior Belt

Please log in to comment
0
Thanks for your reply.
Yes, I could ignore the exit code. But the installation will still never exit except I kill the Rundll32.exe process manually.
Answered 02/17/2011 by: Savage455
Orange Belt

Please log in to comment
0
Possible resons:
1) psiexec.exe shows EULA message during first run.
2) Permissions
3) dll function can require user session.

To avoid these issues please try following scenarios:
1) with "-accepteula" argument
2) with "-s" argument
3) with "-i" argument
4) 2 + 3
5) 2 + 3 + 1

Start from the last one to save your time ;)
Answered 02/17/2011 by: itolutions
Orange Senior Belt

Please log in to comment
0
Also please note about official bug: always put -accepteula as first argument
Answered 02/17/2011 by: itolutions
Orange Senior Belt

Please log in to comment
0
"dll function can require user session" may be the most possible reason. Because if I run the application on other machine locally, it works fine. [align=right] [/align]
Answered 02/17/2011 by: Savage455
Orange Belt

Please log in to comment
0
This this case use "-i" psexec argument. Wich means "iteract with user desktop".
Answered 02/17/2011 by: itolutions
Orange Senior Belt

Please log in to comment
0
I add a "-i" to the psexec.exe , it works. Thanks a lot.
Answered 02/18/2011 by: Savage455
Orange Belt

Please log in to comment
0
Better to use msi.Quite so. The 'Unsigned driver' sticky at the top of the forum page will help.
Answered 02/20/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity