Virtualization

The program, unfortunately, does not have any method of defining the location of this temporary folder, it is hard coded into the program.

Here's the holdup... when we play the recording back, it comes back choppy, very choppy.  All I can assume is that it's saving the recording to the virtual drive on the APPV server, inside the virtual TMP folder.

Can I some how force it to use that C:\Program Files\Whatever\TMP\ on the local drive instead of streaming that data back and forth?

Am I off in how I'm assuming things are happening?


Matt, you're little bit off with your assumptions.

App-V packaged applications won't stream cached data between client and the server (there's one virtualization technology called InstallFree which by my understanding actually has this model, but not App-V). At worst, the data in question is being stored in the locally cached virtual environment (i.e. PKG files), which shouldn't incur the latency issue you are seeing but I cannot think of any other explanation.
Additionally, if the recording files are very big, there's additional size-related limitation (little over 100 MB can be cached) for data inside PKG files which you could eventually be hitting. But the thing is, nothing gets copied to/from server related to actual application use/its files (once the data in the actual package is streamed down).

If your application is indeed saving the recording data to one of its subdirectories and it's not changeable, there's sadly nothing that can be done at App-V level to redirect it to the physical system. In this case, the data is saved to inside client's PKG files.

br,
Kalle

Hi Matt,

Are you able to define that folder from within the app? If so, point it to a directory which exists on the client (by that I mean a dir which either already exists or one which you create via a pre-launch script for example) and ensure that directory is excluded when sequencing..

Cheers,
Danny