cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Useful to install FlexNet agent if there is no connection with beacon yet ?

Hello all,

For a proper installation, you need to verify if you have a connection to your beacon so it can download at first connection the policy from that beacon.

If it not succeeds to do this, will it try again (constantly) till he gets the policy? So it will download it when connection is established?

This can be useful for rolling-out the agents in project phase waiting on firewall rules to be set. 

Regards, frank07

(1) Solution
dbeckner
By Level 10 Champion
Level 10 Champion

@Frank07 It depends on the target OS. By default the Windows agents do not check for policy again if the initial bootstrap beacon is unreachable. The only way to force it to check for new policy is to reboot the target device or restart the agent services. The agent for UNIX-like devices is different and will check for policy daily regardless of whether it makes initial connection to the bootstrap beacon.

 

This excerpt is from Page 67 of the Gathering FlexNet Inventory guide. --

"If the policy was not initially available (perhaps because of network issues, or because the inventory beacon
was unavailable when the FlexNet inventory agent attempted to connect, or because policy had not yet been
prepared and distributed from the central application server), FlexNet inventory agent retries policy collection
at each reboot of the managed device until successful. (This behavior is different than for the FlexNet inventory
agent on UNIX-like systems, where it makes a daily attempt to download policy at a random time each day.)"

 

Hope this helps.

View solution in original post

(2) Replies
mfranz
By Level 17 Champion
Level 17 Champion

The default installation method will leave the agent stuck if the bootstrapping process failed (the beacon could not be reached to download and install an initial setting/schedule). Hence it will not try to do anything unless you intervene, e.g. by running the policy client.

And yes, it would be great, if agent default behaviour could be made a bit more robust.

I know, there are quite some workarounds to that. It would just be nice if it was robust by default.

dbeckner
By Level 10 Champion
Level 10 Champion

@Frank07 It depends on the target OS. By default the Windows agents do not check for policy again if the initial bootstrap beacon is unreachable. The only way to force it to check for new policy is to reboot the target device or restart the agent services. The agent for UNIX-like devices is different and will check for policy daily regardless of whether it makes initial connection to the bootstrap beacon.

 

This excerpt is from Page 67 of the Gathering FlexNet Inventory guide. --

"If the policy was not initially available (perhaps because of network issues, or because the inventory beacon
was unavailable when the FlexNet inventory agent attempted to connect, or because policy had not yet been
prepared and distributed from the central application server), FlexNet inventory agent retries policy collection
at each reboot of the managed device until successful. (This behavior is different than for the FlexNet inventory
agent on UNIX-like systems, where it makes a daily attempt to download policy at a random time each day.)"

 

Hope this helps.