Dune: Awakening Server Guide
Guides and release notes are shown in their original language.
On this page
← All guides · GAME GUIDE
Dune is an external deployment, not a conventional single server executable. Synix can install/update its files, back up the selected installation folder, and launch the official deployment tool. The game owns its virtual machines and battlegroup state.
Check prerequisites
The Synix profile checks for at least 24 GB total system RAM, AVX2, hardware virtualization, Hyper-V, and a supported Professional-or-higher Windows edition.
Funcom's official self-hosting guide lists the current game requirements, token process, networking, and deployment steps. Its memory requirement depends on how many game servers/maps the battlegroup runs. Check that guide before changing Windows features or buying hardware.
Synix does not silently enable virtualization or install Hyper-V.
Install and launch
- Add a new Dune: Awakening server through the normal Synix setup workflow.
- Review the detected requirements, installation folder, and profile warning.
- Save and Start the entry.
- Synix launches the official battlegroup.bat tool with an administrator permission prompt because that deployment requires elevation.
- Follow the official tool's initial-setup process and provide your self-host token when requested.
- Complete the VM, networking, and battlegroup configuration in the game's tooling.
You do not need to find an old SteamCMD tab or enable a global Run as Administrator setting just to follow these instructions. Elevation for the deployment tool is distinct from running every Synix-managed server as administrator.
Token and networking
Obtain the self-host token through the official Funcom account portal using the eligibility/setup instructions in Funcom's guide. Keep it private.
The v1.0.25 Synix profile stores 7777 as its default game-port field and 31982 as the deployment/RMQ field. These two values are not a complete VM/battlegroup forwarding checklist. Use Funcom's current official guide for the required port ranges, protocols, and deployment topology; the VM and host are not interchangeable forwarding targets.
In the Synix catalog, the query field's 31982 value is deployment/RMQ metadata. It is not an ordinary A2S query endpoint.
Lifecycle and backup limits
A launcher window closing is not proof that its VMs or battlegroup stopped. Use the official deployment controls to confirm running state and perform VM/battlegroup operations.
Do not assume ordinary Synix process termination, query player counts, or watchdog recovery fully controls the game-owned deployment. The profile deliberately uses external lifecycle tracking and does not offer generated launch-file export.
A Synix ZIP of the deployment folder is not automatically a consistent database/VM backup. Use the game's supported backup/shutdown procedures for its actual persistent data and verify recovery before relying on it.
Implementation reference: Dune profile.