Scense Administrator Guide

  1. Home
  2. Docs
  3. Scense Administrator Guid...
  4. Advanced Application Mana...
  5. Managing App-V Server Configuration Parameters

Managing App-V Server Configuration Parameters

App-V 4.x Streaming Server and Scense.

App-V 4.x is an application streaming solution which conventionally relies heavily on its streaming capabilities. As of App-V 4.5 the applications can either be streamed from a server (RTSP / HTTP) of used ‘stand-alone’. This stand-alone mode involves the App-V application being wrapped in an MSI-package for generic distribution.
Using Scense there’s no need to package the App-V 4.x application into an MSI. Instead the same App-V 4.x application files can be used for either streaming from server or loaded from file. The Scense administrator will decide.

When working with an App-V 4.x streaming server Scense is able to manage the server back-end from the Scense Explorer eliminating the need for maintenance on the server itself.
To enable this functionality the App-V Connection Parameters should be set.
Initially these parameters can be set during the Scense Setup stage, and they can be modified with Scense Explorer.
From the ‘Tools’ tab choose ‘Connection Parameters’ in the ‘App-V’ group.

These parameters are stored as ‘Site Parameters’ for the ‘Default site’. Although the user interface only maps to the parameters for the Default site, it is of course possible to manually overrule these parameters for other sites.

When working with App-V 5 applications there is no streaming server, at least not an active one. Scense Explorer will not interact with the App-V 5 server components because there’s no real need to.
Instead we will instruct the App-V 5 client to retrieve the packages from a certain location.
The administrator can define two paths to the package location, one in UNC format and the other in URL (HTTP) format. The UNC format is mandatory, because this format is used by Easy Delivery and Scense Explorer to provide and access the packages.
The App-V 5 client supports both UNC and HTTP locations. When the HTTP path is specified it will be used by the client, otherwise the UNC path is used to load packages from the server.