Separate servers per groups

[tahdesign1]

My contract houses all of the ADSK software in the house but there are several that are not in my domain or organization.

IT has made a separate server to place an LMTools install on just to house these other seats.

So I intend to have a separate license file produce just for these seats.

Lots of places I see it stated to get a single license file for ALL of the ADSK products on contract but I need to separate them.

Is there any issue with that?

[Mark.Lancaster]

@tahdesign1

Under that condition you will need to create a distributed license model and allocate license (up) to 3 different servers.

[tahdesign1]

Right so my intent is to split my license into two unique license files that are on two unique servers.

[TravisNave]

You can do that but it would be easier to manage a single server controlled
by and options file that splits access. I can assist you with that if
you'd like. Otherwise, I would recommend that your NLMs exist on different
domains/subnets and are not accessible to the other users, respectively.
Does that make sense?

[tahdesign1]

So here is my issue in a nut shell.

On my contract I have two other groups products plus my own.

I am with the MFG eng groups and we have the vast majority of the seats on my contract.

I configure, install, teach, and maintain all of our workstations and vault server but not the other groups.

I only have admin right within my groups workstations and servers.

That being said, the other groups (Production Systems and Product Eng) that have ADSK software on my contract are handled by our IT group.

I want these are separate servers for licensing so that I am not ties to them for my upgrade and the like.

I will supply the IT group the necessary installation media for what they handle and also the properly created license for just those products.

---

@TravisNave wrote:
Otherwise, I would recommend that your NLMs exist on different
domains/subnets and are not accessible to the other users

---

The IT group has already made a new server just to house this instance of LMTools. It is virtual and I can see it VMware but I do not think my users can or would know how anyway. However, I do think that this new server is on the same domain as my current server

[TravisNave]

I don't foresee this being a problem so long as the clients from one group
can't take the licenses from the other server.

[tahdesign1]

Well they are uniquely different products.

All of my seats are either Product or Factory designs seats using Vault Pro.

The other two groups are just running pure AutoCAD and a couple of seats of AutoCAD Design Suite with no Vault involved.

So products being different we should see no issues.

[Mark.Lancaster]

@tahdesign1

Well just because you have AutoCAD or AutoCAD Design suite..  If those users are directed to your other license server, they can still pull license from those suites because there's a thing called Network Cascading license.  AutoCAD will not just pull AutoCAD License, it will pull AutoCAD from any other area that contains AutoCAD information.

In addition since you're 2017 license is based on a network type, these license are most like multi-user/term based license.  If that's the case, term license will always get pulled before any perpetual license that you have.  So if the users can see both license server, than term based license will get pulled first from those license server.

[tahdesign1]

---

@Mark.Lancaster wrote:

@tahdesign1

In addition since you're 2017 license is based on a network type, these license are most like multi-user/term based license.  If that's the case, term license will always get pulled before any perpetual license that you have.  So if the users can see both license server, than term based license will get pulled first from those license server.

---

No all of my products are Networked Perpetual Licenses. We upgraded everything and added a few that we may need before the cut off last year.

I also have some I have a few standalone perpetuals that I left on my contract to use on laptops.

So to that extent I have avoided any of this new licensing model thus far. 

[Darin.Green]

As stated by @TravisNave, using two servers for distributing licenses is not necessary because you can use an Options files to control access to those licenses. Now, I understand there are different departments and you're only an admin in your area. However, there should still only be one license manager configured on a single server for what you need. Also, there's not much you have to do on the server side except configure LMTOOLS (5 mins tops) once a year to update the license file and lmtools.

Although the product are unique, they all share the same licensing schema. Setting up another server is not recommended for what you're trying to accomplish, but instead you should be using an Options File.