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:
Some examples below of how a computer could be licensed and the types of output you can expect.
A second example, but this one using Enterprise Full (aka Enterprise+) licenses (only valid for CSE versions 23.6 and later):
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.)