Pckgr
  • About Pckgr
    • Intro: What is Pckgr?
      • How Package Updates Work
    • Applications Available
      • Request Application
    • Security of Pckgr
      • Microsoft Single Sign On
    • Pckgr Pricing Model
    • Feature Releases and Roadmap
      • Q1 2025 New Features Newsletter
  • 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
        • Private Repository
          • Upgrading a Winget Application to the Private Repository
        • MacOS
      • Deployment Settings
      • Application Management
  • Extra Features
    • Custom Applications
    • Cloning Intune Policies
    • Application Rollbacks
  • INTEGRATIONS
    • Company Portal
      • Windows Applications
      • MacOS Applications
    • Autopilot
    • Microsoft 365
  • Troubleshooting
    • Troubleshooting Steps
    • Install Logs
    • Error Codes
    • 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
  • Deploying Windows Applications to the Company Portal
  • Overview
  • How It Works
  • Deployment Process — Step by Step
  • Update Flow Summary
  • Key Benefits
  1. INTEGRATIONS
  2. Company Portal

Windows Applications

Integrate your Windows Application management with Company Portal with Pckgr

Deploying Windows Applications to the Company Portal

Pckgr allows Windows applications to be made available in the Company Portal, enabling end users to install approved applications on-demand while still maintaining full update management behind the scenes. This guide outlines the process in detail, combining initial deployment with ongoing updates using Pckgr’s dual-deployment model.


Overview

By utilizing a combination of standard and Update Only deployments, you can:

  • Present the latest version of any Windows application to your users inside the Company Portal.

  • Automatically keep installed applications updated via Pckgr-managed update deployments.

  • Avoid reinstallation or redundant updates on devices that haven't installed the application.


How It Works

You will create two separate deployments for each application:

Deployment Type
Purpose

Standard Deployment (Company Portal)

Publishes the application into Intune, allowing assignment as Available in the Company Portal.

Update Only Deployment

Ensures ongoing automatic updates for devices where the application is installed.

This structure allows Pckgr to control versioning and patch management while giving your users full self-service flexibility.


Deployment Process — Step by Step

Step 1 — Create Two Deployments in Pckgr

  1. Open your Application Library in the Pckgr Dashboard.

  2. Locate the application you wish to deploy (e.g., Firefox).

  3. Click the plus ( + ) button twice to add two instances of the application into your Application Library.

You should now have two separate deployment instances for the same application.


Step 2 — Configure Deployment Types

  • Deployment 1 (Standard Deployment):

    • Leave "Update Only" OFF.

    • This will act as your base deployment for Company Portal.

  • Deployment 2 (Update Only Deployment):

    • Toggle "Update Only" ON.

    • This deployment will manage future updates automatically.

The Update Only deployment adds a requirement script to ensure it only applies to devices where the app is already installed.


Step 3 — Assign Applications in Intune

Once both deployments show as Success in Pckgr:

  1. Log into your Microsoft Intune Admin Center.

  2. Navigate to Apps > Windows > All Apps.

  3. Locate both deployments by name.

Assign the Standard Deployment (Company Portal):

  • Edit Assignments.

  • Assign to Available for users or groups.

  • This makes the application visible in the Company Portal for self-service installs.

  • Save changes.

Assign the Update Only Deployment (Updates):

  • Edit Assignments.

  • Assign to Required for users or devices.

  • This ensures any installed version of the app receives ongoing updates.

  • Save changes.

Note: The Update Only deployment will apply updates even for devices where the app was installed outside of the Company Portal, as long as detection identifies the app.


Update Flow Summary

Scenario
Behavior

User installs from Company Portal

The latest version is installed at time of deployment.

Application version is updated

The Update Only deployment applies the new version automatically.

Device never installs app

No update is applied (Update Only deployment is skipped).


Key Benefits

  • Seamless self-service installs for end users.

  • Full version control and patch management via Pckgr.

  • Efficient update targeting — only devices with the application installed are updated.

  • No unnecessary reinstallations or conflicts.

PreviousCompany PortalNextMacOS Applications

Last updated 1 day ago

App available in Company portal

Check out our Blog post!

Company Portal and Pckgr