Software Deployment

- You should never re-package MSIs. Use a transform to apply changes.
- How are you deploying? If via AD/Group Policy, the install will be silent by default. If by SMS/SCCM or similar, specify the silent switch (/Q[n|b|r]) on the command line which the deployment tool is set to execute.

ok ,
I deploy via AD / Group Policy. If the install is silent by default, why it doesn't work ?

The Event Log will give you a clue but the best way is to enable verbose MSI logging on the target (you can do this via GP) and kick off the deployment again. Logs end up in %SystemRoot%\TEMP (not %TEMP%), prefixed 'MSI' and with a .LOG extension. This is an all-or-nothing policy so ALL MSI activity ends up being logged (so remember to disable it once you're done).You'll need to search the logs for unique text to determine which pertains to this install: use the package's ProductCode.

The salient part of an MSI log will be the dozen or so lines above and below the first occurence of the string 'Return value 3.' Post those lines here. Use the CODE tag - button is marked 'CODE' or '<%' depending on your browser), otherwise your post will be too unwieldy.

I am so so so stupid. The path of the MSI files was not good ! I am so stupid sometimes !
Thank you !

FFR, there is a dedicated 'Group Policy' forum here on AppDeploy. It's a sub-set of this forum. See the very top of the page for the link.