INTEGRATING VIRTUAL APPLICATION MANAGEMENT WITH APP-V 5 AND CONFIGURATION MANAGER 2012 SP1

(1)

INTEGRATING VIRTUAL APPLICATION

MANAGEMENT WITH APP-V 5 AND

CONFIGURATION MANAGER 2012 SP1

(2)

Introduction

Page 1 of 61

©2013 Microsoft Corporation. All rights reserved. This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

Some examples are for illustration only and are fictitious. No real association is intended or inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

(3)

Introduction

Page 2 of 61

Introduction

System Center 2012 Configuration Manager helps IT empower people to use the devices and applications they need to be productive, while maintaining corporate compliance and control.

Configuration Manager 2012 provides a unified infrastructure for mobile, physical, and virtual

environments that allows IT to deliver and manage user experiences based on identity, connectivity, and device. Configuration Manager 2012 also increases IT efficiency with simplified administrative tools and improved compliance enforcement. The introduction of Service Pack 1 (SP1) introduces many new features that are focused around Configuration Manager as the single point of management for any application on all an organization’s devices. The following is a list of features that impact application delivery:

 Support for heterogeneous devices including Windows® 8, Windows Phone, Android^TM, iOS®, Mac OS X®, Nokia, and legacy Windows Mobile as well as traditional MSI, virtual applications, and script based installers.

 Windows 8 support for application delivery rules over metered connections.

 Cloud integration with Windows Intune for device management from Configuration Manager console that reaches devices.

 Native integration of Application Virtualization (App-V) 5.0 and legacy versions.

With the additional support, application modeling now includes support for devices previously unavailable for management in organizations, without additional tools. Configuration Manager 2012 SP1 enables organizations to manage all of their application assets on all of their devices with native support for the application types as well as integration with the Window Intune service. Windows Intune is a cloud based service that provides Configuration Manager administrators with the ability to reach out and manage devices that are not part of the organization’s Active Directory domain as well as devices that aren’t connected to the corporate network. The additional support in Configuration Manager 2012 SP1 provides a complete application management solution across all devices and all application types in most organizations, whether homegrown, purchased from a vendor, or through the device specific application store.

Configuration Microsoft 2012 SP1 adds support of Application Virtualization (App-V) 5.0 applications.

App-V 5.0 provides benefits over traditional applications as it transforms applications into centrally managed, virtual services that are never installed and do not conflict with other applications. App-V dramatically accelerates application deployment, upgrades, patching, and retirement by eliminating time-consuming processes and simplifying the application management lifecycle.

This document provides information regarding the native App-V integration with System Center Configuration Manager workflows, enabling IT administrators to manage physical and virtual applications through a single management experience. Together, App-V and Configuration Manager 2012 SP1 let IT empower users with the services they need to be productive from anywhere, on whatever device they choose.

Note: Throughout this document, the terms “Configuration Manager” or “ConfigMgr” refers to Microsoft System Center 2012 Configuration Manager SP1, and the term “App-V” refers to Microsoft Application Virtualization 5.0.

(7)

Introduction

Page 6 of 61

Audience

This document is intended for IT administrators interested in utilizing Configuration Manager to deploy Microsoft Application Virtualization (App-V) 5.0 applications to users and devices, thereby gaining the benefits of App-V 5.0 with the additional scale and features of Configuration Manager.

Prior Knowledge

The administrator using this guide should have previous knowledge of the following technologies:

 System Center Configuration Manger 2012

 Microsoft Application Virtualization

Additional technical information is available for ConfigMgr 2012 at: http://technet.microsoft.com/en- us/library/gg682041.aspx

Additional technical information is available for App-V 5.0 at: http://technet.microsoft.com/en- us/library/jj713487.aspx

This document provides details for the integration of App-V 5.0 with Configuration Manager 2012 SP1 as well as for integration of App-V 4.6 SP2 from a coexistence scenario and transitioning to App-V 5.0. For detailed information on App-V 4.6 SP1 and greater management with Configuration Manager please read the Virtual Application Management with Microsoft Application Virtualization 4.6 and System Center Configuration Manager 2012 whitepaper available at:

http://download.microsoft.com/download/1/5/A/15AD0DD6-40A8-49E3-86D6-C21E5D0BC7F8/App- V%20and%20ConfigMgr%202012%20White%20Paper.pdf

(8)

Overview

Page 7 of 61

Overview

Configuration Manager 2012 SP1 was designed to provide the same level application management features that are provided in the App-V 5.0 infrastructure. The following overview of App-V 5.0 and Configuration Manager 2012 SP1 should be reviewed prior to undertaking the planning, setup and configuration

Application Virtualization 5.0

Microsoft Application Virtualization (App-V) transforms applications into centrally managed services that are never installed and do not conflict with other applications. IT professionals and end-users alike face challenges in today’s work environment. End-users speak many languages, are geographically dispersed, and may not be connected to corporate networks at all times. IT must meet the needs of these users, and provide solutions that are fast, flexible, and reliable. App-V can help with the challenges you face day-to-day and enable your business to be more flexible and responsive to changing needs.

With the release of App-V 5.0, virtual applications work more like traditionally installed applications than previous versions. Users do not have to change the way they use applications because they are virtual. App-V 5.0 makes it easy for IT to work with virtual applications stored in easily accessible locations in the file system and registry, and provides diagnostic messages with meaningful feedback, helping users resolve problems on their own.

App-V 5.0 enables separately packaged, virtual applications to communicate with each other and with traditionally installed applications through well-known communication paths. This gives businesses the best of both worlds, providing isolation that reduces conflicts and resource-intensive regression testing, while at the same time allowing applications to interact and communicate when needed, enabling dependency-based scenarios and better-together application deployment.

App-V provides flexible infrastructure planning, which allows IT to deploy, track and service App-V applications centrally with the included server solution, or integrate with Configuration Manager for additional benefits and scalability.

For additional information on App-V 5.0 visit: http://www.microsoft.com/en- us/windows/enterprise/products-and-technologies/mdop/app-v.aspx.

Configuration Manager 2012 Service Pack 1

Microsoft System Center 2012 Configuration Manager enables delivery of user experiences across a wide range of devices, while also ensuring that you meet corporate control and compliance

requirements. Learn more about the product capabilities in this comprehensive System Center solution.

Configuration Manager 2012 Service Pack 1 provides the same benefits as before but has been enhanced to provide additional benefits including, Windows 8 support, additional application type delivery, additional client support, cloud service integration, metered connection detection and delivery rules to name a few.

For more information on additional features of Configuration Manager 2012 SP1 visit:

http://technet.microsoft.com/en-us/library/jj591552.aspx.

(9)

Reasons for Integrating Configuration Manager and App-V

Page 8 of 61

Reasons for Integrating Configuration Manager and App-V

System Center 2012 Configuration Manager with Service Pack 1 has built-in support for App-V 4.6 SP1 and newer, up to App-V 5.0. Providing a comprehensive deployment and update service for virtual applications that is built for enterprise deployments. Service Pack 1 for Configuration Manager 2012 reduces the App-V infrastructure to the App-V Sequencer and Client and takes the place of the management, publishing, and streaming components in a typical App-V full infrastructure. Integrating Configuration Manager with App-V consolidates application delivery into one infrastructure and provides additional benefits over the App-V infrastructure.

Integration of App-V 5.0 with Configuration Manager 2012 SP1 supports the following App-V 5.0 features:

 Virtual Application Connections: Enables grouping together one or more virtual application packages to provide communication, while maintaining isolation from other virtual applications and the operating system.

 Virtual Application Extensions: Enable specific well-defined application extensions between physical-and-virtual and virtual-to-virtual applications. Some extensions are shortcuts, file type associations, and protocol handlers (URL redirection).

 Dynamic Configuration Files: Enable configuration of specific extensions on a per-target basis.

With dynamic configuration files, different settings like database connectivity, shortcuts, File Type Associations, and protocol handlers can be defined so the application only has to be sequenced once, and can be deployed to different users or systems with a configuration customized specifically for them.

App-V 5.0 continues to provide the isolation and virtualization features that have provided benefits to organizations. Please read the documentation listed in the Introduction section to find out more about App-V 5.0.

(10)

Page 9 of 61

Benefits of Integration

System Center 2012 Configuration Manager offers a rich set of capabilities for managing virtual applications from the Configuration Manager infrastructure. Configuration Manager with App-V

integration enhances the virtual application delivery model and provides features that are not available with an App-V full infrastructure model.

Configuration Manager and App-V Integration, Improvements and Enhancements

 Single management infrastructure: By integrating App-V’s virtual application management capabilities into Configuration Manager, enterprises can leverage Configuration Manager to manage all of their application management tasks, both virtual and traditional. App-V

integration in Configuration Manager provides most of the native App-V classic infrastructure capabilities, including user and computer targeting, streaming, ease-of-deployment, quick application update process, asset management, and application lifecycle management.

Integration helps IT reduce the cost of managing and maintaining multiple infrastructures and training personnel. Integration provides the added benefit of using a single lens/unified tool for viewing, comparing, or aggregating information about virtual and physical applications.

 Scalability: Configuration Manager is designed for large enterprise management and can scale to support hundreds of thousands of devices. Configuration Manager Distribution Points can host the virtual application package content for both streaming and local delivery scenarios, thus removing the need to deploy and maintain a large number of App-V streaming servers. In addition, Configuration Manager provides robust client roaming capabilities, allowing end users to access their content from the nearest Distribution Point when roaming outside of their assigned site boundaries.

 Explicit targeting and scheduling: Configuration Manager provides the ability to target systems or users with a collection of management capabilities, including virtual applications. The ability to schedule and deploy applications and updates to specific devices and users provides the flexibility that organizations need with required applications, while allowing users to simultaneously install optional applications as needed.

 Application Modeling: Configuration Manager 2012 application model architecture supports having one application with multiple deployment types. This enables administrators to model an application one time and then provide a self-service portal that allows the user to select their required application. Modeling allows IT to configure what type of the deployment (MSI, App-V, phone, or tablet) is delivered to the device requesting the application. IT configures the type of deployment by defining global conditions to identify what type of device is requesting an application. These conditions can include, but are not limited to, device type, location, or primary user of a device. By using application modeling, App-V applications can be configured with a dependency to the App-V Client. Thus, when IT entitles an App-V application to a user, Configuration Manager will ensure the App-V client has already been delivered. If it hasn’t, it will remediate the device prior to the virtual application delivery.

 Internet Deployments: Administrators can now utilize Configuration Manager’s built in Internet- Based Client Management solution to deliver App-V applications to off-premise users. In

addition to user delivery on the internet, Configuration Manager 2012 also allows App-V

(11)

Page 10 of 61 application streaming to an internet user, thereby reducing the amount of data a user may need prior to launching an application.

Additional capabilities with Configuration Manager and App-V Integration

 Operating system deployment: Configuration Manager’s operating system deployment feature can deploy virtual applications as part of the process of laying down the OS, thereby reducing the time required to get a new system up and running for an end user.

 Empower user productivity: With Configuration Manager 2012, IT can provide users the ability to select their own applications. Users can utilize a self-service portal to install applications they need to be productive. This feature also enables IT to set up applications that have multiple deployment types and ensures delivery of the correct type of application (MSI or App-V) to the correct device. For example, users could receive MSI-based applications on their primary device and App-V applications when they log on to non-primary devices. In addition, support for third party solutions, like Citrix®, enables users to receive the same application on their non-managed and potentially non-Windows devices via a session hosting an App-V version which provides improved server consolidation and ease of provisioning. All of this is accomplished by defining an application with the metadata required to select the best deployment method for specific users, locations, and devices, according to criteria defined by IT.

 Complete desktop management: App-V also integrates with existing features within

Configuration Manager, such as support for system targeting, operating system deployment, software and hardware inventory, software metering, asset intelligence, and Wake-On-LAN to support virtual applications. Enterprises get the best of both worlds: The flexibility of using virtual applications in App-V and the rich set of management features that Configuration Manager provides with this integration.

(12)

Architecture

Page 11 of 61

Architecture

Deploying a Configuration Manager solution with integrated App-V for managing virtual applications requires a Configuration Manager Primary Site, Management Point, and Distribution Point. Additionally, the Application Catalog is required when applications are made available to users for self-installation.

The architecture of an integrated solution includes the App-V Sequencer for creating packages on packaging workstations. Delivery of the necessary client agents (Configuration Manager and App-V Client) to the necessary devices is required to complete the solution.

Figure 1:Configuration Manager with App-V Infrastructure

NOTE: The ConfigMgr Site Server and Distribution point can reside on the same server.

(13)

Architecture

Page 12 of 61

Components

The table below outlines Configuration Manager and App-V components that enable integrated Configuration Manager with App-V infrastructure. Some of these components can be installed on the same machine. Please refer to Configuration Manager documentation for reference.

Table 1: Configuration Manager and App-V Components

Configuration Manager Primary Site

A part of the Configuration Manager site hierarchy required for managing the distribution and deployment of applications to client machines.

Configuration Manager Distribution Point

A site system role responsible for hosting application content that is made available to Configuration Manger clients. Such data can include files for applications, packages, software updates, operating system images, boot images and drivers.

Configuration Manager Management Point

A site system role that manages a client’s actions. It is responsible for relaying information to a client from the primary site. These actions include local machine policies and content locations.

Configuration Manager Application Catalog (Optional)

A web portal used by end-users to request software that has been published by a Configuration Manager administrator. The catalog interacts with a Configuration Manager client to install software as soon as a client has requested it.

Microsoft App-V Sequencer The App-V Sequencer packages applications into the App-V format for deployment with Configuration Manager.

Configuration Manger Client The Configuration Manger client interacts with ConfigMgr server roles to facilitate the download of content and perform the installation of applications. For App-V, it instructs the App-V client to publish virtual applications and assists in locating App-V

streaming content locations. Supported client devices include desktop/laptop PC’s, session (Remote Desktop Session Host and Citrix XenApp™), and Virtual Desktop Infrastructure (VDI) clients.

App-V Client (Windows Desktop and Remote Desktop Services)

The App-V client manages the virtual applications launched by the user on the client device. The App-V client performs the publishing of virtual applications and the streaming of application data in the package store.

(14)

Application Virtualization Lifecycle

Page 13 of 61

Application Virtualization Lifecycle

Configuration Manager 2012 enables IT to provide a self-service and user-centric approach to

applications while maintaining corporate compliance by delivering business critical application to users on demand. This “Application Model” is a key feature to Configuration Manager 2012 and App-V integration.

Key Components of the Application Model

The Application Model allows users to fulfill their requirements on demand, while still allowing administrators to control how an application is delivered. Administrators specify data required for a Configuration Manager agent to process and determine the correct delivery method. This information is broken down into several sections:

Application

In Configuration Manager 2012, an application is the primary location to store metadata used by both end-users and administrators. The application also stores information regarding how it will be

distributed and any supersedence rules. The application itself does not define the technical mechanics of the application delivery. Application metadata includes application name, version, and manufacturer.

Deployment Type

A deployment type is the technical way in which an application is deployed to a system. A deployment type is contained within an application and there can be multiple deployment types for a single

application. Typical deployment types include MSI delivery, a script, an App-V 4.6 package, or an App-V 5.0 package. Configuration Manager 2012 SP1 adds many new deployment types to support additional devices and their supported applications.

Since an application can have multiple deployment types, requirements for when a deployment type should be used must be defined. For example, if a user is known to be on their primary device, an MSI deployment type may be the best option. If the same user is logged onto a RDSH session, an App-V deployment is the better option. By defining these scenarios within the application model, it is possible to bring the best experience for the user and IT on any device they use.

Deployments

A Configuration Manager deployment is the action that delivers and installs an application based on the applicable Deployment Type. Deployments are assigned to user- or system-based collections.

Deployments include information about whether the application is to be installed or uninstalled, and if it is available or required. Additional properties of a deployment include the schedule for the application installation and instructions for how the system will obtain the application. The application can be pushed to the device, or users can manage their own application deployment schedule by going to the Software Center or self-service Application catalog.

(15)

App-V and Configuration Manager Integration

Page 14 of 61

App-V and Configuration Manager Integration

App-V Integration with Configuration Manager is streamlined because Configuration Manager is performing the same tasks that are available with the full App-V infrastructure. Organizations with Configuration Manager already in place, or those in the process of implementing Configuration Manager, can implement one infrastructure using a seamless, scalable solution to deliver, report, and manage the application lifecycle from one console. The technical implementation of each of the above points will be detailed and their usage explained throughout this document.

System Center 2012 Configuration Manager SP1 adds support to manage App-V 5.0 applications.

Configuration Manager uses publicly documented interfaces to interact with the App-V Client software.

All integration is implemented using the following methods:

• PowerShell: Configuration Manager uses the App-V Client's PowerShell module to manage App-V objects including virtual applications, connection groups, and dynamic configuration files.

• Configuration Manager Client: Configuration Manager Client determines the appropriate download or streaming location (distribution point), as with any application.

• WMI: Configuration Manager uses the App-V Client's Windows Management

Instrumentation (WMI) classes to query and report on the status of virtual applications that reside on the machine.

• Software Metering: Monitors application usage with Configuration Manager software metering rules.

Application Virtualization Management Tasks

Configuration Manager with App-V integration performs tasks that are usually done with the App-V full infrastructure, as well as automating additional tasks not typically available without additional process.

In general, the following primary tasks must be completed to support App-V integration.

 App-V Client: The App-V client software can be modeled with the correct configuration to ensure the delivery of the App-V Client prior to any virtual application deployment.

 Virtual Environments: Configuration Manager supports App-V Connection Groups utilizing the virtual environments object. Virtual environments allow the administrator to define a set of rules that tell the ConfigMgr client when to create a connection group.

 Dynamic Configuration: Support for delivery and application of dynamic configuration files that support virtual application extensions in application models.

 Application Lifecycle Management: Configuration Manager provides management of applications from delivery, update, and termination using the application catalog built-in wizards and configurations.

 Monitoring and Reporting: Configuration Manager has built-in In Console Monitoring (ICM) for tracking application deployments. There are additional reports for tracking compliance of Virtual Environments.

(16)

Configuration Manager and App-V Interaction

Page 15 of 61

Configuration Manager and App-V Interaction

The Configuration Manager 2012 client and App-V client interact through three different interfaces including PowerShell, WMI, and Component Object Model (COM).

PowerShell

Configuration manager enforcement actions, such as install or uninstall, are executed using the App-V client’s PowerShell module. The App-V module is installed on the system during the App-V client installation and is loaded by the Configuration Manager client when an App-V operation is invoked. The commands used by the CM client are:

Table 2:App-V PowerShell Commands Utilized by Configuration Manager

PowerShell Command Description

Add-AppVClientPackage Registers an App-V package with the App-V Client.

Set-AppVClientPackage Modifies dynamic configuration files on existing App-V packages on the App-V Client.

Publish-AppVClientPackage Publishes extension points for a package. Common extension points are shortcuts and file type associations.

Mount-AppVClientPackage Loads an App-V package into the App-V client cache.

Add-AppVClientConnectionGroup Adds a Connection Group to the App-V Client.

Enable-AppVClientConnectionGroup Enables the Connection Group on the App-V Client.

Disable-AppVClientConnectionGroup Disables the Connection Group on the App-V Client.

Remove-AppVClientConnectionGroup Removes a Connection Group from the App-V Client.

WMI

Configuration Manager queries WMI classes to gather information regarding the App-V client and deployed App-V Applications. By default, the App-V WMI classes are not enabled in Configuration Manager. Please see the Reporting section for more information.

Component Object Model (COM)

The App-V client uses a COM interface, exposed by the ConfigMgr client, when content is required by the App-V client. This interface allows the App-V client to ask the Configuration Manger client for the correct location of required content and the Configuration Manger returns the correct source location (distribution point) to the App-V client.

(17)

Configuration Manager and App-V Interaction

Page 16 of 61

(18)

App-V Client Install and Upgrade

Page 17 of 61

App-V Client Install and Upgrade

Configuration Manager provides the infrastructure required to manage App-V applications and automates the delivery of the App-V Client. Delivery of the App-V Client can be accomplished by creating an application and deploying it to devices like other applications. The Configuration Manager application model provides administrators the capability of modeling their App-V applications with a dependency on the App-V Client installation. This ensures that the App-V Client is only delivered prior to the first App-V application, and that it is not delivered to devices that do not receive any App-V applications.

Configuration Manager 2012 SP1 supports the management of App-V 5.0 and 4.6 SP1 and greater clients. However, when the coexistence of App-V 5.0 and App-V 4.6 is required during a transition to App-V 5.0, App-V 4.6 SP2 is required before installing App-V 5.0.

This section presents the following installation and upgrade procedures:

 App-V Client Installation Model: Utilizes the Configuration Manager SP1 SDK, which includes an Application Kit. The application kit contains several commonly used applications already

modeled for ConfigMgr. Both App-V 4 and App-V 5 are modeled in this kit.

 Installing App-V 5.0 where App-V 4.6 is present: Builds on the App-V client included in the application kit, and modifying to remediate older versions of App-V 4.6 installations.

 Installing App-V Client to Remote Desktop Services: Describes the process of installing the App-V RDS Client with Configuration Manager.

This document does not cover migrations from Configuration Manager 2007 to Configuration Manager 2012 scenarios. From the App-V Client perspective the Configuration Manager 2012 requires App-V 4.6 SP1 or newer. It is assumed that the environment already has App-V 4.6 SP1 based on the requirements of Configuration Manager 2012.

App-V Client Installation Model

An installation model for several commonly used applications is available in the Configuration Manager SP1 SDK which has been made available at: http://go.microsoft.com/fwlink/?LinkId=276784. This model provides administrators with a pre-defined and tested installation logic for the App-V 5.0 client and all required prerequisites. This model is based on utilizing the EXE installation of the App-V Client, which installs all of the prerequisites. The App-V 5.0 Client model provided in the application kit detects the presence of the App-V 4.6 Client. When a previous version of App-V 4.6 is detected, the App-V 5.0 client is not installed. The App-V 5 client will utilize the following three different applications in the kit:

• App-V 5.0 Client

• KB2533623

• WMF 3.0 (PowerShell 3.0)

KB2533623 and WMF 3.0 are prerequisites only required on Windows 7 and Windows Server 2008 R2.

Windows 8 and Windows Server 2012 require no additional software to install the App-V client.

(19)

Page 18 of 61 Steps for Using the Application Model Kit

The application model provided by Microsoft only contains the required Configuration Manager objects.

All source files required by the kit must be downloaded and configured after importing the clients. The following outlines the process:

1. Download the Configuration Manger SDK SP1 from http://go.microsoft.com/fwlink/?LinkId=276784.

2. Install the SDK.

3. Navigate to C:\Program Files (x86)\Microsoft System Center 2012 Configuration Manager SDK\Samples\Application Model\ (default location, may vary depending on installation options).

4. Copy the Application Model Kit.zip to machine with the ConfigMgr console installed.

5. Download the App-V 5.0 Client to a shared location.

6. Open the Configuration Manager console.

7. Navigate to Software Library > Applications.

8. Right click Applications, and select Import Application.

9. Click Browse and select the ZIP file copied in Step 4.

Note: The path must be in a UNC format.

10. Click Next.

Note: The wizard will analyze the contents of the ZIP file.

Figure 2:Import Application

(20)

Page 19 of 61 Notice the Applications and Global Conditions contained within the ZIP.

11. Click Next.

12. Click Next. Click Close.

13. Select the Microsoft Application Virtualization Client 5 application.

14. In the bottom frame, select the Deployment Types tab.

15. Right click the Microsoft Application Virtualization (App-V) 5.0 Client Install from Script deployment type, select Properties.

16. Select the Content tab.

17. Next to Content Location click Browse. Browse to the location setup in Step 2.

18. Click Select Folder.

19. Click OK.

Important: The App-V 5.0 application source has now been updated. Repeat these steps for the WMF framework 3.0 and Microsoft Update KB2533623. Each deployment type contained within those applications will require the content location to be updated. Once complete, the App-V 5.0 client is ready to be deployed to the targeted objects.

Installing App-V 5.0 where App-V 4.6 is present

The Configuration Manager SP1 SDK, which includes the application kit containing the App-V 5.0 Client, was designed to deploy the App-V 5.0 client on devices where the App-V 4.6 Client is not present.

Environments that have the App-V 4.6 client installed will need to be upgraded before both versions can coexist. When the App-V 4.6 Client is present in the environment prior to the installation of 5.0, the App-V 4.6 SP2 client must be configured as a prerequisite of the App-V 5.0 client deployment. In this scenario the App-V 4.6 Client is updated to the App-V 4.6 SP2 client prior to the installation of the App-V 5.0 Client.

The details provided below are one way of ensuring that the App-V 4.6 client is upgraded to SP2 prior to the installation of the App-V 5.0 client. This method utilizes the Configuration Manager App-V 5.0 Client in the ConfigMgr SDK application kit as the basis to reduce effort and eliminate potential errors. The concept is to detect the presence of the previous App-V Client and then remediate it prior to the installation of the App-V 5.0 Client.

To create the new deployment type and follow these steps:

1. Import the App-V 5.0 Application as outlined above.

2. Navigate to the Software Library workspace, expand Application Management, select Applications.

3. Select the imported Microsoft Application Virtualization Client 5 application.

4. In the ribbon, select Properties.

5. Select the Deployment Types tab.

6. Select the only deployment type listed, click Copy.

Note: The existing Deployment Type only installs the App-V client if a 4.x App-V client is not detected.

7. Select the copied deployment type and click Edit.

8. Select Requirements and remove all the ‘App-V 4.x Installed equals False’ requirements.

(21)

Page 20 of 61 9. Click Add.

10. In the Category drop down select Custom.

11. Click Create.

12. Fill out the following information in the Create Global Condition wizard.

a. Name: App-V 4.6.0 or 4.6.1 Installed b. Device Type: Windows

c. Condition Type: Expression

13. Click Add Clause… Fill in the following information:

a. Category: Custom

b. Condition: App-V 4.6.0 Installed c. Operator: Equals

d. Value: True 14. Click OK

15. Click Add Clause… Fill in the following information:

a. Category: Custom

b. Condition: App-V 4.6.1 Installed c. Operator: Equals

d. Value: True 16. Click Ok

17. In the list of Clauses, click the AND connector. Switch the connector to OR.

Figure 3: Add App-V 4.6 Installed Clause

(22)

Page 21 of 61 Note: As seen in the preview window, this deployment type is now configured to only run when a App-V 4.6.0 or App-V 4.6.1 client is found on the system.

18. Click OK.

19. In the Condition drop down, select the newly created App-V 4.6.x Installed condition. Fill out the following values:

a. Operator: Equals b. Value: True 20. Click OK.

21. Select the Dependencies tab.

22. Add the 4.6 SP2 client, both 32-bit and 64-bit, as a dependency.

Note: This deployment type is now configured to only run when a 4.6.0 or 4.6.1 App-V client is detected. When it does run, the App-V 4.6 SP2 client will be automatically loaded on to the client system prior to installation of the App-V 5.0 client.

23. Click OK, and OK again to complete the process.

The final step in the process is to make this App-V 5.0 client application a prerequisite to all App-V 5.0 applications. In doing so, whenever a client installs an App-V application Configuration Manager will ensure the correct set of clients are installed.

Installing App-V Client to Remote Desktop Services

The App-V client for Remote Desktop Services can be installed by adding another deployment type to the App-V client application, which would detect the presence of Remote Desktop Services prior to installation and ensure the proper EXE is selected.

 For more information about deploying the App-V client to RDS servers, please download and read the Integrating App-V for Remote Desktop Services whitepaper at:

http://go.microsoft.com/?linkid=9824870

(23)

App-V Application Lifecycle Tasks

Page 22 of 61

App-V Application Lifecycle Tasks

App-V applications are very similar in lifecycle to traditional or MSI based applications. They have some key differences, based on the fact that they aren’t actually installed, but are instead published. The lifecycle begins with the creation of the App-V package at the Sequencing workstation. After the App-V package has been created, it is handed to the person or group responsible for deploying applications.

The following covers the lifecycle of the application from importing the App-V package as a Configuration Manager application or deployment type, through distribution of the content in the Configuration Manager infrastructure, deploying the application to targets, upgrading the application to a newer version and finally, to retiring the application. The next section defines the application model components that support the App-V application lifecycle from import, distribution, and deployment.

Import and Customization

The new application model introduced in ConfigMgr 2012 allows for multiple deployment technologies to be contained in a single ConfigMgr Application. When a new App-V package has been received, the Software Library should be reviewed for an existing application that matches the software and version of App-V package and, if present, the App-V version should be added as an additional Deployment Type.

For example, if the Software library contains an application for Adobe® Reader 9 with a traditional MSI install and an App-V package has now been created, instead of creating an entirely new application, a new deployment type can simply be created within the existing application. When no defined matching application is present, a new application should be created in the Software Library. This section focuses on the details and customization available in the App-V Deployment Type. For information on creating an Application in Configuration Manager go to: http://technet.microsoft.com/en-

us/library/gg682159.aspx or creating a Deployment Type go to: http://technet.microsoft.com/en- us/library/gg682174.aspx.

Deployment Types

Deployment types are the details about how an application is delivered. A deployment type can be a number of different delivery technologies (MSI, App-V….).

Detection Method

Deployment types for traditional applications typically contain a tab for an administrator to define a detection method. Because App-V applications are always assigned certain properties, the detection method for an App-V 5 application is always based on the same set of properties. These properties are:

 PackageID: The unique identifier of the App-V package.

 VersionID: The unique identifier of the App-V package version.

 App-V Components: The applications contained in the App-V package for publishing to the machine.

PackageID and VersionID are created when an application is sequenced using the App-V Sequencer.

ConfigMgr imports these IDs from the App-V package when an App-V 5 deployment type is created.

App-V Components are the virtual applications contained within the package that are being published in the deployment type (see the Publishing section for selective publishing).

When App-V publishes a package to a machine, information regarding the package is stored in WMI.

This information is queried by ConfigMgr to determine the list of applications currently published to a

(24)

Page 23 of 61 machine. There are four classes in the AppV namespace that provide this information:

AppvClientApplication, AppvClientAsset, AppvClientConnectionGroup, and AppvclientPackage.

App-V 5 deployment types have a unique set of options tailored specifically for virtual applications.

Settings for a deployment type can be found by doing the following:

1. Open the Configuration Manager 2012 Console.

2. Navigate to Software Library > Applications

3. Locate an Application that has an App-V 5 deployment type.

4. Select the application, from the ribbon select Properties.

5. Select the Deployment Types tab.

6. Select the App-5 deployment type, click Edit.

Figure 4: App-V 5 Deployment Type

Each tab contains deployment specific information. These tabs are outlined below:

Content

Administrators specify the location of the assets for delivery for a specific deployment type as well as how the content will be delivered; via streaming or download-and-execute, as well as cache

management settings. App-V packages utilize ConfigMgr’s single instance storage during distribution to reduce the amount of data that is sent to distribution points. For more information on SIS, read review the following TechNet blog post: http://blogs.technet.com/b/hhoy/archive/2012/05/31/an-adventure- in-the-sccmcontentlib-single-instance-store.aspx.

The following options are available for customization regarding content:

(25)

Page 24 of 61

 Persist content in client cache gives administrators the choice of retaining the App-V package in the Configuration Manager cache or having it removed by the normal cache management settings. Retaining the content in cache enables remote differential compression for updates to App-V applications.

 Enable peer-to-peer content distribution utilizing the BranchCache® feature of Windows that allows a client to source from another client on the local network, if available.

 Streaming or Download and Execute options allow administrators to define how content is delivered to a client. See the App-V Application Deployment Options section for more information/

Publishing

Exclusively on an App-V deployment type, the administrator can use the added “publishing” tab to choose which components of virtualized applications to publish for the specific App-V deployment type presented to the end-user. Selective Publishing of App-V virtualized application components enables administrators to utilize one App-V package with several applications and choose to publish only specific applications to devices or users.

Requirements

These requirements are evaluated before a deployment type is selected for use. A Configuration Manager administrator can configure a requirement on any piece of system information (RAM, disk space, a registry key, file, WMI query, or run a script). When an App-V 5.0 package is imported into Configuration Manager 2012, the operating system requirements setup during sequencing are automatically populated to this tab.

Dependencies

Dependencies are additional components that devices must have prior to deployment. If a dependency is missing on a client, it can be remediated as part of the application deployment or as a separate task outside of the deployment. For App-V packages, administrators should create the App-V 5.0 Client as an application and deployment type separate from the virtualized applications that will be deployed, and then make all App-V application deployment types dependent on the App-V client delivery.

Virtual Environments

Configuration Manager supports App-V Connection Groups utilizing the virtual environments object.

Virtual environment objects are a set of rules that determine when a connection group is created on a client. Connection Groups combine two or more applications into a common execution environment enabling communication between collaborative applications. The virtual environment tab within the deployment type only allows an administrator to view virtual environments the deployment type belongs to. To create a virtual environment, see the Virtual Environments section.

(26)

Page 25 of 61

Distribute

After an App-V application package has been created in Configuration Manager, the package must be replicated to the Distribution Points that will be used to deliver the virtual application package to clients.

The Configuration Manager administrator chooses which Distribution Points to send the virtual application package.

Configuration Manager Distribution Points support virtual application streaming by default with no additional configuration. The reference information in the Application object indicates where only a validation or redistribution of content can be performed.

There are several key factors to consider when distributing App-V applications. What is the size of the application? What is the delivery method; streaming or download and execute? Do the users roam when using the application? Do the users move to an off-premise location when using the application?

If the clients utilizing the application do not roam, such as a call center or computer lab, then targeting only the distribution points in which the clients will use is preferable. Directed distribution will allow the administrator to save disk space on distribution points that will never serve the content.

If clients will be actively roaming from one network to another (one boundary to another, one

distribution point to another) then it is required to offer the package on multiple (if not all) distribution points to ensure the content will always be available to the end-user regardless of their physical location.

Deploy

After a virtual application package has been replicated to Distribution Points, a deployment that targets the desired collection(s) should be created. Depending on how a deployment is configured will

determine how the user is presented the application. The following table outlines the available options:

Table 3: Deploy Options

Target Deployment Purpose Installation Initiation

User Target Required Automatically installed on

deployment schedule

Available Application Catalog

System Target Required Automatically installed on

deployment schedule

Available Software Center

When a deployment is created for a virtualized application, the user / system will receive the

deployment and all applications selected using Selective Publishing. Configuration Manager Clients will use normal Configuration Manager Client polling methods to locate the deployment.

(27)

Page 26 of 61 Once an App-V deployment type is selected for install and all prerequisites are installed, then the App-V application is published to the user. See the App-V and Configuration Manager integration section for more information.

Configurable Options:

• Application deployment installation type: Required or Available

• Collection selection of client devices or users to which the package should be deployed

• Scheduling deployments

• User experience for integration in the Software Center and display of notifications For more information on the Create Application Wizard, see http://technet.microsoft.com/en- us/library/gg682159.aspx.

For more information on the Deploy Software Wizard, see http://technet.microsoft.com/en- us/library/gg682082.aspx.

Updating, Superseding and Re-Deploying

As with traditionally installed applications, virtual applications will need to be upgraded over their lifecycle. Virtual application packages deployed with Configuration Manager can be upgraded easily to include service packs, software updates, etc. In order to upgrade virtual applications, the App-V Sequencer is used to create the upgraded package.

Upgrading applications, whether traditional or virtual, uses the supersedence feature. Administrators copy the original application, update the application’s metadata and deployment type source to reflect the new version’s information, and then configure supersedence on the new application. The

administrator deploys the updated application to systems / users, allowing users to access the updated applications in the package. For more information on upgrading applications visit:

http://technet.microsoft.com/en-us/library/gg682071.aspx The following steps outline this process:

Copy the Application

1. Find the initial revision of the application in the configuration manager console.

2. Right Click the application, select Copy.

Configuration Manager makes a copy of the application and names it “PreviousName-Copy”.

Deployments are not copied.

3. Find the new copy of the application.

4. Rename the Application and Deployment Types to reflect the new version of the software.

Update the Application Source

5. Select the new version of the application in the Software Library.

6. In the lower right pane, select Deployment Types.

7. Right click the App-V 5.0 Deployment Type, select Update Content.

(28)

Page 27 of 61

Figure 5: Update Content Wizard

This launches the Update Content Wizard. This wizard is only available on App-V 5.0 deployment types.

8. Click the Browse button and navigate to the new set of source files.

9. Complete the rest of the wizard.

10. Redistribute the Application to Distribution Points.

Supersede the Application

11. Find the new copy of the Application in the Software Library.

12. Right Click the Application, select Properties.

13. Select the Supersedence tab.

14. Click Add.

15. Click Browse and select the original application.

(29)

Page 28 of 61

Figure 6: Supersedence Relationship

The administrator can configure supersedence to either replace or upgrade the application. If the uninstall box is checked, Configuration Manager will first uninstall the old application, and then deploy the new application to the user (replace). For an App-V application, user settings will be lost using this method. Only select the uninstall option for scenarios where replacement of the entire application, including user personalization, is desired or required.

Important: When utilizing the uninstall option with supersedence, if the application being superseded is in use, the uninstall operation will fail causing the deployment to fail. This reports “Virtual

application is currently in use” in the ConfigMgr console. When this occurs, the ConfigMgr client will reattempt the deployment every 2 hours, a maximum of 10 times, and then every 7 days.

If the uninstall option is not selected, the application will do an in-place upgrade. In App-V, if the new Application is from the same lineage as the application being replaced, all user settings are retained during the upgrade.

Note: If the application being upgraded (no uninstall) is in use, the new version is published to the client and becomes available after the users closes and reopens the application.

16. Select a deployment type to supersede the old application from the New Deployment Type drop down.

17. Decide to replace, or upgrade the application and select the appropriate option for the Uninstall check box.

18. Click OK.

19. Notice the check box at the bottom of the Supersedence tab. This option allows you to hide the previous revisions of the application from the Application Catalog.

(30)

Page 29 of 61 Deploy the Application

The deploy wizard offers two additional options for an application that has supersedence rules configured. By selecting the first setting on the Deployment Settings, the administrator can automatically upgrade any superseded versions of the application. Choosing this option allows the administrator to use the Scheduling page to schedule when the upgrade will take place.

Uninstall

The ability to remove virtual applications from a client is one of the benefits of App-V. Virtual

applications are not uninstalled like traditional software; they are instantly removed from the client by unpublishing and removing extension points (shortcuts and FTAs) from the client. Removing an App-V application from a given client requires creating an uninstall deployment targeted at the appropriate collection.

Note: Uninstall deployments do not remove dependencies and require that administrators create additional uninstall deployments.

(31)

Page 30 of 61 Auto Uninstall

Install deployments always take precedence over uninstall deployments. If an application has an install and uninstall deployment that overlaps and targets the same objects in the targeted collections, the application will remain. To configure an application to automatically uninstall when a user / system is removed from the install collection, create a collection based on the deployment status of a deployed application then target an uninstall deployment to it.

select * from

SMS_R_System inner join SMS_G_System_AppClientState on

SMS_G_System_AppClientState.MachineName = SMS_R_System.Name where SMS_G_System_AppClientState.ComplianceState = 1 and

SMS_G_System_AppClientState.AppName= "Application A"

Figure 7: AutoUninstall

(32)

Page 31 of 61 In this scenario, the Install Collection is a collection of systems targeted by Application A. Since install deployments take precedence in Configuration Manager, as long as systems remain in the install collection, the uninstall deployment is ignored. When a system is removed from the Install Collection, the uninstall deployment will be the only available deployment and the application will be removed. The removal will happen the next time the system performs a global evaluation.

Note: The uninstall collection query listed only works for systems. The query must be modified when the install collection contains user objects.

Creating the Uninstall Collection with ConfigMgr Console

This collection query can also be generated through the ConfigMgr console when a new collection is created by adding a query rule to a new or existing collection. Complete the following steps to create a new collection query that will be the target of an uninstall deployment:

1. In either the new collection wizard, or the properties of an existing collection, add a new query rule.

2. Name the rule and ensure the Resource class: drop down is set to System Resource.

3. Select Edit Query Statement.

4. Click the Joins tab.

5. Click the star icon ( ) to create a new join statement.

6. Underneath the Join attribute box, click Select.

7. In the Attribute class drop down, select Application Client State.

8. In the Attribute drop down, select Machine Name. Click OK.

9. Underneath the Base attribute box, click Select.

10. In the Attribute drop down, select Name. Click OK.

11. Click OK again to add the join clause.

12. Select the Criteria tab, and click the star icon to add a new statement.

13. Underneath the Where clause, click Select.

15. In the Attribute drop down, select Compliance State. Click OK.

16. Ensure the Operator value is set to is equal to. In the Value textbox, enter 1.

17. Click OK to add the clause.

18. Click the star icon to add another clause.

19. Underneath the Where clause, click Select.

21. In the Attribute drop down, select Application Name. Click OK.

22. Ensure the Operator value is set to is equal to. In the Value textbox, enter the name of the application you want to create the uninstall collection for.

Note: This value must exactly match that of an application currently in ConfgMgr. If these names do not match exactly, the collection will return no members.

23. Click OK to add the clause.

24. Click OK twice to complete the query build process.

(33)

Page 32 of 61

Retire

Retiring an application disables deployment of the application but does not delete existing deployments of the application. Existing copies of the retired application installed on client computers will not be removed. If an application that has no deployments is retired, it will be deleted from the Configuration Manager console after 60 days. However, any installed copies of the application are not removed.

Please refer to http://technet.microsoft.com/en-us/library/gg682031.aspx for further information regarding retirement.

Delete

At the end of the application lifecycle, when an application is no longer needed for deployment, it should be deleted from the infrastructure. Deleting an application requires that the application is not being actively deployed and requires administrators remove any link to an active application

deployment or task sequence. If the application must be removed from all machines, the administrator will need to create an uninstall deployment to remove the application from any clients and then delete the uninstall deployment prior to deletion of the application.

(34)

App-V Application Deployment Options

Page 33 of 61

App-V Application Deployment Options

Configuration Manager supports two methods for delivery of virtual applications to clients: streaming delivery and local delivery (download and execute). This section describes these delivery methods.

Sequenced application packages contain a fully pre-configured run-time environment for the virtualized application. The application installation process occurs only on the App-V Sequencer workstation during the packaging process. The Sequencer processes handless and applies changes with applications that require system reboots. When a virtual application is delivered to a client PC, the application is ready to run. No application software installation, client PC reboot or post-installation application configuration is required when delivering a virtual application to client PCs. This significantly reduces the time required to deliver a virtual application to a client PC verses the time required to deliver a non- virtualized (i.e., locally installed) application to a client PC. This benefit is independent of the

Configuration Manager application delivery method (i.e., streaming or local delivery) used to deliver the application to client PCs.

Download and Execute

The Configuration Manager Client supports local delivery of virtual applications. With this delivery method, the Configuration Manager Client first downloads the entire virtual application package into the Configuration Manager Client cache. The Configuration Manager client then publishes and mounts the application to the system. When the mount command is run, the App-V file is extracted to the App-V package store.

The following figure illustrates the virtual local delivery (download and execute) process.

(35)

Page 34 of 61

Figure 8: Download and Execute Locally Workflow

1. An application packaging specialist sequences an application and saves the new virtual application package to the App-V Content Source directory.

2. The Configuration Manager administrator creates an application. To create the new App-V application, the Configuration Manager administrator runs the Create Application Wizard from the Software Library or creates an additional Deployment Type for an already existing

application.

For more information on the Create Application Wizard, see http://technet.microsoft.com/en- us/library/gg682159.aspx

3. The Configuration Manager administrator uses the Distribute Content wizard and selects the distribution points where the application will be replicated.

For more information on the Distribute Content Wizard, see http://technet.microsoft.com/en- us/library/gg712694.aspx#BKMK_DistributeContent

4. The Configuration Manager administrator creates a deployment targeting the new virtual application package to a collection of client PCs or users using streaming delivery.

(36)

Page 35 of 61 For more information on the Deployment Wizard, see http://technet.microsoft.com/en-

us/library/gg682082.aspx

5. The Configuration Manager Client evaluates the deployment based on the deployment type criteria.

6. The application is copied into the Configuration Manager Cache.

7. The Configuration Manager client adds the App-V package to the client. The App-V Client creates program shortcuts and FTAs for each program in included in the package. The Configuration Manger client then mounts the App-V package on the system.

8. During the mount command issued by the Configuration Manager client, the App-V client copies the package data into the App-V package store.

9. The user clicks on one of the program shortcuts associated with the virtual application package and the application launches.

Download and Execute Scenario

A user has navigated to the company’s application portal hosted by Configuration Manager. The user searched the catalog, found a needed application, and initiated an install. This application has been configured for download and execute, and client’s machine has the App-V client installed. The following is how the Configuration Manager Application Catalog and Client would complete that installation:

1. The Application Catalog role sends the required information about the application to the client.

This information includes the requirements for the application (for example, windows 7, 32 bit with 1 GB of memory) along with any prerequisite software requirements.

2. The client evaluates the system, checking to see what software is already installed, and verifies the client meets all the requirements of the application. If any requirement is not met, the Application Catalog will inform the user the minimum requirements for the application have not been met and the process will stop.

3. Based on the Configuration Manger Client location a distribution point is selected to download the application’s content. Three files are downloaded for the AppV package to the Configuration Manager Client cache (By default located at C:\Windows\CCMCache\). These files are:

a. AppName.Appv – Contains the source files for the AppV package.

b. AppName_UserConfig.xml – Contains custom user configurations.

c. AppName_DeploymentConfig.xml – Contains custom machine configurations.

d. Any prerequisite software – Additional software, like the App-V Client if modeled as a dependency of the App-V application installation.

Note: For more information about User and Deployment Configurations, see the section Dynamic Configuration.

4. All prerequisite software is installed.

5. The Configuration Manager Client identifies that the application is set for download and execute deployment. Using the Configuration Management infrastructure, the client selects the best distribution point and configures the App-V Client for streaming the content from the Configuration Manager cache.

6. The App-V applications are Added, Published, and Mounted to the client. Configuration Manger generates a Deployment (computer target) or User Configuration (user target) file for publishing based on the application’s dynamic configuration file and settings configured in the deployment

(37)

Page 36 of 61 type (publishing tab) and creates the file in the Configuration Manager cache. The Configuration Manager Client executes the following PowerShell commands to complete the task:

Code Example 1: Download and Execute App-V Package Addition and Publishing Client-side Processing Add-AppvClientPackage -Path 'C:\Windows\ccmcache\c\AppName.appv' -

DynamicDeploymentConfiguration 'C:\Windows\ccmcache\c\AppName_DeploymentConfig.xml' Publish-AppvClientPackage -PackageID {PackageIDGuid} -VersionID {VersionIDGuid} - DynamicUserConfigurationPath

'C:\Windows\CCM\SystemTemp\AppVTempData\{PackageID}_UserConfig.xml’

Mount-AppvClientPackage -PackageID {PackageIDGuid} -VersionID {VersionIDGuid}

The Add command registers the App-V package with the local system. The Deployment Configuration file is applied at this time.

The Publish command makes the App-V package available to the user. It publishes shortcuts, takes over file extensions, etc. The User configuration file is applied at this time.

The Mount command instructs the App-V client to extract the contents of the AppName.appv file to the App-V package store (By default C:\ProgramData\App-V\).

7. The application is now fully downloaded and published to the client machine.

(38)

Page 37 of 61

Streaming

When managed by Configuration Manager, the App-V Client supports streaming virtual applications via HTTP or HTTPS from a Configuration Manager standard Distribution Point server. Streaming via HTTP or HTTPS is enabled by default and configured as part of the Distribution Point properties. This method does not utilize the Configuration Manager cache for delivery of the entire App-V package. Only the Dynamic Configuration Files are placed in the Configuration Manager cache and the App-V Client is configured to stream the App-V package from the distribution point via HTTP(S) on first launch for delivery to the App-V package store.

The following figure illustrates the virtual application steaming delivery process from end to end.

Figure 9: Streaming Workflow

Figure 4 – Streaming Application Delivery Process

1. An application packaging specialist sequences an application and saves the new virtual application package to the App-V Content Source directory. The App-V Content Source directory is a network share that contains sequenced application packages.

INTEGRATING VIRTUAL APPLICATION MANAGEMENT WITH APP-V 5 AND CONFIGURATION MANAGER 2012 SP1