Code Library

AutoLoad packages
One of the new features in Version 4.5 of App-V is the AutoLoad settings in the registry. These settings are created during the client installation and can be adjusted. By default, when a user logs on, the client attempts to load all previously used applications in cache. This ensures all features for are available locally on the computer. For mobile users, this option enables them to leave the network and still be able to use any application that has previously launched. However, this does not give them access to published applications that have not launched before. The AutoLoad options can be modified to download all applications published for a user and can also be triggered by a background publishing refresh.


Application streaming with Streaming Servers
Another new component in Version 4.5 is the Streaming Server. The Streaming Server does not provide the publishing refresh process. It relies on another resource to perform this operation. The publishing refresh process is achieved by implementing a Management Server to handle the publishing refresh and using the Application Source Root (ASR) setting on the client to point to the Streaming Server. You can also use the manifest.xml file created during sequencing to script the package publishing using SFTMIME. These options provide flexibility in remote office scenarios. Streaming Servers implement authorization via NTFS permissions.


Application streaming with File Servers
A file server can deliver packages in an App-V infrastructure, but like the Streaming Server, it cannot provide the publishing refresh process to the clients. As previously noted, this is accomplished by providing a Management Server for the publishing refresh process. This file server could be an actual server or a powerful desktop. File servers implement authorization by using NTFS permissions.


Application streaming with IIS
IIS can also be used for streaming. However, like the Streaming Server and the File server, it cannot provide the publishing refresh process to the clients. The client supports a publishing refresh over an HTTP/HTTPS connection. However, App-V currently has no Web-based publishing refresh service. So the IIS streaming option would require a Management Server to publish applications. IIS Servers implement authorization by using NTFS permissions.


Stand-alone mode with MSI
The App-V Sequencer supports creation of an MSI during the sequencing process. The stand-alone option does not have a formal publishing or streaming procedure. The MSI contains the ICO, OSD, and Manifest. xml files that are necessary for publishing the application on the machine and importing the SFT file into the App-V client cache. However, the package file (SFT) is not created as part of the MSI. It should be placed in the same directory as the MSI to successfully complete. You can place SFT files on a file server. In this scenario, the administrator uses the SFTPATH parameter to specify an alternate location of the SFT file. This removes the requirement that the SFT file to be in the same directory as the MSI. In Stand-alone mode the package will be published and the SFT file contents will be loaded into the client cache completely.


Streaming mode with MSI
Another option is to use MSI packages and choose to stream the SFT file from an alternate location. In this configuration the package is published, but the SFT file is streamed to the App-V client cache. The process of streaming the SFT file is done by default as part of the installation of the MSI, but could optionally be configured to happen when the user launches the application the first time. This mode enables the features of streaming, such as Active Upgrade. The following registry key value must be set on the client to enable Streaming Mode supporting MSI deployment:

HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client

» Configuration\AllowIndependentFileStreaming ¼ 1

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation