Hi,

I am packaging for a client who will not have access to the network location where the application is being installed from after install completes. There is a virtual drive created and then deleted. Does anyone know if there is a property that I can set or something to that effect which will ensure that the entire content of tyhe package is installed locally so as to enable repair? Space on the destination box is not an issue but obviously the repair is essential.

Thanks
0 Comments   [ + ] Show Comments

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.

Answers

0
Try ADDLOCAL=ALL

This should force all of the features and components of the MSI to install locally (unless there are other conditions set on them - this you would need to double check in the tables).

The only thing that should then need to repair would be per-user profile stuff like HKCU, which will be stored in the locally cached version of the MSI (C:\WINDOWS\Installer folder)

The only problem might be if there are any files to be copied into the users profile (anything with an [AppDataFolder] target. If this is the case then one solution would be to copy the MSI onto the local machine and have it install from there (?)

Alan
Answered 12/07/2004 by: ab2cv
Orange Senior Belt

Please log in to comment
0
Cheers alan, I did try this but it did not work. I installed using the property and then removed network cables nd deleted some files and it threw up errors about not being able to locate files. Is there anything else I need to set also? Should I set it in the MSI itself or set it on the cmd line?
Answered 12/08/2004 by: Tribes
Yellow Belt

Please log in to comment
0
When you say that you deleted some files, I take it that you were wanting to test that the self-healing mechanism still works?
If so, unfortunately to self heal correctly, the installation needs to always go back to the original source of the install - no way round this unfortunately. The locally cached version of the MSI only contains the MSI tables, not the files, so this doesn't help either.
It sounds like the only way for this to work for you is to use my last suggestion, which is to copy the MSI installer package to the local machine and then have it install from there. That way, the source MSI is always available locally for any repairs.

Alan
Answered 12/08/2004 by: ab2cv
Orange Senior Belt

Please log in to comment
0
Yea I was checking the self repair which did not work. I have created an exe to launch an admin install of the application and then hide that folder so it will be available for repair if necessary and then kicks off the actual install itself which seems to work. Cheers for your help...
Answered 12/09/2004 by: Tribes
Yellow Belt

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