Branch and Central Deployment: Which Component Goes Where?
Technical teams preparing for deployment always ask the same question: which component goes where, and what is expected on each machine? This article separates the branch side from the central side at requirements level.
The branch side: identical in both editions
The branch runs the queue management software along with kiosk, counter terminal, indicator and call screen components. Their requirements are the same in the Single License and Enterprise editions: Windows 10 or later, at least 4 GB memory (16 GB recommended), a .NET 10 foundation and the required ports configured in the local network.
The central side: Enterprise edition only
In the Enterprise edition, NGQ Manager is installed at the centre and branches are defined from there. Central requirements differ clearly from the branch:
- Operating system: Windows Server 2019, 2022 or 2025
- Database: Microsoft SQL Server 2019 Standard or higher
- Web server: IIS 6 or higher
- Application foundation: .NET 10
For testing and pilot installations, the central software can also run on a Windows 10 or later PC using self-hosting (runs as an executable and serves as a web server). Above 10 branches, moving to an IIS server is recommended.
Pre-deployment checklist
- Are the required ports and permissions configured in the local network?
- Are your corporate certificates ready for HTTPS? Branch software can use the same certificate.
- Is the branch server sufficient in terms of memory and disk space?
- Is the number of terminals settled? During branch setup, device sets can be created automatically from the terminal count.
Going live
Installation is carried out by technical staff, with the required files and libraries supplied as a package. Once definitions are complete, changes made at the centre are applied to branches every 5 seconds by default.
With Single License, deployment ends within the branch. The Enterprise edition has two layers: the centre (NGQ Manager) and the branch. Plan the requirements of both layers separately.
Related articles
Let's plan your scenario together
We will determine the right edition and hardware together, based on your branch count and integration needs.