
emtmeta asked a question.
i have below concerns regarding agent 3rd prty deployment .
suppose the initial agent policy is not downloaded for days due to connectivity issue between agent and beacon server , then
- How often the agent will check the connectivity to beacon server
- Will the agent download the policy immediately once the initial connectivity is established
- Similarly inventory gathering and upload will also be triggered after the agent policy update .
Can you please guide me with the steps of process involved in case an installed agent is missed to communicate with beacon for more than 2 weeks .
Regards,
junaid vengadan
The FlexNet inventory agent uses the following default schedule settings from when it is first installed until the agent has successfully downloaded and applied schedule settings from its policy for the first time:
EventTriggersApply policyOnce schedule settings from policy have been downloaded and applied by the agent, the following schedule details apply:
EventTriggersApply policy- At a random time between 12:05am and 1:05am, then again at a random time between 12:05pm and 1:05pm
- When the computer boots up
- When the operating system detects a new network connection
Update beacon failover setting details- When policy is applied
- At a random time between 12:15am and 1:15am
- When the computer boots up
- When the operating system detects a new network connection
Generate inventory (and attempt to upload it)According to settings configured on the Discovery & Inventory > Settings page in the webUI. For example:

Upload any files that have been unable to be uploaded previouslyI'm not sure if some details here may vary based on version of FlexNet Manager Suite, but these details are accurate at least for current versions (as of mid 2020).
For a more advanced approach to installing the agent with additional default schedule settings that apply before (unless) policy is downloaded, take a look at the following post: FNMS Inventory Agent Deployment