dfoli

Good luck Kire

You have to put it after the install of jre8 in upgrade packages otherwise it will uninstall the jre7 and then the package will see no java when it gets ready to install and it will fail. Then you have no java.

Kire, In the Package Boot Editor I added a Run cmd.exe at the very end with the command-line parameters (/c wmic product where "name like 'Java 7%%' AND NOT name like '%%(64-bit)'" call uninstall /nointeractive) for x86, and (/c wmic product where "name like 'Java 7%%' AND name like '%%(64-bit)'" call uninstall…

Thanks jbaits, that is exactly what I am looking for. All of our systems our x64 and I am using the x86 for x64 Package for the 32-bit. The 32-bit Java works for most of the company, but we have two sections that have programs that need the user to have both 32 and 64 bit Java. This will allow me to deploy Java 8 without…

stcain, Have you been able to get therm to work? We keep getting not applicable for both Reader and Acrobat from systems that have Reader and/or Acrobat on them. If I go to the system itself and run the .msp it installs just fine. I have seen where a couple of others are having the same problem.

jbaits, That worked great for me, but I have some machines that have both x32 and x64 Java. I would like to only uninstall the x32 with the x32 package and the x64 with the x64 package. How could I adjust the parameters to accomplish that?

jbaits, That worked great for me, but I have some machines that have both x32 and x64 Java. I would like to only uninstall the x32 with the x32 package and the x64 with the x64 package. How could I adjust the parameters to accomplish that?

I am using the "Adobe Systems, Inc. Packages" node. * Adobe Systems Acrobat 11 Catalog * Adobe Systems Reader 11 Catalog I have checked the msp's manually and they will update at least back to 11.0.07 in Reader, and 11.0.0 in Acrobat Pro. (I had an old stand alone system that still had Reader 11.0.07, and I did a new…

After about an hour systems are showing up as needing the package. frppugs, if you go to the registry key that the Applicability rules point to, and copy that value into the 'String Value' field of the Applicability rules in the package (replacing the FFFF) you should be good-to-go. I will test installing the package next…

So, I have created the .mst file and added it to the package. I have put '/sAll /msi TRANSFORMS=ReaderDC.mst' in the Command Line (silent install) field. I looked at the Applicability rules and found that they had FFFF in the String Value field. I changed that to the Value that is actually in the key. It is now published…

Thank you jbaits and Kellytice, I will let you know how it goes. frgpugs, my first test running just the package the way it is I had the same problem "Not Applicable", but I had this same problem with both 10 and 11 for the first month or so of each release. With 11 the package wasn't recognized as being needed until I…

I am having the same problem, and I had it with Reader 11.0.10 at first. I tried a lot of different things then, but nothing worked. I got to the point that I downloaded the .exe and was building a package from scratch when I noticed that the Adobe packages had been modified the night before during the sync, so I tried it…

There is an additional catalog called Adobe Systems, Inc Packages. In there you can select reader and/or Acrobat, and classic or continuous track. They have DC 2015, but have not started new packages for DC 2017.