An Intune Deployment template controls who gets an app, how it is named in Intune, which devices qualify, and how new versions are rolled out. Set it up once and reuse it for every app.
Start with the interactive demo to see how to create and set up an Intune Deployment template, step by step:
Or follow the guide below for detailed steps and screenshots of each setting.
How Updates Work
Each time you publish an app, Agentic Packr creates two Win32 apps in Intune:
| App | Purpose |
|---|---|
|
Install app e.g., 7-Zip-x64-26.04 |
Installs the app, makes it available in Company Portal, or removes it for the groups you target. |
|
Update-only app e.g., [Update Only]-7-Zip-x64-26.04 |
Same package, but only applies to devices that already have the app. Other devices report "Not applicable", so it is safe to assign to All devices. |
When a new version appears in the catalog, Agentic Packr waits a set number of days, then publishes a new install app that supersedes the old one, along with a new update-only app. The old update-only app is retired. A few previous install apps are kept so you can roll back if needed.
Create the Template
-
Go to Settings → Templates, open the Intune Deployment tab, and click New template.
-
General: enter a name and description.
-
Metadata: set how apps appear in Intune and Company Portal.
- Owner, Developer, Information URL, Privacy URL, Notes: shown on the app's Properties page in Intune. Developer is prefilled with Splashtop Agentic Packr; keep it so the apps it publishes are easy to recognize in Intune.
- Category: Company Portal category, taken from your Intune tenant.
- Featured app: shows the app on the Company Portal home page.
- Allow available uninstallation: adds an Uninstall button in Company Portal.
- The app name, publisher, and description come from each package, not the template.
-
Naming patterns: set how Intune objects are named. Tokens: {AppName}, {Publisher}, {Arch}, {Version}. Any other text (e.g., a prefix like CF-) is kept.
- Application name default: {AppName}-{Arch}-{Version}
- Update-only name default: [Update Only]-{AppName}-{Arch}-{Version}
-
Advanced: set requirements and return codes.
- OS architecture: x64 and ARM64 by default.
- Minimum OS: required by Intune; default is Windows 10 1607. Choose the oldest build you support.
- Hardware: leave empty for no requirement (entering 0 sets a requirement of zero).
- Additional requirement rules: file, registry, or script checks.
- Device restart behavior: keep No specific action; the User Experience template handles restarts.
- Return codes: 0 and 1707 = success, 3010 = soft reboot, 1641 = hard reboot, 1618 = retry. Anything else is a failure.
-
Install: for each assignment type (Required, Available for enrolled devices, and Uninstall), add a row with + Add group, + Add all users, or + Add all devices. For a group row, set the Group source: Existing group (shared) picks an Entra group; Create a group for this app creates one at publish time.
- New groups use the pattern {AppName}-{Arch}-{Intent} (e.g., 7-Zip-x64-Required) and are created empty.
- Settings on each row: notifications, time zone, availability, deadline, restart grace period (leave disabled), and delivery optimization.
- Skip install: turn on to patch existing installs only, without installing on new devices.
Tip: We recommend assigning Required to a new group per app, Available to All users, and Uninstall to a new group per app.
-
Update-only app: configure patching of existing installs.
- Deploy an update-only app: keep on (default).
- Which installs does it patch: Installs from Agentic Packr (only its own installs) or Any install of this app (also manual and OEM installs; recommended).
- Assignment: All devices, Required (default).
-
Automated updates: these apply to the next version, not the current deployment.
- Follow new versions: automatically repackage and publish new catalog versions.
- Wait before publishing: default is 7 days (range 0 to 90).
- Versions to keep in Intune: 3 is recommended for rollback.
- Supersede the previous version: Let the installer update it (in place) or Uninstall it first.
- Auto-update Company Portal installs: always on; users get the new version within about 8 to 16 hours.
-
Overview: review requirements, names, assignments (targets marked "new" are created at publish), and update policy. Click Save template.
-
Turn on Default so the template is pre-selected when you deploy.