PolicyPak Licensing: On-Premise licensing methods compared.

You can use two methods to get endpoints licensed. Use the LT utility or import the items directly into a GPO. Here’s how you would do either one.

PolicyPak Licensing: On-Prem licensing methods compared

Hi. This is Jeremy Moskowitz, Group Policy MVP and Founder of PolicyPak Software. In this video, I want to show you the two ways that you can import the license files that you’re going to get from Sales. You’ll do this if you’re trialing or if you’re a customer.

By way of example, you’re going to get a zip file, and you’ll see that there’s a handful of different license files. You can see that they’re pretty clearly named. Remember, PolicyPak has multiple components in the Suite, and we’re always adding more.

At the time of this video, there are four components in the PolicyPak On-Prem Suite. There’s “Application Manager,” “AdminTemplatesManager,” Preferences Manager (“PrefsManager”) and Security Manager (“SecManager”). There are also two pieces for the Compliance Reporter. There’s the “ENDPOINTS” that will perform the reporting, and there’s the PPGPCR SERVER” that also has to be licensed.

Assuming you get all the stuff back from the sales team, again, there are two ways you can get the license done. I’m going to show you both.

The first way is in the download of all the bits, there’s a file inside the “Licensing for All On-Prem Products” called “LT” or Licensing Tool. You have to use this tool if you want to generate requests. I’m assuming you’ve already generated your requests, sent those to the sales team, and this is what you got back.

What we’re going to do is “Install a license received from PolicyPak Software, Inc.” What you’ll do is simply “Browse” for this location that has your unpacked files here, and you’ll pick each one of these one-by-one and click “Validate.” It says, “The provided license is valid.” What it’s going to do is, based on where you said you’re going to use it, it will automatically “Create GPO” and link them.

Now if it finds other Group Policy Objects that are already doing this, it could ask you if you want to overwrite them because you have maybe a newer license. That’s totally fine. I’ll go ahead and click “OK” here, and let’s go ahead and see what it does. It also asks you, “Do you want all those links ENFORCED?” That is to help you should somebody later down the line do a block inheritance in Group Policy.

Let’s go ahead and take a look and see what it did here. If I hit Refresh over my “Sales,” “PolicyPak License for Application Manager,” let’s see where it linked it to. It linked it over to the whole domain, which is exactly what it should do. There it is: “PolicyPak License for Application Manager.” It’s linked and it’s enforced so even if somebody later right clicks down the line and selects “Block Inheritance,” this license file will guarantee to make it through.

That’s choice number one. Let me go ahead and delete this for now just so we don’t intersect these two: “PolicyPak License for Application Manager,” “Delete.” That’s choice number one. Choice number two is you can use any Group Policy Object you want.

For instance, if you knew you were going to use it only in “Sales,” which would affect your “East Sales” and your “West Sales” as well, you could “Create a GPO in this domain, and link it here” and call this “PolicyPak: My Licenses” or whatever you want to call it.

So you have a Group Policy Object that’s linked over to where you want to use it. When you click “Edit” on the Group Policy Object, what you’ll do is you’ll use the computer side. Left click on the “PolicyPak” node, then right click and select “License Management.”

When you do this, once you select “License Management,” you get this window that comes up. You can “Import” all the licenses at once. For instance, these four are the four components for the On-Prem Suite as we ship today. The “ENDPOINTS” would help you with licensing the Compliance Reporter Endpoints, and this would be for the Compliance Reporter Server.

Again, what we’re saying is that all the stuff we’re going to do is going to have to be inside of the Sales OU, or else it’s not going to work because that’s, first of all, what we’re scoped for. In other words, that’s what my request was based upon and so therefore that’s what you’re paying upon. That’s also exactly what I’m doing here. I’m linking it over to my “Sales” OU.

So now if I click on the GPO here, you can see that all those licenses are installed here. You can see there are some extra settings here. You can safely ignore those. But you can see that all the licenses are right here and imported. That’s it. So now we’ve lit up the “Sales.”

Let’s review each of the licenses one more time. Let’s just make sure we understand all the license types. The ones that are listed, in this case, “1, 2, 3, 4” are for the four components to make PolicyPak On-Prem Suite do work. If you don’t have these four licenses, then the PolicyPak On-Prem system to manage applications and do admin templates and to keep Group Policy Preferences alive and so on, that’s not going to work because we’re not licensed.

The second piece is the Group Policy Compliance Reporter “ENDPOINTS.” Again, these are the end user machines. If you want them to report to the server, they have to be licensed. What they will be licensed for is to turn on Microsoft items: Microsoft Group Policy Admin Templates, Microsoft Group Policy Preferences and Microsoft Security Settings.

The last piece is the Compliance Reporter “SERVER.” That location also must be licensed.

With that in mind, like I said, you can either use LT and do it one-by-one, or you can create a Group Policy Object. You saw me do that over here. I created a Group Policy Object, and I sucked in the licensing information into each of these machines.

That’s all there is to it. I hope that helps you out and you’re ready to get started. Thanks.

Back