Flexera Agent Version Numbers

[sgillette]

Is there any reason why the Flexera Agent Version Number says  2019 R1 on the Inventory Device Properties page when you display the installed applications but it references  13.7.zxxx   when you use the Inventory Agent Status page??

Which number should we standardize on?

[mfranz · Accepted solution]

Hi Sean,

I guess the reason is that the agent belongs to a specific FNMS release. And while the release has a "readable" version, like 2019 R1, it also needs a "technical" version with major an minor versions. I created a list  for myself a while ago:

• 13.3.*        2019 R1-HF1
• 13.2.*        2019 R1
• 13.1.*        2018 R2
• 13.0.*        2018 R1
• 12.4.*        2017 R3
• 12.3.*        2017 R2
• 12.2.*        2017 R1
• 12.1.*        2016 R1 SP1
• 12.0.*        2016 R1
• 11.5.*        2015 R2 SP5
• 11.4.*        2015 R2 SP4
• 11.3.*        2015 R2 SP3
• 11.2.*        2015 R2 SP2
• 11.1.*        2015 R2 SP1
• 11.0.*        2015 R2
• 10.3.*        2015
• 10.2.*        2014 R3
• 10.1.*        2014 R2
• 10.0.*        2014

I might have missed some recent developments though.

Best regards,

Markward

[Kevin_Hou]

Hello @sgillette 

ARL library tries to use 'market release year' number on the application title , eg: 2019 R1.  The internal version from raw title evidence contains code/build code formatting etc.  Such convention is also used by other vendor such as Microsoft For instance "Office 2013" the internal evidence version you will see is 15.0.xxx ; "Office 2016“ could be 16.0.4266.xxx

While personally I agree with you that from that 'Agent status' page it's better to use Application Title's version which is 'market release' version  "2019 R1" rather than internal program version eg: 13.1 which is hard to map/remember which year of release it was. 

Best Regards

Kevin