You can rerun the mgspolicy.exe with the -t machine flag. This will force a policy update. This will also help determine if the issue is network related.
These were non UNIX devices. Also I can see that the policy wasn't downloaded on machines we looked at, not sure how to get the policy to download at this point.
Unix devices will retry bootstrapping policy at least once per day. Windows devices do not share this behavior and will only retry bootstrapping policy on device reboot assuming this was a transient issue that will correct on retry.
This is a typical boring behavior of windows agent. If they are not able to join the beacon they stop trying.
Another point I already told, is to check for the log for what URLs are trying on the FNMP.
I've seen on a customer some agents sending the policy request with the "administrator.npl" instead of servername.npl.
Are you sure you're running as a system account or full admin ?
For windows you can use the command sent before or restart the service, which could be pretty easier with tools like puppet..
When addressing agent issues please check the following.
- Make sure the agent package contains the fully qualified name of the beacon.
- Can you resolve the fully qualified name of the beacon from the target device?
- Can your telnet over port 80 or 443 (depending on your configuration) from the target device to the beacon.
- If using https can you reach the default web site from the target device? Do you get cert errors?
- If the beacon is using IIS please review the IIS log. Search for the IP of the device your installing the agent on. (Any errors?)
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.
The files in the attached FlexNetInvAgentUNIXInstallFiles.zip archive can be used on UNIX-like operating systems to install and bootstrap the agent in a similar way to what I described earlier in this thread for Windows.
You can build a complete set of files for the installation by (1) extracting the contents of this .zip archive into a directory, and then (2) adding in the actual agent installers for the version you want to deploy with the following names in the same directory (you only need to include files for the operating system(s) you are targeting):
AIX/managesoft.<version>.0.bff HP-UX/managesoft-<version>.depot Linux (i386)/managesoft-<version>-1.i386.rpm Linux (x86_64)/managesoft-<version>-1.x86_64.rpm Mac OS X/managesoft-<version>.dmg Solaris (sparc)/managesoft-<version>.sparc.pkg Solaris (x86)/managesoft-<version>.x86.pkg
Once you've built your set of installation files in this way, install the agent by copying the files to a target computer running a UNIX-like operating system and running the flexia-setup.sh script with root privileges.
As with the Windows agent install steps described earlier, the 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.
The flexia-setup.sh script will:
- Run appropriate commands to install the agent based on the operating system.
- Apply agent configuration settings specified in the UNIXConfig.ini file
- Configure beacons to be used for bootstrapping as specified in the Bootstrap Failover Settings.ndc file
- Attempt to download and configure beacon failover settings from these bootstrap beacons
- Attempt to generate and upload inventory
- Install the bootstrap schedule settings specified in the Bootstrap Machine Schedule.nds file
- Attempt to apply policy.