Hi everyone, hope you’re doing well.

I have a question about license deployment.

We applied a new license to the customer’s client PC—meaning we converted that user PC into a new license server. Now the customer has two license servers in total: the existing server PC and the newly configured customer PC. We are using FlexNet (host ID = MAC address–based licensing). This is not DSLS, so the situation is different.

The issue is that after rebooting the next day, the newly configured customer PC still appears to connect to the original server PC.

We already checked LMTOOLS and the .ini files, and everything looks correct. By “correct,” I mean the new license is still properly installed and configured on the customer PC, just like the original server setup. However, in practice, the license checkout connection still goes to the old server PC.

How can we fix this?
For reference, the original server PC is running Linux, and the customer has 4 client users.

To summarize:

1. There is an existing license server PC, and we applied a new license to a user PC to make it a new license server.

2. To configure LMTOOLS, we uninstalled and reinstalled FlexNet License Manager and applied the new FlexNet license.

3. In the .ini file, we changed the server direction from the original server PC to the local machine (localhost / PC name).

4. We confirmed the license works correctly.

5. After reboot, all settings remain changed, but the actual connection still goes to the original server PC.