- 3 minutes to read

Run Nodinite on Windows Server

Nodinite v7 runs on Windows Server as the full production baseline: every Core Service is an IIS web site, the agents run next to them or on other servers, and identity comes from Active Directory or OAuth 2.0/OpenID Connect. Container hosting (Docker, Kubernetes, OpenShift, Azure Container Apps) is coming; see Runtime Environments for the status of those tracks.

This page explains what the Windows Server runtime looks like and which troubleshooting guide covers each Windows prerequisite: service accounts, gMSA, Kerberos, MSDTC, MSMQ, FIPS, IIS application pools, and agent ports.

Current Scope and Intended Usage

Important

The Windows Server installation is the full baseline runtime. Container deployments currently focus on Core Services only and don't include the same agent coverage.

Understanding the Windows Runtime Architecture

The diagram shows the Windows prerequisites in the order a request meets them: the IIS web site, the service identity that runs it, and the Windows and SQL Server services that identity must reach.

flowchart LR USER["fa:fa-user Users and API clients"] subgraph CORE["Nodinite Core Services Server - Windows Server"] IIS["fa:fa-globe IIS web sites
one port per Core Service"] ID["fa:fa-user-shield Service identity
domain account or gMSA"] WIN["fa:fa-gears Windows prerequisites
Logon as a Service, DCOM, MSDTC"] end subgraph AGENT["Nodinite Agent Server"] AG["fa:fa-microchip Agents
IIS site or Windows Service"] end SQL["fa:fa-database SQL Server
Configuration and Log Databases"] DC["fa:fa-server Domain Controller
Kerberos, KDS"] USER -->|"HTTPS, Portal port"| IIS IIS --> ID ID --> WIN ID -->|"Kerberos"| SQL ID -->|"Kerberos"| DC IIS -->|"Agent port"| AG style IIS fill:#2678BD,color:#fff style ID fill:#93d16d style WIN fill:#FFD525 style SQL fill:#3F827B,color:#fff style DC fill:#3F827B,color:#fff style AG fill:#9E59BB,color:#fff

Diagram: users reach the Core Services IIS web sites (blue); each site runs as a service identity (green), a domain account or a gMSA, which needs the Windows prerequisites (yellow): Logon as a Service, DCOM Local Activation for the Monitoring Service, and MSDTC. The identity reaches SQL Server and the domain controller (teal) with Kerberos, and the Monitoring Service calls the agents (purple) on their ports.

Authentication Model in Windows Server

Service Accounts and Permissions

Kerberos and Authentication

  • PACVerification — Trade-offs of disabling PAC verification when Kerberos ticket validation causes delays

Windows Services and Components

  • Transactions MSDTC — Enable and configure the Distributed Transaction Coordinator for distributed transactions
  • MSMQ Queue Access denied — Restore permissions on an MSMQ private queue that returns access denied

Configuration and Compatibility

Next Steps