Use PolicyPak Cloud to deliver PolicyPak Java Rules Manager policies. Configure websites to use the version of Java you choose, or block Java websites entirely – even for remote machines via the Cloud. Making a Java Deployment Rule Set for your Enterprise has never been easier or more flexible.
PolicyPak Java Rules Manager Use PolicyPak Cloud to choose which version of Java for what website
Hi. This is Jeremy Moskowitz. In previous videos, I show you how you can use Group Policy or the not Group Policy method to map specific websites and Java applets to specific versions of Java. You saw me use “java.org” here to create a policy that would map “java.org” to “Java SE 7 Update 51.” I created a policy earlier that would say for “javatester.org” to go to “Java SE 8 Update 25.”
Well, you can also deploy these same rules to your domain-joined or non-domain-joined machines using PolicyPak Cloud. It’s super easy to do. You just simply right click and “Export as XML.” I actually have a couple of rules here, so I’ll call this “PPJAVA-RULE-1” here. Then I’ll right click this guy for “javatester.org” and “Export as XML” and call it “PPJAVA-RULE-2.” It’s as simple as that.
Then if you have a PolicyPak Cloud account, you simply go to your PolicyPak Cloud account. You can either upload them here in the upload “XML Data Files,” or you can go right to your “Computer Groups” and associate them right to where your computers are.
In this case, I’m going to go right to my special “All” group, and I’m going to “Upload and link a new XML here.” This only takes a second. I’ll go ahead and pick “PPJAVA-RULE-1” here. That first rule was “java.org” to “Java SE 7 Update 51.” Let’s go ahead and note that correctly: “PPJAVA: Java.org to 7 U 51.” Okay, that’s the first one. There you go. You see it’s linked to the “All” group.
We’ll “Upload and link a new XML here” and we’ll pick “PPJAVA-RULE-2.” This one we said was when we are going to go to “javatester.org” and use “Java SE 8 Update 25,” so “PPJava: Javatester.org to Java 8 U 25.” And that’s it.
Now that that’s all locked and loaded here, we have our two rules. Let’s go over to our machine here. this machine is not domain joined. If I were to go to show you that this computer is “NOT DOMAIN JOIN.” What I’m about to do is to launch the “PolicyPak Cloud Client.” Let me go ahead and do that now.
This is going to join the PolicyPak Cloud service and download the client side extension (which is the moving part that does the work), any licenses you have and then also download the XML directives. It does it all in one swoop.
Once that’s done, because the Java rules manager works for all users on the computer, every user will get this. To save a little time, I’m just going to go ahead and run with this user. You can see I have a little shortcut that happened as soon as I joined here.
Now let’s go ahead and test it out. I’m going to just pick “Mozilla Firefox” here. Let’s going to java.com first and then we’ll going to javatester.org second, and we’ll see what it reports. You could use either browser here. You could use Internet Explorer or Firefox. I just happened to use Firefox here.
If I go to “java.com” and select “Do I have Java?” and “Verify Java Version,” it will report not the latest version I have on this machine but the one we’ve specified, which is “Version 7 Update 51.” If I go over to “javatester.org” and select “Test the version of Java used in this browser,” it’s not going to find the latest version. It’s going to tell it “Java Version 1.8.0_25,” which is exactly what the rule says.
So for your non-domain-joined machines if you want to specify when your end users – domain-joined or not domain-joined – go to specific websites, you can map the version of Java you want to the websites. It couldn’t be any easier.
If you want to get started with PolicyPak and PolicyPak Cloud, simply join us for a webinar and you can get started right after that.
Thanks so very much, and we’ll talk to you soon.