Suggested Actions

Suggest an improvement

Submit a request for new functionality or enhancement to an existing feature that would make the product behave more efficiently or extend its capability.

For Example:

  • I would like to see products differently.

  • I would like to see the product do something new.

  • I have an idea for how the product could be improved.

Open a support case

Create a new support case to get help with a problem you may be experiencing. This if the product behaves in a way in contravention to the documentation or displays an error visibly or in any log files or debug.

For Example:

  • I cannot get the product to work the way i want.

  • I donot understand something about the product.

  • I believe I have discovered a problem with the product.

This website uses cookies. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.
OK
kimberly_snyder
Flexera beginner
‎Jun 14, 2019 09:28 AM

FlexNet Agent Change in Beacon

We have a customer who is moving from one FNMS instance to another and will be changing beacon servers as well and have a question regarding the agents currently installed. What is the best method to repoint the agent to the new beacon?
0 Kudos
Reply
3 Replies
tkuivala
Flexera
Flexera
‎Jun 14, 2019 09:57 AM

Re: FlexNet Agent Change in Beacon

Hi Kimberly!

 

You can change the application server of the old beacon to the new application server, this should make sure that all agents will know both beacons.

Once you are fairly confident that all agents have updated their policy, you can delete the old beacon. You can also create an A record just to divert any strays to the new beacon.

Make sure that the new beacons FQDN is resolvable by all clients prior to deleting the old one however.

 

Would this approach work for you?

Reply
mfranz
Shining star
‎Jun 14, 2019 10:34 AM

Re: FlexNet Agent Change in Beacon

Hi Kimberly,

There are multiple possible approaches. Goal of most of them is to create a transition phase for the agents to catch up with the changes in the infrastructure. Here are two:

  1. Keep existing Beacons and integrate them into the new environment until all clients have fetched updated policies & settings. Then remove the old Beacons.
  2. Provide the agents with additional download and upload locations before switiching to the new environment. Then when the switch happens, every client should have the data to connect with the new Beacons. This can be accomplished by adding "fake" Beacon data to the Beacon_MT table, so they are distributed to all existing Beacons and Agents. Of course, it only makes sense if you already have names and protocols of the future Beacons.

Alternatively, you could push the new Beacon details to all machines registries via script, after the new environment went live.

Best regards,

Markward

Softline Group is Europe's leading independent expert in Software Asset Management.
Reply
ChrisG
Community Manager Community Manager
Community Manager
‎Jun 16, 2019 05:57 PM

Re: FlexNet Agent Change in Beacon

One strategy which can be useful in some scenarios is to deactivate an old beacon and the configure a DNS entry pointing the old beacon's name to the new beacon's IP address. This will allow existing agents using the old beacon's name to get to the new beacon with one single centrally managed change.

(Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)
Reply