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
- Core Services (the Web Client, Web API, Log API, Logging Service, Monitoring Service, and MCP Server) run on Windows Server, each as its own IIS web site with its own port, set per environment in the Nodinite Portal.
- Monitoring Agents and Logging Agents are part of the same install package, or are installed on other servers.
- Windows authentication works with Active Directory and Kerberos, and OAuth 2.0/OpenID Connect is also supported; you choose in the Auth step.
- This is the most complete runtime for environments that need full agent support and traditional enterprise hosting.
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.
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
- Use Windows-integrated authentication when the environment already relies on Active Directory and Kerberos; see NTLM vs Kerberos Authentication.
- Use OAuth 2.0/OpenID Connect for modern identity federation or mixed-platform access; see Install Nodinite v7 - OpenID.
- You set both in the Portal Auth step; the CLI writes the settings at install and update.
Service Accounts and Permissions
- gMSA accounts — Configure Group Managed Service Accounts (gMSA) for Nodinite services; no manual password rotation
- Install Certificates for gMSA — Install the secret-encryption certificates that gMSA identities need in
LocalMachine\My - Migrate Traditional Account to gMSA — Move an existing installation from a domain account to a gMSA
- FAQ - gMSA Troubleshooting —
Test-ADServiceAccountfailures, logon errors, and certificate access
- Install Certificates for gMSA — Install the secret-encryption certificates that gMSA identities need in
- Logon as a Service right — Grant the Windows "Log on as a service" right to Nodinite service accounts
- Trusted for delegation — Configure Kerberos constrained delegation for multi-hop authentication (Logging Service → SQL Server → linked server)
- Cannot read configuration file due to insufficient permissions — Resolve IIS access-denied errors reading
redirection.config
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
- Configuration Error - targetFramework — Fix IIS application pools that run with the wrong .NET CLR version
- Windows FIPS Mode Compatibility — What Windows FIPS 140 mode means for Nodinite v7
- Why do Nodinite use port 8000 — Port 8000 for agents installed as Windows Services, and the Portal ports for IIS-hosted agents