The App-V Streaming Model addresses the needs of businesses that want to use Application Virtualization with the streaming capabilities but might not have or want the infrastructure to support Management Servers. Unlike the App-V Management Server, the App-V Streaming Server does not use SQL Server or a management console. These servers use access control lists (ACLs) to manage user access.
Use App-V Streaming Model:
·Where ConfigMgr 2007 SP1 with R2 is already in place and the organization will use it for managing virtual application publishing and delivery.
·Where Active Directory or SQL Server-based servers aren’t present, but the organization still wants to take advantage of streaming virtual applications
Its intended use is deployment in branch offices: it can stream FB1 and FB2 data to clients that require additional data, and it can be used to authorize application usage in branch offices. This means that a client can launch an application from an OSD file that points to a App-V Streaming server. The Desktop Configuration Service of the App-V Management Server may also be used in conjunction with the App-V Streaming Server, so the Management Server configures the application, but the Streaming Server delivers it.
A desktop configuration refresh could mean the transfer of several hundreds of kilobytes of dataper client, per refreshover a WAN link when no App-V server was present in the branch office (and even with a App-V server present, there was still some chatty behavior between the SQL backend and the Management Server).All these problems are remediedby pointing the clients towards the local App-V Streaming Server that uses a WAN-bandwidth efficient mechanism to keep the content in sync.
The following picture shows a typical deployment scenario for a App-V Streaming Server in a branch office.
The App-V client is connected in the branch office. Here is the remainder of the configuration
·The main office contains a App-V Management Server, which uses the well-known SQL and AD backend, and uses a fileserver to host the SFT/OSD/ICO content.
·The branch office uses a App-V Streaming Server that uses a non-specified algorithm to keep its local content directory in sync with the content fileserver in the main office.
·The client is configured to perform a desktop configuration refresh against the App-V Management Server in the main office, which delivers the list of applications that the user has access to.
This makes the advantage of having App-V Streaming Server in branch offices clear immediately. A desktop configuration refresh could mean the transfer of several hundreds of kilobytes of dataper client, per refreshover a WAN link when no App-V server was present in the branch office (and even with a App-V server present, there was still some chatty behavior between the SQL backend and the Management Server).All these problems are remediedby pointing the clients towards the local App-V Streaming Server that uses a WAN-bandwidth efficient mechanism to keep the content in sync.
