Frequently Asked Questions
Nex is a self-hosted Windows endpoint management and orchestration platform that centralizes patching, update health, software deployment, device visibility, maintenance windows and routine endpoint-management functions.
Nex simplifies Windows endpoint management while keeping the management infrastructure inside the organization’s environment. It provides centralized patching, software deployment and device visibility without requiring Azure or public-cloud hosting.
Nex is designed for organizations and IT teams that want practical centralized management of Windows workstations and servers while retaining full control of the management platform within their own network.
No. Nex is intended to provide straightforward Windows endpoint management without unnecessary platform complexity. Maximum-scale guidance will be based on validated load testing rather than theoretical endpoint counts.
No. Nex is fully self-hosted. The Nex Server and its operational data remain inside infrastructure controlled by the organization.
No. Nex does not require Azure or any public cloud service to operate.
Yes. Nex provides centralized Windows management without requiring cloud-hosted management infrastructure. Organizations can reduce cloud consumption and hosting costs by keeping management traffic and data on-premises.
The Nex Server runs inside the organization’s environment. Each managed endpoint runs the Nex Agent as a Windows service.
Nex operational data is stored in a Microsoft SQL Server database controlled by the organization.
No. Nex management traffic remains internal. The platform does not require a public-cloud service to coordinate endpoints.
Nex management traffic is internal. Internet access is only required when Windows devices need to reach Microsoft services to obtain Windows updates.
No. Endpoints communicate with the Nex Server through the organization’s internal network.
Yes. Nex supports HTTPS and TLS for secure communication between endpoints and the Nex Server.
Yes. Nex supports certificates issued through an organization’s internal certificate infrastructure.
The Nex Server is the central management and orchestration point for your Windows environment, coordinating endpoint health checks, update scanning, patch installation, maintenance windows, reboot management, post-update verification, software deployment and device inventory. It communicates with Nex Agents to manage the maintenance lifecycle while keeping management operations and data within the organization's own infrastructure.
Nex uses Microsoft SQL Server. SQL Server Express is available for appropriate deployments, with the supported SQL Server version dependent on the Nex Server installer and Windows Server version being used.
Nex currently targets Windows 10, Windows 11 and Windows Server 2012 R2 through Windows Server 2022. Windows Server 2025 endpoint compatibility is currently undergoing validation
The Nex Agent is a Windows service installed on each managed endpoint. It communicates with the Nex Server, receives instructions and reports endpoint information and results.
No. The Nex Agent runs as a Windows service and does not require an interactive user session.
The Agent cannot obtain new instructions while the server is unreachable. Normal activity resumes once communication is restored.
Yes. Nex coordinates update health checks, update scans, installation activity, maintenance windows and reboot handling.
No. Windows devices obtain update content through Microsoft’s Windows Update infrastructure. Nex orchestrates the update process around it.
Patch orchestration is Nex’s controlled workflow for endpoint maintenance: Health Check → Update Scan → Assessment → Maintenance Window → Installation → Reboot → Post-Patch Health Check.
Yes. Nex tracks reboot-required conditions and coordinates restart activity as part of the update workflow.
Installing an update is only one stage of the patching process. Nex coordinates endpoint health, update discovery, maintenance windows, installation, reboot requirements and post-update verification as part of a controlled maintenance workflow.
Yes. Nex Update Health assesses conditions that may affect successful patching, including pending reboot state, Windows Update readiness and relevant Windows services.
The Nex Agent reconnects to the Nex Server after Windows starts, allowing Nex to continue the maintenance workflow and reassess the endpoint's update and health state.
Windows patching involves more than installing updates. Orchestration coordinates the stages and dependencies around patching, reducing repetitive administration while giving IT teams greater visibility and control over the complete maintenance lifecycle.
Yes. Nex centrally coordinates software package deployment to managed Windows endpoints.
Package content is stored on infrastructure controlled by the organization and distributed through the Nex Server.
Yes. Deployment results are returned to the Nex Server for administrator review.
Nex collects endpoint, OS and hardware inventory information to provide visibility of managed systems.
Yes. Nex Collections allow administrators to organize endpoints for easier targeting and management.
Yes. Nex manages supported Windows workstation and Windows Server operating systems.
Yes. Nex Server includes licensing controls governing authorized use.
Yes. Nex includes a time-limited trial workflow.
Yes. Nex supports an offline licensing workflow where license information can be generated externally and imported.
A Nex recovery plan should include the Nex SQL database, server configuration, package repository, certificates and deployment-specific configuration.
Yes. Recovery involves restoring the server environment, database, configuration, packages and certificates.
Start with the communication path: verify the Nex Server, Nex Agent service, DNS, routing, firewall and certificate trust. Then review the Nex logs.