Hi everyone,

I am currently working on installing an application to my Vista workstations, and I have run into a bit of a problem.

The MSI that I am attempting to install from a shared resource will deploy, and install via group policy, but will crash when we try to execute the program. I have also created a batch script, run locally as administrator, logged onto the domain as administrator and the same thing occurs. Please see the script below;

runas /user:domain.name\administrator "msiexec /i \\domain.name\Release\Software\Folder\install.msi /passive /l* c:\log.txt"

I have tried this with, and without the run as parameter, with the same result.

The interesting part is, if I manually navigate to the .msi file and run it (just a simple double click), it will install, and run without any problems at all.

Can anyone please shed some light on the reason why this is occuring. As you can imagine, it is extremely inpractical to have to goto every machine and manually install this software, and doing so via group policy, or even a logon batch script, is a much more realistic idea.

Thanks in advance!

DEFINITLEY A FAILED INSTALL THE PROGRAM CRASHES, I WOULD COMPARE THE FAILED INSTALL AND THE GOOD INSTALL YOUR MISSING A FILE OR TWO FER SURE CHECK THE DIRECTORY SIZES AND ALSO DO A SEARCH ON ALL FILES THAT WERE CHANGED OR MODIFIED FOR 1 DAY ONLY THE DAY YOU INSTALL BOTH REMOTE/SHARED AND LOCAL/LOCAL SYSTEM..... IF YOU HAVE ALL THE FILES AND THE SIZES ARE THE SAME ITS GOT TO BE A REGISTRY ENTRY COMPARE THE FAILED AND GOOD LOAD YOULL FIND THE ANSWER,,,