Skip to content

System Requirements

Hard Drive and Storage

  • SATA Hard drive (SSD recommended).
  • 10GB Minimum Free Hard Disk Space (Dependant on data workloads).

Processor

  • Intel i5 Quad-core 2.6GHz or Higher recommended.

Memory

  • 8GB RAM Minimum (16GB RAM Recommended).

Operating System

  • Microsoft® Windows® 2022 Server Standard Edition and Data Centre Editions.
  • Microsoft® Windows® 2025 Server Standard Edition and Data Centre Editions.
  • Microsoft® Windows 10 Pro/Enterprise (32 and 64 bit)*.
  • Microsoft® Windows 11 Pro/Enterprise.

Important

  • Only customers that have the Windows 10 ESU (Extended Security Updates) package should use Zynk with Windows 10. For security reasons we do not recommend running any business critical applications on Windows "Home" editions

Access Rights

  • You will require full Administrative rights to install any software.
  • Any workflows that pick up local files not created by the integration will require full access to the data path where those files are stored.
  • The user Zynk is set to run as requires "Log on as a batch job" to be enabled.

Additional Notes

  • You will require an Activation key to use Zynk, if you are not an existing customer please Download a trial of Zynk.
  • If you are integrating with Sage 50, Sage 200 or ACT!, an instance of that software will need to be installed on the same machine that Zynk is installed on.
  • Zynk requires the .Net Framework version 4.8, which may need to be installed during the installation process.
  • Older versions of Zynk use SQL Server Compact Edition 4.0 which may need to be downloaded and installed during the installation process.

  • Zynk will run on most virtual machines, though we are aware of some minor issues with Oracle VirtualBox.

  • We strongly discourage the use of Zynk on laptop computers. This is due to the increased risk of issues occurring from the machine not being correctly shutdown or losing power during a workflow run. If you choose to install Zynk on a laptop machine, we strongly recommend only running the workflow manually to avoid issues with data loss.