Beginner setup / PBO-only

Your server.
Connected in five steps.

Install one server-only mod and one connection file. No Agent or client mod is needed. Players do not need to download anything.

You need access to your server files (FTP or a file manager), its startup settings, and a license for this server.

Already installed? Go to Updating an existing server. Do not repeat first-time enrollment for a routine PBO update.

STEP 01 / PORTAL

Add your server and download PBO-only

Create an account, or log in if you already have one.
Open Servers, select Add server, name your server and select a license: paste your serial or choose Buy.
For that server, choose Download PBO-only (the button also shows the current version). Extract the ZIP on your computer.

Servers / Your selected serverDownload PBO-only (version)

Illustration of the download choice, not a real screenshot. Choose PBO-only, not Download with Agent.

The ZIP contains @infiSTAR and direct-enrollment.txt at its top level. The connection file is private, works once and is valid for 24 hours. Do not share it or its contents.

STEP 02 / SERVER FILES

Stop DayZ, then upload the mod folder

Stop the server in your provider panel or normal server tool. Back up the files and startup settings you will change.

Using FTP or your provider's file manager, copy the extracted @infiSTAR folder into the DayZ server root, not the mission folder or your own game's folder.

DayZ server root/
|-- DayZServer_x64.exe     (Windows server executable)
|-- @OtherMod/            (keep your existing mods)
`-- @infiSTAR/
    `-- addons/
        `-- infistar_scripts.pbo

Example folder layout. On Linux, use the root containing your DayZ server executable. Avoid an extra nested @infiSTAR folder.

STEP 03 / CONNECTION FILE

Put the connection file in the actual profiles folder

Find -profiles= in your server's startup settings. Its value is the folder DayZ uses for profiles. If your host hides this setting, ask them for the actual DayZ profiles directory; do not guess from a folder name.

Inside that directory, create infiSTAR if necessary. Copy direct-enrollment.txt from the top level of the ZIP into it.

Startup example: -profiles=C:\DayZServer\profiles
Destination:     C:\DayZServer\profiles\infiSTAR\direct-enrollment.txt

Startup example: -profiles=/srv/dayz/profiles
Destination:     /srv/dayz/profiles/infiSTAR/direct-enrollment.txt

Startup example: -profiles=ServerProfile
Destination:     <server working directory>/ServerProfile/infiSTAR/direct-enrollment.txt

Path examples, not paths to copy blindly. Relative paths resolve from the server process's working directory. Respect filename case on Linux.

The file belongs inside <profiles>/infiSTAR/, not directly in the profiles root. Do not rename it or use the Agent's enrollment.json instead.

Own Windows or Linux machine? Optional file-placement helper

Use this instead of manually copying the connection file above, not as an extra step. You must still copy @infiSTAR in step 2 and configure startup in step 4.

Run INSTALL_PBO_ONLY.cmd on Windows, or sh INSTALL_PBO_ONLY.sh on Linux, from the extracted package. Enter the absolute path of the actual profiles directory when prompted, without surrounding quotes.

These helpers only move direct-enrollment.txt into the chosen profiles directory. They do not install the mod folder, edit launch arguments or start DayZ. On a rented host with FTP-only access, use the manual steps instead.

STEP 04 / STARTUP SETTINGS

Add infiSTAR to your server-only mods

If you do not already have -serverMod, add:

-serverMod=@infiSTAR

If you already use server-only mods, append ;@infiSTAR inside the existing value. Keep the other mods and use one -serverMod argument:

Before: "-serverMod=@ExistingServerMod;@AnotherServerMod"
After:  "-serverMod=@ExistingServerMod;@AnotherServerMod;@infiSTAR"

In a provider panel with a dedicated server mods field, append @infiSTAR to its semicolon-separated list instead of pasting an entire command line. Save your settings.

Keep your existing -mod, -profiles and other startup arguments. Do not add infiSTAR to -mod or a client Workshop mod list. No client keys or signatures need to be installed for this server-only package.

STEP 05 / CHECK THE CONNECTION

Start DayZ and check your portal

Start DayZ using your usual provider panel or server tool.
Log in to the portal and select the same server you downloaded the package for.
Allow startup and telemetry time. On MGT-hosted servers this can take about one minute; other hosts may take longer. Refresh or reselect the server if needed.
Check for an online connection and current telemetry in the Live Workspace. An empty player list alone does not mean the connection failed.

After successful first enrollment, the PBO removes the one-time connection file. That is expected. Keep the saved infiSTAR profile files for future restarts.

Continue to start, stop and restart DayZ through your normal host tools. If the server remains offline after startup and a few minutes, use the checks below.

Updating an existing server (no new enrollment)

Stop DayZ and back up the installed PBO. Download PBO-only for your existing server, extract it, and replace only @infiSTAR/addons/infistar_scripts.pbo. Start DayZ again and allow telemetry time.

Keep your existing profile files and credentials. Do not copy the new one-time enrollment file, reset the installation, or delete Agent state or the command ledger for a routine update.

Troubleshooting: offline, startup problems or HTTP 401

Finding settings on a hosted server

Use your host's file manager or FTP to find the server root. Look for the server-only mods field and the actual profiles path in its startup or command-line settings. Provider interfaces differ; if either is hidden, ask the host for the active server root, profiles directory and how to append a server-only mod. Do not guess paths or replace their existing mod list.

Server stays offline

Check the selected portal server, the PBO folder layout, your saved -serverMod value and the actual -profiles destination. Check the DayZ server logs for infiSTAR loading or connection errors. The server needs outbound HTTPS access to https://dayzsa.infistar.de; no inbound portal port is needed for PBO-only setup.

First enrollment expired or was rejected

If logs specifically identify an expired or already-used first-enrollment token and this installation has not enrolled successfully, stop DayZ, download a fresh PBO-only package for the correct server and replace only the one-time direct-enrollment.txt in the correct profiles location. Start DayZ again.

HTTP 401 Unauthorized

A 401 means authentication was rejected, not automatically that enrollment expired. If it happens in the browser, sign in again. If it comes from DayZ or the Agent, identify the failing component and request in its logs first. For a previously connected installation, preserve its credentials and ask support to investigate the server ID and error time. Do not post tokens, passwords or full credential files.

DayZ does not start

Check your provider's startup error and DayZ logs, mod paths, quotes and semicolon-separated mod list. PBO-only setup does not use server-launch.json. Restore your backed-up startup settings if necessary to isolate the problem.

Do not delete credentials, Agent state or the command ledger as a generic fix. Recovery of an existing installation needs diagnosis, not repeated re-enrollment.

Experimental optional client mod

The server-only installation works without a client mod or player downloads. The separate client mod is experimental, almost empty and completely optional. Its current source attempts to send a single client-presence report without delivery confirmation; it does not establish any additional anti-cheat protection. It is not available for download in this guide. Do not add a client mod or key based on this note.

Advanced: optional Agent (separate setup)

The Agent is not required for the PBO-only setup above. Leave it out if you only have FTP or provider-panel access.

On a server machine you control, the Agent adds a restricted BattlEye RCon bridge: it can query players, bans and admins, send a server-wide message, lock or unlock the server, and load or write bans. Agent process control is optional and disabled by default. Current Agent versions verify the recorded process identity before starting, stopping or restarting a managed process; a legacy installation that only stored a PID refuses those actions until the stored state is cleaned up with support. These features depend on the corresponding portal commands and local setup; they are not required for the PBO connection.

For RCon, enable and configure BattlEye RCon on the DayZ server, run the Agent on the same host, set INFISTAR_RCON_PASSWORD to its RCon password and, if needed, set INFISTAR_RCON_PORT to the configured UDP port (default 2302). The Agent connects to 127.0.0.1; the RCon service must be reachable there. Protect the password and do not expose RCon publicly just for the Agent. Only the operations listed above are supported, not arbitrary RCon commands.

If you deliberately want to set up the Agent on a machine you control, select Download with Agent for your server and follow the included agent/README.md and platform-specific instructions. The Agent has its own agent/enrollment.json; it is not the PBO connection file.

Check the actual package's platform requirements before proceeding. Do not run Windows launchers on Linux or assume the PBO file-placement helpers install an Agent service. Keep existing credentials intact when updating.