My mobile policy is shown as checked out on my SilkMeter license server machine but has been checked in on my local machine. How can I remove the orphaned license from my SilkMeter license server machine?
If a license becomes orphaned on the license server there is no way to check it back in, other than to wait for it to expire.
Unfortunately it is not possible to provide this functionality as there is no way to see when such a license is really orphaned and when it is checked out to a client which is not connected. Providing this functionality would constitute a breach in license security. If the license server could check in licenses, without first checking that they are actually checked out on the client, then we could be forcing the license back into the server and checking it out again to different machines, while the first client still has them checked out. Therefore duplicating the use of the license.
However, it can happen, for example by editing policies.dat, that you receive an error message that says;"There is no mobile Policy on the local system checked out from this host"
when you try to check a license back in. This license is not fully orphaned and, because the license server can still check that it exists on the client, it can be checked back in using the following command on the client machine:smCmdTool ci segue XXXXXXX
in the following directory:C:\Program Files\Borland\SilkMeter\bin
where XXXXXXX is the policy id.
NOTE: As stated at the top of the polices.dat file, this file should not be edited as it can lead to unexpected behaviour.