I have to create an MSI of an application that must be assigned to computers in an Active Directory environment using group policy. The software in question requires absolutely that its configuration files are present in the user's application data folder. Of course when doing this, files in the MSI for the application data path go to C:\windows\system32\config\systemprofile\application data rather than any or all user's profiles.

I've experimented with the Active Setup, to run the MSI setting the StubPath key to msiexec /f {GUID}. Whilst this works, the app is quite large and a reinstall of the whole app to copy a couple of files seems inefficient. I've thought of running a batch file or second MSI from the StubPath -- but are these approaches to be recommended?

I've seen with certain MSIs such as Office, where the first time any particular user runs the software, Windows Installer pops up and completes the "user" part of the installation. This seems to be a different mechanism to Active Setup.

I would be grateful for any advice on the best way to achieve this.
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
To only repare userprofile & HKCU use: msiexec /fu {GUID}

Adding a top feature with userprofile & HKCU component resources will minimze the time when the self-healing mechanism checks for broken components.

Auther your userprofile component with a keypath to a HKCU regkey instead of a file. Also make sure not to have mixed User & Machine resources in components.
Answered 11/03/2006 by: AngelD
Red Belt

Please log in to comment
0
Hi inselaffe,
One possibilty would be, to install the config files to the program location and copy them with 'duplicate files' to each profile when they login for the first time after the installation. Either with self healing or active setup. With this you would not have to have the source allways available (But with GPO install this wouldn't be a problem here, except that the users need read permission to the source), because the needed files would not have to be copied from the source location.
Please read this post: http://itninja.com/question/distribution-message21

With active setup, the command line would have to be msiexec /fup {GUID}
(msiexec /fu {GUID} only writes missing registry keys, but no files)

Regards, Nick
Answered 11/03/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Thx for the headup nheim!
Answered 11/03/2006 by: AngelD
Red Belt

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