Files in AppData for exisiting users
Hi,
I have created a package which delivers common runtime files to Program Files but then the user files are set to every user's \AppData.
This works fine when I do an install and also when a new user logs onto the machine the correct files are copied to the new profiles AppData when the application is first run from the shortcut on the desktop. The problem is with users who already had profiles when the install was done, if they use the shortcut it is launching the userfiles under the profile of the original installee and doesn't install the user files to their profile. Any ideas greatly appreciated.
Tim
I have created a package which delivers common runtime files to Program Files but then the user files are set to every user's \AppData.
This works fine when I do an install and also when a new user logs onto the machine the correct files are copied to the new profiles AppData when the application is first run from the shortcut on the desktop. The problem is with users who already had profiles when the install was done, if they use the shortcut it is launching the userfiles under the profile of the original installee and doesn't install the user files to their profile. Any ideas greatly appreciated.
Tim
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Babadog
15 years ago
No we just run a library file in users AppData, with the shortcut launching the common runtime and then the users own lbr. I have got the path to the libraries being stored in HKCU and that installs correctly, it is just the libraries that don't.
Posted by:
AngelD
15 years ago
Any component installing files under the user's profile should have a HKCU registry entry as keypath for its component, is this true for you?
Posted by:
anonymous_9363
15 years ago
To my mind, the app is reading the location of the libraries from somewhere and that somewhere is pointing at the wrong user's profile folder. As RJ alluded, does the app use an INI or something like that to store the path data? Perhaps a registry value in HKLM? As usual, a process/file/registry monitor will show you exactly what the app gets up to.
Posted by:
jcarri06
15 years ago
If the installation is working fine when a new user logs on but not existing users, it could point to the existing user haven't conflicting data/config/registry causing a bit of trouble. Have you tried to force a self heal under a user who's not working correctly? If forcing a self heal works, you could look into putting an entry into ActiveSetup to trigger it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.