Please excuse my translation (or lack of !).
That would seem to be something like 'failed to execute the virusscan msi package' ?
This would suggest the agent has done it's job - which is to get the package to the client machine but now the client cannot execute the msi installer locally for some reason.
I'd find the local msi log generated by the instaler and take a look at it for more detail.
It's not failed to execute the msi package, it's "An error has occured while downloading VSE870.msi"
Thank you for the translation, it helps
In that case I suggest you have a look at the text version of the agent log file on the actual machine.
Find the same time period, hopefully this will contain more information than the remote XML log.
The log you can view from the ePO server is really only a summary.
Hard to say from that unfortunately.
I'd suggest stop running the deployment task every policy enforcement, just schedule it instead (can't be sure if this is set, but since it looks like deployment runs every asci i'd say it's likely).
Make sure you only have one product in the deployment task. Sometimes trying to chain multiple installations isn't a good idea. I can't tell if you have set this or not, just asking !
Check the obvious - enough free disk & temp space on the client. Validate a local install outside of ePO is successful.
You might be best off opening a support call to look deeper though.
Thanks for your help
The task was set to run every 15 min from 9 am to 5 pm, and it is the only product installed.
Space is not an issue and the package files manually downloaded works fine.
I'll try and call the tech support.
Again, thanks a lot