Documentation of implementation the App-V 4.6
Despite already being in an enhanced version, the App-V is still unknown to many professionals. However, it is a tool for virtualization, but instead of hosts virtualizes applications. Your previous name was SoftGrid that product was purchased by Microsoft.
Basically, the App-V allows applications to be "streamlined" and generates a packaged application, extension osd.
Note that the application is installed on the server role "Sequencer" (1 item) that generates the package that is distributed by System Center or by own App-V Server (item 3) for users who have the applications published by rules in ad run by the console App-V (item 2).
It is also possible not to use a structure as complex as the preceding and only one server that drilling and distributes the application, but note that in this diagram use both stations as Terminal Services or RDS (Remote Desktop Service) in Windows 2008.
The advantage of using the RDS/TS to publish the application is that users don’t have to have the application installed in the farm, for example, creating a much more versatile environment when using this template.
The application can be sent to the client both by proprietary protocol (RTPS/S) as HTTP. See the references at the end to use HTTP in the process of publishing and distribution of packages.
ADVANTAGES AND FUNCTIONING
The benefits of App-V begin in fact do not have the installation package on individual machines. With that we don’t need a msi publish in AD or in SCCM. The application is copied in the user’s machine by the App-V client in the first run and dynamically extracted when execution.
As the application sequenciated is nothing more than a witness client which monitors an installation and osd copies all changes created by the installer, the role of App-V client is making the virtual copies of files (dll, exe, bin, etc.) to the corresponding virtual directories and registry keys of virtual form in the Windows registry.
A practical example would be the installation of 3 different versions of Office (2003, 2007 and 2010) on the SAME MACHINE:
- Sequencing server app-V install all 3 versions separately by creating 3 packages containing binaries files, registry keys and other application files
- Using the app-V console called the 3 versions of Office for a user
- The App-V client downloads the 3 packages individually (osd and ancillary files) to a temporary directory content
- The app-v client create 3 shortcuts in season for individual versions, without which the application is physically installed
- Clicking on the icon of each release the App-V client the osd explodes and creates the registry keys and copies the application files, put in a virtual layer
- The application runs and end this virtual layer is destroyed
This usage model will allow to run an application the user does not have "remnants" of your binaries in the operating system, allowing new applications compatible with the oldest.
Another advantage is the undisputed since update to stream a service pack or hotfix the client will not download the entire package, but only the updates. In addition, of course, that when updating the server customers are updated automatically.
WHO IS ENTITLED App-V
The App-V is not sold separately in format FPP (box) as other products. The previous version that is named SoftGrid was part of MDOP package that was composed by other applications.
Now the App-V is sold as part of the package Microsoft Desktop Optimization Pack, as a tool Microsoft Application Virtualization for Terminal Services or to MSDN subscribers.
Hot site of product: http://www.microsoft.com/systemcenter/appv/default.mspx
Implementing App-V in RDS/TS: App-V Remote Desktop Services.docx (119,87 kb)
Publishing and distributing by HTTP: http://blogs.technet.com/b/appv/archive/2010/12/02/guide-to-configuring-microsoft-app-v-to-both-publish-and-stream-via-http.aspx