I am installing MSI from network location. During repair application is looking for MSI which exists on network location and user dont have access to it. Issue occurs only when application is distributed through SCCM. Local repair works ok.

I cannot use SourceList property as the application may reside on multiple servers. I tried ADDLOCAL and ADDSOURCE properties, no luck.

Is there a way around it?

Thank you.
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 normally indicates that there are files that need to be put in place during the repair. For anything else the repair will use the stripped version of the MSI that is cached in <WinDir>\Installer.

What you can do is use the DuplicateFile table. Put all files that go into a user's profile into the programfiles directory and then make duplicates using the aforementioned table that go to the profiles. Have a look through this thread on appdeploy to get a good idea how to go about this.

Another option might be to set SCCM to do a 'download and run' installation of the software, instead of installing directly from the network.

Answered 12/13/2011 by: pjgeutjens
Red Belt

  • Download and run installation will cache the application source for the time of installation and then will remove it.
    It will again start searching for source files again.
Please log in to comment
It is recommended that for this application you write a script to locally copy the source from server while installation to a local directory like: C:\Windows\DownloadedInstallations\ and then run the application from there with the script.
This way your source will not be deleted and the repair can happen.
Answered 03/21/2012 by: piyushnasa
Red Belt

Please log in to comment