%appdata% - Roaming profile
Hi all,
I have a requirement in my application stating an additional file to be installed to the following location -
%Appdata%\Test\Folder\.
The file getting installed to the user-profile, installs fine for all users on launching the advertised shortcut.
Now its all fine for the users having local profiles. But when it comes to a roaming profile the file is not getting installed. I tried using a script to read the value from %appdata% env variable and changing the dirProperty of the component dynamically. Still i can see in the log that the dir property is resolved properly yet the file is not installed. Is there any workouts that i can try or is there any alternative ways to acheive it ???
I have a requirement in my application stating an additional file to be installed to the following location -
%Appdata%\Test\Folder\.
The file getting installed to the user-profile, installs fine for all users on launching the advertised shortcut.
Now its all fine for the users having local profiles. But when it comes to a roaming profile the file is not getting installed. I tried using a script to read the value from %appdata% env variable and changing the dirProperty of the component dynamically. Still i can see in the log that the dir property is resolved properly yet the file is not installed. Is there any workouts that i can try or is there any alternative ways to acheive it ???
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
WayneB
16 years ago
Posted by:
zipsantro
16 years ago
Posted by:
nheim
16 years ago
Hi Rayz,
just use the "AppDataFolder" folder entry.
Then use the "DuplicateFile" table to deploy the file and install it to each profile.
Please read this post from John McFadyen carefully:
http://itninja.com/question/distribution-message21&mpage=1&key=Ṗ
You can use self healing to bring it to the profiles, if you have only advertised entrypoints (shortcuts, file extensions).
If this can't be guaranteed, you should use Active Setup instead.
See: http://www.appdeploy.com/messageboards/tm.asp?m=32877
Regards, Nick
just use the "AppDataFolder" folder entry.
Then use the "DuplicateFile" table to deploy the file and install it to each profile.
Please read this post from John McFadyen carefully:
http://itninja.com/question/distribution-message21&mpage=1&key=Ṗ
You can use self healing to bring it to the profiles, if you have only advertised entrypoints (shortcuts, file extensions).
If this can't be guaranteed, you should use Active Setup instead.
See: http://www.appdeploy.com/messageboards/tm.asp?m=32877
Regards, Nick
Posted by:
rayz_0020
16 years ago
Hey wayne, I did the same way u said it and its working fine.. just cudnt get some time to reply back.. thanks.
Santro, thanks for the reply. But i need to install the file to appdata locally for a local profile but to the %appdata%(in network path) for the roaming profiles. So cant use that...
and Nick. Thanks a lot for tat link. tat was a real gooooood read. Would have to try it yet, as this package is already completed.
Thanks guys...
[:)]
Santro, thanks for the reply. But i need to install the file to appdata locally for a local profile but to the %appdata%(in network path) for the roaming profiles. So cant use that...
and Nick. Thanks a lot for tat link. tat was a real gooooood read. Would have to try it yet, as this package is already completed.
Thanks guys...
[:)]
Posted by:
nheim
16 years ago
Posted by:
jmcfadyen
16 years ago
the appdata folder is in the roaming profile anyway last time i checked.
are you sure this is not "local settings\appdata" ? as this one doesnt roam ?
in that instance you can create an appsearch lookup to indentify the registry key used as the keypath to the component containing the files. When it exists you need to delete the reg key so that the files are dropped on each run regardless of presence.
This in turn creates some overhead but assures non roaming profile locations are also caught during deployments.
So which of these is the lesser evil is your call but it will solve your original requirement assuming the %appdata% folder you mentioned is the non roaming version.
are you sure this is not "local settings\appdata" ? as this one doesnt roam ?
in that instance you can create an appsearch lookup to indentify the registry key used as the keypath to the component containing the files. When it exists you need to delete the reg key so that the files are dropped on each run regardless of presence.
This in turn creates some overhead but assures non roaming profile locations are also caught during deployments.
So which of these is the lesser evil is your call but it will solve your original requirement assuming the %appdata% folder you mentioned is the non roaming version.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.