deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-19 20:33:42 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
Files
b4e018ae78c102c22a65544855b57e7978343a65
windows-itpro-docs/windows/manage/appv-automatic-sequence-a-new-app.md
LizRoss b4e018ae78 Adding text
2017-02-01 09:07:09 -08:00

4.5 KiB
Raw Blame History

title, description, author, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod
title description author ms.pagetype ms.mktglfcycl ms.sitesec ms.prod
Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) How to automatically sequence a new app using the App-V Sequencer eross-msft mdop, appcompat, virtualization deploy library w10

Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)

Applies to

  • Windows 10, version 1703

[NOTE] In Windows 10, version 1703, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see Install the App-V Sequencer.

Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup.

Using the automatic sequence to package your apps provides:

  • Automatic virtual machine (VM) provisioning of the sequencing environment.

  • Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group.

  • Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group.

You have 2 options for provisioning an VM for auto-sequencing:

  • Using a Virtual Hard Disk (VHD)

    -OR-

  • Updating an existing VM

Provision a new VM by using a VHD file

Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer.

Create a VHD file

For this process to work, you must have a base operating system available as a VHD image file, we recommend using the Convert-WindowsImage.ps1 command-line tool.

To create a VHD file by using the Convert-WindowsImage command-line tool

  1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands:

    Convert-WindowsImage -SourcePath "<path_to_iso_image>" -VHDFormat "VHD" -VHDPartitionStyle "MBR"

    Where SourcePath is the full file path to your ISO image, VHDFormat is VHD, and VHDPartitionStyle is MBR.

    Important

    You must specify the VHDPartitionStyle as MBR. Using the default value, GPT, will cause a boot failure in your VHD image.

Provision your VM using your VHD file

After you have a VHD file, you must provision your VM for auto-sequencing.

To provision your VM using your VHD file

  1. On the Host device, install Windows 10, version 1703 and the matching ADK version, making sure that you've selected to install the Microsoft Application Virtualization (App-V) Auto Sequencer component.

  2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see Hyper-V on Windows Server 2016.

  3. Open PowerShell as an admin and run the New-AppVSequencerVM cmdlet, using the following parameters:

    New-AppVSequencerVM -VMName "<name_of_new_vm>" -ADKPath "<path_to_adk_install_folder>" -VHDPath "<path_to_vhd_file>" -VMMemory <vm_memory_size> -VMSwitch "<name_of_network_switch>"

    Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch.

A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start.

Provision an existing VM for auto-sequencing

Have a suggestion for App-V?

Add or vote on suggestions on the Application Virtualization feedback site.
For App-V issues, use the App-V TechNet Forum.

Related topics