[mdt] MSI fails (1619) during build. Run manually (same credentials/path/options) it works?

[pete]

So a couple of MSIs (3 out of ~15 or so) throw up a 1619 error (can't find that MSI/path) when being pushed as part of a task sequence via MDT.

 

Using the same credentials and options manually, the MSI installs fine.

 

I've changed one of the installers to use an explicit UNC path rather than the relative path to the MDT share as Google suggests that may improve reliability for troublesome installers in MDT.

 

Does MDT do something daft that I'm unaware of? Chokes on certain MSI switches (everything's using a basic msiexec /i whatever.msi /qn)?

Edited August 23, 2016 by pete

[pete]

OK,

 

Sort of a fix. Certain MSIs choke on the .\applications\appfolder\ thing that MDT does by default if there's multiple folders (admin install point, for example).

 

The fix (found on a random Symantec KB for deploying one of their agents) is to strip out the leading "." and try it again.

 

YMMV.