Software Deployment Question
MSI cache locations and deploying with SCCM
We have switched assets, configuration management and deployments from BMC Marimba to SCCM 2012
Now when we are deploying MSI's everything is fine, untill we need to repair an application through ARP.
When we had marimba , we had a msi cache directory that marimba referenced.
In my screenshot below, this is what I see when I am trying an ARP repair. Its referring to the SCCM msi cache that is no longer available. My SCCM guy is telling me its how the packages are made and they need to be fixed.
My main questions and concerns are:
Do we need to create/modify vendor and our MSI/MSTs differently?
Is there a way in SCCM to handle these properly for the self heals and ARP repairs to work?
Will Active setup work ?
Will advertised Self Healing key still work?
I thought these functions took place from %WINDIR%\installer