Thanks Brianna!

Hi Brianna,

Do these server and forms licenses auto renew in LFDS 10.4.x? I can't see any mention of it in the release notes/list of changes?

Cheers!

Hi Brianna,

This is fantastic news.  It has definitely been a pain to have to replace every LICX file when renewing licensing.  May I ask why only Forms and LF server?  Would this include the web client? 

We have RIO and subscription clients who use QuickFields, Connector, Web Client, Discussions, etc.  Are all of the components on the roadmap to auto-replace the licx at some point?

It's mentioned in the LFDS list of changes

Directory Server 10.4 introduces the ability to send notifications to registered instances of Laserfiche Forms 10.4 and Laserfiche Server 10.4 when there is a change in the master license. Choose between sending the update notification immediately or during a scheduled time window. Laserfiche Forms and Laserfiche Server can then attempt to automatically retrieve an updated application license.

We picked LF Server and Forns server because they are critical points of "failure" if a subscription license isn't updated and to imrpove the process of reallocating resources (e.g., public portal licenses) but we are considering expanding it out to other applications.

Generally, when a system is upgraded, the application installers should support getting an updated license directly from LFDS. 

Can you share some of the cases where you would use this feature for other products?

Thanks Brianna, missed that! Good to know.

Hi Brianna,

We've tested this on a few of our subscription customers at the time of renewal, and the master license (primary license now) updates automatically, but the LF server itself never updates the license file at c:\program files\Laserfiche\Server\Lf.licx.

Are we saying that this should work from your previous update, as in our testing this has never been the case on any site so far running LF 10.4.x.

Cheers!

Hi Chris,

You are correct: it should work if you are on 10.4.x for both the Laserfiche Server and LFDS.

If you are not seeing the license update, a few troubleshooting tips:

1. Verify that the licensing notifications are turned on under general settings and have the settings you expect:

2. If LF Server received the notification but failed to update the license file, an error should be logged to the event viewer

• If no error is logged, the message from LFDS may not be reaching the Server. Try double-checking the port settings for the LF Server instance within LFDS + checking network settings for the request
   

3. If you have a spare user license, you can check whether LF Server is receiving the message and updating its cache but failing to update the license saved to that file path

1. Add a user license to an LF Server instance and save. This should trigger a message, but you can be extra certain by manually triggering the message with "send relicensing notifications"
2. View the license allocation count in the repository administration console: if it goes up by one, then LF Server is at least receiving the message and updating its cache

4. If the message is received but the license is not updated, the development team suggested that it could be a permissions issue

• Try manually moving the license file to C:\ProgramData\Laserfiche\Server . This path is also checked by LF Server when it tries to update, so no additional changes are necessary
• You can also move the license to a different directory (not Program Files, not ProgramData) and modify the registry key that tracks the license location. This registry key is set during install, and can be used to choose a non-standard license file location.