deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-28 05:07:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Adding content

Browse Source
This commit is contained in:
LizRoss 2017-02-02 09:09:14 -08:00
parent ba5b374b90
commit 13dbedf182
2 changed files with 21 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
windows/manage/appv-auto-batch-sequencing.md
View File

@ -8,7 +8,6 @@ ms.sitesec: library
ms.prod: w10
---
# Automatically sequence multiple apps at the same time using the Microsoft Application Virtualization Sequencer (App-V Sequencer)
**Applies to**
@ -38,13 +37,13 @@ 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. [Liz] What are the options here?
- **&lt;InstallerOptions&gt;.** 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. <!-- [Liz] What are the options here? -->
- **&lt;TimeoutInMinutes&gt;.** 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. [Liz] Is this optional?
- **&lt;TimeoutInMinutes&gt;.** 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. <!-- [Liz] Is this optional? -->
- **&lt;Cmdlet&gt;.** 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 UI. You can use both the cmdlet and the UI together in the same ConfigFile, for different apps.
- **&lt;Cmdlet&gt;.** 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.
- **&lt;Enabled&gt;.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. [Liz] Guessing. This wasn't called out in the text.
- **&lt;Enabled&gt;.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. <!-- [Liz] Guessing. This wasn't called out in the text. -->
**Example:**
@ -75,9 +74,15 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFile
3. Save your completed file, using the name **ConfigFile**.
**To start the App-V Sequencer interface and app installation process**
[Liz] Text here
- Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing:
```ps1
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
```
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.
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.
### 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.
@ -92,11 +97,11 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle
- **&lt;Installer&gt;.** The file name for the app executable. This will typically be an .exe or .msi file.
- **&lt;TimeoutInMinutes&gt;.** 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. [Liz] Is this optional?
- **&lt;TimeoutInMinutes&gt;.** 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. <!-- [Liz] Is this optional? -->
- **&lt;Cmdlet&gt;.** 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 UI. You can use both the cmdlet and the UI together in the same ConfigFile, for different apps.
- **&lt;Cmdlet&gt;.** 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.
- **&lt;Enabled&gt;.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer UI. [Liz] Guessing. This wasn't called out in the text.
- **&lt;Enabled&gt;.** Allows the app to be sequenced by either the cmdlet or the App-V Sequencer interface. <!-- [Liz] Guessing. This wasn't called out in the text. -->
**Example:**
@ -130,17 +135,16 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle
```
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.
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 then running through all of the steps again, until the final package is copied to your output folder. This continues until all of the apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off. [Liz] Didn't they put the output location into the command in step 1? Why do they need to put it there AND in the prompt?
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. <!-- [Liz] Didn't they put the output location into the command in step 1? Why do they need to put it there AND in the prompt? -->
### Review the log files
There are 3 types of log files that occur when you sequence multiple apps at the same time:
- **“%temp%\AutoSequencer\Logs” – ‘New-BatchAppVSequencerPackages-<time stamp>.txt** [Liz] Text here
- **New-BatchAppVSequencerPackages-<time stamp>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the sequencing activities, such as "Copying installer to VM", "Scheduling sequencing task", and so on for each app. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
- **“OutputPath” folder – ‘New-BatchAppVSequencerPackages-report-<time stamp>.txt** [Liz] Text here
- **Output Package” folder** [Liz] Text here
- **New-BatchAppVSequencerPackages-report-<time stamp>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters.
### Related topics
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)

6
windows/manage/appv-auto-sequence-a-new-app.md
View File

@ -115,11 +115,11 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco
A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start.
### Review the provisioning log files
The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are:
The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are:
- **New-AppVSequencerVM-<time_stamp>.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on.
- **New-AppVSequencerVM-<time_stamp>.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on.
- **New-AppVSequencerVM-report-<time_stamp>.txt**: Includes info about the connections made to the VM, showing whether there were any failures.
- **New-AppVSequencerVM-report-<time_stamp>.txt**. Includes info about the connections made to the VM, showing whether there were any failures.
### Related topics