We all know how easy it is to deploy Java to all of our computers using PDQ Deploy. If you would like a refresher you can watch
A default deployment.properties file, located in a User’s profile is where the control panel and exception site list are usually managed. However, this is only on a per-user basis. This is not too helpful to a sys admin needing to manage multiple computers or maintain standard settings across their enterprise.
That’s where creating a deployment.config file comes in. Deploying this file out to your computers allows you to reference your very own deployment.properties file and exception.sites file.
The first line (deployment.system.config) is where you’ll indicate where your customized deployment.properties file is located. In this example I specified a location on a file server. Note that I had to conform to standard URI conventions. This is why the colon has to be escaped and I use forward slashes instead of the standard Windows backslashes.
The second line (deployment.system.config.mandatory=true) means that Java must pull the deployment properties from this file. Just an FYI, making this mandatory means that if the deployment.properties file can’t be located (for instance on a laptop that a user took home) then Java can’t be used or it will revert to the deployment.properties file that lives in a user’s profile. If you don’t want this behavior then set this property to false.
Now onto the bigger fish to fry: setting up properties. There are a great many options, settings and properties available, click here to see the different available properties.
Your file might look something like this:
You can see the last line that deployment.user.security.exception.sites is there with a path to the exception site file (Should you choose to use an Exception Site List). Also note that the deployment.security.level value needs to be either HIGH or VERY_HIGH as Java 8 no longer allows MEDIUM as a security level.
Put one URL per line to add a website to your list of allowed sites. That’s really all there is to that one. Add a new File Copy step (new with the latest PDQ Deploy 6 Beta, otherwise use xcopy or robocopy in a Command step with your deployment.config file attached in additional files)
That’s pretty much it. When you modify the deployment.properties or exception.sites files on your file server (as long as it is in the same directory referenced in your config file) you can rest assured that your Java clients will all pull down the new properties and sites.