Why is "Do Not Allow License Request" disabled?

[Daklu]

I have a Dev Suite w/Automated Test Named-User license assigned to me that I typically like to keep reserved for my main dev computer.  I have a test station computer that has a computer-based LV 8.6 and a computer-based Test Stand Dev System license.  Unfortunately the test station computer always uses my named-user license unless it is already being used by my dev computer.

According to documentation I'm supposed to be able to use NI License Manager to prevent the test computer from checking out my named user license using the "Do Not Allow License Request" option, but it is always disabled.  Any ideas?

[Gist]

Per the License Manager help, "This feature is available only for concurrent licenses hosted by a network license server. If you are using managed concurrent licenses, you must have permission assigned on the network license server. Contact your volume license agreement software administrator for assistance assigning permissions."  Are your licenses concurrent?  If so, are they managed or unmanaged?

[Daklu]

Ahh... I missed the word "concurrent" in there.  No, we do not have concurrent licenses.

So my follow up question is, how can I make the test station computer default to use the computer-based license it has been assigned rather than my user-based license?

[Gist]

Hello,

I would like to set up a test machine to make several different attempts at achieving the behavior you have mentioned without concurrent licenses.  I have a few additional questions for you in order to facilitate this process:

1. What is the exact Developer Suite purchase you have?  You mentioned it includes the Automated Test bundle, but is it the Standard or Professional version of Developer Suite, etc.?
2. Which product are you trying to launch (TestStand, LabVIEW, or both)?

Thanks in advance!

Message Edited by Gist on 12-12-2008 11:34 AM

[Daklu]

DevSuite comes with Labview Professional so I don't know what the difference between "DevSuite Standard" and "DevSuite Professional" is.  Regardless, we have Developer Suite 8.3 with Image Acquisition and Machine Vision and Automated Test.

Setup Details:

• Both computers (my dev comp and the test comp) are connected to the network.
• I'm logged on to both computers using my network credentials.
• I have a named-user DevSuite 8.3 license assigned to me.
• The test computer has a computer-based Labview 8.6 Full Dev System with Mathscript license and a computer-based TestStand 4.1Dev System license assigned to it.
• I believe the test computer LV installation was done using a network DevSuite installer.  (I suspect that's the root of the problem.)  I don't know if the test computer's TestStand installation was done using the DevSuite installer or a TestStand installer.

VLM Results:

• Starting TS on my dev computer first uses the DevSuite license.
• Starting LV on my dev computer first uses the DevSuite license.
• Starting TS on the test computer uses the computer-based TS license.
• Starting LV on the test computer incorrectly uses the DevSuite license.

I suppose if I ran the regular LV installer on the test computer it would switch over to that license instead of my DevSuite license.  Ideally there would be a way to define which license to use if more than one valid license is available.  (Command line switches?)  98% of the time I want the test computer to use the LV Full license, but there's that 2% of the time when I need to use the DevSuite on it.

[Gist]

Daklu,

I noticed that this final post had never been replied to for some reason and wanted to make sure to follow up with you.  I was unable to determine a workaround for this issue.  It appears concurrent licensing will be the only available solution in this instance.  Again, I apologize for the amount of time it has taken for a reply.