Did you purchase Patch or Security Suite? Sorry hit update to fast. Reason I ask is there are vulnerabilities built for jre. What error message are you receiving running via LANDesk. The vulnerability uses for EXE:
/s JAVAUPDATE=0 AUTOUPDATECHECK=0 JU=0
Good page for hints:
Zman - We have purchased Patching.
You indicate that there are already vulnerabilities built for JRE - can I leverage those for initial deployment of the JRE?
I'll check out that website and see what happens...
So you the current vulnerabilities only update Affect Products. So in your case if you have a bare machine with no JRE it will not work. However, you can use the exisiting vulnerability to:
- See what command lines LANDesk is using (see above). They use three scripts....
- JREJDKv1.6.31_Manual. You can clone the vulnerability. RC on the vulnerability and select clone.
- Modify the Detection rules and remove the Affected Products.
- Save as a custom vulnerability
You can now repair the vulnerability via autofix (careful)
Hmmm... Still having issues. Tried copying the install string from the vulnerability, and it didn't help.
What I'm seeing from LDMS is...
Result: Package deployment failed
Return Code: 1619
Well, it's working now, and I feel stupid.
Zman - that link you providied described exactly the same problem I was having. And suggested using the .MSI, which is what I originally started out trying to do with my 6u31 package. I didn't figure it'd help, but I went and unpacked the .MSI to give it a try...
And I noticed, when I unpacked the .MSI, that there was also a .CAB included...
SCCM doesn't really require you to explicitly state what gets copied to the local machine - everything in the directory gets copied over. So I was getting both the .MSI and the .CAB in my SCCM package.
But, when I built my LDMS package, I was only explicitly telling it about the .MSI - so that .CAB wasn't being downloaded to the local machine. Which obviously isn't going to work.
So - built a new package, included both the .MSI and the .CAB, using the same flags we used to use - and it's all happy now.
Correct you can either use a delivery method that states run from source, or if the application has multiple files you must specify them since the only file cached is the main file. MSI has an autodetect button you can use to parse the msi table and automagically add the necessary files. Glad to hear it is working.