MSI Options displayed on MDT deployed image

[Johno]

Issue:
When trying to run an installation from a compressed executable, the
executable extracts to the temporary directory, then displays the MSI command
options page. This is not related to customised packages, simple downloading
the executable from a web site and trying to install it. On the clients
previous Windows XP image (using Ghost) they can run the executable and
install the application without a problem.

Examples:
Blackberry client software
VMWare infrastructure client

Workaround:
My current work around is to copy the expanded files in the temp directory
and then running the msi package.

Environment:
The image is Windows XP SP3, includes Windows Installer 4.5 and all Windows
updates.

How can I correct this, so that installations from compressed executables
work correctly?

Thanks in advance for your assistance.

[Dave Guenthner [MSFT]]

A few troubleshooting thoughts. MDT is running the installation from
network so I would manaully verify that via UNC from the client you can
install the packages without issue. Then I could create a custom task
sequence and add a gather, then the application. In this way, you can map
a drive to deployment point from client and run LiteTouch.vbs, test rapidly
without having to endure the entire OS load. Once you have it, add that to
your deployment task sequence.

Also try using:
msiexec /i %~dp0setup.msi /qb


Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

[Johno]

The applications are not getting installed via MDT, they are additional
applications that IT user have/are downloading and installing on their own
machines. I know I can add these appliactions to the MDT process but thats
not fixing the issue. They also have tried to run these install apps from the
network and copied locally, with the same result

Post by Dave Guenthner [MSFT]
A few troubleshooting thoughts. MDT is running the installation from
network so I would manaully verify that via UNC from the client you can
install the packages without issue. Then I could create a custom task
sequence and add a gather, then the application. In this way, you can map
a drive to deployment point from client and run LiteTouch.vbs, test rapidly
without having to endure the entire OS load. Once you have it, add that to
your deployment task sequence.
msiexec /i %~dp0setup.msi /qb
Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights