Guillaume Bougard

Okay, so indeed, this is a problem related to GLPI-AgentMonitor. It fails to access GLPI-Agent service. I think this can happen if the service failed to start or is still...

So maybe the agent installation just failed. @ngaillard-gantois you'll have to verify if agent service is really installed on the related computers. And maybe just reinstalling the agent can fix...

Hi @ngaillard-gantois so the agent service has not been enabled or it fails to start. Can you figure out why ? Is it set to manual starting or did you...

Also check the `Installer` subkey. Then check also the `C:\Program Files\GLPI-Agent\logs\glpi-agent.log` file. Is it empty or is it reporting any error and is it reporting it stops ? Maybe the...

Can you run the script with `cscript` from an administrative console ? This will give you a better log on output you can share here: ``` cscript //nologo glpi-agent-deployment.vbs ```

Hi @ngaillard-gantois just a point I remember, are you eventually using an old vbs ? I mean, did you use the same vbs from an older version for which you...

Hi @MarcSamD > 2. This issue frequently appear on upgrade of GLPI Agent via GPO or scheduled task (both using the new VBS script), when you said "both using the...

To be sure, can you share the Windows OS version for each of that clients ? You can check the MSI log for such property lines: ``` ... Property(C): VersionNT...

Hi @MarcSamD > ``` > Property(N): WindowsBuild = 9600 > ``` Are you telling this problem occurs on a Windows 8.1 OS or Windows Server 2012 ? If yes, can...

Oh yes, I remember now they made some changes against that number. So MSI is not sharing the right buildnumber. Can you test and reproduce the problem with a nightly...