For applications, which may ask for the full source, to copy some files to i.e. the local user profiles to repair, which are not included in the local windows installer cache, we copied to content first to a local location and installed from there (as the ccm cache is never really persistent). It will then use that location to look for files.
Maybe not the best, but an easy and working solution. And the only one I know if always working. From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Mittwoch, 12. November 2014 03:40 To: [email protected] Subject: RE: [mssms] PS App Deployment Kit and MSI Source My thought was to point it to the application content directory or the DP. Jeff Sent from my Windows Phone _____ From: Jason Sandys <mailto:[email protected]> Sent: 11/11/2014 4:11 PM To: [email protected] <mailto:[email protected]> Subject: Re: [mssms] PS App Deployment Kit and MSI Source What would you like to set it to for the repair? Ultimately, it's just populating the values in the registry so you could simply delete them and allow the repair to use the locally cached copy of the MSI (cached by Windows and not ConfigMgr in %windir%\Installer and listed under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\<Product GUID>\SoureList). It does depend on the MSI itself though whether the locally cached copy is sufficient for this and comes back to the first first question? Where else would you point the source list to? J _____ From: <mailto:[email protected]> [email protected] < <mailto:[email protected]> [email protected]> on behalf of Jeff Poling < <mailto:[email protected]> [email protected]> Sent: Tuesday, November 11, 2014 10:38 AM To: <mailto:[email protected]> [email protected] Subject: [mssms] PS App Deployment Kit and MSI Source I am using the PowerShell Application Deployment Toolkit to wrap an install that does the following: * Uninstalls a supporting application * Installs the primary application * Installs the supporting application again Once installed, I would like for both applications to be able to be repaired from Programs and Features. Since there are multiple MSIs involved and my ConfigMgr application is actually the App Deployment Toolkit executable, I can't see a way to use Windows Installer source management. Is there another way to prevent the MSIs from using the ConfigMgr cache location as the source for repair/modify of the apps? Hopefully that explanation makes sense <https://a.gfx.ms/Emoji_1F60A.png> Thanks, Jeff
