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.ar gs=-Djava. vendor\="S un Microsystems Inc."
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