App-V 5.

App-V 5 includes a built-in reporting feature that helps you collect information about computers
running the App-V 5.0 client as well as information about virtual application package usage. You can
use this information to generate reports from a centralized database.

App-V 5 Reporting Overview

1. The following list displays the end--to-end high-level workflow for reporting in App-V 5:
 The Microsoft Application Virtualization (App-V) 5.0 Reporting server has the
following prerequisites:
 Internet Information Service (IIS) web server role
 Windows Authentication role (under IIS / Security)
 SQL Server installed and running with SQL Server Reporting Services
(SSRS)
To confirm SQL Server Reporting Services is running, view http://localhost/Reports in a web browser
as administrator on the server that will host App-V 5.0 Reporting. The SQL Server Reporting
Services Home page should display.
2. Install the App-V 5.0 reporting server and associated database. Configure the time when the
computer running the App-V 5.0 client should send data to the reporting server.
3. If you are not using an electronic software distribution system such as Configuration
Manager to view reports then you can define reports in SQL Server Reporting Service. Download
predefined Reports from the Download Center at http://go.microsoft.com/fwlink/?LinkId=397255.
4. After importing the App-V 5.0 PowerShell module using Import-Module AppvClient as
administrator, enable the App-V 5.0 client. This sample PowerShell cmdlet enables App-V 5.0
reporting:

Set-AppvClientConfiguration --reportingserverurl <url>:<port>

-reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>

To immediately send App-V 5.0 report data, run Send-AppvClientReport on the App-V 5.0 client.

5. After the reporting server receives the data from the App-V 5.0 client it sends the data to the
reporting database. When the database receives and processes the client data, a successful reply is
sent to the reporting server and then a notification is sent to the App-V 5.0 client.
6. When the App-V 5.0 client receives the success notification, it empties the data cache to
conserve space.

To enable reporting and to initiate data collection on the computer running the
App-V 5.0 client:
?
Set-AppVClientConfiguration \--ReportingEnabled 1

To configure the client to automatically send data to a specific reporting server:

?
Set-AppVClientConfiguration –ReportingServerURL
http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1
-ReportingRandomDelay 30
-ReportingInterval 1 -ReportingRandomDelay 30

This example configures the client to automatically send the reporting data to the reporting server
URL http://MyReportingServer:MyPort/. Additionally, the reporting data will be sent daily between
8:00 and 8:30 PM, depending on the random delay generated for the session. To limit the size of the
data cache on the client:
?
Set-AppvClientConfiguration –ReportingDataCacheLimit 100

Configures the maximum size of the reporting cache on the computer running the App-V 5.0 client to
100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and
data will be overwritten as necessary.
To configure the data block size transmitted across the network between the client and the
server:
?
Set-AppvClientConfiguration –ReportingDataBlockSize 10240

Specifies the maximum data block that the client sends to 10240 MB.

Test data collected

The following table displays the types of information you can collect by using App-V 5.0 reporting.

Client Information Package Information Application Usage

Host Name Package Name Start and End Times

App-V 5.0 Client Version Package Version Run Status

Processor Architecture Package Source Shutdown State

Operating System Percent Cached Application Name

Version

Service Pack Level   Application Version

Operating System Type   Username

    Connection Group

The client collects and saves this data in an .xml format. The data cache is hidden by default and
requires administrator rights to open the XML file. *Sending data to the server*You can configure the
computer that is running the App-V 5.0 client to automatically send data to the specified reporting
server. To specify the server use the Set-AppvClientConfiguration cmdlet with the following settings:
ReportingEnabled
 ReportingServerURL
 ReportingStartTime
 ReportingInterval
 ReportingRandomDelay

After you configure the previous settings, you must create a scheduled task. The scheduled task will
contact the server specified by the ReportingServerURL setting and will initiate the transfer. If you
want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
?
Send-AppVClientReport \--URL [http://MyReportingServer:MyPort/]
\-DeleteOnSuccess

If the reporting server has been previously configured, then the --URL parameter can be omitted.
Alternatively, if the data should be sent to an alternate location, specify a different URL to override
the configured ReportingServerURL for this data collection.
The -DeleteOnSuccess parameter indicates that if the transfer is successful, then the data cache is
cleared. If this is not specified, then the cache will not be cleared.
Manual Data Collection
You can also use the Send-AppVClientReport cmdlet to manually collect data. This solution is
helpful with or without an existing reporting server. The following list displays information about
collecting data with or without a reporting server.

What not to virtualize

There are applications that are not possible or not recommended to virtualise, or require close
investigation. Typically you will find most of the problems are in applications with high OS
integration. Take great care not to consider an application request in isolation but check whether it
works with or depends on other applications or vice-versa. If one unit of the application family cannot
be virtualised then it places a question mark over the others.
Note that the following limitations are characteristics of App-V 5.0 SP3.

Concern Description

No Shortcut This issue is acceptable in some scenarios, such as packages which provide
present dependencies to others which can be linked with connection groups.
However, if this package merely provides a plug-in to another application, it
must contain a shortcut to launch that application in this package's virtual
context. One potential resolution to this issue is to use InstallShield Editor to
add shortcut(s) to the Windows Installer package.

ClickOnce ClickOnce is a per-user installation format which is generally incompatible

with the per-machine nature of virtual package deployment. A ClickOnce
application also may try to automatically update itself, which results in invalid
versioning in the application virtualisation client.  
DO NOT SEQUENCE OR PACKAGE ClickOnce applications. See here for
the correct approach
http://wiki.swissre.com/display/KB/ClickOnce+Deployment+Overview
Concern Description

OS Integrated The files that make up applications like Internet Explorer or Windows Media
Player, or frameworks like the .NET Framework, do not make good
candidates for virtualisation. These files should instead be installed locally on
the machine.

Boot Service Virtualised services are limited to the lifetime of the virtual application, so
services that must start at boot time do not make good candidates for App-V.
It may be possible to extract this service such that it can be installed locally on
the machine and allow the rest of the package to be virtualised.

Complex Applications with complex or unknown integration with other applications or

integration OS components need to be fully evaluated to identify and define interaction
points requirements

COM App-V does not support COM DLL surrogate virtualization (i.e. DLLs that run
Surrogate in Dllhost.exe), so this type of package may not work correctly if virtualised.
DLLs

COM Plus App-V does not support COM Plus components as they are dynamic and
cannot be captured, so this type of package may not work correctly if
virtualised.

Internet Microsoft does not support sequencing of these products

Explorer &
Service Packs

Device Driver System-level drivers such as print drivers or USB device drivers do not work
from a virtualised environment. It may be possible to extract this driver such
that it can be installed locally on the machine and allow the rest of the
package to be virtualised. Any application identified with system drivers will
need to be escalated with a decision whether to have the drivers extracted
and packaged separately as an MSI and deployed as a dependency for the
sequenced application.

Licensing Applications with licensing enforcement tied to the machine, e.g. the license is
Policies tied to the system's MAC address or hard disk serial number. This type of
application should not be sequenced if the activation cannot be completed by
the user at first launch.

Applications For example a program that will initiate a command and launch another
that are program. Normally you would include both programs in the same suite
required by however if this application launches or initiates commands in several
several applications it may not be feasible to include all of the applications in the
applications same suite. This is especially true if one of the reasons you are using App-V
 Concern Description

for is to avoid application conflicts. The virtual "bubble" can see the OS and
information or what’s installed on it but Windows 7 OS cannot see the content of a "bubble"
access and interact with it. On the same note remember that one "bubble" cannot see
inside another. Helper applications like Oracle Client or Java Runtime
Environment can be sequenced separately and connected to another
sequenced applications by using the Connection Groups functionality.

Path hard The application should not have folder/file paths hard coded in the application
coding itself. Some applications hard code the path of files in their executable rather
than parameterising them. Configuration files such as ini, conf, txt etc. and the
Registry are typical places to find application-specific settings.

Microsoft Although one can sequence Microsoft Office plug-ins, it is not advised to
Office Add-Ins sequence them due to many technical & usage issues. For example, in a
situation where there are more than two plug-ins used by a user, if they are
sequenced separately, then the user does not have control over which plug-in
sequence starts when he opens a document. The only Swiss Re accepted
work around to resolve the issue is to create a single suite, or connection
group, of all the plug-ins, and manage the presentation by AD groups /
AppSense or to place them in the core build. Sequencing of Office Add-Ins
requires explicit Swiss Re approval.

Auto Update Applications with automatic updates should not be sequenced if their update
mechanism cannot be disabled. Sequenced applications usually fail to
update. In addition, allowing auto-update leads to non-compliance of
application version.

Sequencing By default all apps would be sequenced independently. If multiple apps need
multiple apps to be sequenced together these would be identified in advance.
together

Final Package Folder

The sequencing process creates the following files:

File Description

 The primary package file, which contains the captured assets

.appv
and state information from the sequencing process.
 Architecture of the package file, publishing information, and
registry in a tokenized form that can be reapplied to a machine and
 File Description

to a specific user upon delivery.

.MSI Executable deployment wrapper that you can use to deploy .appv
files manually or by using a third-party deployment platform.

_DeploymentConfig.XML File used to customize the default publishing parameters for all
applications in a package that is deployed globally to all users on a
computer that is running the App-V client.

_UserConfig.XML File used to customize the publishing parameters for all applications
in a package that is a deployed to a specific user on a computer that
is running the App-V client.

Report.xml Summary of messages resulting from the sequencing process,

including omitted drivers, files, and registry locations.

.CAB Optional: Package accelerator file used to automatically rebuild a

previously sequenced virtual application package.

.appvt Optional: Sequencer template file used to retain commonly reused

Sequencer settings.

Publish in App-V 5.1 Comsole

Pre-publishing tasks
1. Check whether the application requires prerequisites. Ensure they are available in the
production environment.
2. Update the Software Catalogue item with the corresponding DirX role in the DirX Access
Role field.
Ensure to use only DirX roles / AD groups created exclusively for the purpose of software
deployment. See here for further details.

3. Check the workflow and software catalogue whether AppSense modification is required for
the application. AppSense will be defined as a pre-requisite if required. If so, raise a AppSense
Requests in SNOW. The request must reference the Desktop Experience Adaption (DES0xxxxxx)
and have the exported AppSense configurations attached (where possible).
 Publishing
1. Copy the directory containing the sequenced application (typically a sub-directory named
"<AppName> <Version> <Architecture> <Release>" under Final_Package) from
W:\AppData\WPR\WorkingArea to \\prodswsrc.swissre.com\AppV5$
2. Trigger a manual sync between the App-V5 Publishing servers.

  How to trigger a manual sync...

 Manual App-V5 source sync in PROD

Opposed to all other environments, the sequence source files are synced with the help of a
Robocopy job in Production. This sync is scheduled to be executed every couple of hours. However
when publishing or removing a package, you might want to trigger the sync manually to get an
immediate effect. The following steps describe how to trigger this sync.

 Download this script and save it on your computer.

 Right-click the file and select Run with PowerShell.

 Provide your X-account credentials in the Windows PowerShell window.

  Provide your password in the Windows PowerShell credential request window.

The execution of the copy job is very fast. Depending on the amount of files you can expect 1GB
copied in within 10 seconds.

2. Start Internet Explorer by using your x-Account credentials (Shift-RightClick >> Run as
different users).
3. Connect to http://chrv3689:55000.
4. Navigate to [\\appv5streaming.swissre.com\Streamingsource$]<packagename>\ and select
the <packagename>.appv file.

5. Click Add or Upgrade Packages

6. When imported, right-click the application and select Edit AD Access

7.
8. Type corp\CHR-GP-SV-WAE-P-Troubleshooting, and click Check. Select CHR-GP-SV-
WAE-P-Troubleshooting [corp.gwpnet.com] from the drop-down list. The CHR-GP-SV-WAE-P-
Troubleshooting AD group is for testing purposes. The Troubleshooting group should be deleted
after successful testing. Do not add the application related AD groups to the sequence. This will
be done at Rollout.

9. Click Grant Access, then Close.

10. If the application is published through SRGTS (Citrix XenApp), repeat steps 5, 6,7 and 8 to
add the CHR-DP-SV-SS3-P-XDXAFullAdmin-Prod AD group.
11. Right-click the application and select publish

Dynamic Configuration
When you import an App-V Package into the web-based management console, none of the external
configuration files will be imported automatically. By default, the client will receive only settings as
they are defined internally in the .App-V file (AppxManifest.xml).
 If an application is to be published with additional dynamic configuration:

1. Right-click the newly imported application and select Edit Deployment Configuration

2. Select the Advanced tab and click Import and Overwrite this Configuration
3. In the Choose File to Upload window, navigate to the .xml file containing the configuration
(_UserConfig.xml, or _DeploymentConfig.xml). Then click Open

4. The changes will now be applied to the Deployment configuration.

Connection Groups
If an application is part of a connection group:

1. Ensure the other applications in the connection group are imported as per the above steps.
2. Select the Connection Groups tab.
3. If the applicable connection group exists go to step 4. Otherwise:
a. Click Add Connection Group
b. Click New Connection Group and enter the package name of the common
prerequisite without the release number (e.g. Starnet IBM Java 6 JRE App-V 1.6.1.5 x64)

4. Click Edit next to Connected Packages

5. Select the dependent applications and click
6. Now add the primary pre-dependency (Step 1). Ensure the primary dependency is at the
bottom of the list (App-V 5 - Connection groups priorities)
7. For all of the dependent applications tick the Optional tickbox. Leave the primary pre-
dependency un-ticked (Step 2).
8. Click Save

9. Click Edit next to AD Access

10. On the AD Access page:

a. Click Add AD Group.
b. Type corp\ *and the name of the mandatory package. Click **Check.
c. Select mandatory package from the drop-down list.
d. Click Grant Access.
11. Right-click the connection group and select publish

Connection groups will fail to publish if a mandatory package is not published

Mandatory packages are required to be present in cache for a connection group to be published
otherwise delivery will fail with the following event 8012 error:

In order to prevent this error, ensure that the AD group belonging to the Connection Group is added
to the AD Group(s) of the mandatory prerequisite(s). In case you are replacing a package, which
serves as a mandatory package, ensure to replace the proper AD groups of the packages to be
replaced. This action is required in both deployment systems, App-V Server and SCCM!

Post publishing tasks

1. Test the application. Login to a computer where the App-V client is using the productive
server. You can normally use SRVW Win7 Standard.
2. If you are about to publish a sequence which updates/replaces a traditional package (MSI),
follow the procedure described in Enable pre-existing application users for SRVW ready versions <--
does not exist. In case of an update (the same AD groups are used), this step may have been
proceeded with the predecessor version already and isn't necessary anymore.
 PUBLISH IN SCCM 2012

1. Map the share: \\prodswsrc.swissre.com\AppV5$ with your X account for App-V5 content.
2. Copy the directory containing the packaged application (typically a sub-directory
named "<AppName> <Version> <Architecture> <Release>" under Final_Package) from
W:\AppData\WPR\RepositoryLive to \\prodswsrc.swissre.com\AppV5$
Note: If you have done step 1. and still have problems to copy the files, please order in SNOW
APPV: Sequencer User Internal (P) 
3. Open the SCCM Application Integration web interface:
4. Software Catalog entry lists all available records from the SWcatalog. For your quick
findings, automatic type completion is available.
Note: Synchronization from SNOW to the SCCM Application Integration web interface takes place
every 24h.

5. Select the App-V (User) radio button (Manufacture, Product Name, Version, Architecture and
SoftwareID will be pre populated according the SWcatalog information).
If the package requires machines scripts (or administrator rights), select the SRWP (Device) radio
button. Please refer to App-V 5 Dynamic Configuration files for further information.
 Click Create Application to reflect this information at SCCM Application.

6. Search your application in the SCCM console.

  Click here for detail instructions on how to search applications...

 Search for an application

 Open the SCCM Configuration Manager Console and browse to the application root
(\Software Library\Overview\Application Management\Applications).
 Click into the search field, then click the All Subfolders button.

 Type a sub-string of your application into the Search field.

2. Now right-click your application and select Move from the context menu.

3. Mark the Software Distribution folder and click OK.

4. Search the Collection for your application in the SCCM console.

  Click here for detail instructions on how to search collections...

 Search for a collection

 Open the Configuration Manager Console
 Ensure that Asset and Compliance is selected then click the appropriate collection
root. Note that in CM2012 depending on the engineering technology of the application you will find
the collection either under User Collections (App-V) or Device Collections (MSI).
 With the root selected click into the search field. The tool ribbon on the top of the
console will change and display you the search options. Click on the All Subfolders button
 Enter the name (or a substring) of the application in question into the search field and
click the Search button
2. Right-click your collection and select Move from the context menu.
3. Mark the Software Distribution folder and click OK.

Deployment Types

1. Search your application in the SCCM console.

  Click here for detail instructions on how to search applications...

 Search for an application

 Open the SCCM Configuration Manager Console and browse to the application root
(\Software Library\Overview\Application Management\Applications).
  Click into the search field, then click the All Subfolders button.

 Type a sub-string of your application into the Search field.

2. Now right-click your application and select Properties from the context menu.
3. Go to the Deployment Types tab. Do not delete the existing DT - this is the last step to be
performed.
4. Click Add....

5. Select Type Microsoft Application Virtualization 5. Browse for the .appv file of the
sequence (e.g. \\prodswsrc.swissre.com\AppV5$\SAP GUI for Windows 7.30.3 x86 R2\SAP GUI for
 Windows 7.30.3 x86 R2.appv). Click Next.

6. On the Import succeeded screen, click Next.

7. Insert Name convention: SRWP_APPV5_[APPLICATION-NAME]_[APPLICATION-
VERSION]. Click Next.

8. In the Specify installation requirements for this deployment type, click Add…
9. Select Custom. Select SRWP. Click OK.
10. Create a second requirement by clicking Add... again. Select User. Select Primary device.
Click OK. NOTE: Not required for App-V packages with Machine scripts (Device collections).
11. Click Next.

12. If the application has any dependencies expand the following section and follow the steps…
else click Next and continue with the next step.

  Click here to expand...

 Set Application Dependendies

 IMPORTANT Application packages that can potentially work together should NOT normally be set
as mandatory pre-reqs in SCCM. The user will order and need approval if additional packages are
needed. We only set PRE-REQs when the main application cannot work without.

IMPORTANT Pre-requisites have been set as the parent, i.e. the wrong way round. Understand that
the PRE-REQ category are packages such as Excel, Java, Silverlight, ODBC settings etc. the PRE-
REQ enables the parent or main application to fully function. It is absolutely vital to set the order
correctly.
If in doubt, to avoid errors ALWAYS take guidance from the Application IT Owner if the Discovery or
Engineering documentation does not explain clearly whether the pre-req is required and the
relationship order.

 With dependencies:* Insert *Dependency group name*. Click Add…

Note: In a dependency group are only applications which are alternative dependencies to each
other. Never insert two dependencies in the same group which are both required.
 With dependencies: *Select the application and click *OK.
 With dependencies: *Click *OK.
 If the application requires another dependency repeat the Add Dependency steps for
the required application.
2. Check the Summary and if everything is correct click Next.
3. Click Close.

4. Double click on the deployment type.

5. Go to Content. Ensure both Deployment options are set to Download content from
distribution point and run locally. Tick Allow clients to use a fallback source location for
content. Click OK.
6. Go to Application Catalog. Browse for the Icon.

7. Select the Icon and click Open.

  If the icon has not already been extracted, click here and follow these instructions

 App-V 5 - SCCM Application Catalog Icon

When deploying an application using SCCM, an icon is required to provide a visual reference within
the Software Center or Application Catalog.

The extraction of the icon file should be performed during the engineering phase, using IconsExtract
on the physical install. However, if that is not possible, the icon can be extracted during publishing -
using Virtual Package Editor.
Once the icon has been extracted IcoFXPortable should be used to remove any icon sizes 256x256
pixels or bigger.
Both IconsExtract and IcoFXPortable are available in W:\AppData\WPR\Tools
 Extract from physical install
The optimal time to extract an icon would be immediately after the sequence has been saved, but
before the installation is removed from the sequencing machine.
If the application is installed physically on a machine, follow the steps listed in How to get the
Application Icon file.
When extracted, the icon should be included in the package folder.

Extract from sequence

If the icon can not be extracted during engineering, the icon can be extracted from the sequence
using Virtual Package Editor - an AdminStudio application.

 On a sequencing machine, open Start Menu > Programs > AdminStudio >
AdminStudio 201x Tools > Virtual Package Editor
 Open the applications .appv file
 Click Application Data > Shortcuts, then select the main application from the
shortcuts list
 In the Icon field, note the path

 Go to Application Data > Files and Folders and navigate to the icon location
 Right-click the file and select Extract

 Navigate to the package folder and click Save

 Close Virtual Package Editor. When prompted do not save changes to the package.

Resizing the icon

The maximum size for SCCM Application Catalog Icon is 250x250 pixels.
To check the size of the exported icon:

 Open \\corp.gwpnet.com\dfs\GLOBAL\AppData\WPR\Tools\IcoFx
Portable\IcoFXPortable\IcoFXPortable.exe
 Select File > Open and navigate to the .ico. Click Open
 Right-click any 256x256 (or bigger) sized icon and select Delete Image

 Click Yes

 Repeat for the remaining 256x256 (or bigger) sized icons

 Select File > Save, then confirm the overwrite prompt
2. Click OK.
3. Select the dummy Deployment Type named To Delete ! please create a new DT. Click
Delete

4. Click Yes

5. Click Apply and continue to Add Content Locations

 ADD CONTENT Locations

1. Search your application in the SCCM console.

  Click here for detail instructions on how to search applications...

 Search for an application

 Open the SCCM Configuration Manager Console and browse to the application root
(\Software Library\Overview\Application Management\Applications).
 Click into the search field, then click the All Subfolders button.

 Type a sub-string of your application into the Search field.

2. Now right-click your application and select Distribute Content from the context menu.
3. Click Next.
4. Click Next.

5. Click Add.
Click Distribution Point Group.
6. Select DP Group All.
Click OK.
7. Click Next.
8. Click Next
9. Click Close

10. Check if the Content Status after a while is ok - the distribution to all servers is green and
successful.

 Green = Ok.
 Yellow = Distribution is still in progress.
 Red = Distribution faild on one or multiple servers.
If an App-V fails to deploy, often it has do with incorrect icons or other references in the App-V
 definition file.

DEPLOYMENT

Deployment Settings
Ensure to uncheck the Pre-deploy software to the user's primary device option for App-V 5
packages. If missed the package will be installed twice on the target computer, occupying double the
space and duplicate all shortcuts!

Deployment Modes
A deployment gets created automatically when you import an application through the Web UI
described on the first tab.
However you may need to alter some of the attributes related to Deployments.
There are 3 different deployment modes available.

1. Required (ignoring Service Window)

2. Required (during Service Window)
3. Available

Note! In SCCM Microsoft uses the terms Maintenance Window and Service Window. Both
describe the same and are typically set opposed to Business Hours and are typically set from 10pm
to 5am and over the weekend.
Strategy
Application actions should always be executed in a way that involves and disturbes the user as least
as possible. In addition a deployment should take place as close as possible to the schedule. Thus
the above Deployment Mode preferrence order applies.

Required (ignoring Service Windows)

Required (ignoring Service Windows) means that the action (install/uninstall) gets executed
automatically as soon as it hits the computer, regardless of any Service Window settings. This mode
is applicable for software, which doesn't need any user awareness and doesn't disturb a user during
working time.
The Deployment Mode is set during the creation of a Deployment and can't be altered once set. If
you want to change the Deployment Mode, you have to delete the existing one and create a new
one with the value you desire.

To ensure the application action gets executed at any time, ignoring any Service Window, ensure
that on the User Experience tab of the related Deployment, the Software Installation box is
checked.

Required (during Service Windows)

Required (during Service Windows) means that the application action (install/uninstall) gets
announced to the user as like Available but as soon as the computer runs during a Service Window,
the action (install/uninstall) will start automatically. Required (during Service Windows) is
applicable for software, where you don't want to disturb a user with the action (e.g. the installation
consumes lots of computer resources), still want to have the software action executed automatically.
The Deployment Mode is set during the creation of a Deployment and can't be altered once set. If
you want to change the Deployment Mode, you have to delete the existing one and create a new
one with the value you desire.

To ensure the application action is only running automatically when the computer is inside a Service
Window, ensure that on the User Experience tab of the related Deployment, the Software
Installation box is unchecked.

Available
Available means the application action (install/uninstall) gets announced to the user but not
executed. The user has to actively trigger the action (in Software Center). This mode is applicable
for software, where you need the attention of the user, e.g. an update that should only run, when the
user isn't working (with the predecessor).
The Deployment Mode is set during the creation of a Deployment and can't be altered once set. If
you want to change the Deployment Mode, you have to delete the existing one and create a new
one with the value you desire.

Important - User Collection linked Deployments

All Deployments linked to a user targeting collection (e.g. App-V Deployments) have to have set their
purpose to Required as else they won't be visible to the customer (they do not appear in Software
Center). Be aware that once a purpose is set it cannot be altered. You have to create an new
 Deployment from scratch.

ADD Virtual Environments

Overview
Applications that have connection group functionality will require the creation of an App-V Virtual
Environment.
Virtual Environments are ruled based definitions and are assessed dynamically client side if and
when applicable.
Using the OR operator to connect members within a group means they will be considered optional.
Delivery of which applications are delivered is controlled via the individual application collection
membership configuration.

Process
1. Open the SCCM Console.
2. Navigate to Software Library (1). Right-click App-V Virtual Environments and select
Create Virtual Environment (2)

3. The Name field should contain the primary dependency name with out the specific version.
Versions should only be used to distinguish multiple Virtual Environments, with different versions of
the same application.
4. Click Add...
5. In Group name, enter the same as the Virtual Environment name. Then click Add...

6. In the Specify Application window:

a. Select Software Distribution (1)
b. Click the primary dependency (2)
c. Tick the checkbox (3)
d. Click OK (4)

7. Click OK to close Add Applications window

8. Click Add...
9. In Group Name enter Dependencies of <Primary dependency>, then click Add...

10. In the Specify Application window:

a. Select Software Distribution (1)
b. Click the dependency (2)
c. Tick the checkbox (3)
d. Click OK (4)

11. Repeat for remaining applications. If necessary, use the Increase Order and Decrease
Order to correct issues with file and registry precedence.
12. When complete, click OK to close Add applications window
13. Click OK to close the Create Virtual Environment window

Priorities
SCCM currently does not give the ability to set the priority of a virtual environment nor does it handle
any conflicts dynamically. So if Package A is a member of two separate connection groups and a
user launches Package A, it will fail to launch. That is because SCCM delivers all connection groups
with the same 4.2 billion priority value.
 Launch Process inside App-V Virtual

A common troubleshooting task for the Microsoft Application Virtualization 5 client (App-V 5) is to
investigate or modify a local package by opening a process inside the context of an App-V
application.  This is also known as opening a process "in the App-V bubble" App-V 5 offers several
alternative methods to perform this task that differ significantly from techniques available in previous
versions of the product. Each method detailed below accomplishes essentially the same task, but
some methods may be better suited for some applications than others depending on whether the
virtualized application is already running.
Launching a process inside an App-V 5 virtualized environment can be done according to the next
options:

 Get-AppvClientPackage PowerShell Cmdlet

 The Command Line Switch “/appvpid:<PID>”
 The Command Line Hook Switch “/appvve:<GUID>”
 Run Virtual

Get-AppvClientPackage PowerShell Cmdlet

You can use the Start-AppVVirtualProcess cmdlet to retrieve the package name and then start a
process within the specified package's virtual environment (substitute the name of your package for
"<Package>"):
?
$AppVName = Get-AppvClientPackage <Package>
Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe

Hint: If you do not know the exact name of your package, you can use the command line Get-
AppvClientPackage executable, substituting the name of the application for "executable"; for
example: Get-AppvClientPackage Word. This method allows you launch any command within the
context of an App-V package whether the package is currently running or not. This is similar to using
the sfttray /exe cmd.exe /launch "App-V Application" syntax in App-V 4.6.

The Command Line Switch “/appvpid:<PID>”

This allows you to apply the /appvpid switch to any command which will allow the command to run
within the virtual process of the virtual process you selected by its PID (Process ID) as in the
example below:
?
cmd.exe /appvpid:8108

To obtain the process ID (PID) of your App-V process, use the command tasklist.exe from an
elevated command prompt and obtain the PID of your process. This method has the advantage of
launching the new executable in the same App-V environment as an already-running executable.

The Command Line Hook Switch “/appvve:<GUID>”

Where the /appvpid switch requires the virtual process to already be running, this switch allows you
to start a local command and allow it to run within the virtual environment of an App-V package and
will initialize it. The syntax is as follows:
?
cmd.exe /appvve:<PACKAGEGUID_VERSIONGUID>

For example:
?
cmd.exe /appvve:aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-
55555555

To obtain the package GUID and version GUID, of your application, run the Get-AppvClientPackage
cmdlet, then concatenate the package GUID and version GUIDs with an underscore between them.
For example:
?
PS C:\> Get-AppvClientPackagePackageId : aaaaaaaa-bbbb-cccc-dddd-eeeeeeee
VersionId : 11111111-2222-3333-4444-55555555
Name : MyApp 1.10

would yield the command line:

?
cmd.exe /appvve:aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-
55555555

Run Virtual

Run Virtual is an option to start a shortcut from a virtual environment by adding a registry key to the
registry. In this case a shortcut within the package is not required. However this option is available, it
is not recommended to be used, as this option only allows one package to be loaded from an
executable

PUBLISH-REFRESH

Overview
Changes in the App-V Management Console can take up to 10 minutes to be visible by the App-V
client. This is due to a setting in the App-V Publishing Server registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Server\PublishingService\PUBLISHING_M
GT_SERVER_REFRESH_INTERVAL is set, by default, to 600. This value represents the number of
seconds between refresh.
This setting is controlled via group policy.
 Detecting when a refresh has occured
Below lists two easy methods to manually check if a change in the Management Console has been
detected by the Publishing server.

Event viewer
If changes are detected by the publishing server, an event is raised in the Microsoft-AppV-Server-
Publishing > Operational event log.

1. On the publishing server, open Event Viewer

2. Expand Applications and Services Logs > Microsoft > AppV > Server-Publishing >
Operational
3. Click Filter Current Log.
4. In <All Event IDs>, type 11. Click OK

5. Refresh the event log until the corresponding change appears. TIP: Because the refesh is a
set interval, previous Event ID 11 timestamps will provide a guide for when the next refresh will
 occur.

Internet Explorer
Another alternative is to navigate to the Publishing server URL and refresh the returned XML until
the change appears.

1. Open a web browser.

2. Navigate to http://<Publishing Server>:55001/

3. Refresh the page until the change appears.

Client Data Storage Locations

The App-V client performs tasks to ensure that virtual applications run properly and work like locally
installed applications. The process of opening and running virtual applications requires mapping
from the virtual file system and registry to ensure the application has the required components of a
traditional application expected by users. This section describes the assets that are required to run
virtual applications and lists the location where App-V stores the assets.

Name Location Description

Package %ProgramData%\App-V Default location

Store for read only
package files

Machine %ProgramData%\Microsoft\AppV\Client\Catalog Contains per-

Catalog machine
configuration
documents

User %AppData%\Microsoft\AppV\Client\Catalog Contains per-

Catalog user
configuration
documents

Shortcut %AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups Stores previous

Backups integration
points that
enable restore
on package
unpublish

Copy on %AppData%\Microsoft\AppV\Client\VFS Writeable

Write roaming
(COW) location for
Roaming package
modification

Copy on %LocalAppData%\Microsoft\AppV\Client\VFS Writeable non-

Write roaming
(COW) location for
Local package
modification

Machine HKLM\Software\Microsoft\AppV Contains

Registry package state
information,
including VReg
for machine or
globally
 Name Location Description

published
packages
(Machine hive)

User HKCU\Software\Microsoft\AppV Contains user

Registry package state
information
including VReg

User HKCU\Software\Classes\AppV Contains

Registry additional user
Classes package state
information

Package Files

The Sequencer creates App-V packages and produces a virtualized application. The sequencing
process creates the following files:

File Description

 The primary package file, which contains the captured assets

.appv
and state information from the sequencing process.
 Architecture of the package file, publishing information, and
registry in a tokenized form that can be reapplied to a machine and
to a specific user upon delivery.

.MSI Executable deployment wrapper that you can use to deploy .appv
files manually or by using a third-party deployment platform.

_DeploymentConfig.XML File used to customize the default publishing parameters for all
applications in a package that is deployed globally to all users on a
computer that is running the App-V client.

_UserConfig.XML File used to customize the publishing parameters for all applications
in a package that is a deployed to a specific user on a computer that
is running the App-V client.

Report.xml Summary of messages resulting from the sequencing process,

 File Description

including omitted drivers, files, and registry locations.

.CAB Optional: Package accelerator file used to automatically rebuild a

previously sequenced virtual application package.

.appvt Optional: Sequencer template file used to retain commonly reused

Sequencer settings.

What’s in the appv file?

The appv file is a container that stores XML and non-XML files together in a single entity. This file is
built from the AppX format, which is based on the Open Packaging Conventions (OPC) standard. To
view the appv file contents, make a copy of the package, and then rename the copied file to a ZIP
extension. The appv file contains the following folder and files, which are used when creating and
publishing a virtual application:

Name Type Description

Root File Directory that contains the file system for the virtualized
folder application that is captured during sequencing.

PackageHistory.xml XML Information about the sequencing computer (operating

File system version, Internet Explorer version, .Net Framework
version) and process (upgrade, package version).

AppxBlockMap.xml XML Layout of the appv file, which uses File, Block, and
File BlockMap elements that enable location and validation of
files in the App-V package.

StreamMap.xml XML List of files for the primary and publishing feature block. The
File publishing feature block contains the ICO files and required
portions of files (EXE and DLL) for publishing the package.
When present, the primary feature block includes files that
have been optimized for streaming during the sequencing
process.

[Content_Types].xml XML List of the core content types in the appv file (e.g. DLL,
File EXE, BIN).

FilesystemMetadata.xm XML List of the files captured during sequencing, including

l File attributes (e.g., directories, files, opaque directories, empty
directories,and long and short names).
 Name Type Description

AppxManifest.xml XML Metadata for the package that contains the required
File information for adding, publishing, and launching the
package. Includes extension points (file type associations
and shortcuts) and the names and GUIDs associated with
the package.

Registry.dat DAT Registry keys and values captured during the sequencing
File process for the package.

HOW TO SEQUENCE

Overview
Purpose
The purpose of this document is to described how to apply the common sequencing standards that
must be adhered when certifying App-V sequenced applications regardless of the intended target:
Traditional Windows 7 SRWP PCs, XenApp SRGTS Terminal Server, or XenDesktop SRVW VDI. It
should be possible for different people, in different locations to develop App-V packages according
to the established definitions and produce predictable output.

Responsibilities
Only an engineer using the approved managed engineering infrastructure is permitted to sequence
applications - as per the Software Certification Process
The Engineer installs and configures the application following the installation instructions according
to installation manual document. Go back to the Discoverer if the document isn't valid. It is the job of
the engineer to comb through the installed assets of the package to locate and translate information
to make the software as machine, OS, and user independent as possible. This can be a difficult task
to perform. Applications can store such information in so many ways and in so many locations that it
is a real challenge for the sequencer to find them all.

Required Inputs
Do not attempt sequencing for a production target without having Full Discovery as input.
Copy the source media to the Sequencing VM as installing from a network share is not
recommended.

Sequencing Infrastructure
 Engineers must use the approved managed engineering infrastructure described here: Packager
VMs (Discovery, Engineering, Test, UAT)
Sequencing must be carried out on the current Sequencing Build of the current version of the SRWP
reference build (Win 7 x64 SP1 today). See How to build the standard Sequencing VMs

Sequencer Tool
The Microsoft Application Virtualization (App-V) Sequencer monitors and records the installation and
setup processes for software applications. Use the Sequencer to create a sequenced application
that runs inside a virtual environment. The Sequencer creates a virtual application that can be
distributed to target computers and that runs in a self-contained, virtual environment. The virtual
environment contains the information necessary to run the virtual application on the target computer
without interacting with the operating system installed on the target computer.

Naming Conventions
The App-V Package Name, App-V Path, and App-V parent folder name all use the same value. It is
important that naming conventions are followed to ensure the name is compatible with all of the
different delivery and reporting platforms.
See Sequencing - Naming Conventions

Limitations
There are applications that are either not possible or not recommended to virtualize. Some other
application require closer investigation.
See App-V 5 Sequencing Standards - What not to virtualise

Pre-sequencing considerations
Before sequencing, ensure the Pre-Sequencing Considerations have been reviewed.

The Sequencing Process

The sequencing process is split in to three key phases:

1. Pre-Sequencing Steps: actions to be performed before launching the sequencer tool. For
example, if the application has product dependencies on other applications, these applications must
be installed locally before starting the sequencing process, e.g. business applications, middleware.
This should include launching of any pre-dependencies to ensure their "first launch tasks" are not
included in the final sequence.
2. Monitoring Steps: These steps include the configuration of the sequence (e.g. name and
sequence type) and the installation of the application.
3. Post-Monitoring Steps: The post monitoring steps include "first-run tasks" (such as
accepting license agreements), the installation report, and use of the package editor.

Pre-Sequencing Steps

1. Fully review and understand all installation documentation (paying specific attention to the
"Pre-Requisites", and "Additional Inputs" sections), as well as the discovery questionnaire in SNOW.
2. Create a 'Checkpoint' with Microsoft Virtual Machine Manager (SCVMM).
3. Ensure all source files are accessible. If space permits, source media should be copied
locally. If not, command line based installers (e.g. batch files or scripts) should be accessible via a
mapped drive.
4. Install any pre-requisites. For physical installations, use the certified application installation
method. App-V applications can be installed using the sequencer Tools > Expand Package to
Local System option.
5. Launch any pre-dependencies. This is to ensure "first run tasks" of dependencies are not
captured in the sequence.

Monitoring Steps

1. Open Microsoft Application Virtualization Sequencer.

2. Select the option Create a New Virtual Application Package. This will launch the wizard for
creating a new virtual package.

3. Packaging Method:
a. Select Create Package (default) option to create a new package from scratch.
 b. Click Next.

4. Prepare Computer:
a. If no issues are detected, click Next and continue to the Type of Application window.
b. Otherwise:
i. Double-click any warnings to show a detailed description.
ii. Correct all issues that the sequencer reports.
iii. Click Refresh.
iv. Repeat for any remaining issues.
v. Report and record any that cannot be solved.
vi. Click Next.

5. Type of Application:
a. Select Standard Application (default).
b. Click Next.

6. Select Installer:
a. Select the installer for the application - This option typically applies to sequencing
only a single application using a single installer. This will define the executable file to have the
sequencing wizard automatically launch the installer for you.
b. Perform a custom installation - Select this option to start monitoring and then
manually install your application installer(s) if more than one installer or no installer setup at all.
c. Click Next.

7. Package Name:
a. Define the Virtual Application Package Name. Follow the standards defined,
Sequencing - Naming Conventions.
b. Click Next to continue.

8. Install and configure the application as per the discovery documentation.

a. If an Installer was selected in the Select Installer screen, the installer automatically
launches and pops-up with the installation Screens. Install the application as documented in the
discovery install instructions.
b. If a custom installation was chosen: Install all in the sequence mentioned as per the
discovery install instructions.. Do the file, folder, registry related operations in this phase, if any.

NOTE Applications that require a Reboot:

Applications that require a reboot to complete the installation will no longer require the reboot when
delivered to the client machines. This is because the Sequencer will monitor the operations that
need to be completed during reboot and process them prior to saving the package and prior to
delivery to client computers.
For applications requiring a reboot, if given the option click “yes.” The Sequencer will reboot and
automatically continue once logged back on to the sequencing workstation after the reboot has
taken place.
9. Tick I am finished installing once you are done with installations and click Next.

Post-Monitoring Steps
 The Sequencer collects system changes to the virtual environment.

1. Configure Software:
a. Many applications have first-run tasks such as accepting license agreements, etc. At
this stage, execute the required application(s) at least once by selecting the application and clicking
the Run Selected or Run All buttons (multiple executions are recommended to ensure any second-
run tasks are executed.
 b. Once two launches have completed, Click Next to continue.

2. Installation Report:
a. Double click an item in the report to view detailed information about the issue as well
as suggestions about how to resolve it. Mostly below items will be shown in the report:
i. Excluded Files
ii. Drivers
iii. COM+ System differences
iv. SxS Conflicts
b. Click Next to continue.

3. Customize:
a. Select Stop now.
b. Click Next to continue.

4. Create Package
a. Select Continue to modify package without saving using the package editor. to
modify the Virtual Package.
b. Click Next.

5. Completion:
a. Double click on each item in the report to view detailed information about the issue
as well as suggestions about how to resolve it.
b. Reported issues are saved along with the package in a report.xml file. Click Close.
6. Now check the different tabs and make modifications if required. Refer to Additional
Sequencing Configuration Steps and Sequencer Configuration Tabs for further information.

7. When customization is complete:

a. Click File > Save to save the package.
b. Create a folder with the same name as the sequence.

c. Open the new folder, then click Save.

8. Microsoft Application Virtualization Sequencer can now be closed.
9. Copy the folder to the deliverables sub-folder - Final package - under IN_PROGRESS.

Updates Made Outside the Sequencer

If you need to run a script. Develop a script if an application needs it. See more detail App-V
Scripting. Add the script to the package using App-V Configuration Editor (ACE)

PUBLISH & REMOVAL

Publishing or removing applications from the Packaging environment uses the same procedures as
the UAT environment. These processes are linked below.
Replace the following references:

 appv5pkg.swissre.com as the Management and Publishing server

 appv5pkgsrc.swissre.com for the shared content store
 The access permissions and SNOW role are the same for both UAT and Packaging
environments.
   AppV5 Publishing

 App-V5 Publishing

Note: Changes in the App-V Management Console can take up to 10 minutes to be visible by the
App-V client. For more information refer to App-V 5 Publishing Refresh
You will need access permission to the server to fulfill this task (x-account). Ensure you are a
member of the Admin group CHR-GP-SV-AP0-D-APPV5FullAdmins-UAT by ordering membership
via the SNOW role APP-V5: Local Administrator (T).

Application import
1. Copy the directory containing the sequenced application (typically a sub-directory named
"<AppName> <Version> <Architecture> <Release>" under Final_Package) from
W:\AppData\WPR\WorkingArea to \\appv5uatsrc.swissre.com\AppVStreamingSource$
(file://\\appv5uatsrc.swissre.com\AppVStreamingSource$)
2. Start Internet Explorer by using your x-Account credentials (Shift-RightClick >> Run as
different users).
3. Connect to http://appv5uat.swissre.com:55000.
4. If the application you are going to put into UAT has been tested previously, ensure to remove
the previous version entirely from the UAT environment (App-V5 - Remove Sequence UAT).
Otherwise go to the next step.

  How to remove the previous version...

Be aware that when a package is a member of a connection group, it will automatically remove the
package from the connection groups without any warning!

a.
i. Right-click the previous release and select Delete

ii. When prompted, click Confirm

iii. Delete the applications folder from
\\appv5uatsrc.swissre.com\AppVStreamingSource$
(file://\\appv5uatsrc.swissre.com\AppVStreamingSource$)
5. Navigate to \\chrv3687\AppV5StreamingSource$
(file://\\chrv3687\AppV5StreamingSource$)\<packagename>\ and select the <packagename>.appv
 file.

6. Click Add or Upgrade and copy the link to the .appv file into the textbox and select Add
Package
7. When imported, right-click the application and select Edit AD Access

8. On the AD Access page:

a. Click Add AD Group.
b. Type corp\domain users, and click Check.
c. Select Domain Users [corp.gwpnet.com] from the drop-down list
d. Click Grant Access.

9. Click Packages and navigate to the application.

10. Right-click the application and select Publish.

Dynamic Configuration
When you import an App-V Package into the web-based management console, none of the external
configuration files will be imported automatically. By default, the client will receive only settings as
they are defined internally in the .App-V file (AppxManifest.xml).
 If an application is to be published with additional dynamic configuration:

1. Right-click the newly imported application and select Edit Deployment Configuration

2. Select the Advanced tab and click Import and Overwrite this Configuration
3. In the Choose File to Upload window, navigate to the .xml file containing the configuration
(_UserConfig.xml, or _DeploymentConfig.xml). Then click Open

4. The changes will not be applied to the Deployment configuration.

Connection Groups
If an application is part of a connection group:

1. Ensure the other applications in the connection group are imported as per the above steps.
2. Select the Connection Groups tab.
3. If the applicable connection group exists go to step 4. Otherwise:
a. Click Add Connection Group
b. Click New Connection Group and enter the package name of the common
prerequisite without the release number (e.g. Starnet IBM Java 6 JRE App-V 1.6.1.5 x64

4. Select the created Connection Group and click Edit next to Connected Packages
5. Select the dependent applications and click
6. Now add the primary pre-dependency (Step 1). Ensure the primary dependency is at the
bottom of the list (App-V 5 - Connection groups priorities)
7. For all of the dependent applications tick the Optional tickbox. Leave the primary pre-
dependency un-ticked (Step 2).
8. Click Save

9. Click Edit next to AD Access

10. On the AD Access page:

a. Click Add AD Group.
b. Type corp\domain users, and click Check.
c. Select Domain Users [corp.gwpnet.com] from the drop-down list.
d. Click Grant Access.
11. Right-click the connection group and select publish

  AppV5 Removal

 App-V5 Removal

Note: Changes in the App-V Management Console can take up to 10 minutes to be visible by the
App-V client. For more information refer to App-V 5 Publishing Refresh
You will need access permission to the server to fulfill this task (x-account). Ensure you are a
member of the Admin group CHR-GP-SV-AP0-D-APPV5FullAdmins-UAT by ordering membership
via the SNOW role APP-V5: Local Administrator (T).

Remove application
Be aware that when a package is a member of a connection group, it will automatically remove the
package from the connection groups without any warning!

1. If the application is part of a connection group, ensure that all other components have also
finished UAT before removing; or alternatively, ensure this application is no longer required in the
connection group.
2. Start Internet Explorer by using your x-Account credentials (Shift-RightClick >> Run as
different users).
3. Connect to http://appv5uat.swissre.com:55000.
4. Right-click the previous release and select Delete

When prompted, click Confirm

5. Delete the applications folder from \\appv5uatsrc.swissre.com\AppVStreamingSource$
(file://\\appv5uatsrc.swissre.com\AppVStreamingSource$)

Remove applications from a Connection Group

1. Click Connection Groups then select the connection group
2. Click Edit next to Connected Packages
3. Select the application from the list then click

4. Repeat for any other unwanted applications.

5. Click Save

Remove Connection Group

1. Right-click the connection group and select delete

2. Confirm deletion of the group

SHORTCUT LINKED SEQUENCES

Overview
Some applications are launched via a shortcut that points to an executable in another App-V
application (i.e. Java Web Start applications).
In previous versions of App-V, the virtual (VFS) location could be used to launch the application.
With App-V 5, shortcuts must launch via a physical location first - before being able to access the
virtual environment.
For example:
Application A consists of a single shortcut that launches javaws.exe from a separate Java package.
In previous versions the shortcut would launch "C:\Program Files\JRE\bin\javaws.exe"
http://webstart.swissre.com/appa/app.jnlp
With App-V 5, this is not possible. There are two workarounds:

1. Point the shortcut to open cmd.exe first; then have the command and switches run in a
command window. This is the preferred method
e.g. %windir%\System32\cmd.exe /c START "" "C:\Program Files\JRE\bin\javaws.exe"
http://webstart.swissre.com/appa/app.jnlp.
With this method cmd.exe is running in the virtual environment - it can see the original install path
within the virtual file system.
Note: The double quotes after the START command are to supply a blank window title.
2. Edit the shortcut by replacing C:\Program Files with either:
%LOCALAPPDATA
%\Microsoft\AppV\Client\Integration\<PackageID>\Root\VFS\ProgramFilesX64 - when the
package is published to the user.
%ALLUSERSPROFILE
%\Microsoft\AppV\Client\Integration\<PackageID>\Root\VFS\ProgramFilesX64 - when the
package is published globally.
%PROGRAMDATA%\App-V\<PackageID>\<VersionID>\Root\VFS\ProgramFilesX64 - can also
be used, but the path is now dependent on the VersionID.

<PackageID> refers to the pre-dependency not the package containing the

shortcut.

"Command Prompt" Process

1. Open the sequencer
2. (Optional)
a. Select Tools > Expand Package to Local System...
b. Navigate to the pre-dependency package. Select the .appv file and click Open

3. Begin sequencing the application. When ready to create the shortcut(s): Select New >
Shortcut from the right-click menu.
4. In Type the location of the item, enter %WinDir%\System32\cmd.exe /c START ""
"<Path to exe>\<executable>.exe" <switches> (avoid hard coded paths, where possible).

5. Click Next
6. Complete the remaining shortcut creation steps as appropriate
7. Change the icon of the shortcut to the icon specified in the discovery
8. Complete the sequencing of the application

"Physical location" Process

1. Copy the pre-dependency to the machine

2. Import the package using powershell commands:

a. Add-AppvClientPackage -Path <Path to appv>\<package>.appv
b. Publish-AppvClientPackage -Name <Package Name> (Note: Wildcards can be
used)

3. Make a note of the PackageID

4. Sequence the application. When ready to creating the shortcut(s): Select New > Shortcut
from the right-click menu.
5. In Type the location of the item, enter %LOCALAPPDATA
%\Microsoft\AppV\Client\Integration\<PackageID>\Root\VFS\<Path to .exe>. Include plus any
additional parameters, then click Next
 NOTE: %ALLUSERSPROFILE% should be used for globally published applications.
6. Complete the remaining shortcut creation steps as appropriate
7. Change the icon of the shortcut to the icon specified in the discovery

FINAL PACKAGE NAMING

Final Package Folder

The sequencing process creates the following files:

File Description

 The primary package file, which contains the captured assets

.appv
and state information from the sequencing process.
 Architecture of the package file, publishing information, and
registry in a tokenized form that can be reapplied to a machine and
to a specific user upon delivery.

.MSI Executable deployment wrapper that you can use to deploy .appv
File Description

files manually or by using a third-party deployment platform.

_DeploymentConfig.XML File used to customize the default publishing parameters for all
applications in a package that is deployed globally to all users on a
computer that is running the App-V client.

_UserConfig.XML File used to customize the publishing parameters for all applications
in a package that is a deployed to a specific user on a computer that
is running the App-V client.

Report.xml Summary of messages resulting from the sequencing process,

including omitted drivers, files, and registry locations.

.CAB Optional: Package accelerator file used to automatically rebuild a

previously sequenced virtual application package.

.appvt Optional: Sequencer template file used to retain commonly reused

Sequencer settings.