Some issues have been identified for certain customers on the 2019 R2 versions of the beacons and so for On-Premises customers running 2019 R1 or earlier beacons we recommend that you do not upgrade those beacons at this time without a specific reason to upgrade.
You can upgrade your application server and agents and these will continue to work with the 2019 R1 beacons (if they are on separate servers). Our current recommendation is to wait for the June 2020 release FlexNet Manager Suite 2020 R1 before considering further beacon upgrades.
The next release is expected to contain some changes which will significantly improve performance during certain discovery and remote execution operations compared to the performance of beacon versions 2019 R2.
There have been issues with downloading packages and also in some cases (particularly where DNS is disabled in the environment) there have been CPU spikes on the beacons.
This bug also prevents our new agents from getting profile loaded, which leads to a fact that numerous new agents go comfortably numb. In the middle of a service provider transition this is kind of hell break loose for us....
We are a new customer who installed FNMS 2019 R2 on premise, so all our beacons are this version. What options do we have now? Are we required to re-install the entire system at a different version? Or, could just the beacons be re-installed as a different version?
@DiannaB we downgraded each of our beacons to v13.2.0.1104 and left the rest of the system at FNMS 2019 R2. You should be able to download the v13 beacon engine installer from your downloads page.
Did you already checked the IIS Failed Request Logging log file (setup to monitor error code 404) so identify where the agent would like to download the file? The known issue is rather characterized by an error 500 internal server error and wrong file permission.
@DiannaB - if you now have 2019 R2 beacons deployed and are not experiencing any particular problems with beacon operation (such as problematically high CPU usage), then my recommendation would be to stick with what you have and make no changes.
The problems alluded to in this post will not affect most environments - the post is suggesting to avoid upgrading existing beacons to the 2019 R2 unnecessarily or without good reason. The post is not advising avoid all use of the 2019 R2 beacon version, and if you have it deployed and it is operational then that's great.
If you have the 2019 R2 beacon deployed and are having problems then possible courses of action would be to post a query in the FlexNet Manager forum to see what others have done for the particular issue you have observed, and/or raise a case with your FlexNet Manager support provider for advice in relation to the specific problem you have observed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.