Starting June 2017, the PolicyPak Preferences component is available only upon request.

It's still part of what you paid for, and you can ask for it at anytime.
But why is not included since June 2017? Well, PolicyPak Preferences (PPPrefs) is typically not needed for on-premise scenarios.
And because PPP calls the operating system in a way that can sometime be unreliable, we are making it an upon-request license.

You might ask "When would I NEED the PPP license" Here are the scenarios for which you should request a PPPrefs license:

1. You want to use PolicyPak over MDM. (This is automatically included when we issue an MDM license.)
2. You want to deliver user-side-only Microsoft's GPPreferences items to computers (like what's seen in this video).
3. You want to deliver GPPrefs items using SCCM or some other non-GP method.

In those cases, or if you think you have another case, then email: [email protected] and we can get it to you.

It would be helpful in your email to let us know the circumstance in which you plan to use PPPrefs.

Then, because introducing PPPrefs can sometimes have unexpected OS integreation issues, we suggest you gradually roll out your PPPrefs license affecting only several machines at a time.

If you do encounter a problem, simply remove the PPPrefs license and any GP + PP + Preferences issues should go away.

Permalink : click here

PolicyPak Preferences Manager handles every single one of the Group Policy Preferences: more than twenty configurable options.

Permalink : click here

Yes we can do a local admin password reset on multiple machines which are not connected to the domain.
First, we will configure the policy in native Microsoft Preferences:

Then export it using PolicyPak Preferences manager in an XML file format:

Last step would be linking that XML to the appropriate group where your targeted client computer located.

Permalink : click here

From time to time, a Microsoft Group Policy Preference item is not compatible with PolicyPak trying to process it with PolicyPak Preferences component.

We have worked around many of these items, but some still remain.

As such, we have recommended that all on-prem customers un-license PolicyPak Preferences component unless its absolutely necessary for a specific use case.

This problem only manifests itself when the computer is DOMAIN JOINED and then also getting Microsoft Group Policy Preferences items while PolicyPak Preferences component is licensed.

To that end, here is the documentation to un-license a single component, like PolicyPak Preferences: If you’re an on-Prem cloud or MDM customer.
https://www.policypak.com/knowledge-base/licensing/what-if-i-want-to-unlicensed-one-component-on-prem-like-pppreferences.html

Permalink : click here