diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 2a62e2f44f..fc5aedce2e 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -37,7 +37,7 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. - - **<InstallerOptions>.** The command-line options required for the app installation. This only applies to cmdlet sequencing, it doesn't apply if you use the App-V Sequencer interface. + - **<InstallerOptions>.** The command-line options required for the app installation. - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself. diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index 10fa90119e..597648b8cd 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -1,6 +1,6 @@ --- -title: Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) -description: How to automatically sequence a new app using the App-V Sequencer +title: Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10) +description: How to automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer). author: eross-msft ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,131 +8,159 @@ ms.sitesec: library ms.prod: w10 --- - -# Automatically sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) +# Automatically update multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer) **Applies to** - Windows 10, version 1703 -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. +Updating multiple apps at the same time follows the same process as [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However for updating, we pass the previously created app package files to the App-V Sequencer cmdlet for updating. -Using the automatic sequencer to package your apps provides: +There are 2 approaches to updating multiple apps at the same time: -- Automatic virtual machine (VM) provisioning of the sequencing environment. The process for this is covered in this topic. - -- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see ... - -- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, see ... - -## Automatic VM provisioning of the sequencing environment -You have 2 options for provisioning an VM for auto-sequencing: -- Using a Virtual Hard Disk (VHD) +- Using a cmdlet in PowerShell -OR- -- Updating an existing VM +- Using the user-interface provided by 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. +### Update multiple apps by using a PowerShell cmdlet +Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM by using the `copy-item` command, and then starting the App-V Sequencer and your specified app installations. -#### 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 create your ConfigFile for use by the PowerShell cmdlet** +1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad. -**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: +2. Add the following XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. + + - **<InstallerFolder>.** The file path to the folder with the app installer. + + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. + + - **<InstallerOptions>.** The command-line options required for the app installation. + + - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. + + - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. + + - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. + + - **<Enabled>.** Allows the app to be updated by either the cmdlet or the App-V Sequencer interface. + + **Example:** + + ```XML + + + + Notepad_Update + C:\Windows + notepad.exe + /S + C:\App-V_Packages\Microsoft_Apps\notepad.appv + 20 + True + True + + + Word 2016 + C:\Program Files (x86)\Microsoft Office\root\Office16 + winword.exe + /S + C:\App-V_Packages\Microsoft_Apps\winword.appv + 20 + True + True + + + + ``` +3. Save your completed file, using the name **ConfigFile**. + +**To start the App-V Sequencer interface and app installation process** +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating: ```ps1 - Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR" + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. + Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch updating and _OutputPath_ is the full file path to where the updated packages should be copied. + + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing all of the updating for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. + +### Update multiple apps by using the App-V Sequencer interface +Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. + +**To create your ConfigFile for use by the App-V Sequencer interface** +1. Determine the apps that need to be updated and then open a text editor, such as Notepad. + +2. Add the following XML info for each app: + + - **<Name>.** The name of the app you're adding to the package. - >[!IMPORTANT] - >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image. + - **<InstallerFolder>.** The file path to the folder with the app installer. -#### Provision your VM using your VHD file -After you have a VHD file, you must provision your VM for auto-sequencing. + - **<Installer>.** The file name for the app executable. This will typically be an .exe or .msi file. -**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. + - **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps. - >[!NOTE] - >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). + - **<TimeoutInMinutes>.** The maximum time interval that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself. -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). + - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps. + + - **<Enabled>.** Allows the app to be updated by either the cmdlet or the App-V Sequencer interface. -3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters: + **Example:** + + ```XML + + + + Notepad_Update + C:\Windows + notepad.exe + C:\App-V_Packages\Microsoft_Apps\notepad.appv + 20 + True + True + + + Word 2016 + C:\Program Files (x86)\Microsoft Office\root\Office16 + winword.exe + C:\App-V_Packages\Microsoft_Apps\winword.appv + 20 + True + True + + + + ``` +**To start the App-V Sequencer interface and app installation process** +- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating: ```ps1 - New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory -VMSwitch "" + New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - - 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. + Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch updating and _OutputPath_ is the full file path to where the updated packages should be copied. -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. + The cmdlet creates a "clean" checkpoint on the VM, the first app installer listed in the ConfigFile is copied from the Host computer to the VM, and then a new session of the VM opens and the App-V Sequencer is started so you can start the updating process. After completing all of the app updating and package creation for the first app on the VM, you'll be prompted in the PowerShell window to provide the full file path to the output folder on the Host computer, where the final package is copied. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. +### Review the log files +There are 3 types of log files that occur when you sequence multiple apps at the same time: -### Provision an existing VM for auto-sequencing -If your apps require custom prerequesites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM, install the Microsoft Application Virtualization (App-V) Auto Sequencer from the ADK tools, and provision your VM for auto-sequencing. +- **New-BatchAppVSequencerPackages-