deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Continued making edits

Browse Source
This commit is contained in:
Heidi Lohr
2018-07-12 14:13:41 -07:00
parent e32cd5eb30
commit 3a4766aa21
1 changed files with 17 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
windows/application-management/app-v/appv-dynamic-configuration.md
View File

@ -14,16 +14,16 @@ ms.date: 04/19/2017
You can use dynamic configuration to customize an App-V package for a user. This article will tell you how to create or edit an existing dynamic configuration file.
When you edit the dynamic configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and providing a way to keep package content and custom settings independent.
When you edit the dynamic configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and provides a way to keep package content and custom settings independent.
## Advanced: Dynamic Configuration
## Advanced: dynamic configuration
Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no additional customization). If you want to adjust these defaults for a particular user or group, you can create and edit the following files:
- User Configuration file
- Deployment configuration file
- Deployment Configuration file
These .xml files specify package settings and allow for packages to be customized without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed.
These .xml files specify package settings let you customize packages without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed.
>[!NOTE]
>The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements.
@ -546,15 +546,15 @@ In addition to Extensions, other subsystems can be edited:
The following table describes the various script events and the context under which they can be run.
|Script Execution Time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the Virtual Environment of the package|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)|
|---|---|---|---|---|---|
|||||||
|||||||
|||||||
|||||||
|||||||
|||||||
|||||||
|||||||
|---|:---:|:---:|:---:|:---:|:---:|
|AddPackage|X||||(SYSTEM, N/A)|
|PublishPackage|X|X|||(SYSTEM, User)|
|UnpublishPackage|X|X|||(SYSTEM, User)|
|RemovePackage|X||||(SYSTEM, N/A)|
|StartProcess|X|X|X|X|(User, User)|
|ExitProcess|X|X||X|(User, User)|
|StartVirtualEnvironment|X|X|X||(User, User)|
|TerminateVirtualEnvironment|X|X|||(User, User)|
<table style="width:100%;">
<colgroup>
@ -643,22 +643,18 @@ The following table describes the various script events and the context under wh
</tbody>
</table>
 
### Using multiple scripts on a single event trigger
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client.
**How to use multiple scripts on a single event trigger:**
#### How to use multiple scripts on a single event trigger
For each script that you want to run, pass that script as an argument to the ScriptRunner.exe application. The application then runs each script separately, along with the arguments that you specify for each script. Use only one script (ScriptRunner.exe) per trigger.
**Note**  
We recommended that you run the multi-script line from a command prompt first to make sure that all arguments are built correctly before adding them to the deployment configuration file.
>[!NOTE]
>We recommended that you run the multi-script line from a command prompt first to make sure that all arguments are built correctly before adding them to the deployment configuration file.
 
**Example script and parameter descriptions**
#### Example script and parameter descriptions
Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run.