Help
FAQFAQCommunityCommunityUser GuideUser GuideContactContactCustomer InfoCustomer Info

Best Practices for Application Packaging: Integrating PacKit into Your Workflow

Navigating the complexities of application packaging can be daunting, especially with the variety of formats, deployment requirements, and customization steps.

To streamline this process, let’s explore best practices for packaging and deployment, using a complete ecosystem approach that integrates PacKit. With Advanced Installer and PacKit, you can optimize your workflow from repackaging EXEs to deploying with Intune or MECM, making application packaging more efficient and secure.

ImportantPacKit is a centralized, Windows-based tool for post-packaging configuration and deployment. Designed for IT professionals, it automates tasks like generating Intunewin files, integrating with PSAppDeployToolkit, and providing one-click deployment to Intune and MECM.

The Application Packaging Workflow

The packaging workflow can be broken down into three main components:

  • Vendor Package - The installer provided by the software vendor, whether in EXE or MSI/MSIX format.
  • Advanced Installer Customization Step - Repackaging or modifying the installer to suit deployment needs.
  • PacKit Customization Step - Wrapping or further preparing the package for specific deployment environments.

NoteThis ecosystem of tools—Advanced Installer’s Repackager, the MSI/MSIX Editor, and PacKit—works together to simplify complex tasks, minimize manual effort, and enhance control over the deployment process.

Ai best practice

Start with the Application: What Type of Installer Do You Have?

The process begins by analyzing the application you need to deploy. The path forward depends on the type of installer provided by the vendor:

  • EXE Setup with Silent Switches: If the installer is an EXE with silent installation support, you can skip directly to deployment steps or wrap it in a PowerShell script for additional automation.
  • Non-Silent EXE Setup: If the EXE doesn’t support silent installation, it will need repackaging.
  • Vendor MSI/MSIX: If the installer is an MSI or MSIX, you can use it as is or modify it if customization is required.

Handling Non-Silent EXE Setups with Repackaging

For installers that lack silent switches, repackaging is necessary. Advanced Installer’s Repackager tool can convert the EXE setup into an MSI or MSIX format, making it compatible with silent deployment and easier to manage in enterprise environments.

Why Repackage?

  • Standardization: Convert non-standard setups into MSI/MSIX packages.
  • Control: Add configurations and custom actions that the original installer may not support.
  • Automation: Easily deploy packages using deployment tools like Intune or MECM once they are standardized.

Once repackaged, you’ll have the option of deploying it as an MSI or MSIX, depending on your infrastructure needs and the application’s compatibility.

Using the MSI/MSIX Editor for Quick Customizations

If you’re working with a Vendor MSI or MSIX that’s close to meeting your deployment requirements, the MSI/MSIX Editor can handle minor adjustments without full repackaging. This tool allows you to edit MSI/MSIX files, adding or modifying properties, creating transforms (MST files), and ensuring that the package meets your organization’s standards.

When to Use the MSI/MSIX Editor?

  • Minor Customizations: For tasks like adding custom actions, setting default properties, or configuring shortcuts.
  • Transform Creation: For managing different configurations through MST files without altering the original installer.
  • Patch Creation: Apply patches to update MSI files without repackaging.

Final Steps with PacKit: Wrapping, Intune Integration, and Deployment

Once your package is ready, PacKit takes center stage by handling the final deployment tasks:

  • Wrap with PowerShell App Deployment Toolkit (PSADT): PacKit can wrap the MSI/MSIX or EXE into a PowerShell deployment script using PSADT. This allows you to add pre-installation checks, custom logging, error handling, and more.
  • Generate Intunewin Files: PacKit simplifies creating .intunewin files for Intune deployments. This is essential if your organization uses Intune to manage applications.
  • Upload to Intune/MECM: With direct upload options, PacKit can send your packaged application straight to Intune or MECM, saving time and reducing the risk of manual errors during the upload process.

Why Use PacKit for Deployment?

  • Automation: PacKit streamlines the wrapping and uploading process, reducing repetitive tasks.
  • Customizable Deployment: With PSADT integration, you can add custom deployment actions tailored to your environment.
  • Error Reduction: Automated steps reduce the likelihood of human error, making deployments more secure and reliable.

Conclusion: A Streamlined Ecosystem for Application Packaging

By following these best practices and integrating PacKit into your application packaging workflow, you can make deployments more efficient, consistent, and secure. This ecosystem of tools—Advanced Installer’s Repackager, the MSI/MSIX Editor, and PacKit—works together to simplify complex tasks, minimize manual effort, and enhance control over the deployment process.

With the right tools and practices in place, you can tackle any application packaging scenario, from handling non-silent EXEs to managing large-scale deployments with Intune or MECM.