962 B
nh3-pve's AMT is in TacticalRMM's MeshCentral (group PFI-AMT, device nh3-pve-amt)
[2026-10-02] nh3-pve's AMT is in TacticalRMM's MeshCentral (group PFI-AMT, device nh3-pve-amt). The adds had failed silently because TRMM installs MeshCentral WANonly (meshuser.js:2682 drops AMT adds). Prime ruled hybrid; switched 0812, 14/14 agents back, AMT connected at once (16.1.25, TLS fine). UPDATE 0859: it now PHONES HOME (CIRA) — MeshCentral mpsPass, ana-gw VIP/policy 76 on 4433, AMT settings via scripts/amt-cira-setup.py, AMT moved static → DHCP (Intel: CIRA needs DHCP; reservation keeps .61). Tunnel is independent of nh3-pve. ⚠ While phoning home the AMT REFUSES LAN management (:16993 dark), so manage it via MeshCentral; revert body servers/nh3-pve/amt-ethernet-static-revert.xml. 2FA still not forced. Prime's MeshCentral login token is vaulted pfi-tacticalrmm/meshcentral-login-token. → servers/pfi-tacticalrmm/README.md