Software Deployment

Have the MSI create the installer locally and then add that local location to the Sourcepath list.

WHat is the best way to do this? Isnt registry informtion local by default?

Thanks.

verify the Key in the Component you wanna have repaired.

Maybe the modified key is not a key, if this is the case the entry will never be selt repaired.

but if the key is changed - the whole Component will be repaired.

This is a great topic, because I, too, have always wondered how to FORCE an MSI to cache itself completely locally... but I have never found out how.

I know about adding the local dir to the InstallPath property inside the MSI, but this hasn't worked.

Any ideas?

- Sean Roberts

Maybe I'm misunderstanding the question, but wouldn't this simply be a matter of copying the entire installation package locally first and then kicking off the installation from there? Then the default sourcepath set would be a local one, and if for example your company uses a custom action or macro to set other sourcepaths, you just add a custom action at the end to wipe out any other items? As long as you are copying it locally to a secure location, it would phone home on self-healing, but 'home' would always be local. Or are you looking to essentially just disable self-healing period, regardless of where the source exists?

My original question can be clarified as follows:

I thought registry data (HKCU for example) could be recreated without access to the original source (i.e. phoning home). What situation would cause an install to need the original source for registry data?

I know how to avoid it doing this, but I wanted to understand the why.

Thanks.