The FlexNet inventory agent bootstrapping technique for Windows that @mfranz has alluded to is to use the MSI transform and associated files attached here.
The Word document contains details of what the MSI transform does, but a summary it will help with :
- Installing a bootstrap schedule that is different from the default bootstrap schedule. For example, your bootstrap schedule may be configured to be more aggressive in how often it reattempts to make an initial connection to a beacon to download policy. This can be helpful to mitigate situations where the agent gets installed at a point in time when the agent cannot connect to a beacon.
- Installing a failover settings package containing settings to use a number of beacons for agent bootstrapping (instead of just a single beacon).
- Attempting to connect to a beacon to download policy settings to be applied as part of the agent installation process.
- Gathering inventory and attempting to upload it immediately at agent installation time.
A sample msiexec command line to install the agent using this transform and associated files is:
msiexec.exe /i "FlexNet inventory agent.msi" TRANSFORMS="InstallFlexNetInvAgent.mst" GENERATEINVENTORY=YES APPLYPOLICY=YES BOOTSTRAPSCHEDULE="Bootstrap Machine Schedule" BOOTSTRAPFAILOVERSETTINGS="Bootstrap Failover Settings" REBOOT=ReallySuppress /l*v "%TEMP%\FlexNet inventory agent-install.log" /qb-
The attached sample Bootstrap Machine Schedule.nds file encodes event details that include:
- Re-attempt to connect to a beacon and apply policy every 5 hours and upon a new network connection. Once policy has been successfully applied, the bootstrap schedule will be replaced with the regular operational schedule as per the agent policy settings.
- Generate inventory daily.
- Attempt to upload any files awaiting upload every 13 hours and upon a new network connection.
The attached Bootstrap Failover Settings.ndc file encodes details for a number of beacons to be used for bootstrapping. You will need to edit this file so that it contains beacon details appropriate for your environment.
All files should get placed in the same directory as the FlexNet inventory agent.msi file.
@rclark0 - that is a somewhat long and indirect answer to your original problem. From your description it sounds like many agents were installed at a time when they could not successfully connect to a beacon (for whatever reason - the reason may not be important if it is transient). However on subsequent reboots the agents are re-attempting and succeeding to connect to a beacon, and the backlog of unreported agents is slowly going down. Using a different bootstrap schedule that re-attempts connections at other times and not just upon reboot as described above may have sped up the process of getting agents reporting.
Thank you, but we only have one Beacon in this environment, the connection is there but the Flex agent software cannot connect to the beacon
Hi @ChrisG ,
I tested your solution with the modified .nds file and is working fine, now I have only 1 package which I can distribute, regardless of which beacon is available.
I wonder if such a solution exist for Linux/Unix packages, because for this I still need separate packages in BSA, to target specific beacons.
Thank you for your support and I wish you a nice day.