MSI Self Healing with SCCM
Hi,
We are starting to deploy applications using SCCM and would be grateful for some advise around MSI self healing when the applications are deployed using SCCM.
With SCCM the MSI installer files are copied to the SCCM cache folder on the target device and the applications are then installed from this cache folder. SCCM then regularly clears out the cache folder (to free up disk space) and consequently when required the MSI self healing fails as the source is no longer available.
Any advise would be greatly appreciated.
We are starting to deploy applications using SCCM and would be grateful for some advise around MSI self healing when the applications are deployed using SCCM.
With SCCM the MSI installer files are copied to the SCCM cache folder on the target device and the applications are then installed from this cache folder. SCCM then regularly clears out the cache folder (to free up disk space) and consequently when required the MSI self healing fails as the source is no longer available.
Any advise would be greatly appreciated.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
Tom,
first distinction that has to be made is between repairs that need access to the files in the MSI, and repairs that don't (say only regkeys are being put in place).
If no files need to be repaired, windows installer will actually use its own cached version of the MSI that is kept in <Windir>\Installer, which is a version stripped of all files, but which still contains all the rest of the installer logic.
As for the second case. I believe there's an opion when creating a program for a package in SCCM, called Installation Source Management, which allows you to link an MSI file to a program, and which will ensure that the InstallSource entries on the client machines will be kept up to date with DP information instead of cache data, which should solve your issue.
Kind Regards,
PJ
first distinction that has to be made is between repairs that need access to the files in the MSI, and repairs that don't (say only regkeys are being put in place).
If no files need to be repaired, windows installer will actually use its own cached version of the MSI that is kept in <Windir>\Installer, which is a version stripped of all files, but which still contains all the rest of the installer logic.
As for the second case. I believe there's an opion when creating a program for a package in SCCM, called Installation Source Management, which allows you to link an MSI file to a program, and which will ensure that the InstallSource entries on the client machines will be kept up to date with DP information instead of cache data, which should solve your issue.
Kind Regards,
PJ
Comments:
-
In cases were the application is installed by SCCM - it seems that the app is coded to go look to the sccm server first - Under windows 7, it doesn't seem like the application will go to the installer folder anymore. We lose the application cache during the process because the task sequence is being executed from a boot CD that is also imaging the PC. when the MSI needs to do a self-heal it is trying to get the MSI from the SCCM server that did the original application installation. In our case this has been done by an sccm server at a 3rd party integration provider and the original server is not visible on the network to our users and it is causing the application to fail. Why is win7 not looking to the installer folder first? - craigwb 11 years ago
Posted by:
anonymous_9363
13 years ago
It's worth noting that AppDeploy has a dedicated SCCM/SMS forum.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.