Activate your license
Enter your license key and deployment ID in the console, what the License page shows, and what the portal sends when it checks in.
- For
- Administrators
- Applies to
- Billet 1.0
- Updated
A Billet deployment is licensed by Billet's license service at license.billetstream.com. The portal proves its license with the service when you enter it, then checks in about once an hour.
What you need
- Your license key (it starts
bmlic_) and the deployment ID it was issued for. Both are on the page that issued the key, and the key is shown there once. - Outbound HTTPS (port 443) from every portal node to
license.billetstream.com. Nothing is opened inbound. - The portal server's clock kept accurate by NTP. An answer dated more than five minutes from the server's own time is refused.
Enter it
- In the console, open Deployment and find License. Only system administrators can.
- Put the deployment ID in the first box. The box opens with an ID the portal made for itself: replace it with the one that came with your key.
- Paste the license key and press Activate.
The portal asks the license service before it keeps anything. If the service refuses the key, nothing is stored and the page says why. On success the page reads Licensed.
The key is not shown again, on this page or in the audit log. It is stored encrypted. If you lose it, ask for a new key and use Replace the key.
What the page shows
| The page says | It means |
|---|---|
| No license | Nothing is held yet. Enter one. |
| Licensed | The license service confirmed it within the last two hours. |
| Licensed, not verified lately | The license is good, and the service has not been reached for over two hours. Check the portal's outbound HTTPS and DNS. |
| Not yet in force | The license's term has not started. |
Under the state, Desktops in use counts desktops with at least one person assigned, against what the license covers. A second person on a desktop is not a second seat. Portal nodes lists each node counted.
Check now checks in straight away.
What the portal sends
At start and about once an hour, each portal node sends:
- the deployment ID, and its own install ID (a random identifier made when it first starts),
- for each day, the most desktops in use and the most sessions live.
When a node first joins it also sends its operating system, architecture, the portal's version, and a one-way digest of its host name and machine ID. Nothing it sends names a tenant, a person or a desktop.
If it will not activate
See License messages.
More than one portal node
Enter the license once. It is kept in the shared database, and a second node joins it by itself shortly after it starts.