Deploying applications to an App-V Streaming Server involves copying the sequenced packages into the Content share and providing them with proper access control list entries. Then, edit the registry to configure the App-V Desktop Client to use an App-V Streaming Server. It can also be configured using the App-V Group Policy template for large-scale deployment of App-V Streaming Servers.
The content share is a normal file share on the App-V Streaming Server. The Content folder can be located anywhere on the server’s files system. By default, a Content folder is created in C:\Program Files\Microsoft System Center App Virt Streaming Server\content.
Note Microsoft recommends relocating the Content directory at the top level of a local data partition (D:\Content) rather than on the system partition. Also, the content directory should be located on the App-V Management Server rather than on a separate file server, DFS server, and so on. Customers have experienced significant performance and reliability issues when locating the content on a separate server.
The App-V Desktop Client still requires a connection to App-V Management Server. The connection with the App-V Management Server will provide application usage and enforce log usage and the refresh interval policy. When the client has satisfied the management requirements to stream applications, the client retrieves the OSD and ICO files from the local App-V Streaming Server. The local streaming server has been configured in the client’s registry.
To manually configure a client computer, open the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration registry subkey in Registry Editor (Regedit.exe), edit the values shown in Table 199, and then restart the client computer.
Table 199. Values for Manually Configuring the Client Computer
Registry value |
Configuration data |
Explanation |
ApplicationSourceRoot |
RTSP://STREAMING_SERVER_NAME_FQDN:554 |
This is the RTSP path to the App-V Streaming Server. If the server is a secure server, remember to use RTSPS with port 322. |
IconSourceRoot |
\\STREAMING_SERVER_NAME_FQDN\Content |
The share name on the App-V Streaming Server or URL from which the client will copy icon files. |
OSDSourceRoot |
\\STREAMING_SERVER_NAME_FQDN\Content |
The share name on the App-V Streaming Server or URL from which the OSD file will be streamed. |
A Group Policy administrative template is also available to configure these values on a large scale. For addition information on importing the administrative template, see the Windows Server 2003 or Windows Server 2008 documentation. Note that there is no need to modify the sequenced application OSD files after the client has been configured: The client automatically overrides the OSD default streaming server.
Related Topics