Home →
More on Networks →
Servers (5.x) →
Monitoring License Use on 5.x Concurrent Network
4.7. Monitoring License Use on 5.x Concurrent Network
Applies to: Palisade Concurrent Network releases 5.x
(If you have 6.x, or a mix of 5.x and 6.x, see Monitoring License Use on 6.x Network.)
What sort of reports can I get on how your concurrent network licenses are being used?
There are three different views, which provide slightly different information:
- At the command line in your serial-number folder, type the command
palserveractutil -view -long
The display will show a number on the Hybrid line. This number is the total number of licenses you have, exclusive of any that are currently borrowed. In other words, it is the number currently in the pool for network use, including those in use and those not in use. If you downloaded your licenses in groups or individually, rather than all at once, you will see multiple license records and you'll need to add up the Hybrid numbers. Any borrowed licenses will be shown as "Deduction type: ACTIVATION".
Example: You have six licenses. Currently one is borrowed and three are in use on the network. The Hybrid: line shows 5, which is the one borrowed license subtracted from your total of six. The borrowed license is shown after the main display; the three on-network users are included in the Hybrid: line but not shown separately.
- In LMTools, on the Server Status tab, click Perform Status Inquiry. You will see the number of licenses issued and the number in use. The "Issued" number is all licenses including any borrowed licenses, and the In-use number includes both borrowed licenses and those currently being used on network. Below this summary you'll see the user name and machine name for licenses in use on network, and the machine name and borrow date for borrowed licenses. (The borrow date is the date the license was borrowed, not the date it is due to be returned.)
Exception: Server Status is erased if you stop and restart the server. In that case, the Issued number does not include the licenses that were borrowed before the last server start. As the borrowed licenses are returned, or their borrow-till dates arrive, the Issued number will rise until it matches your license total.
Example: You have six licenses. Currently one is borrowed and three are in use on the network. Server Status shows 6 issued, with 4 in use (one borrowed plus three in use on the network.) If you now restart the server, Server Status will show Issued: 5 (six .total, less one borrowed before the server start).
Special note: Starting in spring 2011, we have seen occasional cases where licenses are working but do not show up in Server Status. In such cases, please use method 1 or method 3 to track your licenses.
- In LMTools, on the Config Services tab, click View Log. You will see the in and out timestamps for each license used on network or borrowed. There are five relevant types of entry
OUT: user@machine -- user opened the software and is using it on network
IN: user@machine -- user closed the software
OUT: ACTIVATED LICENSE(S)@machine: license was borrowed
IN: ACTIVATED LICENSE(S)@machine: borrowed license was returned
plus a notation when a user is denied a license because all licenses are in use
Exception: The debug log is erased if you stop and restart the server. In this case it will not show any previously borrowed licenses, and when the previously borrowed licenses are returned it will not show IN: lines for them. It will show OUT: and IN: lines for licenses borrowed after the latest server start.
All three of these methods require logging on to the server. There is no way for a client computer to check how many licenses are available or in use, or who is using them.
Last edited: 2014-10-14