![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How Licensing Works Topic Summary: Created On: 12-Apr-2007 22:00 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
HELP!! Need run down on how exactly licensing works from the client's perspective. I believe I had this understood for v5.2 of DOORS, lost track of it for v7.1, and now we are migating to v8.1 and our install package I suspect is in error and I'm going to need to understand it such that I can automatically fix clients that have poor licensing.
We've got licensing in place on the server OK. I'm conserned with what it looks like internally on the client. Of particular interest are the 'LM_License_File" and "TELELOGIC_License_File" environment variables, and whether these change depending on which user is currently logged in. Also of interest is the Registry Entries for FlexLM found here on the Registry: HKEY_Local_Machine\Software\FLEXlm License Manager\TELELOGIC_LICENSE_FILE, as well as of course the corresponding HKEY_Current_User value. - Louie |
|
![]() |
|
![]() |
|
When we converted from v7.1 to v8.0, there was no issues with the FlexLM licenses. So I do not understand your issue?
|
|
![]() |
|
![]() |
|
Louie, I had reason to investigate this recently after we moved our license server to a different machine and I had to work out what needed to be updated on each of the client machines. All of my clients use windowx XP, so I cant comment for Linux etc. As far as I could work out, the only thing that made any difference at all was the regisrty entry for HKEY_Local_machine\Software....The environment variables seem to be left over from older windows 95 implementation but seem to be innefective now. I updated 200+ clients to the new license server address in the registry entry, and have had no problems since then (about 4 weeks now). Rgds
Andrew.
------------------------- Andrew Tagg Thales Air Systems, Melbourne Australia. andrew.tagg@thalesatm.com |
|
![]() |
|
![]() |
|
Yes, if DOORS v7.1 is working you can install v8.1 without specifying licenses, so long as you reboot the client after install. Yes, if you run the license utility and specify the license port@server, it works.
But there is a problem for v7.1 licensing when you intend to install v8.1 and change the licensing, or when you just plain need to change the licensing. The license utility appears to append the specified port@server to the end of whatever exists (at least it used to do that), making it hard to change licensing, something that's required by law ..err.. legal government contract for those of us working on more than one project in more than one database. Since rerunning the license setup is a little unrealistic and requires admin rights to the machine, I'm looking for another way to quickly swap out licensing, and to do that I figure I need to mess with environment variables as well as Registry entries, requiring me to understand how that all works. I thought I understood when v52 was in use here, but the internals seem to have changed for v7.1 and again for v8.1. For example, now the variable is 'Telelogic_License_File' and not 'LM-License-File', even thought the later seems to work. - Louie |
|
![]() |
|
![]() |
|
I vaguely remember doing somethign like this with a Login Script (kixtart) to make the registry change. I can't remember exactly how we changed the environment variables but it was through Group Policy in the Active Directory. I don't think it is a built in feature of GP; one of our IT guys may have modified/installed a 3rd party package to assist in updating all the clients variables.
Hope this helps. Craig ------------------------- Craig Forant me@craigforant.com |
|
![]() |
Telelogic DOORS
» Administration
»
How Licensing Works
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.