Floating License Server: Quick Setup Guide

Need to share software licenses across your team? Here’s how to set up a floating license server in minutes.

What you’ll get:

• Share licenses between users instead of buying individual copies
• Control and monitor license usage from one place
• Let users access software from any network computer

Quick Setup Requirements:

Component	Minimum Specs
CPU	1 GHz processor
RAM	2 GB
Storage	4 GB free space
Network	Static IP address
OS	Windows/Linux/Mac

3 Steps to Get Started:

1. Install server software:

TurboFloatServer.exe -i

2. Configure your network:

• Open TCP port 22350
• Set up static IP
• Configure firewall rules

3. Add your license:

TurboFloatServer.exe -a="YOUR_PRODUCT_KEY"

That’s it – your floating license server is ready to use. The rest of this guide covers detailed setup instructions, user management, security best practices, and troubleshooting tips.

Key Feature	What It Does
License Pooling	Share licenses between multiple users
Usage Tracking	Monitor who uses what and when
Remote Access	Use licenses from any network location
Central Admin	Manage all licenses from one dashboard

Related video from YouTube

Before You Start

Here’s what you need to set up your floating license server:

Computer Requirements

Component	Minimum Specs	Recommended Specs
CPU	1 GHz	2.0 GHz or higher
RAM	2 GB	4 GB
Storage	4 GB free space	8 GB free space
Network Card	100 Mbps	1 Gbps

Network Setup

Setting	Requirement
Port	TCP 22350 (default)
IP Address	Static IP
Firewall	Program and port exceptions
Internet	Initial access for activation
DNS	Registered hostname

Supported Systems

Operating System	Versions
Windows	XP, Vista, 7, 8, 10, 11
Windows Server	2000, 2003, 2008, 2012, 2016, 2019, 2022
Mac OS X	10.7.3 or higher
Linux	All major distributions

Access Rights

Permission Type	Details
System Level	Windows Administrator or root access
Server Management	Rights to start/stop services
License Management	Access to add/remove licenses
File System	Read/write access to server directories
Network	Rights to configure firewall rules

Set up your Windows firewall like this:

1. Open Windows Defender: Go to the firewall settings
2. Add Program: Create exception for license server executable
3. Configure Port: Open TCP port 22350
4. Enable Access: Allow inbound connections

"For assigning licenses to users, you need to be the global admin or User management admin in the organization." – Gene, Microsoft Community Contributor

Note: Your server works offline after setup, but needs internet for first-time activation and updates.

Setting Up the Server

Here’s how to get your server up and running:

Software Installation

You’ll need to download "ArtworkFlexPkgWindowsV11.14_with_dongle_support.zip" (4.5 MB) from the FTP server. Extract it to any Windows folder and check that you’ve got all the files.

Basic Configuration

First, open TurboFloatServer-config.xml. Here’s what to change:

Setting	What to Enter	Why
Listening Port	13	For TCP connections
Proxy Address	Optional	Only if you use one
Server IP	Your static IP	From your network

Next, grab PowerShell (run as admin) and type:

TurboFloatServer.exe -i

For network access, you’ll need:

• Access to wyday.com, limelm.com, and ibe-software.com
• Both HTTP and HTTPS open
• A physical machine (virtual servers won’t work)

Adding Your License

Here’s what to do:

1. Get your product key from the customer portal
2. Run: TurboFloatServer.exe -a="YOUR_PRODUCT_KEY"
3. Double-check that it worked

If you’re planning to handle thousands of jobs, go for a beefier setup like c6in.4xlarge

Quick Tips:

• Stick to physical Windows machines
• Keep internet on for the setup
• Check UserManual.html if you get stuck
• Use ANSI for license files

That’s it – you’re ready to go.

Server Settings

Here’s what you need to know about setting up your server:

Basic Settings

Your server needs these core configurations:

Setting Type	Configuration	Details
Network	Port 443 (HTTPS)	For customer access
Security	Microsoft Updates	OS and SQL Server updates
API Access	IP Restrictions	Management API limited to specific IPs
Encryption	CommunicationEncryption	Different from AdminEncryptionKey
Firewall	TCP Ports 27000-27010	Server-client connections

Want to block unwanted access? Set these rules:

Block Type	How to Set	Purpose
IP Addresses	Server Properties	Stop bad actors
Computer IDs	Global or Per Key	Block specific machines
HTTP Methods	Security Section	Limit allowed operations

Extra Settings

Here are the power-user options:

Setting	Purpose	Configuration
User Limits	Max users	Set connection limits
Session Management	User tracking	Set timeout rules
License Groups	Access control	Set up role-based rules
Debug Logging	Fix issues	Configure log settings
Auto-restart	Keep running	Set recovery options

What Your Server Needs:

• 64 MB RAM (minimum)
• Windows Server 2019/2016/2012 or Linux
• Stable hardware
• Internet connection (first setup + updates)

The SDK pings floating servers automatically to show that your instance is still running and using its license.

Backup Must-Haves:

• Full system
• IIS config files
• SQL Server DBs
• License Server folders

Keep your backups off-site. Always.

sbb-itb-738ac1e

Setting Up Users

Here’s what you need to know about setting up users with your license server:

Computer Requirements

Users need these basics to connect:

Component	Requirement	Notes
Operating System	Windows/Linux/OS X	Must match server compatibility
RAM	64 MB minimum	For client software
Network Access	Port 9412 open	For Windows security software
Storage Space	100 MB	For client software installation
Firewall Settings	Allow incoming connections	From license server IP

Connection Steps

Here’s how to connect computers to your license server:

Step	Action	Details
1. Install Client	Download from server	Copy command-line tools to /sbin
2. Set Server Location	Use IP or hostname	Via environment variable or installer
3. Configure License Path	Set INTEL_LICENSE_FILE	Points to server’s port@hostname
4. Test Connection	Run rvlstatus	Checks server connectivity

You can set up client licenses in three ways:

1. Client License File

Put the file in your system’s default license folder:

• Windows: \Program Files\Common Files\Intel\Licenses
• Linux: /opt/intel/licenses
• OS X: /Users/Shared/Library/Application Support/Intel/Licenses

2. Port@Hostname

Set up using INTEL_LICENSE_FILE environment variable:

• Format: port@hostname
• Example: 27000@license_server

3. Server License

Apply server license settings directly to the client and keep files in sync.

Testing Your Setup

Check if everything works:

Test	Command	What It Shows
System ID	rvlsysid	Machine ID
License Status	rvlstatus	Active licenses
Server Location	rvlsetserver	Server path

The system checks out floating CALs from the license server when users need them.

Your setup includes:

• Command-line tools in /sbin
• License client software
• TurboFloatServer-config.xml
• Server connection settings

Server Care

Checking Server Health

Here’s how to check if your license server works:

Command	What It Does	What You’ll See
lmutil lmstat -c 27000@server	Shows if server’s running	"License server UP"
lmutil lmstat -a	Shows who’s using licenses	"8 licenses issued, 3 in use"
lswhere	Gets server location	"192.168.1.100"
lsmon	Shows current users	"User: defaultUser on DefaultComputer"

On Windows, you can check status through:

• Command prompt
• License Management Center (http://localhost:1084)
• Windows monitoring tools

Fixing Problems

When things break, here’s what to do:

Error	What It Means	How to Fix
-4	No licenses left	Free up unused licenses
-5	Wrong feature	Double-check software version
-15	Server connection failed	Look at server status and firewall
-96	Server’s not answering	Check the license log

Check these ports:

Port	What It’s For	What to Do
27000	Main license manager	Open TCP inbound
27001-27003	Vendor programs	Test connection
1084	Web access	Update firewall rules

Backup Steps

Back up these key files:

What to Back Up	Where to Find It	How Often
License Files	Windows: C:\ProgramData\FlexNet	Daily
	Mac: /Library/Preferences/FLEXnet	Daily
Server Config	Main install folder	Weekly
Log Files	System logs	Monthly

If your hardware fails, here’s what to do:

1. Get the System Ready

Install your OS and license server software.

2. Put Files Back

Move license files to your FLEXnet folder.

3. Test It Out

Run this to see your licenses:

fwappactwiz –list

4. Fix Any Issues

If licenses don’t work, try:

fwappactwiz –repair PRODUCT_KEY

"It is always good to split functionality over different systems." – Jos Meijer, Community Contributor

Keeping the Server Safe

Here’s how to lock down your license server and keep it running smoothly:

User Controls

Your first line of defense? These core security measures:

Security Measure	Setup Steps	Purpose
SSH Key Auth	1. Create SSH key pair 2. Disable password login 3. Add public key to server	Blocks password attacks
IP Limits	1. Set allowed IP ranges 2. Block unknown IPs 3. Add subnet masks	Limits server access
Two-Factor Auth	1. Install 2FA app 2. Enable in server settings 3. Set up backup codes	Double-checks identity
Access Codes	1. Create unique codes 2. Assign to user groups 3. Set expiration dates	Controls who gets licenses

Want remote access? Here’s what to set up:

Setting	Configuration	Location
Remote Access	Allow Access From Remote Clients	Admin Control Center
Client Limits	Specify allowed machines/subnets	Access Restrictions field
User Pairs	Set user-machine combinations	User Restrictions field

License Rules

Keep tabs on your licenses with these tools:

Tool	What to Track	How Often
Usage Reports	Active licenses vs. total	Daily
User Logs	Login times and duration	Weekly
Access History	Failed login attempts	Daily
License Status	Expired or near-expiry licenses	Monthly

Here’s what you NEED to do:

1. Clean up unused services monthly
2. Set up failed login alerts
3. Make users log out when done
4. Check usage patterns quarterly

"Make sure you know how the licenses are enforced: license manager server, honor system, some kind of token/dongle, or something else." – Jos Meijer, Community Contributor

Stay on top of maintenance:

Action	Timing	Benefit
Service Audit	Monthly	Spots weak points
Password Updates	Every 90 days	Fresh access codes
SSL Certificate Check	Monthly	Keeps data private
Firewall Rules Review	Quarterly	Updates protection

Tips for Success

Here’s what you need to know about setting up and running your server:

Setup Basics

Your server needs these specs to work well:

Setting	Configuration	What It Does
CPU Cores	2+ cores	Handles user requests without lag
RAM	16 GB+	Keeps things smooth when busy
Storage	SSD only	Makes license checks snap
SQL Memory	4 GB+	Speeds up database work

Make It Fast

Want better speed? Do these things:

What to Do	How to Do It	Why It Works
Fix IIS Pool	Set 29-hour recycle	No more slow first requests
Set Up Cache	Add local caching	Faster license checks
Watch SQL	Keep an eye on memory	Quick database responses
Pick Network	Go with LAN	Faster checkouts

Keep It Running

Here’s what to check and when:

Do This	When	Why
Check Memory	Every week	Catch problems early
Reset Pools	Each month	Fresh start, no junk
Back Up SQL	Every day	Keep data safe
Test Speed	Every week	Spot slowdowns

Stay Current

Keep everything up to date:

Part	When	What to Do
SQL Server	Monthly	Get security fixes
IIS	Every 3 months	Update web parts
OS	Monthly	Add critical updates
License Software	Weekly	Get new features

For fast networks, remember:

• Put users on fast LAN
• Set up VPN for remote work
• Know how to fix license issues
• Watch your user count

Remote access options:

Type	Works Best For	Watch For
LAN	Office staff	Network speed
VPN	Work-from-home	Connection issues
Internet	Global teams	Extra security
Hybrid	Mixed groups	Setup time

Related posts

• Node-Locked Licensing: 10 Tips for Software Developers
• Software License Management: 2024 Guide
• Software Licensing Models: Complete Guide 2024
• License Key Management Systems: Guide