Skip to main content

Prerequisites & compatibility

This article consolidates the hardware/software prerequisites, OS/SQL/IIS/.NET compatibility, supported browsers and devices, as well as network dependencies required to deploy Hamilton Apps (Visitor / Meeting / Deskbooking) within your own infrastructure

Updated over 2 weeks ago

1) Application & database servers

Roles: 1 WEB/API (IIS) server and 1 SQL Server server (they can be shared on the same host or deployed separately).

Minimum capacity (standard project guidance)

  • CPU/RAM: 2 vCPU / 8 GB RAM.

  • Storage: 100 GB for OS & application (SSD recommended) + SQL volumes (Data/Log) according to expected volumes.

Operating systems

  • Windows Server 2019 (64 bits), 2022 (64 bits)

IIS & .NET

  • IIS 10 with .NET 3.5 and .NET 4.8

DBMS — Microsoft SQL Server

  • SQL Server 2019, 2022

  • Driver: Microsoft OLE DB Driver for SQL Server 18.2+.

Required permissions: a local administrator installation account (IIS) and database creation rights on the target SQL Server instance for running the installation script.


2) Client workstations & browsers

  • Standard workstations: full web access via modern browsers (Edge/Chrome/Firefox/Safari).

  • Reception workstations (Visitor): a dedicated utility (ClickOnce) for workstation identification and entry/exit traceability.

  • Minimum resolution: 1024×768.


3) Devices & mobility (optional)

iPad (Visitor)

  • Use cases: pre-registration / self check-in / signature / parcels.

  • iOS 15+; kiosk mode recommended via an MDM.

  • Network: HTTPS to the API (port 443, configurable).

Room display tablets (Meeting)

  • Supported models: Philipps 10BDL5051T, QBIC TD‑1070 / TD‑1070 Pro.

  • Power: PoE recommended. Network: Wi‑Fi/PoE over HTTPS 443 to the API.

Badge/label printing (Visitor)

  • Brother QL‑820NWB (kiosk/reception), Evolis Zenius, Evolis Tatto RW2, Zebra ZD521T.

  • Connectivity: USB / network / Wi‑Fi depending on the model.


4) Network & security (summary)

  • User access: HTTPS 443 to the WEB/API server.

  • Directory/SSO: LDAPS recommended (port 636) or SAML v2 / ADFS.

  • Email: SMTP access to the organization’s mail relay.

  • Optional integrations: Microsoft Graph or Exchange (Meeting), access control, Guest Wi‑Fi.

  • TLS 1.2+ on the front end; certificates from a trusted CA; enable HSTS on the reverse proxy if applicable.


5) Accounts & secrets

  • Service accounts: SQL access, directory read, SMTP sending, SSO/Graph, access-control connectors.

  • Use an enterprise vault to store secrets, with planned rotation and access logging.


6) Installation prerequisites (to prepare)

  • Server: OS up to date, IIS + required roles, .NET 3.5/4.8, SQL OLE DB 18.2+.

  • SQL: reachable instance, default collation, a dbcreator account for deployment.

  • Certificates: TLS for the portal FQDN (full chain); LDAPS if used.

  • Network: required openings (HTTPS, SMTP, LDAPS, integrations).

  • Accounts: dedicated services (least privilege) and an updated vault.


7) Validation checklist

  • HTTPS access to the portal from the LAN.

  • SQL and LDAP/SSO connectivity verified.

  • SMTP sending successful (notification test).

  • iPads/room screens can reach the API on 443.

  • Badge/label printing tested (model & queue).

  • SQL backups and restore points ready.

Did this answer your question?