Windows GLPI Agent 1.10 Install by MSI // Delete C: Security about glpi-agent

[tristangallet]

Adding information : Antivirus is Windows Defender and SCCM Client is installed. OS could be Windows 10 or 11.

[g-bougard]

Hi @tristangallet

... but on 5 Lenovo Laptops, the drive C has lost all the security, so the user can not see it (Access denied) and the system is very unstable.

What do you mean by the drive C has lost all the security ? Do you mean it occurred during installation or the computer can have lost all the C security for another reason ?
Also, by the system is very unstable, do you mean it is only unstable since the installation ?

Anyway, can you also provide your installer commandline ?

In general, a 1603 installation failure is due to an unavailable msi-server service. If you're not using our official vbs, you should use it as it checks since few version the msi-server service is available.

[tristangallet]

Hello, during installation of the GLPI agent, all security rights have been removed from C:
After rights have been removed, people can not log in and use the computer.
We're using Microsoft Policy to deploy the msi, it has been worked since GLPI agent 1.6 without problem.
Using a vbs is not secure because we can not encrypt it.

[g-bougard]

Using a vbs is not secure because we can not encrypt it.

I'm not a MS Policy deployment expert. I just know 70 or 80% of our customers use the vbs without reporting any problem with glpi-agent 1.10.
Also if I understood well, you put the MSI on a shared folder. I imagine this share is secured. Why not putting the vbs in the same place and start it in place of a msiexec command ?

This is up to you to explain us how the installation is processing in you context. We can't guess it. Until you provide more info (like the installer commandline I requested), we can only suppose you're triggering a windows os issue for which we can't do anything. And for now, you provided too poor info, so I can't help to identify what could be the real problem.

A point, you can add an installer option to generate a full installer log: for example /L*V "C:\glpi-agent-install.log", see msiexec windows commands doc for more details.

[tristangallet]

We're not using a command but a policy to deploy it.
To configure the package with the good parameters, we have a policy to add the good registry keys.
It's not a security problem, the share is the same and the security is READ for auhtenticated. We can see the log that the Windows policy has been read. I know that this is poor info, it's not logical and the first time i've seen such a bug. I will test the policy this week on more machine to see if it comes again.

[g-bougard]

What was the latest version you installed without any error ?

[tristangallet]

GLPI Agent 1.9

[g-bougard]

GLPI Agent 1.9

Nothing essential changed between 1.9 MSI & 1.10 MSI. Then as I don't see any issue, I'll move this issue as a Q&A discussion if you have more to share or need some help.