ConfigMgr with Smart Windows Installer Source Location Manager

Recently in one of my customer environment, Application packaging team encountered issues with the deployments which required application upgrade or self-healing property. During Application upgrade or repair it prompted for source files. This location was network location which no longer exist and some of them referred CCM Cache which got removed or deleted during ConfigMgr 2012 client migration. In this post we will see how ConfigMgr can handle this issue.

Let’s take the example of chrome package which was installed from file server directly earlier and when tried to repair now it prompted for source files on file server which no longer exist anymore as shown below.

In this scenario to correct the source file location from offline file server to ConfigMgr Distribution point we need to update the product Code as shown below for the application properties.

After updating Windows Installer product code as above, Windows Installer source list update cycle need to be initiated manually as shown below otherwise it will take a while to update automatically.

Verify the log C:\Windows\ccm\logs\SrcUpdateMgr.log and confirm the Install Source URL location is updated as shown below.

Verify the log C:\Windows\ccm\logs\SrcUpdateMgr.log and confirm the Install Source URL location is updated as shown below.

Verify the below registry path and confirm new Key ‘URL’ is created automatically and appended with the DP’s holding ‘Chrome’ package as shown below.

HKLM\ Software\Classes\Installer\Products\\SourceList\URL

Now as seen below I am able to repair the chrome and it is not prompting for the source location...J........Thanks to ConfigMgr Windows Installer Source Location Update Manager