We know you want to get started with a PolicyPak trial… fast!
Good news, we only need a few pieces of information to get started. Typically we can get started with only:
Warning: The details in this article get you started WITHOUT having to “count” number of computers (which means we cannot get you a formal quote.). Only when you COUNT the computers are we enabled to provide you a formal quote. This process is SLOWER and OPTIONAL, but does mean we can get you a formal quote: https://kb.policypak.com/kb/article/1079-how-to-request-licenses-from-policypak-by-creating-a-license-request-key/. Then send your License Request Key XML to your sales person to get a formal quote generated.
So, here's the rundown of how you can get A TRIAL LICENSE QUICKLY. You need to just pick ONE:
With PolicyPak, you don’t even need a license file from us to get started.
TIP: This is the RECOMMENDED way to get going … fast… with PolicyPak.
Simply rename a computer to have COMPUTER in the name, and … that’s it. You’re done. Here’s the two methods of how to do that in Windows.
Here’s a video showing what happens when you rename a computer and how PolicyPak reacts: https://kb.policypak.com/kb/article/483-testing-and-troubleshooting-by-renaming-an-endpoint-computer/
After you rename your computer to have COMPUTER in the name, then:
If you’re trying our PolicyPak Enterprise, PolicyPak Professional or PolicyPak SaaS … they all come with an included PolicyPak Cloud license. Your trial should automatically generate credentials to cloud.policypak.com (aka the PolicyPak Cloud Service.)
When you install the PolicyPak Cloud client, a license is automatically taken from PolicyPak Cloud (and also the PolicyPak Client Side Extension is installed.) You install a new machine into PolicyPak cloud by installing the PolicyPak Cloud Client like what’s seen here.
Here’s the videos to get started immediately with PolicyPak Cloud: https://kb.policypak.com/kb/section/195/
If you want to use Active Directory / GPO method to deliver PolicyPak settings, we need your domain name. And if you have multiple domains, that’s fine. We can make you ONE KEY which contains all your domain names.
The best way to get the domain name would be to run this simple Powershell command
$env:userdnsdomain
It will then produce the output of the domain name, which is the minimum requirement to make you a license key.
Once we generate the key, it will be in the PolicyPak Portal. Download the key and install it using these directions: https://kb.policypak.com/kb/article/1080-how-to-install-universal-licenses-for-new-customers-via-gpo-sccm-or-mdm/
Then follow these directions to get started with on-Prem Active Directory/ Group Policy: https://kb.policypak.com/kb/section/194/
If you’re using Intune specifically, we can turn on PolicyPak for your Intune instance. We need the Intune Company name. Run this PowerShell script which will return INTUNECOMPANYNAME.TXT and send it to your sales person.
Once we generate the key, it will be in the PolicyPak Portal. Download the key and install it using these directions: https://kb.policypak.com/kb/article/1080-how-to-install-universal-licenses-for-new-customers-via-gpo-sccm-or-mdm/
Then follow these directions to get started with PolicyPak and Intune (making sure to follow the “Walk Before You Run” video):https://kb.policypak.com/kb/section/196/
When you enroll machines into your MDM, you do so with a UPN name. Start out by noting which UPN name you use *@fabrikam.com or whatever yours is. We recommend you take a screenshot of this page from an enrolled Windows 10 machine, then continue.
Once we generate the key, it will be in the PolicyPak Portal. Download the key and install it using these directions: https://kb.policypak.com/kb/article/1080-how-to-install-universal-licenses-for-new-customers-via-gpo-sccm-or-mdm/
Then follow these directions to get started with PolicyPak and your MDM service (making sure to follow the “Walk Before You Run” video):https://kb.policypak.com/kb/section/196/