Networknet archive Blog

App-V: Stream virtual applications from a file share

Originally published 2 comments

App-V supports several options for streaming an SFT deployment file. RTSP, RTSPS, FILE, HTTP and HTTPS are available for the Server URL.

I currently use RTSP and am evaluating the FILE option to store virtual packages on a file share. I want to replace the App-V streaming servers with file shares.

I imported my new Jing virtual application into the App-V management server and refreshed my local App-V client to publish it.

The icon appeared on the desktop. When I opened the shortcut, I immediately received the following "Application Virtualization Error".

The Application Virtualization Client could not launch Jing 2.4.10231.1521.

The operation failed because you do not have sufficient permissions to stream from a file. Report the following error code to your System Administrator.

Error code: 4615186-14902204-0000180B

AllowIndependentFileStreaming had not been set when the App-V client was installed.

ALLOWINDEPENDENTFILESTREAMING = 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.

To allow streaming of an SFT file from a file share, change the following registry value to 1 and restart the "Application Virtualization Client" service.

Code1 line
1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration\AllowIndependentFileStreaming

I used the following script to update my clients and allow FILE streaming:

Code3 lines
1
2
3

reg add HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration /v AllowIndependentFileStreaming /t REG_DWORD /d 1 /f
net stop sftlist
net start sftlist

References

1 comment

Comments from the original WordPress site, kept read-only.

  1. Tim Mangan

    If you are still publishing from the App-V server, I don't see the point. RTSP will support disruptions in the streaming process that CIFS will not. Even if you do want to go that way, I would recommend a client ASR ("FILE:\\server\share") override in the client registry while keeping the OSDs pointing to RTSP (makes it easy to cut over without editing the packages, and to change back). You still need the registry setting you identified at the client. In either case, with file: you still get the app fully cached (whether created with a small FB1 or not), and a form of "active update". The kicker is that you can't replace the file on the server without a maintenance window, and is better not to have the _2.sft naming.

    If you do get rid of the App-V server completely, then you will also need to disable RequireAuthorizationIfCached setting, and probably set LimitedDisconnection timer to zero (although I am unclear if that last one is truly needed), and possibly add permissions depending on how you get the virtual apps there. Stand-alone client is a great way to go!

1 mention