Hi,
I've always put new licence keys into \\licensing\
However on a couple of our servers I've found that they now have to go into
\\licensing\share\data
to work. I found this out through trial and error, in both cases where I had to do this there was no old .lic key anywhere that I could find.
Why the difference? One of the servers was PP9.5, the other 2017R2 (we have a version of each for regression testing our packages), but another PP9.5 server works fine with just \\licensing\
Also I noted in the latest licence key install notes (for partners) that it said to
1. Select Start | All Programs | BIOVIA | Licensing.
2. Right-click on License Administrator 7.6.x and select Run as administrator.
3. In the dialog that appears, select License Administrator | License File | Install License.
...
However I cannot find License Administrator 7.6.x on any versions of our PP server from 9.1 to 2017R2?
Are BioVia changing the licencing method going forward?
Simply putting the key into the relevant licencing folder above worked though.
Just interested to know whats happening (this was on windows)?
Thanks
Joe
I've always put new licence keys into \
However on a couple of our servers I've found that they now have to go into
\
to work. I found this out through trial and error, in both cases where I had to do this there was no old .lic key anywhere that I could find.
Why the difference? One of the servers was PP9.5, the other 2017R2 (we have a version of each for regression testing our packages), but another PP9.5 server works fine with just \
Also I noted in the latest licence key install notes (for partners) that it said to
1. Select Start | All Programs | BIOVIA | Licensing.
2. Right-click on License Administrator 7.6.x and select Run as administrator.
3. In the dialog that appears, select License Administrator | License File | Install License.
...
However I cannot find License Administrator 7.6.x on any versions of our PP server from 9.1 to 2017R2?
Are BioVia changing the licencing method going forward?
Simply putting the key into the relevant licencing folder above worked though.
Just interested to know whats happening (this was on windows)?
Thanks
Joe