License manager problem

It's all in documentation - it should be straight forward.

In the past LGTO didn't recommend mix usage of license manager and licenses from NW (unless it had to be set it up that way).

To confirm that your server has obtained its licenses from the license manager server, look in the "Registration" window for your Networker server and look at the enabler codes - if the enabler codes all start with something like "EXT-GEMS-............." then you are using the license server.

If you don't see this, then you need to make sure that you've:
a) deleted all of your old licenses from within "Registration" on your Networker server
b) configured the "license server" value in the properties of your Networker server, and
c) set "Update licenses" to yes.

Saying all that - we found a bug in the license manager included with Networker v7.2.x whereby Power Edition Storage Nodes would not be automatically picked up by Networker servers, and we had to leave that one authorised on the original Networker server to make it work.

HTH,
John

I just ran into the issue of the License Manager not updating appropriately after converting one Data-Zone to Capacity Licensing.

Here is what happened.  I moved the Licenses from Data-Zone-A to be converted to Capacity licensing to a License Manager Server without AUTH codes.

I configured Data-Zone-B server to use both Local and Server Licenses.  I saw the additional client capacity.

Everything was good and on track.

I did the Capacity License update 1 week later and let them sit there for a week or 2.  No issues.

Went to REHOST those Traditional Licenses from Data-Zone-A to the License Server so they could be used by Data-Zone-B

After the Traditional licenses had valid AUTH codes I notices that Data-Zone-B did not reflect the changes.

I deleted the "EXT-#" license in the Data-Zone-B server and then went to the Server Properties to "Update Licenses".

Within a few seconds I have a new "EXT-#" connection to the License server and the capacity was more in line with what I expected to have.

- This is in a v7.6.1 infrastructure.