If you are deploying the MSI, launch the EXE manually now. In most cases, the x86 version will suffice.Ĭopy the EXE to a network share where computers have read/execute. The version that you deploy depends on the browser architecture version that you use. If you see a higher failure rate, swap to the MSI. Download the offline installer from here. If you are using SCCM or another deployment suite, I would start with an EXE based deployment.

deploy the executable with a run once Group Policy Preferences scheduled task.deploy the executable with a run once startup script.You will have to do one of the following instead: If your deployment method relies on Group Policy, you can’t deploy the executable with Group Policy Software Installation. Personally, I have had better success with the executable in this release. It can also be deployed by extracting the MSI ( as seen in previous Java guides). Unlike some previous versions, Java 8 can be easily (and successfully) deployed with just the executable. So far, this theory has held true throughout the Java 8 release cycles. Whether you are just a release behind or very much out of date, you can use this guide to deploy the latest version of Java 8. For us administrators, it becomes more difficult to deploy with each version. And it probably pooped itself – I’m not checking though. We all know that it is going to act out somehow.

Deploy Google Chrome for Work with Group Policy.

Deploy Office 2013 with Group Policy – The Simple Way!.

Deploy Java Runtime Environment with Group Policy.

Deploy Adobe Flash Player with Group Policy.

Deploying Java 8 101 – Or why is Java still around?.