| Task | Command/Tool | Frequency | | :--- | :--- | :--- | | | lmstat -a -c [port]@[server] | Daily | | List users by host | lmstat -a | grep -B 3 "Users of" | On demand | | Remove a hung license | lmremove solidworks username host | As needed | | Re-read license file | lmreread -c [license_file] | After adding seats | | Full server status | lmutil lmstat -c [port]@[server] -S | Weekly | | Restart daemons | lmdown -c [license_file] -force (then lmgrd -c ) | Monthly (off-hours) |
In this post, we will tear down what a SolidSquad license server actually is, how to move beyond the “spray and pray” method of license management, and how to build a resilient, auditable system that doesn’t ruin your engineers’ mornings. First, let’s clarify the jargon. "SolidSquad" isn't a formal software company. In the engineering world, it is shorthand for the ecosystem of floating license managers—most notably FlexNet Publisher (FNP), which powers Dassault Systèmes products (SOLIDWORKS, CATIA, SIMULIA) and many others. solidsquad license servers
Without data, you lose. With a SolidSquad log, you win. | Task | Command/Tool | Frequency | |