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 😊
Thanks,
Jeff
