diff --git a/windows/manage/appv-auto-batch-sequencing.md b/windows/manage/appv-auto-batch-sequencing.md index 98d6dc29ce..9210cdf5ec 100644 --- a/windows/manage/appv-auto-batch-sequencing.md +++ b/windows/manage/appv-auto-batch-sequencing.md @@ -13,7 +13,7 @@ ms.prod: w10 **Applies to** - Windows 10, version 1703 -Sequencing apps requires you to install and start the Microsoft Application Virtualization Sequencer (App-V Sequencer), install the necessary apps, and to collect any changes made to the operating system during the installation and building of the App-V package. +Sequencing apps requires you to install and start the Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package. There are 2 approaches to sequencing multiple apps at the same time: @@ -24,7 +24,7 @@ There are 2 approaches to sequencing multiple apps at the same time: - Using the user-interface provided by the App-V Sequencer ### Sequence multiple apps by using a PowerShell cmdlet -Sequencing multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of sequencing. This file is then used by the sequencing 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. +Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. **To create your ConfigFile for use by the PowerShell cmdlet** 1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad. @@ -39,11 +39,11 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - **<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. + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, 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. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based sequencing, 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>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -51,18 +51,18 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile - Notepad - C:\Windows - notepad.exe + Skype + Need to get + Need to get /S 20 True True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe + Power BI + Need to get + Need to get /S 20 True @@ -80,9 +80,9 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced 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 sequencing of the app begins from the command-line. After completing all of the app sequencing and package creation 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. + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation 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. ### Sequence multiple apps by using the App-V Sequencer interface Sequencing multipe apps at the same time requires that you create a **ConfigFIle** to collect all of the info related to each round of sequencing. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM. @@ -98,11 +98,11 @@ 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. - - **<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. + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, 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. - **<Cmdlet>.** Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based sequencing, 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>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -110,17 +110,17 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle - Notepad - C:\Windows - notepad.exe + Skype + Need to get + Need to get 20 False True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe + Power BI + Need to get + Need to get 20 False True @@ -136,9 +136,9 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - Where _VMName_ is the name of the virtual machine (VM) where you'll run the batch sequencing and _OutputPath_ is the full file path to where the sequenced packages should be copied. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced 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 and the App-V Sequencer is started so you can start the sequencing process. After completing all of the app sequencing 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. + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation 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. ### Review the log files There are 3 types of log files that occur when you sequence multiple apps at the same time: diff --git a/windows/manage/appv-auto-batch-updating.md b/windows/manage/appv-auto-batch-updating.md index eb414c9535..82eb64a999 100644 --- a/windows/manage/appv-auto-batch-updating.md +++ b/windows/manage/appv-auto-batch-updating.md @@ -24,7 +24,7 @@ There are 2 approaches to updating multiple apps at the same time: - Using the user-interface provided by 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. +Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations. **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. @@ -41,40 +41,40 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - **<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. + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, 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>.** AIndicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** - ```XML - Notepad_Update - C:\Windows - notepad.exe - /S - C:\App-V_Packages\Microsoft_Apps\notepad.appv + Skype_Update + Need to get + Need to get + /S + C:\App-V_Packages\Microsoft_Apps\skype_update.appv 20 True True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe + Power BI + Need to get + Need to get /S - C:\App-V_Packages\Microsoft_Apps\winword.appv + C:\App-V_Packages\Microsoft_Apps\power_bi_update.appv 20 True True - ``` + ``` + 3. Save your completed file, using the name **ConfigFile**. @@ -84,9 +84,9 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - 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. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full 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. + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing updating and package creation 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. @@ -104,11 +104,11 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - **<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. + - **<TimeoutInMinutes>.** The maximum amount of time, in minutes, 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 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>.** Indicates whether the app is included in the batch process. You can include as many apps as you want in the batch file, but optionally enable only a few of them. + - **<Enabled>.** Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them. **Example:** @@ -116,21 +116,21 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** - Notepad_Update - C:\Windows - notepad.exe - C:\App-V_Packages\Microsoft_Apps\notepad.appv + Skype_Update + Need to get + Need to get + C:\App-V_Packages\Microsoft_Apps\skype_update.appv 20 - True + False True - Word 2016 - C:\Program Files (x86)\Microsoft Office\root\Office16 - winword.exe - C:\App-V_Packages\Microsoft_Apps\winword.appv + Power BI + Need to get + Need to get + C:\App-V_Packages\Microsoft_Apps\power_bi_update.appv 20 - True + False True @@ -143,11 +143,11 @@ Updating multipe apps at the same time requires that you create a **ConfigFile** ```ps1 New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath ``` - 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. + Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full 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 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. + The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing updating and package creation 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. -### Review the log files +### Review the log files There are 3 types of log files that occur when you sequence multiple apps at the same time: - **New-BatchAppVSequencerPackages-