Thanks for your reply.
Sorry I don't clearly understood your suggestion.
To make clear case - We have written batch file to create package & which is running as 'Local System' .
And this Batch file calling MSI executable to install as silent so it also get run as local system which get fail.
I guess I don't completely understand Why are you using PSexec? Landesk can do all that a lot easier. Are you using a distribution package within Landesk? Under Tools - Distribution - Distribution Packages. Create a batch file job that calls your exe within Landesk and have it run as Local System.
Or you can create a distribution with your EXE file and put in the switches you need or can you extract the exe and get the MSI files and create an MSI packages? Sorry for the confusion
He was saying that it was failing via LD, but when he manually tested running the exe as system via "psexec -sid cmd" it was showing him the error he attached above.
I had this same issue when I was deploying CrashPlan as SYSTEM. The issue stemmed from the fact that the %temp% directory for SYSTEM where the files are being expanded to is a non-executable location so the install fails.
The work around I used was to have the exe (that contained the msi and cab files) extract its contents to a pre-defined location and then call the msi directly from there.
Example in PS:
mkdir "C:\Windows\ExtractCPP" -Force
& "CrashPlanPROe.exe" /extract:C:\Windows\ExtractCPP
# Wait for extract to finish
Start-Sleep -s 10
C:\Windows\System32\msiexec.exe /i C:\Windows\ExtractCPP\7E15D2D\Installer-x64.msi /qn /OtherSwitches....
You could also pre-extract the MSI and deploy that directly instead of doing it on the fly.
Hope this helps,
I extracted first exe to get MSI & then run MSI successfully.
Many thanks Peter & Cloevin.