Starting with XenDesktop 7.0 Citrix has made Microsoft App-V 5.0 as its default solution for Application Streaming.
This guide introduces Microsoft App-V 5.0 to existing Citix Streaming Customers. Familiarity with Citrix Application Streaming (CAS) and relevant terminologies is assumed. This document deals with Administrative components. User experience is not covered.
This document applies to App-V 5.0 RTM, App-V 5.0 SP1 and App-V 5.0 SP2 at the time of writing. App-V henceforth refers to App-V 5.0 (RTM, SP1 or SP2).
Document points you to links which will help in configuration of App-V components.
Detailed information about integration , App-V 5.0 is provided in references section.
CAS had 2 mandatory and 1 optional components for deployment of CAS applications. Streaming Profiler was used to capture changes during installation in a “CAS Profile”. When Streaming Client will be pointed to these changes, it will extract them and use them to launch application using environment details specified by CAS Profile. If CAS applications are to be delivered via Citrix Receiver then CAS applications need to be deployed on XenApp.
App-V 5.0 has components similar to that of CAS.
1.1 App-V 5.0 Sequencer = Citrix Streaming Profiler
Using the Citrix Streaming Profiler, an Administrator runs the setup of Application A to create Citrix Streaming Profile for that application.
The equivalent App-V component is App-V Sequencer. Usage of App-V Sequencer is detailed here
1.2 App-V 5.0 Client = Citrix Application Streaming Client
When pointed to valid CAS Profile on Network Share, Citrix Application Streaming Client used to “stream” needed files to machine and used to execute applications contained within CAS Profile. App-V 5.0 has equivalent component called App-V 5.0 Client. Details about deployment and usage are mentioned here
1.3 App-V Management Server + App-V Publishing Server = Citrix XenApp
Citrix XenApp is used to deliver CAS applications via Citrix Receiver. XenApp is used to configure Icon, File Type Associations and Users for a CAS application. When a user points Citrix Receiver to this XenApp server, the user receives this application.
This metadata management role is played by App-V Management Server and Publishing Server. Administrator configures Users, File Type Associations etc. in App-V 5.0 Management Server.
App-V Publishing Server is the interface App-V Client uses to access application data. URL of App-V Publishing Server is provided during configuration of App-V Client.
2. CAS Deployment & App-V 5.0 Deployment
3. Connection Groups in App-V = Inter Isolation Communication in CAS
CAS executed applications in tightly isolated bubbles called Sandboxes. Application running in one sandbox could not see or access application running in another sandbox.
CAS allowed users to link multiple different profiles together. Applications in these linked profiles could access each other. This was called as Inter Isolation Communication (IIC).
Similar concept in App-V is called as Connection Groups. Connection Groups work similar to IIC in CAS. Two packages connected by Connection Group can see each other and use each other’s services.
Connection Group should be used wherever customer has used IIC earlier. E.g. Office + Adobe.
Overview of IIC:
4. Why App-V 5.0 over Citrix Application Streaming?
- Sequencing of App-V is easier than CAS Profiling
- App-V 5.0 offers better programmability via PowerShell cmdlets.
- App-V 5.0 lets you connect App-V 5.0 packages on the fly using Management server. CAS users needed to create a separate profile for IIC.
- App-V 5.0 Sequencer-Client does not separately install Microsoft Visual Studio Redistributables. They are carried as a part of package.
- App-V CALs are included in RDS CALs since Windows Server 2008 and later.
Citrix XenDesktop and Microsoft App-V 5.0
- App-V 5.0 Integration with XenDesktop7.0
- Tips/Tricks for Using App-V Integration with XenDesktop 7.0
- Microsoft Paper on App-V 5.0 and Citrix
Citrix XenDesktop 7.x
Microsoft App-V 5.0