Stand-alone mode in App-V is useful where you are deploying App-V applications via Group Policy or a 3rd party ESD (using the MSI file), or you have the App-V packages available on a file share and import them with the SFTMIME command.
|ALLOWINDEPENDENTFILESTREAMING||TRUE / FALSE||Indicates whether streaming from file will be enabled regardless of how the client has been configured with the APPLICATIONSOURCEROOT parameter. If set to FALSE, the transport will not enable streaming from files even if the OSD HREF or the APPLICATIONSOURCEROOT parameter contains a file path.|
|REQUIREAUTHORIZATIONIFCACHED||TRUE / FALSE||Indicates whether authorization is always required, whether or not an application is already in cache.|
Importing a Package in Stand-Alone mode
A common scenario for stand-alone mode is to test packages. To import a package in this mode, you can use the SFTMIME ADD PACKAGE command.
The simplest way to use this command is to copy your package to the local computer and using an elevated Command Prompt, change to the folder were the package is located. For example, I have a Mozilla Firefox package stored locally – I can use the following commands to import the package:
CD C:\Common\Packages\MozillaFirefox4_US SFTMIME /ADD PACKAGE:"Mozilla Firefox 4" /MANIFEST MozillaFirefox4_US_manifest.xml /OVERRIDEURL MozillaFirefox4_US.sft /CONSOLE
There are plenty of resources on the Internet that discuss the configuration of the App-V Client in stand-alone mode:
- Stand-Alone Delivery Scenario for Application Virtualization Clients on TechNet
- Microsoft have a TechNet Virtual Lab: Learning to Configure App-V for Standalone Client Mode, this also has a companion PDF document
- Tim Mangan has written a white paper on configuration of the client and deployment of applications in a stand-alone environment
- Alex Verboon has an article on Configuring App-V Standalone Mode through Group Policy
- Finally, you can see the stand-alone mode App-V Client in action in this video by Ruben Spruijt: