The FlexApp Packaging Automation framework is made up of a Primary Packaging Manager and one or more Packaging Capture Agents that run the packaging jobs and place the resulting packages in the specified storage locations. Capture Agent VM must be 64-bit architecture.
Primary Packaging Manager
| Component | Minimum Requirements |
|---|---|
| Virtual Machines | 1 VM to be used as the Primary Packaging Manager. The ProfileUnity Management Console can be used as the Primary Packaging Manager or a new VM can be created. |
| VM OS Support | Windows 10/11 or Windows Server 2016/2019/2022/2025 |
| VM vCPU | 2 vCPU |
| VM Memory | 4 GB |
| VM Storage | 1 GB free on C: |
| Prerequisites | Microsoft® .NET 8.0 is automatically installed |
| Network and Firewall | Primary Packaging Manager listens on TCP/9075 and connects to TCP/9074 on Packaging Capture Agents. |
Packaging Capture Agents
| Component | Minimum Requirements |
|---|---|
| Virtual Machines | 1+ 64-bit VM(s) to be used as Packaging Capture Agents *Liquidware recommends 3+ VMs for large batch jobs and 2+ for linear/DEVOPS/one-off processing to maintain redundancy. |
| VM OS Support | Windows 10/11 or Windows Server 2016/2019/2022/2025 |
| VM vCPU | 4+ vCPU |
| VM Memory | 8+ GB |
| VM Storage | 40 GB free on C: |
| VM Free Space |
Free disk space is needed locally, usually C:, on each Packaging Capture Agent VM for capturing application installations. It is recommended to have at least double what you think you will ever need for your largest capture. |
| Prerequisites | Microsoft® .NET 8.0 is automatically installed. |
| Network and Firewall | Packaging Capture Agents connect to TCP/9075 on Primary Packaging Manager. |
Network or Cloud Storage
A network file share or a cloud location used to store new packages is required. In addition, storage for the installer EXEs and MSIs that will be accessed by the Capture Agents will be needed.
Silent Install Requirement
Applications are required to install silently due to the headless nature of FPA. Most application installers require the use of flags on the CLI to indicate a silent install. Test each installer’s silent install commands manually prior to using in a packaging job. There must be no user-interaction involved during install. Prompts will hang capture until the timeout.
Multi-Administrator Package Creation
When multiple package administrators are sending packaging jobs to the same Primary Packaging Manager it is recommended that any PathUsername or InstallerUsername be a service account created for this purpose and stored in the DefaultsJSON file. As a result, the service account will handle all file operations on the network share preventing the need for each admin to use their own credentials.
