Switch Agent upgrade from Third Party Tool to FNMS Automatic Deployment

[mrasch]

Hello guys,

we would like to change our approach of upgrading the FNMS agent to higher versions. Instead of using third party tools like the Ansible Tower for the UNIX devices, we would like to use the agent auto self upgrade feature of FNMS.

In the documentation, it is not recommended to do that if a third-party tool was used for the deployment.

"Avoid using automatic deployment by FlexNet Manager Suite when you are using third party tools to deploy FlexNet inventory agent, as conflicting specifications of the version to deploy can cause damage to the existing installation and upgrade failures."

@https://docs.flexera.com/FlexNetManagerSuite2022R2/EN/WebHelp/index.html#topics/InvSet-InvAgentVerCautions.html

Has anyone done this before and can share his/her experience?

KR,

Max

[mag00_75 · Accepted solution]

We have a very mixed environment, some that we run completely with third party and some with third party initial deployment followed by automatic deployment. Your third party deployment needs to be configured so it will not try to downgrade the agents again. And even if you have configured it in the right way we sometimes get agents that gets broken. 

My recommendation is to run some tests based on your environment, you can create target rules that only apply for certain device names/ip ranges etc and you will see how it goes. However Debian package is not possible to upgrade in case you use that, but RPM works.