I have packaged all these apps which reside on a network share and want to ensure that the packages deployed to clients, perform self repair/heal locally and not via the source on the network due to comms restraints.
Through my testing, I found that some of the packages deployed via SMS and using a local admin account and testing by deleting a few key files, the advertised shortcut wants access to the network share for the source.

I remember...I think using the property SOURCEDIR=fvomus for a repair or simular. Can someone please help me how to remediate my packages....I had seen the resolvesource action...should this be used in some way?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Hmmm...quite a confusion of terms here...

You probably want to check the 'InstallSource' value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\<ProductCode>.

The ResolveSource action will do exactly that - it checks that the source can be accessed.
Answered 08/26/2009 by: VBScab
Red Belt

Please log in to comment
Hey thanks for the quick reply!
Yeah maybe the resolvesource action is not quite what I am looking for....
I just want to ensure when the package is already installed, that a repair will need not try to locate the network source of the installation (via SMS) but instead look locally.
I thought originally the SOURCEDIR property provided this....but then this let me the resolvesource action which I know is not quite what I am looking for,,,,I have used the installsource value previously in one of my packages but this just provided a profile directory property.
You are right...confusion of terms.
Answered 08/26/2009 by: tron2ole
Third Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity