Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Windows VersionInfo in Agent exe #10

Open
pszafer opened this issue Feb 4, 2022 · 5 comments
Open

Add support for Windows VersionInfo in Agent exe #10

pszafer opened this issue Feb 4, 2022 · 5 comments

Comments

@pszafer
Copy link

pszafer commented Feb 4, 2022

Hi,
Currently after FIA is installed it display same versioninfo as perl interpreter installed
image

Would be possible to add there version info of FusionInventory Agent currently installed?
Then it would be pretty easy to configure agent installation with eg. Ansible without any additional script.
https://docs.ansible.com/ansible/latest/collections/ansible/windows/win_package_module.html#parameter-creates_version

@g-bougard
Copy link

Hi @pszafer
actually, fusioninventory-agent.exe is just a copy of perl.exe. This is handy to do that so you can see a "fusioninventory-agent" program in details runnning programs in place of "perl.exe" for FusioInventory-Agent service in taskmgr.
FusionInventory-Agent being a perl software, you should probably do more than just check an exe version.
The version is really defined in C:Program Files\FusionInventory-Agent\perl\agent\FusionInventory\Agent\Version.pm.

@pszafer
Copy link
Author

pszafer commented Feb 4, 2022

Ok, I know, unfortunately most automated software uses VersionInfo for upgrade process.
Thanks for response!

@pszafer pszafer closed this as completed Feb 4, 2022
@ddurieux
Copy link
Member

ddurieux commented Feb 4, 2022

It can do it, because at each future version, we will update the perl version, except if we create 2 FusionInventory agent release in a very very short in time, the version will be different between 2 versions.

@pszafer
Copy link
Author

pszafer commented Feb 4, 2022

Great, so consider it in next release 👍

@pszafer pszafer reopened this Feb 4, 2022
@ddurieux
Copy link
Member

ddurieux commented Feb 4, 2022

yes, that's it ;)
In couple weeks for the next release (end February I think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants