In Release Notes Q3, we’re introducing several exciting updates that enhance your application packaging and deployment workflows with more granular control, improved automation, and streamlined connector management.
Customizer: Per-Application Settings and Redesigned Edit Page
The Apptimized Customizer now lets you tailor settings per application within a project. From installation parameters to PowerShell automation, you control how each app behaves while keeping organizational standards intact.
Each app now opens in a dedicated edit page instead of a modal, displaying all configuration layers at a glance – including the newly added settings listed below.
- Disable auto-update
- Remove desktop shortcuts
- Define custom detection methods
- Adjust installation parameters
- Add PowerShell scripts
- Upload additional files directly through the interface.
This update streamlines packaging workflows with greater transparency and automation, eliminating the need for duplicate projects or manual edits.
PSADT v4 Integration Across Apptimized Packaging
Self Service now includes a PSADT v4 template, integrating the latest PowerShell App Deployment Toolkit directly into your process. PSADT v4 introduces cleaner scripting logic, simplified configuration, and updated ADT-prefixed functions. It also brings a modern configuration format that makes deployments more reliable and easier to maintain. As part of this update, APE now uses the PSADT v4 template when preparing packages, including generating the corresponding installation and uninstallation commands used for wrapping PSADT-based packages into Intunewin.
Factory has also migrated to PSADT v4, bringing the same improvements into the core packaging workflow. Customers using default guidelines are fully migrated, while customers with individual packaging requirements are partially migrated based on their custom instructions. With PSADT v4 now powering Factory, packaged applications benefit from a more secure, consistent, and maintainable foundation – giving teams a clearer, more efficient way to build and customize application packages at scale.
Connector Improvements: Intune & SCCM
Intune Connector Updates
This quarter brings a set of improvements that make Intune integrations faster and easier to manage – especially for customers operating large environments.
New Intune Templates Page
Template management now mirrors the familiar Assignment Templates workflow. Templates have been moved to a dedicated page, offering clearer navigation and more working space for editing and reviewing configurations.
The updated interface now includes
- Search and pagination for easier management of large template lists
- Clone option to quickly duplicate existing templates
- A cleaner table layout for template name, display name, and status
Improved Assignment Template Table
The Assignment Templates section within Intune environments has been enhanced with:
- Search and pagination for easier navigation
- Alphabetical sorting by default for more predictable behavior
These changes make it simpler to manage and reuse templates across multiple Intune-connected environments.
SCCM Connector Improvements
Ensuring reliable deployments remains a key focus this quarter for SCCM connector. It now includes path length validation for packaged applications.
Path Length Validation
The connector now checks the full file path that SCCM will use – combining the Content library location with the detected path to the executable inside the package. If the combined path exceeds 255 characters, it is highlighted in amber and accompanied by a warning – helping prevent issues during SCCM deployment or distribution point processing.
To improve accuracy, the connector also analyzes the archive to locate the actual executable file and validate the correct final path inside the package.
Packaging Pitfalls Series
To support teams in building more reliable and predictable application packages, we continue expanding the Apptimized Packaging Pitfalls blog series – a collection of practical guides that highlight common packaging issues and how to avoid them.
The latest blog post – Packaging Pitfalls Part 7: How to Avoid Forced Reboot After Installation – focuses on one of the most disruptive issues in enterprise deployments. The article explains why unexpected reboots occur and how to detect reboot triggers in installers. It also highlights packaging practices that help prevent service interruptions for end users.
Final Thoughts
This year, Apptimized Care has taken a major leap forward. From introducing Customizer at the start of the year, to adding multilingual packaging in Q2, and now bringing per-application settings in Q3, Care is becoming one of the most flexible and customizable patch-management solutions on the market. With continuous improvements to the Intune and SCCM connectors – both supporting automated push workflows – Care gives you more control and consistency. These enhancements make it easier to adapt packages to your environment with almost no manual effort.
As we wrap up our Release Notes Q3, make sure to try the new features in your Portal and check out the Packaging Pitfalls entry on the Apptimized blog to stay ahead of common packaging challenges. Our team remains committed to helping you deliver secure, reliable, and consistent applications at scale. And if you’re new to Apptimized, book a demo to see how these capabilities can streamline your application management from day one.
