Software Deployment

If I run the command option from the above screen and manually change to the C:\KACE\Applications\39 and tell it to run Adobereader.bat it seems to work. So the question what is happening that causes KACE either not to see this file or be in a different default directory when trying to execute the task. - jason.rfpco 10 years ago

I've moved the /passive to before the MSI and MSP instruction as follows -
msiexec.exe /passive /i adberdr11000_en_us.msi TRANSFORMS=acroread.mst
msiexec.exe /passive /update AdbeRdrUpd11004.msp

Testing now and will see what happens. - jason.rfpco 10 years ago

check the xml code also if it fails again and note the type of file the engine encode this as (app, script, bat). I have had it think the task was a exe when it was a bat file and that would cause that type of error - SMal.tmcc 10 years ago

Failed - here is the XML code for the task

According to the XML<Task ID="86">
<Name>Install Adobe Reader XI - TEST</Name>
<WorkingDirectory>%systemdrive%\KACE\Applications\86</WorkingDirectory>
<CommandLine><![CDATA[AdobeReader.bat]]></CommandLine>
<Parameters></Parameters>
<PostTaskAction>None</PostTaskAction>
<KACETaskType>Application</KACETaskType>
<FileType>Batch</FileType>
<Type>PO</Type>
<Guid>1538f5e5a3b8e1</Guid>
</Task> - jason.rfpco 10 years ago

Simple.

1642 is telling you that the patch isn't correct for the installed product.

http://support.microsoft.com/kb/290158

How you proceed depends on why WI thinks that that's the case. Does the patch get applied in a stand-alone test? If you remove the patch entry from the command ilfe, does that flavour of Reader get installed?

BTW, my rule of thumb for command files and script of any kind is: aways, always, always, always, ALWAYS use full paths for everything on the command line. Never EVER assume that the OS will find the file. - anonymous_9363 10 years ago