Did you check on the client to see if the package actually ran? You've specified an EEDK key under "Product Detection Key"; this is a key that is supposed to exist with a different value after the installation of the package in question. In this current configuration, even if it succeeds, the task will report as failed because the key you listed here does not have the value "JAVA866" after the client task completes.
Also, your installation string references a specific path. Likely this "C:\TEMP\Build" directory doesn't exist on the client, so the MSI won't run. The script you referenced is using a for /f loop to assign the current directory to the variable SRCDIR so it can call the installation file with an absolute path.
Thanks for the reply,
i see activity on the client, i changed the location to a network folder:
in the eventvwr i even get messages that an installer transaction is beginning and ending but no install actually happens.
Beginning a Windows Installer transaction: \\xxxxxxxxxxx\JAVA\jre1.8.0_66.msi. Client Process Id: 9692
Ending a Windows Installer transaction: \\xxxxxxxxxxx\JAVA\jre1.8.0_66.msi. Client Process Id: 9692.
.exe from c temp also works but also no installation happening:
Beginning a Windows Installer transaction: C:\TEMP\Build\jre1.8.0_66.exe. Client Process Id: 12916.
Ending a Windows Installer transaction: C:\TEMP\Build\jre1.8.0_66.exe. Client Process Id: 12916.
Can you me maybe send me an example for installing a .exe ?
I don't understand what could be wrong.