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.
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.