/build/static/layout/Breadcrumb_cap_w.png

Setup writes in C:\users\public, how to exclude from user pkg file?

I've got a nasty setup which writes about 50 MB data to C:\Users\Public\AppName. This location is captured by the MS sequencer in the user profile; %AppData%\SoftGrid Client\bladiebla\UsrVol_sftfs_v1.pkg. So the roaming profile limit is reached very quick. Is there a way to tell the sequencer to place these files in the sft (machine) part?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: pjgeutjens 12 years ago
Red Belt
3
If it's just a setup log (i.e. not linked to the actual application's function) I'm pretty sure you should take the file out of the sequence alltogether..

Comments:
  • If in the other hand you actually need that data in the package, you should probably script a copy of that data from the package to the real user profile directory pre-launch, so store it somewhere else in the package (not VFS) and then copy it to the actual location on the client.

    Might also be worthwhile to check if the application won't just regenerate the data if you leave it out of the sequence - pjgeutjens 12 years ago
  • The application really needs the data. These files are updated frequently. But the option to make it part of the "real" C:\users\public is a good idea. Will search further to find a 100% App-V solution. If I can't find it I'll copy it. - subsense 12 years ago
Posted by: subsense 12 years ago
Purple Belt
-1
Excuse me for triple post, it seems an issue with out new proxy

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ