I have two scenarios - one that is successful and one that is not.
I deploy a msi to a test group of 10-12 computers and it installs successfully, according to SCCM (with return code 0) And testing proves it to have been a successful install. I use the following "script" to install
the software:
taskkill /f /im application_name.exe /T
msiexec.exe /i "msi_name.msi" /qn
After testing, I deploy the same exact msi, using the same exact script, to 1500 computers and it installs successfullyaccording to SCCM (with return code 0)
But after that, we find that we are missing a key file (happens to be a DLL) from the msi install. We used verbose logging and the log file indicates that the file was written to disk during the install...
But it is missing and part of the application doesn't work. A repair of the application fixes it and writes the dll to disk.
Any ideas why deploying the same msi, using the same batch file, would fail when deploying to a larger audience?
Would appreciate any ideas!
