I copied a .MSI to 5000+ systems and then used the following command line running as a program advertisement from SCCM to install the software:

msiexec /i c:\software\App120\App120.mis /qn

All this MSI does is replace all files within the application folder with new files. It ran fine on 1600+ systems but on 700+ the program replaced all the files with the exception of a single file. I checked the properties of the file that was not replaced and the only attribute that was set was Archive.

The ConfigMgr log (execmgr.log) shows the install as successful. Nothing appears in the system logs either. I then ran the install again on one of the failed systems using "msiexec /i c:\software\CM120\CM120.mis /qb /l*vx c:\cm120install.txt" and then reviewed the resulting text file. Again no errors were reported and the MSI log reported install success.

This is driving me nuts. Any ideas as to why 2 systems sitting next to each other in an office would have one work perfectly and the other replace all the files with the exception of one file which, as luck would have it, prevents the app from working properly?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


this might sound silly ,,,, but can you cross check again your cmd line . - msiexec /i c:\software\CM120\CM120.mis /qb /l*vx c:\cm120install.txt" ......
you mis-spelt "msi" twice in your post.
Answered 11/03/2011 by: egkr
Senior Yellow Belt

Please log in to comment
My guess would be that the file in question is a non-versioned file (e.g. a TXT, XML or something that's NOT a DLL, EXE and so on) and that the file in your MSI is older than the one on the machines.

The safest route for a package like yours is to add the containing folder to the RemoveFile table. That way, the entire folder gets deleted before the InstallFile action executes.

I imagine that if the command line had contained that typo, God and his angels will have intervened to install the package on 1600+ machines. :-)
Answered 11/04/2011 by: VBScab
Red Belt

Please log in to comment