Raypack, msi file in all users Appdata
Hi there,
I'd like to place a file of a Installation in the users appdata. the Problem is, we'll deploy with sccm and then it writes the file in system32/System... instead of C:\users\xyz123\appdata\roaming
so, i'd like to copy this file for all users in the appdata Folder. how is this possible in raypack?
and pls, try to explain it for a guy that doensnt know much about packaging :/Answers (4)
Search for John MacFadyen's article about self-healing.
Essentially, the steps are:
- create a new feature called, say, 'CurrentUserData'
- in the new feature, create a new component containing the user profile-targeted data
- ensure that the component has registry data as its key path. If the component doesn't natively have registry data, create some. I use something like 'HKCU\Software\[ClientName]\SelfHealing\[ProductName]\[ComponentName]\[ComponentID]. Export the registry key somewhere where you can access and import it in future - saves having to recreate the key next time.
- find an existing feature which contains an advertised entry-point, normally an advertised shortcut. If the existing shortcuts are non-advertised, create new ones which are.
- if there are no shortcuts or other advertised entry-points, use Active Setup to trigger self-healing.
- move the existing feature in the feature tree so that it becomes a child of your new feature
Done!
hi,
yes, i could solve it with active setup. it was standard disabled in the property table. And then i had the issue, that it only worked for the first installation. if i installed it twice (sccm things..) it didnt worked anymore. i could solve it with a remove script that "kills" the active setup key of the product in the registry..
Thanks for you help
If a second installation was attempted, that installation ought to have failed, since Windows Installer - unless specifically instructed - won't overwrite an existing installation so, what exactly "didn't work any more"?
have a read of the MSI.CHM it should explain directory hierarchy.
It sounds like Raypack is using a variable based on old profiles.
Did you capture the install or add the files??
The appdata roaming folder should be just 'AppDataFolder' in the MSI.
As per the above notes, the component that installs the files will need an HKCU key path. If your package has a shortcut, make sure its advertised, it should all be good. If you don't have a shortcut, you will need to explore the ActiveSetup route. but you will still HAVE to have the key path as an HKCU key.