Reinstall package won't install files
Hi!
I've created a small package with user-specific files and registry entries. The package is to be installed with SCCM or manually with an admin account. To solve the problem with the HKCU entries, I've also set up Active Setup in the registry, and that works just fine. Now I need to find a solution for installing the four files that every user need in their profile folder. I've tried things like reinstalling the package, repairing the package, but the files just won't show up. I've also tried to manually run the installer but it won't work either.
The only way I've succeded is when I've uninstalled the package and reinstalled it manually logged in as the specific user but that will not solve my problem as the other users then will lose their files.
So...my question now is: isn't there any way to reinstall the package with Active Setup for every user that logs in and get the package to install the files in his/her profile folders?
Hope u guys understand what I mean... :)
Thanks!
I've created a small package with user-specific files and registry entries. The package is to be installed with SCCM or manually with an admin account. To solve the problem with the HKCU entries, I've also set up Active Setup in the registry, and that works just fine. Now I need to find a solution for installing the four files that every user need in their profile folder. I've tried things like reinstalling the package, repairing the package, but the files just won't show up. I've also tried to manually run the installer but it won't work either.
The only way I've succeded is when I've uninstalled the package and reinstalled it manually logged in as the specific user but that will not solve my problem as the other users then will lose their files.
So...my question now is: isn't there any way to reinstall the package with Active Setup for every user that logs in and get the package to install the files in his/her profile folders?
Hope u guys understand what I mean... :)
Thanks!
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
WiseAppPackager
13 years ago
Are you sure that you have populated ActiveSetup correctly?
What entries have you included there?
What entries have you included there?
Posted by:
DarthNiN
13 years ago
Hi!
Thanks for the reply.
I think I've set up everything correctly. I've tried a couple of entries, like "Msiexec.exe /fpu {Package code} /qn", "Msiexec.exe /fauvs {Package code} /qn", "Msiexec.exe /i {Package code} REINSTALL=ALL REINSTALLMODE=vomus", and a few things more. All I get to work is to install the registry entries...NOT the files.
Even if I skip the Active setup and run the installer manually it won't work if it's already installed logged in as another user. I have to first uninstall the app, and then reinstall it again for each user....but that means I'm removing the files for the other users. Seems like the files can only exist in ONE users profile at a time...
Any ideas?
Thanks for the reply.
I think I've set up everything correctly. I've tried a couple of entries, like "Msiexec.exe /fpu {Package code} /qn", "Msiexec.exe /fauvs {Package code} /qn", "Msiexec.exe /i {Package code} REINSTALL=ALL REINSTALLMODE=vomus", and a few things more. All I get to work is to install the registry entries...NOT the files.
Even if I skip the Active setup and run the installer manually it won't work if it's already installed logged in as another user. I have to first uninstall the app, and then reinstall it again for each user....but that means I'm removing the files for the other users. Seems like the files can only exist in ONE users profile at a time...
Any ideas?
Posted by:
pjgeutjens
13 years ago
Kristian,
have you given the component(s) containing the user files a HKCU regkey as keypath?
also, when triggering the repair, do the users have access to the original install location from which the msi was installed? Since you're looking to copy files Windows Installer will need access to the full MSI on the original install location.
Rgds,
PJ
have you given the component(s) containing the user files a HKCU regkey as keypath?
also, when triggering the repair, do the users have access to the original install location from which the msi was installed? Since you're looking to copy files Windows Installer will need access to the full MSI on the original install location.
Rgds,
PJ
Posted by:
DarthNiN
13 years ago
Hi!
Yes, the users have full access to the original package, but I thought this triggered the local version of the msi package since I'm not pointing to a msi on a share...or?
Please explain what HKCU regkey as keypath is..?
Thanks!
Yes, the users have full access to the original package, but I thought this triggered the local version of the msi package since I'm not pointing to a msi on a share...or?
Please explain what HKCU regkey as keypath is..?
Thanks!
Posted by:
spartacus
13 years ago
Out of interest, what is the value of the ALLUSERS property in your package ?
Spartacus
Spartacus
Posted by:
spartacus
13 years ago
You mentioned your Active Setup appears to be working for HKCU registry entries, so try moving the four files to an existing component where a HKCU registry value is already set as the keypath.
Regarding your query about HKCU and keypaths, you don't mention which packaging tool you are using, so I'll assume you at least have access to ORCA although if you have any of the the commercial packaging tools such as WISE or InstallShield, they clearly indicate in the interface which resource (file or registry entry) is set as the keypath for a component or if, indeed, one hasn't been set.
So for instance, using ORCA you could review your Component table and look in the 'keypath' column, some will contain values that cross refer to the first column of the registry table and in the latter table, it should be simple enough to find a HKCU entry that is acting as a keypath for a component. Once you have identified a component with a HKCU keypath, move your four files to that component.
Regards,
Spartacus
Regarding your query about HKCU and keypaths, you don't mention which packaging tool you are using, so I'll assume you at least have access to ORCA although if you have any of the the commercial packaging tools such as WISE or InstallShield, they clearly indicate in the interface which resource (file or registry entry) is set as the keypath for a component or if, indeed, one hasn't been set.
So for instance, using ORCA you could review your Component table and look in the 'keypath' column, some will contain values that cross refer to the first column of the registry table and in the latter table, it should be simple enough to find a HKCU entry that is acting as a keypath for a component. Once you have identified a component with a HKCU keypath, move your four files to that component.
Regards,
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.