Installing the Tricerat License Server
If your ScrewDrivers deployment uses concurrent licensing — Concurrent User (CCU) or Concurrent Server (CCS) — you need a Tricerat License Server before installing any other component, so licenses are ready to check out the moment agents come online.
Nodelocked licensing? Skip this page
With Node Locked Server (NLS) licensing there's no license server — you enter your nodelock key during each component's installation. Not sure which model you have? See the license types overview.
Before you install
- Use the latest License Server version from the Tricerat downloads share — your account team or Tricerat Support provides the link. ScrewDrivers 7.9.6+ requires v6.0.7.0 or later — see License Server Compatibility for the per-release table — and the newest version is backward compatible with all v6 and v7 products.
- Pick a home for it: a dedicated server, the SQL Server machine, or an admin workstation all work — small deployments routinely share a machine. It needs network connectivity from every ScrewDrivers component, and Windows Server 2016 or newer.
- Verify .NET 4.8 on the chosen machine:
Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\' |
Get-ItemPropertyValue -Name Release |
ForEach-Object { $_ -ge 528040 }
# Returns True if .NET 4.8 or higher is installed - Have your v7 activation code from Tricerat — v6 codes don't work with v7 products.
Install and activate
- Run the installer locally (
TriceratLicenseServer_<version>_x64.exe) — not from a UNC path. Accept the license agreement and the default installation path; the installer configures Windows Firewall for the license service automatically. - Activate your license with the v7 activation code when prompted. After installation, verify the license appears with the correct user or server count in the license server's administration tools.
- Confirm the service is running and reachable from another machine:
Test-NetConnection -ComputerName license-server.domain.com -Port 6200
When components install later, you'll point them at this server's hostname — keep it handy.
After installation
- The default configuration works for most environments; if you tune
lmx-serv.cfg, see Optimizing Your Tricerat License Server Configuration — and note that future License Server upgrades reset the file to defaults. - Trouble activating, or users not receiving licenses once components are installed? Troubleshooting License Issues covers the diagnostic path.
- When a new License Server version ships, upgrade in place — configuration and activation carry forward.