Monday, January 18, 2016

Java Deployment

So an issue arose lately where I needed to push out a Java install for a select few computers in my domain because of an upcoming Oracle Go-live. Since the numbers are around 50-60 out of 400 computers I definitely don't want to push it to all of them.

Originally I went the GPO route.  I had a script designed that worked on a test vm, a coupe GPO's to push out both the java install itself but also the deployment.properties, and exceptions.sites however I ran into issues getting the exceptions to appear in the gui and I had an environment setting string that I needed to enter.

*I ran into trouble finding the above, so for future generations since Oracle failed to document this.. if you need a custom env setting for your java it can be added to the deployment.properties file much like:

deployment.javaws.jre.0.args=-Djava.vendor\="Sun Microsystems Inc."


Back to the deployment.. with so much trouble and inconsistencies I ran into using GPO I opted instead for PDQ Deploy from Admin Arsenal.  Within 30 minutes of installing the Demo version I had a package created that successfully pushed Java with the exceptions list correctly. It's VERY fast too, and the library they have (accessible after buying a license) is immense! $500 is a big pill to swallow for one seat and I kinda wished the library access was allowed for longer than 1 year however this product is going to help me out tremendously in the near future.  Since I was able to expense this to a larger project and it won't hit my department I'd say it's a double-bonus in my situation.

However since I am unable to generate a list of only the computer objects for users that require this specific version of Java now we have to tackle deploying enterprise-wide.  Once we do PDQ Deploy will handle it with relative ease.


No comments:

Post a Comment