-
Bug reporting acknowledgmentYes, I read it Professional supportNone Describe the bugWith this version and the previous one it is impossible to deploy software . The client software remain in the "state and prepared mode while if we put version 1.7.2 on windows everything is ok An idea? Thank you To reproduceWith this version and the previous one it is impossible to deploy software . The client software remain in the "state and prepared mode while if we put version 1.7.2 on windows everything is ok An idea? Thank you Expected behaviorOperating systemWindows GLPI Agent versionv1.14 GLPI version10.0.18 GLPIInventory plugin or other plugin versionGLPI Inventory v1.4.0 Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
|
Hi @falco2001 your issue description seems more a help request than a bug report. So I'm moving it on Q&A discussions. |
Beta Was this translation helpful? Give feedback.
-
|
There's a lot of possible reason why a task remains in prepared status. The first I see when you speak of this still works with v1.7.2 is we changed the default task installed and the Deploy task is no more installed by default since v1.8. If you managed to install silently glpi-agent, you have to add an option to install Deploy task too: |
Beta Was this translation helpful? Give feedback.
-
|
You can verify which tasks are installed running |
Beta Was this translation helpful? Give feedback.
-
|
Hello, on the fleet of 1000 machines with version 1.7 I did nothing everything was in registry keys windows here I have this the machine goes up well and no deployment! I have this: c:\Program Files\GLPI-Agent>glpi-agent.bat -version c:\Program Files\GLPI-Agent>glpi-agent.bat --list-task Available tasks :
target local0: local C:\Program Files\GLPI-Agent target server0: server https://lxc-glpi10-dev.ens-lyon.fr/ I put in the file agent.cfg disable software deployment tasks#no-task = deploy Le 07/05/2025 à 10:02, Guillaume Bougard a écrit :
|
Beta Was this translation helpful? Give feedback.
-
|
by entering in the registry keys:
|
Beta Was this translation helpful? Give feedback.
-
|
no I had not installed the overall I have everything now I will have to test the deployment! Available tasks :
target local0: local C:\Program Files\GLPI-Agent target server0: server https://lxc-glpi10-dev.ens-lyon.fr |
Beta Was this translation helpful? Give feedback.
-
|
j have this : |
Beta Was this translation helpful? Give feedback.
-
|
Redirect loop means what it says. There's a wrong redirection somewhere. Maybe this is related to an address set as "Base URL" into the "Assets" frame on your entity configuration. |
Beta Was this translation helpful? Give feedback.
-
|
j have : |
Beta Was this translation helpful? Give feedback.
-
|
what should you put in root entity url agent and what should you put in registry key with version 1.14? |
Beta Was this translation helpful? Give feedback.
-
|
ok it was not necessary to put from/ after the glpiinventory url in the registry key. Put the complete package otherwise no deploy and in the registry key the same as before and entity idem as before on version 1.7 |
Beta Was this translation helpful? Give feedback.
There's a lot of possible reason why a task remains in prepared status. The first I see when you speak of this still works with v1.7.2 is we changed the default task installed and the Deploy task is no more installed by default since v1.8. If you managed to install silently glpi-agent, you have to add an option to install Deploy task too:
ADDLOCAL=feat_DEPLOYas this is described here