Prerequisites
What has to be ready before installation: a host, a database, read access to inventory, a service account, and network reachability.
Updated
This list is for whoever prepares the environment before installation day. If everything here is ready, the installation itself is short.
Host
One machine, physical or virtual. In production it is preferable that the application server and the database do not share a machine, though it is not required.
[VERIFY] — exact resource requirements (CPU, memory, disk) depend on inventory size and are agreed with the deployment team.
Database
A reachable SQL Server instance with a dedicated database for the application.
- The application account needs read and write on that database only.
- Inventory sources require read access only.
Service account
A domain account the application runs as. It is needed for three things: reading the corporate directory, sending mail through the relay, and authenticated access to internal interfaces that require domain authentication.
A local or system account will not work against an interface requiring domain authentication, and that failure appears as a runtime authorisation error rather than an installation error.
Network reachability
| Target | For |
|---|---|
| Application database | Read and write |
| Inventory sources | Read |
| Corporate directory | Contact search, group checks |
| Mail relay | Invitations and notifications |
No outbound internet access is required. If your policy blocks egress entirely, the system works.
A mailbox or address the invitations are sent from. Worth deciding in advance, because it appears on every invitation issued and changing it later changes the organiser identity on existing events.
Edit this page
This page is the file content/docs/en/v1/install/prerequisites.mdx