← All guides
ASA Manager · Step-by-step

ASA Manager: workspace export, updates and support

Back up the manager workspace, restore its settings, update a server and prepare a useful support report.

TBB ASA Server Manager workspace screen, captured from the desktop application
Workspace settings and the Open manager data action · Actual prototype 0.7.3 interface with sample data; final build may differ.

The workspace contains manager records. It is different from the large ASA installation, world saves and downloaded mods.

1. Find the manager data

  1. Open Settings in the left menu.
  2. Review the default Server files, Backups and SteamCMD folders.
  3. Use Open manager data to reveal this Windows account’s manager data.
  4. Close the manager before manually copying its complete data directory.

Default manager data is under %LOCALAPPDATA%\TeaBagBrit\ASAServerManager. Workspace defaults do not move existing files when changed.

2. Export the workspace

  1. Open Tools & health and choose Workspace.
  2. Click Export workspace.
  3. Save the ZIP in a separate recovery location.
  4. Keep the matching server-world backups too.

The export contains profiles, shared configurations, bundles, clusters, schedules and preferences. It does not copy all server binaries, world files or external cluster transfer data.

3. Restore the workspace

  1. Stop all managed servers.
  2. Export the current workspace before replacing it.
  3. Open Tools & health → Workspace → Restore workspace.
  4. Choose the saved export and read the review/confirmation.
  5. Confirm only when the replacement is intended.
  6. Review every restored path, profile, port and password before starting a server.

Restore replaces the manager’s settings; it does not relocate or restore server/world files. The app makes a BeforeRestore workspace export first. Restoring Windows-account-protected credentials on a different PC/account may require re-entering passwords.

4. Update the ASA server

  1. Select and stop the server.
  2. Keep a fresh world backup.
  3. Use Update in the installed server’s action row and review the target folder.
  4. Wait for SteamCMD completion.
  5. Start and inspect Console, including mods and map loading.

Install server appears for a missing installation in the revised build; Update is for an installed stopped server.

5. Update the manager app

Close the app before running a new official installer. Keep your exported workspace and server backups first. Check the version shown in the app against the intended release. Do not assume a source ZIP has updated an already installed executable.

6. Export a support report

Use Tools & health → Workspace → Export support report. Save it locally, inspect it and remove private information before sharing. Include the app version, Windows version, selected server/map, expected result, actual result and exact reproduction steps.

Console and error diagnosis

Explore ASA Server Manager

View the project →