Action1 5 Documentation 5 Prepare Multi-File Custom Packages

Prepare Multi-File Custom Packages

In order to streamline app distribution and delivery, Action1 enables you to upload custom packages consisting of multiple files and deploy them through the Action1 App Store. For example, you can create a package for Microsoft Office apps or development tools such as java distributions, node.js. Once this package is uploaded to Action1 Cloud, you will be able to deploy it as any regular package. Managed endpoints will download the package data using our cloud file-sharing technology, which works by sharing chunks of data across multiple computers. Let’s say you have 100 endpoints and need to download a 2GB package. Each endpoint would download approximately 20 MB and share it with other managed endpoint endpoints. This way Internet traffic usage is minimized and download reliability is accomplished.

What kind of packages can you create? 

You can create ZIP packages with:
  • EXE and other files such as configurations
  • MSI with MST (transform) files that customize your installation, for example, add a license code or create a preconfigured profile. For custom transform (*.MST) files, consider using the ORCA tool.

Prepare a ZIP Package

  1. Download 7-Zip 19.0.
  2. Create a work folder, such as C:\\work.
  3. Copy your files to this folder. Make sure to include a setup file (EXE or MSI). Alongside, add configuration files, etc.
  4. Select all files in the folder and specify Add to archive.

 Next Steps

  1. Add a new package to the App Store. For more information on creating new apps, see Add Custom Packages to App Store.
  2. Add a version and upload the ZIP you’ve generated.
    • For EXE-based packages, make sure to specify the EXE name in silent switches. For example,  setup.exe /q. Use quotes if the setup name contains spaces, e.g., “my setup.exe” /q.
    • For MSI-based packages, add an MSI name in properties as a first parameter (e.g., “my setup.msi” param1=value1), embrace file names that contain spaces in quotes. To enforce a transform file (*.MST), specify setup.msi TRANSFORMS=transforms.mst.
  3. Deploy the package to your managed endpoints. For detailed instructions on how to roll out packages, see Deploy Software with App Store.

cloud patch management solutions action1

MSP Solution

Centralize endpoint management and boost efficiency of IT service delivery.

automated server patch management action compliance

Patch Management

Identify and deploy missing OS and third-party software updates.

cloud software deployment tools windows

Software Deployment

Distribute software and updates across managed endpoints.

software distribution tools software inventory action1

IT Asset Inventory

Keep a detailed inventory and manage hardware and software assets.

web client remote desktop

Remote Desktop

Support users via seamless remote desktop connection.

web based rdp client

Unattended Access

Provide administrative support and manage remote devices.

automated patch management action1

Endpoint Management

Run PowerShell, custom scripts, reboot computers and restart services.

API integrations action1


Integrate Action1 RMM to your IT ecosystem.

computer inventory tool for compliance

Reports and Alerts

Conduct endpoint security audits with comprehensive reporting.