You are viewing limited content. For full access, please sign in.

Question

Question

Rio: Generating license files over multiple domains

asked on July 29, 2015 Show version history

Hi,

We have Rio License Manager/Directory Server running on a different site on domain A and wish to setup a Laserfiche Server instance on domain B.

When generating a license file for this machine on domain B, we noticed that the lf.lic contains the local host name (LicenseServer="myserver.local") of the Directory server. 

Without modifying the local machines "hosts" file for each server, is there anyway to generate a license file containing the FQDN of the server?

Many thanks,

Dom

 

0 0

Replies

replied on July 29, 2015

What version of the License Manager are you using? Starting in License Manager 8.3.1 (and now into Laserfiche Directory Server) all generated license files will reference the license server using the fully qualified domain name.

0 0
replied on July 30, 2015

Hi Alex,

We're on 9.2.0.567 but the Directory Server is on a completely different site to where the Laserfiche Server on domain B is.

We're hoping to send notifications for licensing over the internet using https when the Laserfiche server connects to the DS for updates.

Many thanks

0 0
replied on August 12, 2015

So far the only fix for this we have come up with is by changing the hosts file on the server and mapping the external IP address of the directory server to the host name found found in the lf.lic license file.

Is there support for Rio in an environment over the internet using https/SSL?

Many thanks,

Dom

0 0
replied on November 18, 2016

With the latest version release 10.1.1.320 I have nearly completed another test of this scenario.

Using a hosts file on the remote Laserfiche server, all works well, but it is going to be dependent on maintaining the host file.

I see during the install of LFDS that enpoints are configured with FQDN, but this information is not stuffed into the license file for the remote laserfiche server that I generate (and it really complains if I edit the license file).

I was just about to see let it run for a few days without a hosts file, but ran into a license problem on LFDS.

In my scenario, I used the FQDN names in the endpoint configuration during the LFDS install and I also used an SSL certificate generated with the FQDN.

Has there been any update on allowing for the FQDN being inserted into the license file?

Thanks...LeWayne

0 0
replied on November 18, 2016

I tested on LFDS 9.2 and 10, and as Alex said, the FQDN in is the license file: they are all machine.domain.com. It must be something specific to your setup. If you open a support case, we may be able to pinpoint what is different between your machine and our machines.

1 0
replied on November 18, 2016

Hmmm, I hadn't read Alex's message clearly.  I am going to try one more thing related to the network setting on the server.

0 0
replied on November 18, 2016

The issue occurs when there isn't a primary DNS Suffix.  Adding a connection specific DNS suffix didn't seem to do the trick.

The server isn't a domain controller or even part of a domain.

I used netdom to add an alternate FQDN and then make the FQDN the primary name.

ie. substitute "myserver" and "mydom.com" for the situation

netdom computername myserver /add:myserver.mydom.com

netdom computername myserver /MakePrimary:myserver.mydom.com

a reboot is required as well.

After this I added a repo user to the server on LFDS and generated a new lf.licx file.  Once place on the remote server and restart the laserfiche service, it knows of the new user and can communicate with LFDS.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.