| > What are the advantages of actually specifying the license server name
> Lan Manager Licensing Agent Setup for NT 4.0?
The advantage is that if your license server is not in the
local network, not providing the name will cause it to fail.
> Does it speed up obtaining or verifying a license?
It may slightly speed up obtaining a license. This is assuming
that the name you give is for a License Server that is working
properly and has the licenses you need. Otherwise it might
slow down obtaining a license.
Providing a name (or names) will do nothing to speed up (or
slow down) verification.
> Could someone give an overview of what how the agent works, if the
> server is specified, does it look at only this license server.
No, but it does put the named server at or near the top of
the list.
If you want to group licenses, use license groups.
> Although not recommended, if there are multiple servers how is that
> handled?
Who doesn't recommend multiple servers? They are harder
to manage because they have no remote management interface
but they provide for fallback in case one of the servers
is down when you need a new license.
Multiple servers are done like multiple transports, first
come - first served.
|
| > Who doesn't recommend multiple servers? They are harder
PATHWORKS Guide to Managing PATHWORKS Licenses
Page 2-2
Digital recommends that you use a single PATHWORKS license server to
provide licenses to all clients requiring a PATHWORKS license in a LAN.
...There is no technical reason why you could not use...multiple
PATHWORKS license servers per LAN...However, using a single PATHWORKS
license server per LAN, at least to start, provides a good degree of
local control while keeping the administrative activity to a minimum.
Also, the use of too many license server can produce performance
degradation.
|