Serial number and License Server

[Anonymous]

Hi all, have a bit of an issue regarding multiple serial numbers and a license server, I'll try to explain as clear as possible:

I work for a big multinational with offices all around the world and I'm creating an Acad 2017 deployment that I hope to use in multiple countries.

Problem is that each country has it's own licensing system and thus has ordered his own instance of Acad and created his own license file. So we have multiple license servers, but I'm trying to manage this with the ADSKFLEX_LICENSE_FILE system variable.

My question is: Can I create a package with a serial number from country A and use that deployment in country B that has it's OWN license server, with a license file that has absolutely no reference to the serial number I used? Does the license server care about the serial that I used to create the deployment? Or does the license server only grant licenses to installations that have a serial code that was used to generate the license file?

I hope this was clear enough.    

Thx

[Otto]

Hello Jeroen.Debehets and welcome to the Autodesk community!

It looks like you need to get a License File. Community members with similar questions found the following article(s) useful:

Requesting a Network License File

If this information was helpful, please consider marking it as an Accepted Solution by clicking on the "Accept as Solution" link, below. Taking a moment to do this will help others with similar questions find useful answers. Thank you!

Kudos (click on the link or the "thumbs-up!" icon), are also gratefully received! (Even a bot likes praise.)

If this answer missed the mark, please let us know so that other community members can lend a hand. Any additional details might help, too: consider including relevant screenshots, log files, error messages, or system specs.

[Anonymous]

Yeah, license servers are configured, no problem there. So not really a solution ^^

[Mark.Lancaster]

@Anonymous

The auto-bot tries to assist.. 

Activation is really through the network license file so it really doesn't matter which serial # is used in the deployment.   However you have to put in the license server name so some installation will have an incorrect license manager listed and then it has to be adjusted using the system variable you have indicated.  My concern is that someone installs using the deployment and then doesn't change the license server location and well you could be in trouble if you don't have a global license agreement.  Meaning someone overseas is using a license for the states.

@TravisNave any other thoughts?

[Anonymous]

Yeah, he probably does his best ^^ 

Regarding the license server: We have two pilot countries and our plan was to deploy the sys variable via GPO to both countries, setting the correct server for each. And leaving the License server name in deployment blank.

My only concern was that the license file in country two has been set up with a completely other account and thus a serial that has nothing to do with the original. 

[Mark.Lancaster]

@Anonymous

Unless something has changed for 2017, "And leaving the License server name in deployment blank" this is not possible.  Without putting a license server in the deployment creation steps, you cannot continue until it contains a related name.

[TravisNave]

Agreed.

Sorry for the delay, btw.  What you could do is create a license server path pointing to 127.0.0.1 or localhost so that it has something listed.  It should error stating it cannot find the NLM, but it will let you pass.  You can then use the ADSKFLEX_LICENSE_FILE variable to direct the installations where you want them to go and/or modify the LICPATH.LIC with a batch to do the same.  Alternately, your setup INI file that will be created for your deployment will also have the path to the NLM.  You can modify that after the fact to if need be.

Hope one of those helps.

Good Luck!

[Anonymous]

Thanks for the help guys.

@Mark.Lancaster Something must have been changed then, because I was definitely able to create the deployment by only filling in the serial, and leaving the server field blank. I could also install Acad fine from this deployment, but got the (expected) no-valid-license error when booting Acad.

@TravisNave I can't for the life of me find any NLM path in either one of the .ini files...

I guess I'll have to test the deployment in both countries, approach I'm thinking to take:

1. Create deployment with serial from country A

2. Single license server, leave field blank

3. Set license server vial system variable

4. Deploy correct variable with GPO to each country (server A for country A, server B for country B)

This seems like it could work. Unless you guys have anything further to add?

[markcalloway · Accepted solution]

Hi,

You can use any serial number in the deployment as this has nothing to do with the licensing.

If you can leave the license server name blank then using GPO to create the system variable for each location sounds like a good way of do this.

Let us know if you run into any issues.

[truongquocloc9]

need support