We are trying to completely restrict the installshield's concurrent licenses borrowing using the BORROW_LOWWATER option by setting it to a number greater than or equal to the actual concurrent licenses we have. However, license borrowing is still possible with this option in place in our vendor daemon's option file.
We want to use this option instead of others like INCLUDE/EXCLUDE to lower down the administrative work. Has anybody tried this usecase and been successful? please advise.
We have 'x' installshield standalone licenses and 'y' installshield premier licenses, now using BORROW_LOWWATER we want to make this all licenses not available for borrowing like below:
BORROW_LOWWATER f1 x
BORROW_LOWWATER f2 y
Where, f1 & f2 are the codes of the features we have.
But, this doesn't seem to work for us. Please let us know the result once you try this at your end.
Also, how can we create a new license with the activation code we have, so that the created license file has all the lines as in the license file (counted_Borrow.lic) in the screenshot you shared on reply of 08-Aug?
Hi @npenneti When you use the activation code then it will be a Trusted activatable license and not a License file license am I correct? in that case options file will not work also we can not use the activation code in the license file.
I have heard from my teammate who set up our FnP that he had used a activation code while adding the licenses to FnP, we see a . lic created, also, we had used options file in conjunction with this .lic to restrict licenses checkout to machines and users and it worked.
as the license file was created, I'm considering it as a cert based license instead of a trusted storage based license.
is there a way I can get a new license file from the products download page or else where, so lines like FEATURE be in it?
@npenneti It would be good if you raise a support case and we can have a call to discuss this issue so that we can understand the requirement clearly and help you to fix it as soon as possible.
