Pckgr
  • About Pckgr
    • Intro: What is Pckgr?
      • How Package Updates Work
      • PckgrBot
      • Homage to Winget
    • Applications Available
      • Request Application
    • Security of Pckgr
      • Microsoft Single Sign On
    • Pckgr Pricing Model
  • Getting Started
    • Setting up your Dashboard
      • Signing Up
      • Managing Companies
      • Connecting Tenants
      • Adding Team Members
    • Creating Deployments
      • Application Library
        • Detect Applications from Intune with Pckgr
        • Application Status Tag
      • Repositories
        • Winget
        • Private Repository
          • Upgrading an Application to the Private Repository
        • MacOS
      • Deployment Settings
      • Application Management
  • Extra Features
    • Custom Applications
    • Cloning Intune Policies
  • INTEGRATIONS
    • Company Portal
    • Autopilot
  • Troubleshooting
    • Install Logs
    • Error Codes
    • Winget Issues
      • Winget Pre-Install
      • Winget CDN Issue
      • Repair Winget with PowerShell
    • Applications that Require to be Closed Before Updating
    • Frequently Asked Questions
  • SUPPORT
    • Pckgr ChatBot
    • Support Email
    • Delete your account
  • Policies
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  1. INTEGRATIONS

Company Portal

Managing applications with the Company Portal

PreviousCloning Intune PoliciesNextAutopilot

Last updated 2 months ago

For customers wanting to use the Company Portal, you might be finding that your users are installing an application only to find that once a new version is released they are now outdated.

Here is where our Company Deployment strategy comes in!

  1. Start by going to the Application page and creating two deployments of an application.

    Here we will deploy Firefox Twice (Make sure to select "All Apps" from the drop down so you can make multiple deployments)

  2. Deploy one of these apps with "Update Only" turned off and one with "Update Only" turned on.

  3. Once Deployment is complete, head over to Intune to make your group deployments

  4. Select normal deployment (Update Only turned off) and edit the assignments. Select either a group or all users for the Available category. This will be your Application that shows in the Company Portal. Save Changes.

  5. Select the second deployment (Update Only turned on), edit the Assignments and set the Required field to all users or devices. This will act as an updating package that will deploy an update when the application is detected on the device. Keep in mind this will also target devices which installed the application without the Company Portal.

  6. Pckgr will then continue to deploy updates to these packages

Flow

  1. User downloads and installs application from the Company Portal (This will always be the latest version)

  2. When the application updates, the users device will be targeted by the second deployment and will force the application to update

  3. The detection from the application in the Company Portal will still show as up to date.