Version 5.0

Trial Guide

Published: November 1, 2012

Feedback: Send suggestions and comments about this document to appvdocs@microsoft.com. Please

include the guide name and published date with your feedback.

Important Notice

This document is provided “as-is.” Information and views expressed in this document, including URL and

other Internet website references, may change without notice. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious.  No real association or

connection is intended or should be 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. You may modify this

document for your internal reference purposes.

2012 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, ActiveX, Excel, SoftGrid, SQL Server, Windows, Windows PowerShell, and

Windows 7 are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

IMPORTANT NOTICE........................................................................................................................................... 2

INTRODUCTION TO THE TRIAL GUIDE.................................................................................................................. 4

PRODUCT DOCUMENTATION.............................................................................................................................. 4

TRIAL SYSTEM REQUIREMENTS........................................................................................................................... 7

CHECKLIST OF TASKS......................................................................................................................................... 10

INSTALLING MICROSOFT APPLICATION VIRTUALIZATION MANAGEMENT SERVER AND PUBLISHING SERVER......11

INSTALLING MICROSOFT APPLICATION VIRTUALIZATION DESKTOP CLIENT........................................................20

INSTALLING MICROSOFT APPLICATION VIRTUALIZATION SEQUENCER...............................................................22

SEQUENCING XML NOTEPAD 2007.................................................................................................................... 25

SEQUENCING SILVERLIGHT® FOR INTERNET EXPLORER......................................................................................36

PUBLISHING OFFICE 2013 PREVIEW................................................................................................................... 39

OFFLINE DEPLOYMENT USING THE SEQUENCER-GENERATED MSI FILE...............................................................41

TROUBLESHOOTING.......................................................................................................................................... 41

ACCESSING THE MICROSOFT SUPPORT KNOWLEDGE BASE................................................................................41

CONTACTING MICROSOFT TRAINING................................................................................................................. 42

MICROSOFT APPLICATION VIRTUALIZATION OFFICIAL DOCUMENTATION..........................................................42

Introduction to the Trial Guide

This Trial Guide is designed to help system administrators quickly set up a limited Microsoft® Application

Virtualization (App-V) evaluation in a test environment. This guide details the steps necessary to install

Microsoft Application Virtualization server components for both Microsoft Application Virtualization

Management Server and Microsoft Application Virtualization Publishing Server. The system administrator

will be able to successfully install Microsoft Application Virtualization Desktop Client, publish the shortcuts

of sequenced applications, and then stream and run these virtual applications on App-V clients. The

administrator will also learn to virtualize a select set of applications using the Microsoft Application

Virtualization Sequencer.

To help this process flow as smoothly as possible, this guide should be read carefully before installing the

Microsoft App-V platform.

Audience for This Guide

This guide was written for Microsoft Windows® system administrators. As an information technology (IT)

professional, the user should have sufficient knowledge and experience to accomplish the following tasks:

Set up operating systems and install applications.

Add computers to domains.

Set up and work comfortably with Active Directory® Domain Services and Microsoft Domain Name

System (DNS).

Product Documentation

Comprehensive documentation for App-V is available on Microsoft TechNet in the App-V TechCenter at

http://go.microsoft.com/fwlink/?linkid=269780. The TechNet documentation includes online Help for the

App-V Sequencer, the App-V Client, and the App-V Server.

Overview of Microsoft Application Virtualization

Microsoft Application Virtualization enables the administrator to deploy, update, and support applications

as services in real time, on an as-needed basis. When App-V is used, individual applications are

transformed from locally installed products into centrally managed services. Applications become

available everywhere they need to be—no computer pre-configuration or changes to operating system

settings are required. Microsoft Application Virtualization consists of the following components:

Microsoft Application Virtualization Management Server

The App-V Management Server provides a centralized location to manage the App-V 5.0 infrastructure for

delivering virtual applications to both the App-V Desktop Client and the Remote Desktop Services

(formerly Terminal Services) Client. The App-V Management Server uses Microsoft SQL Server® for its

data store, where one or more App-V Management servers can share a single SQL Server data store.

The App-V Management Server authenticates requests and provides the security, metering, monitoring,

and data gathering required by the administrator. The server uses Active Directory and supporting tools to

manage users and applications.

The App-V Management Server has a Silverlight®-based management site, which enables administrator

configuration of the App-V infrastructure from any computer. By using this site, administrators can add

and remove applications, manipulate shortcuts, assign access permissions to users and groups, and

create connection groups. The App-V Management Server is the communication conduit between the

App-V Web Management Console and the SQL Server data store. These components can all be installed

on a single server computer, or on one or more separate computers depending on the required system

architecture. For more information on planning and App-V infrastructure review

http://go.microsoft.com/fwlink/?linkid=269785.

Microsoft Application Virtualization Publishing Server

The App-V Publishing Server provides App-V Clients with entitled applications for the specific user and

hosts the virtual application package for streaming. For the purposes of the Trial Guide, the Publishing

Server will be installed on the same machine as the Management Server. In production these two roles

can be separated providing greater scalability of the infrastructure.

Microsoft Application Virtualization Desktop Client

The App-V Windows Desktop Client retrieves virtual applications, publishes the applications on the client,

and automatically sets up and manages virtual environments at runtime on Windows endpoints. The

App-V Client stores user-specific virtual application settings, such as registry and file changes, in each

user's profile.

Microsoft Application Virtualization Remote Desktop Services (RDS) Client

The App-V RDS Client enables Remote Desktop Session Host servers to utilize the capabilities of the

App-V Desktop Client for shared desktop sessions.

Microsoft Application Virtualization Sequencer

The App-V Sequencer is a wizard-based tool that administrators use to transform traditional applications

into virtual applications. The Sequencer produces the application “package,” which consists of several

files. These files include a sequenced application (APPV) file, a Windows Installer file (MSI) that can be

deployed to clients configured for standalone operation, and several XML files including Report.XML,

PackageName_DeploymentConfig.XML, and PackageName_UserConfig.XML. The UserConfig and

DeploymentConfig XML files are used to configure custom changes to the default behavior of the

package.

Trial System Requirements

The following section lists the computer systems used for this evaluation; detailed installation steps are

provided later in the document. This document demonstrates setting up an App-V 5.0 infrastructure with

Windows 7 SP1, Windows Server 2008 R2, and SQL Server 2008 R2 as they are the most common at

the time this document was written. Look for updates to this document that include Windows 8, Windows

Server 2012, and SQL Server 2012 at a later date.

Important: This trial is designed to explore the features of Microsoft Application Virtualization. This document was not designed for evaluating how Microsoft Application Virtualization should be implemented in a production environment. As such, it is strongly recommended that the trial is implemented in a test lab environment using non-production, physical or virtual machines, following the exact configurations described in this guide.

Note: Do not lock down any components of the computers, and do not try to reuse standard operating system images.

A list of the machines and software requirements for the Trial Guide, including links to prerequisite

installers, is provided in the table below. Detailed step-by-step instructions are provided in the document,

including links to known steps for specific tasks.

Machine Role Operating System Requirements Additional Software

Domain Controller

Provides authentication to clients, and App-V Server.

Windows Server 2008 R2 SP1 with all current patches

1.4 GHz or faster processor (64-bit)

1 GB of RAM

40 GB of disk space

Network Card

Roles and Features

Active Directory Domain Services

Microsoft DNS

App-V Server*

Hosts App-V Management, Publishing, and Database Server

Windows Server 2008 R2 SP1 64-bit with all current patches***

1.4 GHz or faster processor (64-bit)

2 GB of RAM

80 GB of disk space

Network Card

External Software

Microsoft .NET Framework 4.0 Extended

Microsoft Visual C++ 2010 SP1 Redistributable Package for 64-bit

Microsoft Visual C++ 2010 SP1 Redistributable Package for 32-bit

Microsoft Silverlight

PowerShell 3.0

Roles and Features

Application Server

Web Server (IIS)

SQL Server 2008 R2 (64-bit)

Database Engine Services

App-V Client Windows 7 Professional, Enterprise, or Ultimate (32-bit or 64-bit) with Service Pack 1 and all current patches***

1 GHz or faster processor

1 GB of RAM

40 GB of disk space

Network Card

External Software

Microsoft .NET Framework 4.0 Extended

PowerShell 3.0

App-V Sequencer** Windows 7 Professional, Enterprise, or Ultimate (32-bit) with Service Pack 1 and all current patches***

1 GHz or faster processor

1 GB of RAM

40 GB of disk space

Network Card

External Software

Microsoft .NET Framework 4.0 Extended

PowerShell 3.0

* The core roles for managing the App-V 5.0 environment are all hosted on the same machine in the Trial Guide, as it is intended for testing only. In production environments, it is recommended to split these roles between several different hosts.

**Always sequence 32-bit applications on a 32-bit operating system (OS). This includes sequencing 32-bit applications for delivery to 64-bit clients. When sequencing 64-bit applications, they must be sequenced on a 64-bit OS and can only be delivered to 64-bit clients. This guide will use Windows 7 Enterprise SP1 (32-bit).

***Do not install Silverlight or .Net 4.0, these applications will be installed in the Trial Guide.

All computers must be members of a common domain (Figure 1). Virtual machines can be used on a

single physical computer that meets the system requirements of this trial. Ensure that the minimum

hardware requirements for each operating system are met for each system.

Figure 1: Application Virtualization trial in an isolated network

In this trial, it is important to set up Microsoft Application Virtualization in a test lab, completely separate

from a production network. The purpose of this evaluation is to acquire basic experience with the App-V

platform. Any questions relating to integration into a production environment, such as security concerns

and enterprise-level design should be addressed later. In addition, this guide covers only basic platform

functionality to simplify the procedures and focus on proof of concept.

Checklist of Tasks

The following table lists all the tasks that need to be completed. The tasks must be completed in the order

they are presented for the desired outcome of a working App-V infrastructure. Completion of all tasks

listed under “Basic Tasks” will result in a successful basic system evaluation. To continue with evaluating

other system components, refer to the list of tasks under “Additional Information.”

Basic Tasks

Area Task

Server Setup Set Up the Active Directory Domain Services Domain Controller

Set Up the Microsoft Application Virtualization Management Server

Install Microsoft SQL Server 2008 R2

Install the App-V Management Server and Publishing Server

Client Setup Installing Microsoft Application Virtualization Desktop Client

Sequencer Setup Installing Microsoft Application Virtualization Sequencer

Sequencing XML Notepad 2007

Sequencing Silverlight ® for Internet Explorer

Application Deployment

Publish the Application s

Application Test Stream and launch the Application s

Office® 2013 Preview Publishing Office 2013 Preview

Additional Information

Area Tasks

Standalone MSI Offline Deployment Using the Sequencer-Generated MSI File

Troubleshooting Troubleshooting App-V

Installing Microsoft Application Virtualization Management Server and

Publishing Server

The section details the step-by-step process of installing Microsoft Application Virtualization Management

Server and Publishing Server.

Note: The software and operating system versions listed in the following section must be used to ensure

that the instructions and screen shots are accurate for testing and evaluation.

Set Up the Active Directory Domain Services Domain Controller

The following items must be configured on the domain controller computer:

Active Directory Domain Services

DNS

Note: Step by step instructions for setting up Active Directory Domain Services is available at: http://technet.microsoft.com/en-us/library/cc755059(v=ws.10).aspx. This guidance assumes a test environment and will create a new forest.

Configure the Active Directory Groups and Accounts

Perform the following steps on the Windows Server 2008 R2 SP1 Domain Controller.

Active Directory

Before installing the App-V Management Server, the following objects in Active Directory must be created:

Organizational Unit (OU): Create an OU in Active Directory for Microsoft Application Virtualization–

specific groups and for the necessary Microsoft Application Virtualization domain account. For this

trial, call the OU “AppVTrial.” Create all new Active Directory objects in this OU throughout the trial.

Microsoft Application Virtualization Administrative Group: Microsoft Application Virtualization

requires selection of an Active Directory group to use as an App-V administrators group for controlling

administrative access to the Management Console. Create a global security group named “AppV Administrators,” and add to this group every user who needs to use the Management Console, by

default add the built-in administrator.

Note: For the purposes of this guide, only a single-domain setup is described in this test lab environment.

If groups are created, create them as global groups. Multi-domain and multi-forest scenarios are

supported but are outside the scope of this guide.

Microsoft Application Virtualization Users Group: The Trial Guide assumes that every user account

that accesses Microsoft Application Virtualization Management Server functions is a member of a

single group for general platform access. Create a group named “AppV Users.” Microsoft Application Virtualization Computers Group: The Trial Guide assumes that every

computer account that accesses Microsoft Application Virtualization Management Server functions is

a member of a single group for general platform access. You can use an existing group (such as

Domain Computers) or create a new group. Create a group named “AppV Computers.” Add the

App-V Client computer to the AppV Computers group.

Domain Test User Account: This account will be the user test account for Microsoft Application

Virtualization end-user functionality. Add your domain test user account to the AppV Users group

presented earlier in this list.

Application Groups (Optional): Microsoft Application Virtualization associates the right to use an

individual application with an Active Directory group. For the purposes of simplifying this guide, all test

applications are associated with the Microsoft Application Virtualization User Group (AppV Users),

even though many other options exist for production use, such as creating separate AD groups for

specific applications.

Set Up the Microsoft Application Virtualization Management Server and

Publishing Server

The following items must be installed on the Windows Server computer before installing Microsoft

Application Virtualization Management Server or Publishing Server. The computer must also be a

member of the Active Directory domain in which the accounts and groups were created. For the purpose

of this Trial Guide, Windows Server R2 SP1 has been installed, and the Management Server and

Publishing Server will be installed on the same Windows Server computer. In large environments the

Management Server and Publishing Server should be on separate Windows Server computers.

Perform the following steps on the computer that will be the App-V Management Server:

Install Prerequisites

All prerequisites must be met before the App-V management server will properly be installed.

Install Microsoft .NET Framework 4.0 Extended

.NET 4 Framework is required for PowerShell 3.0 and App-V server components..

1. Download Microsoft .NET Framework 4.0

2. Close all running programs and save all work before proceeding.

3. Run dotNetFx40_Full_x86_x64.exe.

4. Read and accept the license terms. Click Install.5. On the Installation is Complete page, click Finish.

Install Microsoft Visual C++ 2010 SP1 Redistributable 64-bit Package

C++ 2010 is a programming package required for the App-V server components.

1. Download Visual C++ 2010 SP1 Redistributable for 64-bit.

2. Close all running programs and save all work before proceeding.

3. Run vcredist_x64.exe.4. Read and accept the license terms. Click Install.5. On the Installation is Complete page, click Finish.

Install Microsoft Visual C++ 2010 SP1 Redistributable 32-bit Package

C++ 2010 is a programming package required for the App-V server components.

1. Download Visual C++ 2010 SP1 Redistributable for 32-bit.

2. Close all running programs and save all work before proceeding.

3. Run vcredist_x86.exe.4. Read and accept the license terms. Click Install.5. On the Installation is Complete page, click Finish.

Install Microsoft Silverlight

Silverlight is required to use the management web site on the server.

1. Download Microsoft Silverlight.

2. Close all running programs and save all work before proceeding.

3. Run Silverlight_x64.exe.

4. On the Install Silverlight page click Install now.5. On the Enable Microsoft Update page click Next.

6. Click Close.

Install Windows PowerShell 3.0

PowerShell 3 is used to control the management server. .NET 4 is a prerequisite to this update.

1. Download Windows6.1-KB2506143-x64.msu.1. Close all running programs and save all work before proceeding.

2. Run Windows6.1-KB2506143-x64.msu.

3. In the Windows Update Standalone Installer dialog, click Yes.

4. Read the license terms and then click I Accept.5. On the Installation complete page, click Restart Now.

Configure the Application Server

Add the Application Server role and all required role features needed. Additionally, ensure the following

role services are selected.

.NET Framework 3.5.1 Features

Configure IIS 7.5 for Windows Server 2008 R2 SP1

Add the Web Server (IIS) role with the following role services enabled:

Common HTTP Features

o Static Content

o Default Document

Application Development

o ASP.NET

o .NET Extensibility

o ISAPI Extensions

o ISAPI Filters

Security

o Windows Authentication

o Request Filtering

Management Tools

o IIS Management Console

Register ASP.NET with .NET 4.0 Framework in IIS

These registrations are required for proper installation of all App-V server components.

1. Open a command window as administrator.

2. Run the following two commands

a. “C:\Windows\Microsoft.Net\Framework\v4.0.30319\aspnet_regiis.exe” –ir

b. “C:\Windows\Microsoft.Net\Framework64\v4.0.30319\aspnet_regiis.exe” -ir

Install Microsoft SQL Server 2008 R2

Note: Using SQL Server 2008 R2 Express Edition is not a supported configuration. Installation of one of

the following editions of Microsoft SQL Server: Standard, Enterprise, or Datacenter with the following

feature: Database Engine Services is required.

1. Run the appropriate SQL Server 2008 R2 installer file

2. Click on Installation in the left pane of the SQL Server Installation Center window.

3. Next choose New installation or add features to an existing installation.4. On the Setup Support Rules page click OK..5. If prompted, enter a product key and then click Next.6. Read and accept the license agreement, and then click Next.7. On the Setup Support Files page click Install.

a. When the Setup Support Files step is complete, the wizard will close and re-open. Wait for it

to re-open before continuing

8. On the Setup Support Rules page, review all rules to ensure a Status of Passed, repairing all rules

that have not passed (ignore the warning for Windows Firewall), and then click Next.9. On the Setup Role page, select SQL Server Feature Installation and then click Next.10. On the Feature Selection page choose Database Engine Services and then click Next.11. On the Installation Rules page click Next.12. On the Instance Configuration page click Next 13. On the Disk Space Requirements page click Next.14. On the Server Configuration page, click Use the same account for all SQL Server services. For

Account Name enter NT AUTHORITY\SYSTEM and click OK.15. Change all Startup Types to Automatic and click Next.16. On the Database Engine Configuration page click Add Current User (domain\administrator), and

then click Next.17. On the Error Reporting page click Next.18. On the Installation Configuration Rules page click Next.19. On the Ready to Install page click Install.20. On the Complete page click Close, then close the SQL Server Installation Center window.

Install the App-V Management Server and Publishing Server

Perform the following steps on the computer that will be the App-V Management Server and Publishing

Server:

1. Login to the server as a domain admin account. Ensure this account also has local administrative

privileges.

2. Run appv_server_setup.exe.

3. On the Microsoft Application Virtualization (App-V) Server 5.0 Setup wizard, click Install.

Figure 2: App-V Server 5.0 Setup wizard

4. Read and accept the license agreement, and then click Next.

5. On the Feature Selection page, select Management Server, Management Server DB, and

Publishing Server features and then click Next.

Figure 3: Feature Selection page

6. On the Installation Location page, accept the default installation location, and then click Next.7. On the first Create New Management Server Database page, click Next.

Figure 4: Create New Management Server Database page

8. On the second Create New Management Server Database page, click Next.9. On the Management Server Configuration page, enter the Active Directory security group which will

be responsible for managing App-V (DOMAIN\AppV Administrators), in the Port binding field type

888 and then click Next.

Figure 5: Management Server Configuration

10. On the Publishing Server Configuration page in the Port binding field type 889 and then click

Next11. On the Ready page, click Install.12. On the Finished page, click Close.

Reminder: Use new or unused machines or virtual machines for the purpose of this trial.

Configure the Publishing Server refresh interval

By default the Publishing Server polls the App-V database for published applications every 10 minutes

(600 seconds). This is called a publishing refresh. For the purpose of this Trial Guide, change the

publishing refresh interval to 10 seconds to reduce wait times during publishing. Evaluation of the correct

interval for a production environment is outside the scope of this document.

1. Click Start and type regedit and press Enter.2. Navigate to HKLM\Software\Microsoft\AppV\Server\PublishingService.3. In the right hand pane, find the value PUBLISHING_MGMT_SERVER_REFRESH_INTERVAL.

4. Right click the value, select Modify.5. In the value data field, enter 10. Click OK.

6. Close the registry editor.

7. Click Start and type CMD.8. At the command prompt type iisreset /noforce, press Enter.

9. Close the command prompt.

Share the content folder

The content share is the central library of App-V packages. The content store contains the source files of

the packages published by the App-V publishing server.

1. Open Windows Explorer.2. Create a folder on the root of the C: drive named Content.

NOTE: In the production environment, the content folder should not be placed on the same drive as

the operating system files as it can affect performance of the system. Ensure the use of a different

drive in a production environment.

3. Browse to C:\, right click the Content folder, go to Properties.4. Click the Sharing tab, click Advanced Sharing.5. Check Share this folder. Click Permissions6. Click Add. Click Object Types. Select Computers. Click OK.7. In the Enter the object names to select box, enter the name of the App-V management server.

Click OK.8. Click Add. Type AppV Administrators, click OK.9. Click the AppV Administrators group, in the Permissions for AppV Administrators section

click Full Control.10. Click OK, Click OK, Click Close.

Configure Windows Firewall to Allow Incoming Connections

1. Open Control Panel, open Windows Firewall2. Click Advanced Settings.

3. Click Inbound Rules, in the actions pane click New Rule…4. Select Port, click Next5. Select TCP, in the Specific local ports: field, enter 888,889, click Next6. Click Next, Unselect Private, and Public, click Next7. In the Name field, enter AppV Server Connections, click Finish

The installation of the Microsoft Application Virtualization Management Server and Publishing Server is

now complete. Publishing an application after the installation of the Application Virtualization Sequencer is

discussed later in this guide. If any errors were encountered during the process, please refer to the

Troubleshooting section at the end of this guide.

Installing Microsoft Application Virtualization Desktop Client

The section guides details the step-by-step process of installing Microsoft Application Virtualization

Desktop Client on a Windows 7 computer.

Perform the following steps on the computer that will be the App-V Client

1. Login as an account with local administrator privileges.

2. Download and install .NET Framework 4.0

3. Download and install Windows6.1-KB2506143-x64.msu (64-bit client OS) or Windows6.1-

KB25061430-x86.msu (32-bit client OS), Restart the workstation.

4. Login as an account with local administrative privileges and run appv_client_setup.exe.

5. In the Microsoft Application Virtualization (App-V) Client 5.0 Setup dialog box, click Install.6. Read and accept the license agreement, and then click Next.7. On the Microsoft Update Opt In page, select I don’t want to use Microsoft Update and then

click Next.8. On the Customer Experience Improvement Program page, click Install.9. When the installation is complete, click Close.

Configure the App-V 5.0 client to communicate with the App-V 5.0 Publishing Server

1. Click Start | All Programs | Accessories | Windows PowerShell | Windows PowerShell, right

click, Run as Administrator.2. At the PowerShell prompt, type the following commands, each on its own line, pressing Enter

after each command:

a. Set-ExecutionPolicy Unrestricted

Note: Setting the PowerShell script execution policy to unrestricted is not recommended, but

in the lab environment it is sufficient. For more information on the PowerShell Execution

policies see http://technet.microsoft.com/en-us/library/hh849812.aspx

b. Import-Module AppVClient

c. Add-AppvPublishingServer -Name name_of_AppV_Publishing_Server -URL

http:// name_of_appv_server:889

d. Set-AppVPublishingServer –ServerID 1 –GlobalRefreshEnabled 1 –

GlobalRefreshOnLogon 13. Close Windows PowerShell4. Restart the workstation.

Note: If Task Scheduler is opened as an Administrator, two new tasks are created to perform the

App-V Client Refresh operations: The User task, which was created during the installation of the App-

V 5.0 Client; and the Global task, which was created by the previous PowerShell commands.

Figure 6: Task Scheduler showing the App-V 5.0 Client refresh task

Note: In the previous step, the App-V client was configured to communicate with the App-V Publishing

server. If this step was skipped, the App-V client would be in stand-alone mode. For more information

about stand-alone mode, see the Offline Deployment Using the Sequencer-Generated MSI File

section, later in this guide.

Installation and configuration of the Microsoft Application Virtualization client is now complete. Exploration

of the virtual application management client console is detailed later in this guide. If any errors were

encountered during the process, please refer to the “Troubleshooting” section at the end of this guide.

Configure the Windows Firewall for App-V 5.0 client to server communication

All communication between the App-V Publishing Server and App-V Client is initiated by the App-V Client.

The built-in Windows Firewall requires no additional configuration in order for the client to communicate in

this fashion. Some third party firewall block any unknown outbound traffic initiated from aclient. In this

case, you must create rules for the AppVClient application to initiate outbound connections. Please refer

to third-party documentation for further information about creating outbound rules.

Installing Microsoft Application Virtualization Sequencer

The Microsoft Application Virtualization Sequencer is used to create the virtual applications and

application packages that are streamed from the App-V Publishing Server to the App-V Clients.

Before You Install Microsoft Application Virtualization Sequencer

The Sequencer computer must meet the same minimum requirements as Microsoft Application

Virtualization Desktop Client. Virtual machines are ideal for sequencing because they can easily be reset;

however, a physical computer with a clean image on a local partition can be used to enable rapid re-

imaging after each package sequencing operation has been completed.

NOTE: Always sequence 32-bit applications on a 32-bit sequencing OS. This includes sequencing 32-bit applications for delivery to 64-bit clients. When sequencing 64-bit applications, they must be sequenced on a 64-bit sequencing OS and can only be delivered to 64-bit clients.

Note: Additional information on sequencing beyond what is contained in this guide is available on

TechNet at: http://technet.microsoft.com/en-us/library/cc817192.aspx and at:

http://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx

There are two main methods for setting up the Sequencer computer for this trial:

Option 1: Virtual Machine

Perform a fresh install of a supported operating system to a virtual machine (VM). Do not use a "standard

desktop image" or install any other applications on this image at this time. If using Hyper-V, create a

snapshot; after each application sequence, copy the sequence to the content share, and then apply the

saved snapshot to get back to a "clean" operating system.

Option 2: Physical Computer

Perform a fresh install of a supported operating system to the physical computer. Do not use a "standard

desktop image" or install any other applications on this image at this time. Use a disk imaging utility to

store an image of the first partition on the second partition. This method allows rapid restoration of the

sequencing computer to a "clean" installation of the operating system after each time an application is

sequenced.

Install Microsoft Application Virtualization Sequencer

Important: The computer used for the Sequencer must contain only a fresh installation of the Windows

operating system. Do not install Microsoft Application Virtualization Sequencer on a computer that hosts

Microsoft Application Virtualization Management Server or Microsoft Application Virtualization Desktop

Client.

Reminder: DO NOT use a standard desktop image, use a fresh install of the operating system with no

additional software installed.

Perform the following steps on the computer that will be the App-V Sequencer

Install the Sequencer

1. Login using an account with local administrative privileges.

2. Download and install .NET Framework 4.0

3. Download and install Windows6.1-KB25061430-x86.msu. Restart the workstation.

4. Login using an account with local administrative privileges and run appv_sequencer_setup.exe.

5. In the Microsoft Application Virtualization (App-V) Sequencer 5.0 Setup dialog box, click Install.6. Read and accept the licensing agreement, and then click Next.7. On the Customer Experience Improvement Program page, click Install.8. When the installation is complete, click Close.

9. Launch the services management console, disable the Windows Defender service.

10. Reboot the Sequencer workstation.

Note: Even though there is no prompt to reboot the system, a reboot is required to complete the

installation. Also, Windows Defender and other anti-virus applications should be turned off prior to

sequencing. If an application’s setup file must be downloaded from the internet, make sure to download it

from a computer with active anti-virus.

Prepare the computer for sequencing

The App-V sequencer will automatically check the current state of the system to ensure no outstanding

issues on the system (such as a pending reboot, Anti-Virus enabled, etc.).

1. Click Start | All Programs | Microsoft Application Virtualization Sequencer | Microsoft Application Virtualization Sequencer to open Microsoft Application Virtualization.

2. Click Create a New Virtual Application Package.3. Select Create Package (default), click Next.

Figure 7: Prepare Computer Screen – Showing Warnings

4. Review and resolve any outstanding issues identified by the sequencer.

5. Close the sequencer.

Note: Now, save a snapshot of the VM or a fresh image if using a physical computer. The sequencing

computer can now be reset to a clean base state with the operating system and the Sequencer installed

after each package sequencing operation has been completed. Prior to creating a snapshot or image,

FIRST ENSURE that the sequencer is not open.

Sequencing XML Notepad 2007

This section provides detailed instructions for implementing a simple sequencing process. Use XML

Notepad 2007 as a test case that can be easily and quickly deployed using the Microsoft Application

Virtualization platform.

Perform the following steps on the App-V Sequencer:

Important: Follow these steps exactly as written.

1. Download XML Notepad 2007 to the desktop.

2. Create a directory on the desktop of Sequencer desktop called XMLNotepad2007.3. Click Start | All Programs | Microsoft Application Virtualization Sequencer | Microsoft

Application Virtualization Sequencer to open Microsoft Application Virtualization Sequencer.

Figure 8: Microsoft Application Virtualization Sequencer

4. Click Create a New Virtual Application Package. The Sequencing Wizard appears.

5. On the Packaging Method page, select Create Package (default), and then click Next.6. On the Prepare Computer page, the Sequencer will look for and report on any services running that

could potentially cause problems while sequencing.

If the Sequencer recommends stopping any processes on the machine, be sure to stop those processes now. Once the processes are stopped return to the Sequencer and click Refresh.

When the Sequencer displays Your system is ready to create a virtual package, no issues were detected, click Next.

Figure 9: Computer Ready for Sequencing

7. On the Type of Application page, ensure Standard Application (default) is selected and then click

Next.8. On the Select Installer page, ensure Select installer for the application is selected, click Browse

then browse to the downloaded XmlNotepad.msi file click Open,, and then click Next. 9. On the Package Name page, in the Virtual Application Package Name field, type XML Notepad

2007, in the Primary Virtual Application Directory (required) field type C:\Program Files\XML Notepad 2007, and then click Next.

Figure 10: Entering Virtual Application Name and Primary Installation Directory

10. The Sequencer will now begin monitoring the system and launch the XmlNotepad.msi installer file. If

prompted to Run or Cancel the installer, click Run.11. On the Welcome page, click Next.12. Accept the terms of the XML Notepad 2007 license agreement, and then click Next.13. On the Custom Setup page, review the default installation location and then click Next.

Note: In previous versions of App-V, it was recommended that the default installation location be changed

to a subdirectory of the virtual drive letter that clients will be using as their “sandbox” location (typically the

Q:\ drive). Since App-V 5.0 clients no longer require the virtual drive letter, there is no need to change the

default installation location during sequencing.

14. On the Ready to Install page, click Install.

Figure 11: Ready to Install XML Notepad 2007

15. On the Completed setup of XML Notepad 2007 page of the XML Notepad setup wizard, click

Finish.

16. After a few moments, an Internet Explorer window will open. Close this window.

17. Back in the Sequencer, check the box labeled I am finished installing and click Next.18. On the Configure Software page, select XML Notepad 2007 and then click Run Selected.

Figure 12: Run programs to manage first use tasks

19. XML Notepad 2007 opens. Close XML Notepad 2007.

20. Back in the sequencer, click Next.21. On the Installation Report page, click Next.22. On the Customizing page, select Customize. Further configure the virtual application package

and click Next.23. On the Prepare for Streaming page click XML Notepad 2007, and then click Run Selected.

Figure 13: Prepare the application for Streaming

24. XML Notepad 2007 opens. Close XML Notepad 2007.

25. On the Prepare for Streaming page, click Next.26. On the Target OS page, click Next, accepting the default to allow this package to run on any

operating system.

Figure 14: Configure Allowed Operating Systems

27. On the Create Package screen, select Continue to modify package without saving using the package editor and then click Next.

28. On the Package completed page, click Close

Note: The package editor opens allowing the administrator to make any necessary changes, including

changing supported OS’s in the Deployment tab, or changing the shortcut locations or FTA’s (file type

associations) in the Shortcuts and FTAs tab.

Figure 15: App-V Sequencer Package Editor

29. In the Package Editor, click the Shortcuts and FTAs tab.

30. In the Applications pane, right-click Readme, select Remove and then click OK31. Review the information in the remaining tabs. Click File | Save.

32. In the Save As dialog box browse to the XML Notepad 2007 folder (created earlier on the desktop)

and click Save.33. Close the Sequencer.

Note: Browse to the new package folder and open it to view the contents, displaying file extensions in

Folder Options. Note the files created. Previous versions of App-V created an .sprj file, icon files, and one

or more .osd files (and an optional .msi file). App-V 5.0 creates an .appv file, several .xml files, and

an .msi file by default.

34. Copy the XML Notepad 2007 folder to the content share on the App-V Publishing Server.

Note: Microsoft Application Virtualization Sequencer–generated MSI files can be deployed to clients

without a configured Publishing Server. See the Offline Deployment section of this Trial Guide for more

information about configuring clients for offline operation and deploying Sequencer-generated MSI files.

Publish the Application

Next, import the newly sequenced application on the App-V Management Server and publish it to the

client computer.

Perform the following steps on the App-V Management Server:

1. Launch Internet Explorer and browse to http://localhost:888/console.html.

Note: If this website is inaccessible, make sure the current logged-in user is a member of the AppV Administrators group in Active Directory. If not, logout and log back in and add the current user to the

group in order to receive access.

Figure 16: The App-V 5.0 Management Console

2. In the Packages node of the console, click ADD or UPGADE PACKAGES.

3. In the ADD or UPGRADE PACKAGES dialog box, click Browse.

4. In the Choose File to Upload dialog box, browse to XML Notepad 2007 by its UNC path (ie: \\

appvserver\content\XMLNotepad2007), select XML Notepad 2007.appv, click Open, and then click

Add.

5. In the PACKAGE IMPORT dialog box, click Close.

Figure 17: Successfully adding a package to the AppV Management Server

6. Right-click the xml notepad 2007 package and select edit active directory access.

7. In the FIND VALID ACTIVE DIRECTORY GROUPS AND GRANT ACCESS field, type domain\AppV

Users, click Check, click AppV Users [Domain FQDN], click Grant Access and then click Close.

Figure 18: Assigning Permissions to a User Group

8. Right-click the xml notepad 2007 package and then click publish.

Note: The Status field will turn from a black icon to a green icon, and the status should now say

published.

Stream the Application

Perform the following steps on the App-V Client:

To access the newly published application, log off of the Microsoft Application Virtualization Desktop

Client computer and log on as a member of the user group to which the application is assigned. The

application will now be available to clients at the designated shortcut locations.

1. Launch XML Notepad 2007 from the desktop icon.

2. Once the applications successfully launches, close XML Notepad 2007.

Note: If the package had been optimized for the streaming on the first launch there is a status bar above

the notification area.

Sequencing Silverlight® for Internet Explorer

This section details the creation of a virtual environment for Windows Internet Explorer with the Microsoft

Silverlight plug-in. The web plug-in will appear only when an instance of Internet Explorer is launched

from within the virtual environment created for the plug-in application. When Internet Explorer is launched

from an icon not provided by the App-V Client, the plug-in will not be available because the plug-in is

being virtualized rather than installed on the client OS. Because Internet Explorer is part of the operating

system, it cannot be sequenced. It will therefore be necessary to point to the local Internet Explorer

executable file on each Microsoft Application Virtualization Client, and apply the changes within the virtual

environment so that they can interact with the local environment.

Perform the following steps on the App-V Sequencer:

Caution: The virtual machine used for sequencing must be reset, or if using a physical computer, the

clean image must be restored before starting a new sequencing task. This ensures each sequencing task

begins with a clean system containing only the Sequencer installation. This is a critical requirement for

all sequencing work with App-V. The App-V 5.0 Sequencer will check the system and recommend the

machine be reset to a clean state if necessary.

Figure 19: Prepare Computer Screen

Note: Before sequencing Microsoft Silverlight in this test environment, ensure the App-V Client and

App-V Sequencer workstations do not already have Microsoft Silverlight installed. An easy way to test this

is to launch Internet Explorer on each system, and browse to

http://name_of_appv_management_server:888/console.html. The App-V Management console

requires Microsoft Silverlight. If Microsoft Silverlight is installed, uninstall it before continuing in this guide.

Figure 20: Silverlight not installed in Internet Explorer

Sequence Silverlight

1. If not already done, launch Internet Explorer and complete the Set Up Windows Internet Explorer 9 wizard to user preferences then close Internet Explorer.

2. Download the latest Microsoft Silverlight installer and save to the user’s desktop.

3. Create a folder on the Desktop named IE with Silverlight4. Click Start | All Programs | Microsoft Application Virtualization Sequencer | Microsoft Virtual

Application Sequencer.5. Click Create a New Virtual Application Package.

6. On the Packaging Method page, select Create Package (default) and then click Next.7. On the Prepare Computer screen, if the Sequencer recommends stopping any processes on the

machine, be sure to stop those processes now. Once the processes are stopped, return to the

Sequencer and click Refresh.

8. When the Sequencer displays, Your system is ready to create a virtual package, no issues were detected, click Next to continue.

9. On the Type of Application page, select Add-on or Plug-in and then click Next.10. On the Select Installer page, select Select the installer for the application and then click Browse.

11. In the Select installation file dialog box, browse to Silverlight.exe, click Open, and then click Next.12. On the Install Primary page, click I have installed the primary parent program, and then click

Next.13. On the Package Name page, in the Virtual Application Package Name field, type IE with

Silverlight, in the Primary Virtual Application Directory (required) field, type C:\Program Files\Microsoft Silverlight and then click Next.

14. If an Open File – Security Warning box opens, click Run.

15. On the Install Silverlight splash screen, click Install now.

16. On the Enable Microsoft Update splash screen click Next.17. On the Installation successful splash screen click Close.

18. On the Installation page, select I am finished installing and then click Next.19. On the Installation Report page, click Next.20. On the Customize page, select Customize and then click Next.21. On the Prepare for Streaming page, click Next and then click Yes.

22. On the Target OS page, click Next allowing this package to run on any operating system.

23. On the Create Package screen, select Continue to modify package without saving using the package editor and then click Next.

24. On the Completion page, click Close.

25. In the Package Editor click the Shortcuts and FTAs tab.

26. In the Applications node, right-click Microsoft Silverlight, click Remove, and then click OK.

27. In the Applications node, right-click Applications and select Add Application.

28. In the Add Application dialog box, click Browse, browse to C:\Program Files\Internet Explorer\iexplore.exe and then click Open

29. In the Add Application dialog box, in the Name field, type IE with Silverlight. In the Version field

type 1, and then click Add.

30. In the Applications node, expand IE with Silverlight, right-click Shortcuts, and then click Edit Locations.

31. In the Shortcut Locations dialog box, click Desktop and then click OK.

32. Click File | Save As.

33. In the Save As dialog box, browse in to the IE with Silverlight folder (created earlier on the desktop)

then click Save.

34. Close the Sequencer.

35. Copy the IE with Silverlight folder to the content share on the App-V Management Server.

36. Add the new application to the App-V Management Console, following instructions in the section

Publish the Application.

37. Switch to the App-V Client Machine, log off and log back in as a user in the AppV Users group.

38. Test the package by launching the IE with Silverlight application, and browse to

http://name_of_AppV_Management_Server:888/console.html. The console should successfully

open.

Reference

For more information about general App-V sequencing best practices, see the following Microsoft

website:

Best Practices for Sequencing at http://go.microsoft.com/fwlink/?LinkId=269953

Publishing Office 2013 Preview

This section provides instructions for importing and publishing Office 2013 Preview version with App-V

software. Because Office 2013 Preview is provided to customers already in the App-V format, there is no

need to sequence the application. Note that the download links listed below are for a trial release only.

This version of Office 2013 cannot be activated, but functional testing is available during the trial period.

Note: The release version of Office 2013 will not have a downloadable App-V package, but will have the

capability of creating one without sequencing by utilizing the Office Deployment Tool (part of Office 2013

Click-to-Run). This documentation will be updated when the release version of Office 2013 becomes

available with creation steps for the App-V package.

Enable Package Scripts on the App-V Client Computer

To publish Office 2013 properly, package scripts must be enabled on the client. This allows the App-V

package to run scripts to add and publish the Office 2013 App-V package.

Perform the following on the App-V Client Computer.

1. Login to the computer as an account with local administrative privileges.2. Navigate to Start > Programs > Accessories > PowerShell > PowerShell | Right Click > Run

as Administrator3. Click Yes at the UAC prompt.

4. Type the following commands:

a. Import-module AppVClientb. Set-AppVClientConfiguration -EnablePackageScripts 1

5. Logoff the computer.

Download and Publish the App-V package

Since Office 2013 Preview is already provided in an App-V format, the only steps required are to

download the App-V files, import them into the management server, and publish the application.

Perform the following on the App-V Management Server.

1. Login to the computer as an AppV Administrator.2. Create a Directory in C:\Content\ called Office2013.3. Go to the following link to see the Office 2013 Preview App-V source files.

a. http://www.microsoft.com/en-us/download/details.aspx?id=30423

4. Download the following three files to the folder you created above.

a. ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86.appv

b. ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86_DeploymentConfig.xml

c. ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86_UserConfig.xml

5. Launch Internet Explorer and navigate to http://localhost:888/console.html

6. Click ADD or UPGRADE PACKAGES7. Click Browse8. Navigate to \\{management server name}\content\Office2013 and select the

ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86.appv file. Click Open.

9. Click Add.

10. Wait for the Package Import process to complete. Once completed, click Close.

11. Right click the Office 2013 package and click Edit Active Directory Access.

12. In the Search Box, type contoso\AppV Computers, click Check.

13. Click AppV Computers [contoso.com] when it appears, click Grant Access. Click Close.

14. AppV Computers is now listed under AD Access.

15. Right click the Office 2013 Package, click Publish.

16. The status of the package is now listed as Published and the status indicator is green.

17. Wait a minute for the publishing server to refresh before proceeding to the next section.

Launch Office 2013 Preview on the Client

To verify the package is functioning properly, log back into the client and see that the application has

properly published.

Perform the following steps on the App-V Client Computer.

1. Log off the App-V client computer and log on to initiate a global publishing for Office 2013.

Note: The publishing operation may take up to 2 minutes.

2. Navigate to Start > All Programs > Microsoft Application Virtualization Client > Microsoft Application Virtualization Client

3. Click VIRTUAL APPS.

4. Office 2013 is now be listed.

a. If Office 2013 is not listed in the list, logoff and logon the computer again.

5. Close the Microsoft Application Virtualization Client window.

6. Navigate to Start > All Programs > Microsoft Office 2013. 7. Launch any of the Office 2013 Preview applications.

Note: This version of Office 2013 is in a preview version only. This version of Office 2013 cannot be

activated.

Note: The basic tasks for evaluating the main features of the App-V system have now been completed. The next section includes additional optional tasks and information about several other aspects of the App-V system for further evaluation.

Offline Deployment Using the Sequencer-Generated MSI File

The Microsoft Application Virtualization Sequencer has an option to create an .msi file that automates the

addition of the virtual application. The MSI file can be used by an Electronic Software Distribution system

to automatically publish the shortcuts and FTAs and to load the application into cache. It can also be used

directly on the client in standalone mode. This mode is meant for rarely connected users who need the

power of virtualized applications but do not have access to a server, or for deployment of virtualized

applications using a third-party ESD solution other than System Center Configuration Manager (SCCM).

The Group Policy administrative template is available at http://go.microsoft.com/fwlink/?LinkID=269890

for centrally managing settings with Group Policy.

Troubleshooting

This section details how to access the App-V 5.0 event logs.

1. Navigate to Start | Control Panel | Administrator Tools | Event Viewer.

2. Expand Application and Services Logs | Microsoft | AppV

Note: The subfolders displayed within the App-V container will depend on which system (sequencer,

management server, or client) requires troubleshooting. Under those additional subfolders, Admin

and/or Operational log files are displayed. Use the information available for troubleshooting App-V

related problems by searching Microsoft support for any specific knowledge base articles.

Accessing the Microsoft Support Knowledge Base

To access the Microsoft Support knowledge base and search for answers to the most frequently asked

questions, go to Microsoft Support.

Contacting Microsoft Training

To register for training courses, to obtain course descriptions, and to get information about Microsoft

certifications, go to Microsoft Training & Events.

Microsoft Application Virtualization Official Documentation

Additional whitepapers and guides can be found on the App-V TechNet site at:

http://go.microsoft.com/fwlink/?linkid=269780.