Java 7u9 and SCCM

I'm trying to deploy Java through SCCM and am having a problem. The installation is being called from a cmd file. When run manually and locally it works fine. However, when pushed out through SCCM with admin rights the Java splash window opens and I click next I get an error that states something to the effect of "The file you are trying to run is missing or invalid".

Like I said, the splash screen opened so the installation did start. Any ideas?

Re: Java 7u9 and SCCM

Originally Posted by jheibeck

I'm trying to deploy Java through SCCM and am having a problem. The installation is being called from a cmd file. When run manually and locally it works fine. However, when pushed out through SCCM with admin rights the Java splash window opens and I click next I get an error that states something to the effect of "The file you are trying to run is missing or invalid".

Like I said, the splash screen opened so the installation did start. Any ideas?

This may help, it'll give you the MSI file and you can run this instead of a CMD file (if you are just trying to install Java rather than anything else fancy?)

Also, what version of SCCM are you using? 2007 or 2012? are you trying to push it out or offer it out? Can you post the CMD file so we can see what it is doing? Are you running it direct frmo the DP or from the cache? Also, do you want it to run silently or interactively?

Also, what version of SCCM are you using? 2007 or 2012? are you trying to push it out or offer it out? Can you post the CMD file so we can see what it is doing? Are you running it direct frmo the DP or from the cache? Also, do you want it to run silently or interactively?

You can't use start /wait in front of the wmic command so this was the only way I could do what is needed.
This is a mandatory assignment, no interaction so itb should be running from cache. But, since it was not working I had to make it interactive to see what was happening. Everything works till java. Java pops up the first screen, I click next and it can't find the rest of the installer. It does create the log file, but it is empty.
If run from scratch locally it all works fine.