01 / Your command desk
Server Manager
Windows 10 or 11 · x64
Install the controller on a supported PC. Keep the complete extracted application folder together.
0.3.4 preview limits: Cloud requires the existing local bridge at http://127.0.0.1:9104; Runtime also uses this PC's existing service. The Python helpers depend on an existing interpreter pinned on the build PC; Python is not bundled. On another PC, catalog and drafts can work while preflight and Runtime checks refuse. This build does not install a node agent. Dell installation and licensed gameplay remain unverified.
Download Server Manager 0.3.4118,227,550 bytes · extract the complete ZIP
SHA-256: 6638f7991b1f618cc8add5642e0fea56314c4b43bbb1d94dc100c1d2167593c4
02 / Host and remote controller
Native Windows Server Manager
Windows 7 SP1 and newer · .NET Framework 4.8
Use the same native app to manage existing nodes or enroll its host. Choose Sign in to manage existing nodes on your control PC, then select the Dell after it is enrolled.
Remote controls include viewing the active desktop, mouse and keyboard input, registered file roots and transfers, system inventory, registered service operations and reboot. An active, unlocked user session is required for desktop and files.
03 / Your Dell node
Legacy-compatible host
Windows 7 SP1+ · .NET Framework 4.8 · unsigned preview
On the Dell, extract every file and open Luminae Node.exe. Verify the authorized Cloud endpoint and explicitly enroll this computer with your existing account.
In System controls → Set up machine services, review Windows UAC, sign in privately as the current Cloud owner, choose local service/file permissions and optionally enable workforce contribution. Setup preserves this node's identity while rotating its credential.
The automatic SYSTEM broker stays connected at boot; games and workforce scripts run as restricted LocalService. Open the app normally after setup, or sign out/in, for its visible desktop helper. Locked and secure desktops refuse access. Use the game and Minecraft player tabs for separate reviewed actions.
Physical Dell acceptance for Windows 7, service recovery, hardware, Java/game/modpack and licensed players remains pending. Minecraft agent clients run on a separately configured modern PC; arbitrary client-required modpacks are unsupported. This download includes historical 0.1 instructions for reference; use these current 0.2.2 setup steps.
04 / Check before installing
Host compatibility check
Windows 7 and later · PowerShell 2+
A small local script reports Windows version, architecture, RAM and system-drive free space. It does not enroll a node, install software or upload its output.
Checking the compatibility script…
Available preview / 0.1.0-integration.1
Minecraft player bridge
Modern Windows 10/11; Node.js 22 or newer installed separately; not Windows 7
Full-folder kit; Node bridge core remains 0.1.0. Integration revision adds bounded asynchronous modern-agent player dispatch and the shared --once drain. Read cloud-agent-integration/CLOUD-INTEGRATION-ADDENDUM.txt first and adopt only its reviewed source hunks under the existing Cloud owner; no automatic update, enrollment or runtime start. Requires a reviewed modern Cloud agent with explicit player opt-in and your own licensed Microsoft Minecraft Java account in its private login flow. Node.js is installed separately; no account/auth cache is bundled. Actual server join and licensed gameplay on the Dell remain unverified. Arbitrary client-required modpacks are unsupported.