Frequently Asked Questions

Who is this software for?

People/businesses/MSPs packaging Win32 applications for MS Intune will benefit from Pckgr. Pckgr deploys vigorously tested applications at extreme speeds and therefore will benefit people looking to speed up the time taken to package applications. Building a library of 30 applications will require probably less than 5 minutes work, then time to let the applications upload to Intune.

Have the applications been tested?

Yes, applications are tested with Microsoft's Smart Screening, Static Analysis, Anti-Virus testing and Cryptographic Verification.

The Pckgr team then tests the applications' functionality by deploying the apps onto new windows 10/11 devices.

The applications you see in the Pckgr library will only be available if they have passed all these tests.

What do i do if my app fails deployment?

Delete the application and try to deploy again. If the app fails deployment, it is most likely due to a system error on MEM's side as a result of uploading multiple application simultaneously. We are working out ways to prevent this happening

Can MSPs use this Intune packaging tool?

Yes, MSPs can use this software just as anyone else would. We have made it simple for MSP technicians to easily swap between their tenants.

What format are the applications in?

The applications are in Win 32 format and are sourced from Microsoft Winget.

Can I use this on the computer as well as mobile?

Yes, this is a web application and can be used anywhere.

Auto-updates explained

You will not have to do anything when a new update is released. The applications will be updated automatically and will silently appear in your Intune library.

Pckgr pushes the first initial package to Intune and then captures the App ID. Each time Pckgr finds an update, it uses the Graph API to update certain fields of that package (like the version param in the PowerShell script). This means that you will only have one instance of each application. Pckgr uses Version Params so the scripts will only install the version that it specified. You will also see fields such as the application name and version update to reflect the new version accordingly.

Pckgr was designed to allow the customer to make changes to the initial deployment without them be overwritten during an auto update. To summarize, an app's settings will not be reset after Pckgr triggers an auto update.

Can you help me prevent repackaging a custom app? / Can I bring my own application to prevent repackaging?

You can upload your custom application to your private library then clone its configuration directly from Intune.

Now that the app is in Pckgr, you can deploy it again without having to re-package. This will save the user from repackaging the same application multiple times.

How can I report an issue?

Please bring it to our attention by emailing us or using the chat bot, we will work to resolve the issue as soon as possible.

We would love to hear about any issues or questions you have.

Why doesn't your library have all of Winget's apps?

Although Winget has a rigorous testing process for applications to just become available, sometimes some application deficiencies still leak through! Pckgr staff check each application before it becomes available in the Pckgr library and therefore Pckgr chose to not allow every Winget application to be available in case of failures.

Pckgr is effectively testing the Winget Apps to ensure users are getting the cream of the crop to prevent any packaging or deployment issues.

The most used applications have been added to the Pckgr library with plans to greatly increase the application library.

The app I want isn't in the Pckgr Library. Can you please add this application?

Please recommend applications you would like to see in the Pckgr Library via our chatbot.

With your help, we will increase the library to host applications which you find most useful.