The Steam Site Server allows licensees of the Steam PC Café Program to share commercial licenses in their local network. The following instructions will walk you through the setup of the Steam Site Server. Additional information about the program can be found here.
Once you have extracted the documents from the zip file and added the server account to your site location, it’s time to run the server in your local network.
First, navigate to the folder that the server files have been extracted to. Right click the steamconsole.cfg file and select Open With > Notepad. Please note that the .cfg extension may be hidden by your operating system.
Find the line in this file that includes the command "@sStartupScript" and change < account > to the server account name that you have selected for the location; you'll also need to enter the password of the account where it says < password >.
Delete the // characters from before @sStartupScript and save the file; this will activate the command when running the SteamCMD.
Next, run SteamCMD by double clicking it. The SteamCMD will automatically log in in on every launch, using the account credentials you have entered into the steamconsole.cfg file. The first time you're launching the SteamCMD, you may need to enter the Steam Guard code that will be sent to the email address associated with the Site Server Steam account.
Once you've successfully logged in, the SteamCMD will present you with the screen below.
The content cache allows you to download game files once and then distribute them through your local network to the individual game stations. Patrons that bring their own computer or laptop can also access the game files instead of using your location's Internet bandwidth. Please note that the game files will be saved on your server machine and you may need to increase your hard drive space depending on the amount of games that you will offer.
Navigate to the folder where you previously extracted the server files to. The folder will be named "site_server".
In order for the content cache to work properly, you will need to un-comment the command lines in the steamconsole.cfg file. Un-commenting can be done by removing the "//" at the beginning of each line. Once you make changes to the steamconsole.cfg file, remember to save the changes before launching the SteamCMD again.
In our sample arcade configuration, we have chosen to create a content folder on the main hard drive and set the cache limit to 500GB. Click the button below to expand the example.
// This enables the site license server functionality in steamcmd, must be set to 1
// *** EDIT ME ***
// This will let steamcmd login to your site account automatically at startup.
// You MUST login for the site license server to operate
// Content cache configuration
// It is recommended that you enable the content cache, to improve efficiency of Steam game updates at your site
// and reduce the traffic on your internet links.
// *** EDIT ME ***
// Steam client game downloads will proxy through this port on the site server.
// This must be set to something greater than zero for the content cache to operate.
// Recommended setting: 80, or another port that is free on your server and accessible to clients.
// *** EDIT ME ***
// The location of the game download cache on the server machine.
// You should create the cache directory before running the server.
// The maximum size on disk of the game download cache (default = 100GB)
// Optional flag to enable the Steam clients on your network to share downloads with each other, reducing traffic
When a game is launched for the first time in your network, the download request will be sent to the server machine. If the game files are not cached on the server yet, the server will download them automatically, cache them, and return them to the client machine. If the game content cache is already available on your server, the server will automatically send the files to the client machine.
To run a Steam Site Server, you just need a secure Windows 7 or Windows 10 PC connected to the location's network. You will also be able to run it on Windows Server 2012 R2 and 2016. If you are also using the Site License Server as a content server cache we recommend that it has enough storage to support 1TB of content data.
Yes, the feature will only be properly functioning if server and stations are on the same subnet. Packets are not forwarded to other subnets and only client machines that are in the same network will have access to the license pool and content cache feature.
This error usually indicates that the account used to run the Site Server has not been added to the site location on the Steamworks partner page yet. Please navigate to Steamworks and make sure you log in with your master account. You can double check the account credentials under the "Sites" option at the top or by clicking here. If no server account has been assigned yet, a site server account must be added to the license agreement first, by clicking the "Manage Users" option on the Steamworks page. Once added, you will be able to assign it to a site location. A site server account is basically a Steam account that does not own anything.
The communications between the Steam client and the Site License Server use UDP broadcast packets over port 27036. If the client machine is not receiving those packets, then it won’t be able to discover and connect to the Site License Server. You can find a list of required ports for Steam here.