claudetools/.claude/memory/reference_pluto_build_server.md

name, description, type

name	description	type
Pluto Build Server	General-purpose Windows build VM — hostname PLUTO / Unraid VM name "Claude-Builder" / 172.16.3.36. For any EXE needing native Windows MSVC compilation (utilities, Howard's tools, GuruRMM + GuruConnect agents). Drive via /rmm (agent enrolls as PLUTO) when SSH key isn't authorized.	reference

Pluto is a Windows Server VM on Jupiter. It is the general-purpose Windows build machine for any project needing a native Windows executable — not just GuruRMM.

• Hostname: PLUTO (VM on Jupiter)
• Unraid VM name: Claude-Builder — the VM is listed as "Claude-Builder" in Unraid; it is the SAME machine as PLUTO / 172.16.3.36. There is no dedicated pluto vault entry — don't go searching for one.
• Drive it remotely without SSH: PLUTO runs a GuruRMM agent (client "AZ Computer Guru"). Use /rmm — resolve hostname PLUTO → agent id at runtime (IDs change on re-enroll; do not hardcode) — to run PowerShell on it. This is the path to use when a workstation's SSH key isn't authorized (e.g. GURU-5070, see below).
• Static IP: 172.16.3.36 (confirmed static 2026-04-19)
• SSH: ssh -i ~/.ssh/id_ed25519 Administrator@172.16.3.36 (key auth)
• Authorized keys (verified via RMM 2026-05-26): gururmm-build@gururmm-server and guru@gururmm-build (the build server's keys), present in both C:\ProgramData\ssh\administrators_authorized_keys and Administrator\.ssh\authorized_keys. The old guru@DESKTOP-0O8A1RL key (retired machine) has already been rotated out. NOTE: no personal-workstation key (e.g. GURU-5070) is currently authorized — the ssh -i ~/.ssh/id_ed25519 Administrator@172.16.3.36 workflow below works only from a host whose pubkey is in the file; add GURU-5070's pubkey to administrators_authorized_keys if you need direct workstation SSH.

Installed Toolchain

• Rust: stable-x86_64-pc-windows-msvc (rustup at C:\Users\Administrator\.cargo\bin)
• VS Build Tools: Installed with Microsoft.VisualStudio.Workload.VCTools (MSVC linker, CRT, Windows SDK)
• Git: v2.47.1.windows.2
• OpenSSH: Win32-OpenSSH, sshd set to Automatic startup

Use Cases

Use Pluto when you need a native Windows MSVC build — produces proper .exe files with no MinGW runtime dependency. Examples:

• Utilities (internal tooling, one-off scripts compiled to EXE)
• Howard's tech tools (MasterBooter, Slint GUI apps, etc.)
• GuruRMM agent MSVC builds (when MSVC target is preferred over the automated MinGW build on the Linux server)
• Anything using Windows-only APIs or needing code signing via signtool

Note: Routine GuruRMM agent builds are automated on the Linux server (172.16.3.30) via MinGW + jsign. Use Pluto for MSVC-specific builds or one-off tooling.

Directory Layout

• C:\builds\ — general project builds (create a subdirectory per project)
• C:\gururmm\ — GuruRMM repo clone

Typical Build Workflow

# 1. SSH in
ssh -i ~/.ssh/id_ed25519 Administrator@172.16.3.36

# 2. Clone or pull project
git clone https://azcomputerguru:<token>@git.azcomputerguru.com/azcomputerguru/<repo>.git C:\builds\<project>

# 3. Build
cd C:\builds\<project>
cargo build --release

# 4. SCP output back
# From workstation:
scp -i ~/.ssh/id_ed25519 Administrator@172.16.3.36:"C:/builds/<project>/target/release/<name>.exe" ./

Not Neptune

Neptune is a separate existing server (email/web hosting). Pluto is only for builds.