Installer Overview
What RasterexInstaller.exe installs, the installation flow, and what to do after installation.
Before running the installer, ensure these requirements are met.
- Windows Server or Windows 10/11
- Administrator rights (Run as Administrator)
- IIS installed with Static Content feature (required for all packages)
- Node.js installed (required for running the db backend)
Download the current supported installer for new deployments and upgrades.
The latest release includes the new calculate-then-apply calibration workflow. After installation, or after any backend .env change, restart the DB backend process or service so the new configuration is applied.
Installer releases
Download the version you need
| Version | Release date | Notes | Download |
|---|---|---|---|
4.1.3Latest | Available now | Added CAD updates for block details, block attributes, and layer details. | Download |
4.1.2 | Available now | Updated calibration flow: calibrationStart, calibrationSet, calibrationScaleCalculated, calibrationAddScale, and calibrationCancel. Use calibrationSet to calculate a candidate scale, then calibrationAddScale to apply it. | Download |
4.1.1 | Available now | Added 3d tools, and fixed the quatity tag for measurement tool | Download |
RasterexInstaller.exe is a self-contained Windows installer (Burn bundle) that installs three MSI packages in sequence.
The installer bundles everything needed, just download and run as Administrator.
- Backend: 3rd-party Rasterex document canvas engine
- Rasterex Backend: Express.js server files for API and file processing
- Rasterex Canvas: The user interface for viewing and interacting with documents
Packages install in this order. Each must complete before the next begins.
- 1. Backend: Interactive license UI (user must accept)
- 2. Rasterex Backend: Copies server files to C:\Program Files\RasterexBackend
- 3. Rasterex Canvas: Creates IIS site on port 4203
After installation, additional configuration is required for production deployments.
- Does NOT install Node.js - You must install Node separately to run the backend
- Does NOT run the backend as a service - See the NSSM page for service setup
- Does NOT configure HTTPS/SSL - See SSL & Domain Setup for production security
- Does NOT set up reverse proxy - See Reverse Proxy page if routing backend through IIS