When deploying App-V infrastructures in many cases it is useful to preload a set or all applications so the users can directly start working. Wilco van Bragt describes what you can do.

 Some scenarios where you would like to preload an application

1. In Terminal Server infrastructures almost all application are used on all servers, so why won't you preload them already.  I also know organizations where the same idea is used for workstations, where enough disk space is available.
2. To minimize bandwidth usage when the workstations are staged on the central location, but are placed on a sublocation.
3. I have seen some applications that function correctly when during operating additional part were streamed, while the function perfectly when the application was preloaded.
4. To distribute the load on the network when a new application will be enrolled (and will be used by the majority of the employers).

Of course you can preload the applications manually, but in larger infrastructures you would like to automate this process. In this article I will describe how applications can be preloaded for the above mentioned scenarios.

Source: http://sbc.vanbragt.net/mambo/index.php?option=com_content&task=view&id=1338&Itemid=192