The order to set things up in
A checklist for a new Billet deployment, from the first server to the first person connecting, with a link to each step.
- For
- Administrators
- Applies to
- Billet 1.0
- Updated
Each step depends on the one before it. Work down the list.
1. Plan the names and the network
- Choose a public DNS name for the portal, for example
portal.example.com. - Choose a public DNS name for each relay, for example
relay.example.com. - Get a TLS certificate for each name that a browser trusts. Let's Encrypt is fine.
- Check the ports in Network ports are open where they need to be.
See Before you install the server.
2. Install the portal
- Install the portal on a Linux server.
- Put it behind a reverse proxy that holds the TLS certificate.
- Sign in to the console for the first time and replace the first-run account.
- Create the certificate authority.
- Activate your license.
3. Install a relay
- Install a relay and enroll it with the portal.
4. Set up a tenant
- Create a tenant and connect single sign-on, so people can sign in.
5. Add desktops
- Register the desktop and create an enrollment token.
- Install Billet Host on the machine.
- Assign the desktop to a person.
6. Check it, then connect
- Check the deployment is ready.
- Have the person install the desktop app, sign in and connect.