diff --git a/windows/manage/appv-automatic-sequence-a-new-app.md b/windows/manage/appv-automatic-sequence-a-new-app.md index e609d0dfb1..87f0b66e6e 100644 --- a/windows/manage/appv-automatic-sequence-a-new-app.md +++ b/windows/manage/appv-automatic-sequence-a-new-app.md @@ -17,7 +17,7 @@ ms.prod: w10 >[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](appv-install-the-sequencer.md). -With the previous versions of the App-V Sequencer, you've had 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 has introduced an updated App-V Sequencer that can automatically sequence your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup. +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: @@ -27,31 +27,45 @@ Using the automatic sequence to package your apps provides: - Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. -## Provision your VM You have 2 options for provisioning an VM for auto-sequencing: -- Provision a new VM by using a Virtual Hard Disk (VHD) +- Using a Virtual Hard Disk (VHD) -OR- -- Provision an existing VM +- Updating an existing VM -### Provision a new VM for auto-sequencing by using a VHD file -Provisioning your new VM includes setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer. +## 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. ->[!IMPORTANT] ->For this process to work, you must have a base operating system available as a VHD image file. If you need a tool to create your VHD file, you can use the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. This tool is now a Function, so it must first be loaded and then called by its name, without the extension. Code examples and more info about the tool are included on the download site.

Additionally, when you run this tool to create your file, you must explicitly specify the parameter 'VHDPartitionStyle' as 'MBR'. The default partition value, 'GPT' will cause a boot failure in your VHD file. +### 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](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool. -**To provision your VM using a VHD file** +**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: + + ```ps1 + Convert-WindowsImage -SourcePath "" -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](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server) +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](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server). -3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the required parameters: +3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + ```ps1 + New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" ``` - New-AppVSequencerVM -VMName -ADKPath -VHDPath [-VMSwitch ] [-VMMemory ] [-CPUCount ] [-SessionSetupTimeout ] [UseADKWebInstaller] - ``` - Where the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters. + + 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. diff --git a/windows/manage/change-history-for-manage-and-update-windows-10.md b/windows/manage/change-history-for-manage-and-update-windows-10.md index a794ec798f..01ba55717c 100644 --- a/windows/manage/change-history-for-manage-and-update-windows-10.md +++ b/windows/manage/change-history-for-manage-and-update-windows-10.md @@ -14,6 +14,12 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in >If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history). +## February 2017 +| New or changed topic | Description | +| --- | --- | +|[Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-automatic-sequence-a-new-app.md) |New | + + ## January 2017 | New or changed topic | Description |