Guide22 min
Schedule an Azure VM to Start Daily and Deallocate Itself When Idle
Configure an Azure server VM to start itself daily, update Windows, and deallocate when idle, so it runs about an hour or two a day instead of 24/7.
Install a Steam dedicated server with SteamCMD, open its ports, start it at boot, update it, back it up and move it, each step checked by what the server did.
Running a dedicated game server is mostly the same job whatever the game. You install it with SteamCMD, open its ports, start it at boot, update it, and back it up so a dead machine doesn’t cost the world. These guides do each step on Windows Server, with 7 Days to Die as the worked example. Each step is checked by what the server did, because SteamCMD’s exit code of 0 doesn’t prove an install or an update happened.
| What you need | Read |
|---|---|
| The app ID to install a server with, and whether it needs a Steam login | Find a server’s Steam app ID, checked for 25 common servers |
| SteamCMD and the server installed | Install SteamCMD and a dedicated server |
| Its ports open in Windows Firewall, and its saves where you choose | Configure the server and open its ports |
| The server running after a reboot, and stopped without losing the world | Start it at boot and stop it cleanly |
| Updates only when a new build ships | Update only on a new build |
| A copy of the world off the machine | Back up to Amazon S3 |
| A restore that doesn’t merge the old world back in | Restore without merging |
| The same server on a new machine | Move to a new Windows Server |
| A cloud VM that isn’t billed around the clock | Start daily and deallocate when idle |
To build one server from an empty machine, read the 7 Days to Die series in order.
9 articles
Guide22 min
Configure an Azure server VM to start itself daily, update Windows, and deallocate when idle, so it runs about an hour or two a day instead of 24/7.
Guide12 min
A 7 Days to Die dedicated server running the old world on a new Windows Server, its build and save files checked against the old one before players move.
Guide13 min
Run a 7 Days to Die server from a Windows scheduled task with no time limit, and stop it over telnet so the shutdown finishes and the world is saved.
Guide11 min
Compare the buildid in the appmanifest with SteamCMD's app_info_print and run app_update only when they differ. Success! and exit code 0 prove nothing.
Guide7 min
Each server's app ID comes with whether an anonymous SteamCMD install starts, and only two of the 25 were refused with No subscription.
Guide11 min
A copied restore such as xcopy /E keeps files the backup lacks. Rename the live Saves folder aside and move the archive's in; the old world stays beside it.
Guide9 min
SteamCMD and a dedicated server installed on Windows Server, checked by the success line, the executable and the build ID rather than the exit code.
Guide14 min
A 7 Days to Die server that starts on a clean Windows Server, with its saves where you choose and TCP 26900 and UDP 26900 to 26902 open in Windows Firewall.
Guideupdated Oct 202622 min
The world lands in S3 every morning as an archive that restores onto a fresh server, and the task's result says whether that morning's copy arrived.