You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > 110: All Things Licensing > Knowledge Base > 07: Licensing Troubleshooting: All Methods > 01: How can I tell how a machine is licensed (by GPO, MDM, or XML file), and also know for what components it is licensed?
01: How can I tell how a machine is licensed (by GPO, MDM, or XML file), and also know for what components it is licensed?
print icon

You can use the ppupdate command line tool to both refresh cached policies and determine the licensing method. When the command is run, you can determine:

  1. Methods of licensure (Group Policy, MDM, and/or XML)
  2. Legacy License, Universal License, or Enterprise Full (aka Enterprise+) Universal License
  3. Start and Expiry Date
  4. Which GPO or from which XML file is performing the license
  5. Which Components are licensed
  6. Which Components are licensed for which Capabilities (for instance PolicyPak Least Privilege Manager Standard vs. Complete). Tip: Enterprise Full licenses always show Complete for all components.
  7. When a specific component is expressly disabled via an ADMX policy.
  8. When a specific component is expressly disabled via the license file.
  9. When a specific computer is licensed via multiple methods.

Some examples below of how a computer could be licensed and the types of output you can expect.

How can I validate on a few endpoints that I am VALID and won’t expire?

A second example, but this one using Enterprise Full (aka Enterprise+) licenses (only valid for CSE versions 23.6 and later):

 

  • Use the PPUPDATE command which will always show if you are VALID and licensing type.
  • Example of a machine getting Universal licenses successfully:

  •  

    Tip: Enterprise Full licenses are not honored by pre 23.6 CSEs. You MAY run multiple licenses “side by side” to transition from your original license to Enterprise Full licenses.

Additional Examples for various circumstances are below.

Example 1: Computer in the name, acts fully licensed for all components. Very useful for testing licensing issues.

Example 2: Completely unlicensed.

Example 3: Some items are licensed and not others. Typical when a customer is a Professional Customer and has purchased licenses for SPECIFIC components.

Example 4: Licensed by placing the XML file directly upon the machine, and not by GPO.

Example 5: When a component is licensed, but expressly disabled by ADMX.

Example 6: When a computer is licensed via multiple methods

Example 7: When a computer is licensed for SOME components via PolicyPak Cloud
Note: The Expiry date expresses when the computer is required to check-in by to maintain the license; not the actual expiration date of all computers. (That information is only found in PolicyPak Cloud Portal.)

Feedback
1 out of 1 found this helpful

scroll to top icon