When working on clients system, we were working with a temporary Master license for LFDS. A new Site was created under the temporary license. When switching back to the production Master license, we were receiving errors saying that the Site ID was mismatched. So is the Site connected with the Master license? If not, what causes the error we were saying? We were using LFDS 10.3.1.
Question
Question
Answer
Yes, the licensing database is associated with the master license that was used during its creation. You cannot use a different master license with a different SiteGuid with that database.
Are there any plans to handle clients who are on demo licenses that then convert to full Rio licenses? Every time this happens, we have to completely reconfigure LFDS and setup all the users and groups again just because the master license changed.
Can we submit a feature request to activate a new master license with an activation key without needing to start over with LFDS from scratch? Or perhaps somewhere that the SiteGuid can be updated when importing a new master license file?
Any updates on a workaround/solution for this?
I have a Client that is moving their Laserfiche System to a new network and domain. They are working to secure test license for this so they can validate the process.
They also plan to 'transition' from Windows accounts to SAML accounts for authentication. So using a copy of the existing LFDS database with a potential test license will be vital from implementation.
Following up here to ask the same, is there any update on this? I'm about to migrate a client to new servers, and during this we're moving from RIO to Subscription. I'd like to install in the new environment using their new license, test everything, and then cut-over their migration DBs and data. If what I'm understanding here is accurate, I won't be able to use the prior RIO DB in the LFDS that I installed in the new environment using the subscription due to SiteGuid conflicts. How can we ensure I don't run into this issue as it'll delay everything if we have to recreate the settings in LFDS by hand.
I'd say perhaps use the same RIO license to setup the new environment. And then once you're ready to cutover, then you can update the license to subscription.
That won't work for us because RIO only permits a single LFDS installation, and we need to keep their current environment active while we work on installing and testing the migration. But I like the way you are thinking!
Understood. I am assuming that for some reason you don't want to use the current Production LFDS application to license the new environment?