LANBear
Start free trial

Vault Setup Guide

One shared game library, set up right.

The full technical walkthrough: pairing the Vault Server, installing the Node app on every PC, designating an Update PC, and (the step most guides skip) actually publishing what it installs.

Chapter 8 · Center panel

Monitor and maintain Vault

The Center panel's Vault page is where you check in on everything day to day. It's also where Chapter 3's Server assignment actually happens: until you've picked a PC and it's checked in, this page shows a picker instead of the sections below. Once paired, it's laid out in a few sections:

  • Health

    Server version, when it last checked in, how many nodes are reporting, and whether the share is provisioned.

  • Server settings

    The drive letter used everywhere, and an address override in case a PC ever fails to auto-discover the Server on its own.

  • Chain

    Every layer that's been published, each one's size, and which one is currently active.

  • Machines

    Every Node, its online status, what it's mounted, and the Update PC toggle from Chapter 6.

  • Maintenance

    A read-only history of chain maintenance. Nothing you need to trigger yourself.

  • Launchers

    Per-launcher toggles for redirecting Epic, Battle.net, Riot, and EA into the shared library, with per-machine status. The launcher list itself is configured by LANBear, not per-center. You just switch each one on or off.

Note

Vault Server and Node updates are staged and applied for you, never silently. The Health section shows a status badge the moment one starts, and again if one ever fails.

That covers the full setup, end to end. From here, the routine is just: install on the Update PC, publish (Chapter 7), and check this page if anything looks off.

Install games and publish them