I have run into some challenges with source control and Autodesk Apps, or any app that isn't installed with an MSI. After the installation of the Autodesk product (using .exe installer), the URL key is added in the registry, and any subsequent updates to the app try to access the URL source. But it fails because the URL key doesn't point directly to the original MSI, just the content source folder (the MSI may be buried in subfolders).
I was hoping SCCM would update the NET key as well, so it could pick up the source from our net share, the same location SCCM gets it from. This does not appear to be the case.
The workarounds I found are as follows:
1. Deploy a reg key that updates the NET key to the proper source location.
2. Use the following command in an app with no content: msiexec /I \\server\source msi location PATCH=\\server\MSP-or-other-update-location
Any ideas? The reg key seems to be the cleanest, I'm just surprised SCCM offer this as a built-in option, seeing as how you can never rely on the SCCM cache to be available.