Install Erde with the MSI

Run Erde-Setup.msi to deploy the Erde server to a Windows machine. The installer copies the application files, configures the host (Windows Service or Internet Information Services (IIS)), opens a firewall port, and opens the browser to the first-run setup wizard. It collects only deployment settings — the database, admin account, and other application settings are configured later in the wizard.

Before you start

• Role required: You must be a local administrator on the target Windows server. The MSI installs per-machine and writes services, IIS sites, and firewall rules.
• Prerequisites: Confirm the machine meets the deployment system requirements. In particular, install the .NET 10 Hosting Bundle first. For IIS deployments, enable IIS before installing the Hosting Bundle.

Steps

1. Copy Erde-Setup.msi to the target server and run it. The MSI opens the Welcome screen; select Next.

2. On the Deployment Configuration screen, choose how Erde is hosted and which port it listens on:

   Setting	What to choose
   Hosting shape	IIS Website (recommended for multi-office and field deployments) or Windows Service (small firm, 1–5 users, single office). The default is IIS Website. For the tradeoffs, see Windows Service vs. IIS.
   HTTP Port	The TCP port Erde listens on. The default is 5000. Make sure no other service uses this port.

3. Select Next. If you chose IIS Website but the ASP.NET Core Module (ANCM) is not detected, the installer shows a Missing Prerequisite dialog. Install the .NET 10 Hosting Bundle and run the installer again, or go back and choose Windows Service.

4. On the Verify Ready screen, select Install and approve the elevation prompt. The installer then:

   • Installs the application to C:\Program Files\Erde\ (the server in api\, the web client in client\).
   • Creates the file-storage folder at C:\ProgramData\Erde\storage\.
   • Configures your chosen host — the Erde Windows Service (started automatically) or the Erde IIS site and app pool.
   • Adds inbound firewall rules Erde HTTP (Domain) and Erde HTTP (Private) on the chosen TCP port. The public network profile is excluded by default. The rules therefore apply only while the server's network connection is classified as Domain or Private — if the connection is on the Public profile, Windows refuses LAN connections to Erde until you reclassify the connection (Set-NetConnectionProfile -NetworkCategory Private) or add a firewall rule for the Public profile.
   • Creates Desktop and Start Menu shortcuts to http://localhost:<port>.

5. Select Finish. The installer opens your browser to http://localhost:<port>/setup. Because no appsettings.Production.json exists yet, the server starts in setup mode and serves the first-run wizard.

Result

Erde is installed and running on the chosen port, but not yet configured. The browser shows the first-run setup wizard at /setup. The application is not usable until you complete the wizard, which collects the database connection and admin account and writes the production configuration.

Continue with first-run setup to connect a database, create the admin account, and start the server in normal mode.

Troubleshooting

Symptom	Cause	Resolution
Installer stops with "The .NET 10 Hosting Bundle is required to run Erde."	The .NET runtime was not found on the machine.	Install the .NET 10 Hosting Bundle (under the Runtime section), then run the MSI again.
Missing Prerequisite dialog appears after selecting Next with IIS Website chosen.	IIS mode needs the ASP.NET Core Module (ANCM v2), which was not detected.	Install the .NET 10 Hosting Bundle, or choose Windows Service instead. If IIS was enabled after the Hosting Bundle, run a repair install of the Hosting Bundle to register ANCM with IIS.
Browser opens but the page does not load on the chosen port.	Another service is using the port, or the firewall blocks it.	Choose a free HTTP Port; the firewall opens only the Domain and Private profiles, not Public.
Erde works on the server itself but other machines on the LAN cannot connect.	The server's network connection is classified as Public, so the installer's Domain/Private firewall rules do not apply.	Check with Get-NetConnectionProfile; reclassify the connection with Set-NetConnectionProfile -NetworkCategory Private (or join the domain), or add a firewall rule for the Public profile on the Erde port.
Server is reached over the network but stays at /setup.	First-run setup has not been completed, so no appsettings.Production.json exists.	Complete first-run setup.

Related

• Choose Windows Service vs. IIS
• Complete first-run setup
• Deployment system requirements