PolicyPak Group Policy Edition licenses are always licensed on a per-computer basis. There is no limit to your use of the components within the product (e.g. PolicyPak Application Manager, PolicyPak Preferences Manager). You may also install an unlimited number of “Admin Stations”.

With regard to PolicyPak Application Manager (one component of PolicyPak Group Policy Edition), a licensed computer can embrace an unlimited number of Paks, whether you create them yourself using our PolicyPak DesignStudio Software, or use one of our growing number of pre-installed Paks.

No. Because we don’t count user accounts – only computer accounts. Service accounts are “users” and don’t count in any PolicyPak product’s licensing.

Everyone’s circumstances are a little different. But we generally license upon the number of end-points (desktops, laptops, and/or concurrent Terminal Services & Citrix connections) you want to manage. See this page for further information on licensing Terminal Services & Citrix connections. If you’d like a specific quote based upon your circumstances, click here or call 800-883-8002.

Yep. We’re flexible within reason. Please call us at 800-883-8002 or click here.

There are two ways to trial PolicyPak Group Policy Edition:

• You can simply run our licensing tool and generate a license request key. You send it to us, and we send you a license that’s valid for 30 days.
• You can rename any computer to have the word “Computer” in the name and all PolicyPak Group Policy Edition components on that machine will act as if they’re fully licensed. You would do this if you didn't want to install any PolicyPak license keys, but still wanted to just try PolicyPak on one or two machines.

PolicyPak Group Policy Edition needs a license for each endpoint you want to manage.

You are welcome to license particular OUs or the whole domain. You are then free to use all of the components of PolicyPak Group Policy Edition – such as PolicyPak Application Manager, PolicyPak Preferences Manager, PolicyPak Admin Templates Manager, and PolicyPak Security Settings Manager – across all those endpoints in any way you choose.

PolicyPak Group Policy Edition:

• Is licensed based upon the number of desktops, laptops and/or concurrent Terminal Services & Citrix connections you have.
• Computers must be domain joined.
• You must true-up every year.
• You pay an initial fee and then renew each year.
• You do not get access rights to PolicyPak Cloud Edition with a PolicyPak Group Policy Edition license.

PolicyPak Cloud Edition:

• Is licensed by purchasing a “pool” of licenses.
• You “consume” licenses until your pool of licenses is used up.
• If you need more licenses at anytime, you can buy them anytime.
• Each license for PolicyPak Cloud Edition includes a license for PolicyPak Group Policy Edition automatically, so you are free to use the PolicyPak functionalities via Cloud or On- Premise as suits you best.

For PolicyPak Group Policy Edition, we supply a “License wizard” (included in your trial download). Then click “Generate an initial request for a new license.”

• PolicyPak Group Policy Edition is licensed per-computer (defined as a valid Active Directory account plus desired concurrent Terminal Services & Citrix connections).
• The license wizard will automatically count the number of computers that you intend to use the product with, based on the Organizational Units (OUs) you selected in your good-faith estimate.
• Tip: Note that there are no restrictions on using the components within PolicyPak Group Policy Edition (such as PolicyPak Application Manager or PolicyPak Preferences Manager) once it’s been correctly licensed. For example, PolicyPak Application Manager is not licensed per-Pak, and you’re always free to use any of our pre-created Paks or create your own Paks.
• You then send us your license request via email. It’s a simple text-based “copy / paste” request. The license request contains only the data needed to license the product, and all of this data is shown to you first. The license request also contains a digital “signature” verifying that the data came from our license management tool.
• Once we receive a PO/ payment, we send you a license file for your domain or OU(s), and PolicyPak Group Policy Edition is licensed for a year.

See the video in the first question showing the license request and license install process for PolicyPak Group Policy Edition.

Yes. You must purchase 100 licenses for PolicyPak Group Policy Edition. If you have fewer than 100 computers, you must still purchase 100 licenses.

Short answer for PolicyPak Group Policy Edition: No.

Short answer for PolicyPak MDM Edition: Yes.

Short answer for PolicyPak Cloud Edition:: Yes..

For PolicyPak Group Policy Edition, your on-prem delivery method (using Group Policy, SCCM, LanDesk, etc) requires that all computers must be domain joined.

For companies which (mostly) want to use the Group Policy method... all computers must be domain joined at least once and have the “knowledge” of what OU they’re in and get the PolicyPak license information first. Then they can go offline and PolicyPak Group Policy Edition and its components will continue to work during the licensing period.

If you have, say, 80% of machines which are Domain Joined and, say 20% of machines which are Non-Domain joined, you can license the 80% with PP Group Policy Edition, and then manage those final 20% with either PolicyPak Cloud -or- MDM Edition.

If a Group Policy Object is linked to a parent OU (or the domain), it applies to all sub-containers as well.

Therefore, for PolicyPak Group Policy Edition, we must count computers in all relevant sub-OUs as well. Our Licensing Tool makes it easy to see which containers are included and exactly how many computers you must pay for.

So, let's assume you have about 3500 machines, but LT reports that you have 7000.

That's a big difference ! Chances are, if you're like most AD admins, you haven't cleaned up for a while.

So, here's what we can do to be helpful:

Item 1: PolicyPak's licensing tool has a built-in way to HELP YOU clean out stale accounts; thus reducing your costs and final count. See the video here and watch the first three minutes for details

Item 2: When you are first purchasing and you become a PolicyPak customer, we can let you be "wildly over" your count for a full year. Said another way, we'll give you a full year to "clean up" your Active Directory. But when it comes time to renew next year, the count demonstrated in LT will be what you will renew upon.

Item 3: As a customer over the long term, if you are "a little bit over", we can usually accommodate this. Like, you have 3500 machines, but LT reports 3700. This situation occurs when you have servers or test machines and/or a small amount of overage. But again, we can only directly accommodate "a little bit over" in this way.

If you have a very special circumstance, it's possible we can accommodate it. You can talk with your salesperson and try to make special arrangements

But our general rules of thumb is our policy as expressed in this statement.

When an OU is selected at any level, all OUs within it are automatically selected and cannot be un-selected. This is because you're licensing from this OU "onward." This enables you to create new sub (child) OUs within the parent at any time during the year.

That being said, there is no way to exclude a child OU from a parent, because you're licensing that parent OU "onward / downward."

You only need to do a mid-year true up when:

• Only licensed specific OUs and
• Your OU structure changed mid-year and
• Your number of computers has increased by more than 20%

In this case, you need an updated license key to fit your newly reorganized OU structure. If your number of pre-paid computers for the current year increased by more than 20%, you must pay a prorated cost for the updated count for the remainder of your current year.

When you go to renew at the end of you current year, starting at that next true-up period, you’ll simply pay the renewal rate for those computers.

For PolicyPak Group Policy Edition, only active Windows computers within Active Directory are counted. Disabled computers will not receive policy therefore they are not counted by PolicyPak.

Additionally, user accounts, Macs, Linux, and anything “Not Windows” is explicitly excluded from the count.

You are only ever charged for active Windows computers within Active Directory for PolicyPak Group Policy Edition.

Anytime a computer’s Active Directory account is moved to an un-licensed OU, or move the computer to another domain (or the license simply expires), PolicyPak Group Policy Edition will stop working.

This means that the product will no longer process new directives, and no longer attempt to keep the machine in compliance.

To be in compliance with PolicyPak licensing, you must express the number of inbound Terminal Server or Citrix inbound connections you are licensed for.

For instance, if you want to use PolicyPak Group Policy Edition with Terminal Services and/or Citrix, and you have a farm with 3 servers and 250 inbound connections, you must license all the inbound connections (250) as if they were counted in Active Directory.

Therefore to be fully compliant, you would license the number of computers in Active Directory plus the inbound Terminal Server and/or Citrix inbound connections. If you don’t wish to run PolicyPak Group Policy Edition on your Terminal Services or Citrix machines these inbound connections do not need to be declared at purchase time.

For example scenarios of how to license PolicyPak Group Policy Edition with Citrix and/or Terminal Services, please see this page

PolicyPak Group Policy Edition works great with VDI machines. You simply need to license them.

To be in compliance with PolicyPak licensing, you must express the number of MAXIMUM connections that can serve users.

The PolicyPak licensing tool can only count enabled Active Directory computer accounts.

So, depending on what VDI solution you use, those computer accounts could be:

• Pre-made in Active Directory and waiting for VDI sessions to be turned on (just like desktops or laptops have pre-made AD accounts.)
• Some pre-made computer accounts in Active Directory. For instance, you could have 5 pre-made AD Computer accounts but the VDI solution treats them as 333 possible sessions.
• No pre-made computer accounts in Active Directory. You could have 444 VDI sessions where computer accounts are created in AD on-the-fly.

Therefore to be fully compliant, you would license the number of computers in Active Directory plus the MAXIMUM number of VDI sessions you can serve to your users.

If you don’t wish to run PolicyPak Group Policy Edition on your VDI machines, then those computers do not need to be declared at purchase time. Simply ensure you don't select the OU during licensing time.

The word “Perpetual” can be a word with a lot of un-clarity when it comes to software licensing. So in the next several questions, we explain in detail our required “True Up” process. In short, PolicyPak Group Policy, Cloud, and MDM Editions are not considered “Perpetual” in that you get to “pay once and use them forever and ever”, like when you buy and license a single copy of Microsoft Office, Quicken, or WinZip for your home.

PolicyPak licenses are only considered “perpetual" for that currently paid up year, until such time that renewal time occurs. During the year, you are welcome to “overuse” what you paid in for the year (see next FAQ question.)

In the previous example, you started with 3,000 machines and grew to 3,300 machines. That’s great – we want you to use your PolicyPak investment the way your company needs to, when you need to. You don’t need to come to us every time your company grows or uses PolicyPak products for more computers. However, we do require that your license catches up with your usage at one-year intervals. We call this “truing up.”

Before the expiration of each one-year license period, the “Technical Contact” on record will be reminded to re-run our license wizard, this time using the audit feature. The license wizard will make a quick inspection of all GPOs within the scope of license for PolicyPak Group Policy Edition.

We simply ask you to re-count where you want to use PolicyPak Group Policy Edition the next year. You send in your updated license request. You “renew” the computers from last year, and “true up” any overage.

Note: It’s possible you have fewer computers than you did last year. In that case, you don’t pay anything for new licenses. However, you are still bound to pay the maintenance fee for the previous year’s license count.

Everything just continues to work. First of all PolicyPak Group Policy Edition is licensed per computer. So you never pay “per user” – ever. Let’s go thru an example.

Let’s assume you initially estimated that the Sales OU, Marketing OU and Research OU would use PolicyPak Group Policy Edition (you’re planning to use a lot of the PolicyPak Application Manager component).

And at that time, our initial discovery found a total of 3,000 computers. But two months later, you add 100 new computers to each of Sales OU, Marketing OU and Research OU

That’s another 300 computers for a total of 3,300 computers. Don’t worry! Your PolicyPak investment continues to work fine!

At the end of your year, we’ll ask you to re-count the number of computers. So now you now have 3,300 computers. And you’ll simply “true up” to pay for those extra 300 computers at the end of the year. And you’ll “renew” the original 3,000. We’ll then give you a new license file which is good for another full year. And, again, if during the year, you “over-use” there is no charge until the end of the year.

You must run the license tool every year to get an updated license file for PolicyPak Group Policy Edition.

If you fail to run the True-Up, then your one-year license expires and the product, with all of its components, simply stops working. For instance, PolicyPak Application Manager will stop processing new directives and will not re-enforce settings. If you are using PolicyPak’s AppLock features, then it will act as if the PolicyPak product wasn’t installed. PolicyPak Group Policy Edition stops working on clients exactly one year after the license file is originally generated for each product.

So, at the 11th month mark, we automatically remind you to run the PolicyPak License Management tool to perform a “True-Up.” We will continue to send email reminders and make a best effort to call you if we see you’re getting close to lapsing. At the one year anniversary, PolicyPak Group Policy Edition will stop functioning – unless you get a new license file from us each year.

By paying for multiple-years in advance for PolicyPak Group Policy Edition, you then lock in your per-computer license cost for the duration of your term.

Every year you get one-year license keys and you are still required to “True up” every year and pay for any overage should your computer count increase from last year.

We give you a one year key, and when you true up, we give you the key for the next year.

PolicyPak Group Policy Edition is on-premise software and has no cloud component. The typical definition is that SaaS is something that is "Web-based" or "hosted software." PolicyPak Group Policy Edition is not that. That being said, you pay for PolicyPak Group Policy Edition is like a SaaS product, in that you pay yearly to keep getting updates and keep it functional.

When you buy the PolicyPak Group Policy Edition, this hooks into your on-prem Active Directory servers and on-prem Windows clients. Therefore, at no time does PolicyPak have access to any data of your company.

The product you want is PolicyPak MDM Edition, because PolicyPak MDM Edition will utilize whatever transport you already have. In contrast, our PolicyPak Cloud Edition product is for organizations which don’t have the need or desire to pay for an MDM service; our Policy Cloud service serves as the transport.

We have a detailed FAQ article on this. Please see this link for the technical how-to.

In order to get PolicyPak to work with your MDM service, your Windows 10 endpoints must receive three things

1. The PolicyPak Client Side Extension (CSE version 1300 or later). This is downloadable in the PolicyPak portal.
2. The License file which enables your specific email suffix (like "[email protected]"). This is provided by PolicyPak Sales team and is “keyed” to your specific UPN.
3. The Group Policy or PolicyPak directives, wrapped up as an MSI file. We provide the utility called the PolicyPak Exporter utility to do this. (You can learn more about the PolicyPak Exporter utility in the “Advanced Concepts” manual or a brief overview: here)

To get started paying for your PolicyPak MDM Edition licenses, we need to see an accurate report of how many Windows 10 machines are currently "joined" to your MDM service. This is your "initial count" and how many you pay for in Year 1. Then, every year you will perform a "True up." You will do this by sending a screenshot and/or report demonstrating how many Windows 10 machines (also known as Windows 10 Devices) are currently registered (also known as Joined) to the MDM service. Unless you have some special agreement with PolicyPak at time of initial purchase, the assumption is that 100% of the joined Windows 10 computers will be paid for, trued-up and licensed.

If you organically grow, you only need to true up once per-year. Only if you grow more than 50% over what you pre-paid for must you true-up mid-year. If you think you're going to grow more than 50% during the year, it is recommended that you pre-pay for your intended usage.

You must pre-pay your intended usage at that point. Additionally, since PolicyPak MDM Edition is "keyed" by email / UPN names, like "@policypak.com", if the company you take over doesn't share the email as yours, you will need to contact sales to true-up then get an additional license key to cover this new company

Maybe. If you have a special circumstance and scenario you want to enable, you must discuss with PolicyPak Sales, which may or may not grant the ability to light up "managed connections" and VDI. Before trying to enable VDI or computers like this with PolicyPak MDM Edition you must discuss this with the PolicyPak Sales team first.

There are some restrictions in installing the PolicyPak Client Side Extension:

1. You may not, without a special arrangement with PolicyPak, deliver the PolicyPak Client Side Extension to a machine capable of serving multiple sessions like Citrix, RDS, VDI or so on. In other words, you cannot consume ONE license on a server, and light up multiple (10,15, 20, 100) inbound connections.
2. When using PolicyPak MDM Edition, since there is no concept of OUs, you are committing to paying for PolicyPak with 100% of the Windows 10 machines which are joined to your MDM service. Said another way, we cannot segment out or “partially license” your MDM investment. All Windows 10 machines which participate in your MDM service must be accounted and paid for.

Because PolicyPak MDM enhances your existing MDM service, absolutely nothing is stored about your users within PolicyPak. That being said, we DO store information about your ADMINISTRATORS so we can contact them via email and phone numbers for updates and so on.

No. The typical definition is that SaaS is something that is "Web-based" or "hosted software." PolicyPak MDM Edition is not that, because it leverages the MDM service you already have. Remember: PolicyPak MDM is NOT itself an MDM service and has no cloud component and PolicyPak MDM never sees or has access to your data. That being said, you pay for PolicyPak MDM Edition like a SaaS product, in that you pay yearly to keep getting updates and keep it functional.

When you buy the PolicyPak MDM Edition, remember ... it is NOT ITSELF an MDM service and has no cloud component. Therefore PolicyPak MDM Edition never sees or has access to your data. Your company data always resides 100% within the MDM solution you choose (Microsoft Intune, VMware Workspace One, etc.) PolicyPak never has any access there.

You declare a specific amount of PolicyPak Cloud Edition licenses to purchase.

Typically, you’ll want to license upon the number of end-points (desktops and laptops).

If you’d like a specific quote based upon your circumstances, click here or call 800-883-8002.

Our sales team can set up your PolicyPak Cloud Edition trial.

A standard trial is 10 licenses for PolicyPak Cloud Edition for 30 days. You can try all products in PolicyPak Cloud Edition (PolicyPak Application Manager, PolicyPak Preferences Manager, PolicyPak Admin Templates and PolicyPak Security Settings) for the 30 days.

However, if you have a special case, need more time, etc. we’re flexible. Just ask and we’ll try to accommodate your trial’s needs.

To obtain your license for PolicyPak Cloud Edition you simply decide how many licenses you want to purchase. Then you can pay for and acquire a “pool” of licenses.

Your initial purchase must be as a block of 100 licenses or more. Our sales team sets up your account and provides you credentials to access the PolicyPak Cloud Edition portal.

PolicyPak Cloud Edition doesn’t have any relation to Active Directory.

So it doesn’t matter if your computers are in OUs ... or not.

Computers “join” PolicyPak cloud if they are domain joined already or not domain joined.

In order to use any PolicyPak Cloud Edition, you must consume a license from the PolicyPak Cloud service. In this way, there are no “unlicensed” places. The computer is licensed everywhere.

Additionally, with a PolicyPak Cloud Edition license, you also automatically get a license to use PolicyPak Group Policy Edition as well.

If the PolicyPak Cloud Edition license expires, the product will no longer process new directives, and no longer attempt to keep the machine in compliance.

After your trial, you agree to purchase a “pool” of licenses for PolicyPak Cloud Edition. The minimum amount of licenses you can purchase is 100. The more licenses you purchase in your pool, the lower your cost per license becomes. Your sales person can give you a specific quote based upon the number of licenses you want in your pool. You can pay via credit card, purchase order, and some other methods.

You can pay for PolicyPak Cloud Edition monthly. You need to let us know this is what you want to do.

Note: It is more expensive to go “month to month” than it is if you purchase a whole year of PolicyPak Cloud Edition upfront.

That being said, you can increase your count as needed month-to-month if you grow.

When no more licenses are available in the pool, computers will try to consume licenses of PolicyPak Cloud Edition anyway. But since they cannot, they go into the “waiting list.”

If you then purchase more licenses (by contacting our sales team) the computers waiting the longest will then acquire licenses from the updated pool (now with more licenses) the next time they try to connect (typically within an hour.)

If you decide to stop paying for PolicyPak Cloud Edition, the components (like Application Manager or Preferences Manager) simply stop working when the license term expires.

For instance, PolicyPak Application Manager will stop processing new directives and will not re-enforce settings. If you are using PolicyPak’s AppLock features, then it will act as if PolicyPak wasn’t installed. PolicyPak Preferences Manager will not deliver Group Policy Preferences using the PolicyPak Cloud service, nor will it return Group Policy Preferences items to compliance.

So, at the 11th month mark, we automatically send email reminders and make a best effort to call you if we see you’re getting close to lapsing. Once all paid up (or using a PO), we re- issue the number of licenses PolicyPak Cloud Edition, and everything continues to work for another year.

By paying for multiple-years in advance for PolicyPak Cloud Edition, you then lock in your per-computer license cost for the duration of your term.

Every year you get one-year licenses uploaded to the Cloud Service. You are still required to touch base every year by your renewal date and let PolicyPak know if should you want to increase your license count from last year.

We give you one-year licenses, and when you confirm your count, we give you the licenses for the next year.

Yes. The typical definition is that SaaS is something that is "Web-based" or "hosted software." PolicyPak Cloud Edition is just that, plus it has a "client component" that you must also install per-endpoint. You can pay yearly or monthly for PolicyPak Cloud.

We have a special FAQ on this topic about PolicyPak Cloud. You can read it here.

PolicyPak products are always licensed on a per-computer basis. Any desktop, laptop, VDI and/or concurrent Terminal Services/Citrix connections count as a license.

You can use PolicyPak Group Policy Compliance Reporter with one of two different types of licenses.

The Free License for PolicyPak Group Policy Compliance Reporter, which allows for unlimited use of the reporting tool:

• You can use Pull mode.
• You can use Push mode (with the server component.)
• You can report ONLY upon PolicyPak products settings (e.g. Application Manager and Admin Templates Manager)

The Paid License, which enables unlimited use of the reporting tool:

• You can use Pull mode.
• You can use Push mode (with the server component.)
• You can report upon PolicyPak product Group Policy settings (e.g. Application Manager and Admin Templates Manager)
• You can report upon Microsoft Group Policy settings (Group Policy ADM/ADMX, Group Policy Preference, Security Settings)

Unlimited Administrators may use the PolicyPak Group Policy Compliance Reporter console. You only pay for endpoints to report data.

You require the PAID license.

Reporting on Microsoft products (including GP Preferences, Admin Templates and Security Settings) via PolicyPak Group Policy Compliance Reporter is only available via the Paid License.

The Free License allows reporting on PolicyPak products only.

Yes, this is possible using the server component of the PolicyPak Group Policy Compliance Reporter.

When the server component is used you can store and share tests, reports and history from a central on-premise server across an entire team of Administrators.

You can use the PolicyPak Group Policy Compliance Reporter “standalone” which means NOT connected to a PolicyPak Group Policy Compliance Reporter server. If you do this you’ll be able to interrogate (Pull) data from endpoints and report on them … but only if they are online when you make your request.

You can use the PolicyPak Group Policy Compliance Reporter “server” which enables your endpoints to “push” their data to the server. Then Administrators connect to the server (and not the endpoints) to run reports.

You are licensed for both “Standalone” and “Server” components when you are licensed.

The Server is optional but recommended to use because data will always be up to date (because it is pushed.)

Additionally, when using the PPGPCR Server, you can save and share tests, results, history and reports to be stored centrally on-premise and shared among multiple administrators.

You can simply run our licensing tool and generate a license request key. You send it to us, and we send you a license that’s valid for 30 days. Request your PPGPCR License by performing these steps (and sending TWO License request files: one for endpoints and one for server.):

For a quote for PolicyPak Group Policy Compliance Reporter, call us at 800-883-8002 or click here.

If you try to request reports from “unlicensed places” here is what happens:

If that unlicensed place IS licensed for PolicyPak On-Premise, you will get data back only for PolicyPak Application Manager.

If that unlicensed place is NOT licensed for PolicyPak On-Premise, you will get no data back.

Anytime a computer’s Active Directory account is moved to an un-licensed OU, or move the computer to another domain (or the license simply expires), then PolicyPak Group Policy Compliance reporter will stop reporting on those target computers.

In the previous example, you started with 3,000 machines and grew to 3,300 machines. That’s great – we want you to use your PolicyPak investment the way your company needs to, when you need to. You don’t need to come to us every time your company grows or uses PolicyPak products for more computers. However, we do require that your license catches up with your usage at one-year intervals. We call this “truing up.”

Before the expiration of each one-year license period, the “Technical Contact” on record will be reminded to re-run our license wizard, this time using the audit feature. The license wizard will make a quick inspection of all GPOs within the scope of license that use PolicyPak Group Policy Compliance Reporter.

We simply ask you to re-count where you want to use PolicyPak Group Policy Compliance Reporter the next year. You send in your updated license request. You “renew” the computers from last year, and “true up” any overage.

Note: It’s possible you have fewer computers than you did last year. In that case, you don’t pay anything for new licenses. However, you are still bound to pay the maintenance fee for the highest amount of computers found in the last three audits.

You must run the license tool every year to get an updated license file for PolicyPak Group Policy Compliance Reporter. If you fail to run the True-Up, then your one-year license expires and the product simply stops working.

For PolicyPak Group Policy Compliance Reporter, you will not be able to see if those target computers are in or out of compliance any longer.

PolicyPak Group Policy Compliance Reporter stops reporting on clients exactly one year after the license file is originally generated for each product.

So, at the 11th month mark, we automatically remind you to run the PolicyPak License Management tool to perform a “True-Up.” We will continue to send email reminders and make a best effort to call you if we see you’re getting close to lapsing. At the one year anniversary, PolicyPak Group Policy Compliance Reporter will stop functioning – unless you get a new license file from us each year.

By paying for multiple-years in advance for PolicyPak Suite (On-Premise Edition), you then lock in your per-computer license cost for the duration of your term.

Every year you get one-year license keys and However, you are still required to "True up" every year and pay for any overage should your computer count increase from last year.

We give you a one year key, and when you true up, we give you the key for the next year.

PolicyPak Group Policy Edition is on-premise software and has no cloud component. The typical definition is that SaaS is something that is "Web-based" or "hosted software." PolicyPak Group Policy Compliance Reporter is not that. That being said, you pay for PolicyPak Group Policy Compliance Reporter is like a SaaS product, in that you pay yearly to keep getting updates and keep it functional.

When you buy the PolicyPak Group Policy Compliance Reporter, all data is kept on-premise in the product. There is no cloud component and no data is transmitted outside your organization.