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

more formatting for scanability

Browse Source
This commit is contained in:
Patti Short 2018-08-28 16:29:05 -07:00
parent 4a97606486
commit ae7258231e
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
mdop/appv-v5/about-app-v-51-dynamic-configuration.md
View File

@ -15,7 +15,6 @@ ms.author: pashort
With dynamic configuration, you can edit the dynamic configuration file to customize how an App-V 5.1 package runs for a user or group. Package customization removes the need to resequence packages using the desired settings. It also provides a way to keep package content and custom settings independent. With dynamic configuration, you can edit the dynamic configuration file to customize how an App-V 5.1 package runs for a user or group. Package customization removes the need to resequence packages using the desired settings. It also provides a way to keep package content and custom settings independent.
## Package manifest and configuration files
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). 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).
@ -26,7 +25,7 @@ When a package gets created, the sequencer generates default deployment and user
Use these generated files to make changes, if necessary, which doesn’t directly affect the package. If you want to add, delete or update the configuration files, make your changes about the default values in the manifest information. Use these generated files to make changes, if necessary, which doesn’t directly affect the package. If you want to add, delete or update the configuration files, make your changes about the default values in the manifest information.
### User configuration file contents (UserConfig.xml) ## User configuration file contents (UserConfig.xml)
The UserConfig file provides configuration settings that get applied for a specific user when deploying the package to a computer running the App-V 5.1 client. These settings don’t affect any other users on the client. The UserConfig file provides configuration settings that get applied for a specific user when deploying the package to a computer running the App-V 5.1 client. These settings don’t affect any other users on the client.
@ -37,7 +36,7 @@ Use the UserConfig file to specify or modify custom settings for a package:
- **Scripts** (user context only) - **Scripts** (user context only)
- **Managing authority** (for controlling co-existence of package with App-V 4.6) - **Managing authority** (for controlling co-existence of package with App-V 4.6)
#### Header ### Header
The header of a dynamic user configuration file looks like: The header of a dynamic user configuration file looks like:
@ -48,7 +47,7 @@ xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
The **PackageId** is the same value as exists in the Manifest file. The **PackageId** is the same value as exists in the Manifest file.
#### Body ### Body
The body of the dynamic user configuration file can include all the app extension points defined in the manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body: The body of the dynamic user configuration file can include all the app extension points defined in the manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body:
@ -57,7 +56,7 @@ The body of the dynamic user configuration file can include all the app extensio
3. **UserScripts** 3. **UserScripts**
4. **ManagingAuthority** 4. **ManagingAuthority**
##### Applications #### Applications
All app-extensions contained in the manifest file within a package have an Application ID assigned, which you find in the manifest file. The Application ID lets you enable or disable all extensions for a given application within a package. The Application ID must exist in the manifest file, or it gets ignored. All app-extensions contained in the manifest file within a package have an Application ID assigned, which you find in the manifest file. The Application ID lets you enable or disable all extensions for a given application within a package. The Application ID must exist in the manifest file, or it gets ignored.
@ -80,7 +79,7 @@ All app-extensions contained in the manifest file within a package have an Appli
``` ```
##### Subsystems #### Subsystems
AppExtensions and other subsystems arranged as subnodes. AppExtensions and other subsystems arranged as subnodes.
@ -578,13 +577,13 @@ _**Supported extension subsystems:**_
``` ```
##### UserScripts #### UserScripts
Use scripts to set up or alter the virtual environment. You can also execute scripts at the time of deployment or to clean up the environment after the application terminates. To see a sample script, refer to the user configuration file generated by the sequencer. Use scripts to set up or alter the virtual environment. You can also execute scripts at the time of deployment or to clean up the environment after the application terminates. To see a sample script, refer to the user configuration file generated by the sequencer.
The Scripts section below provides more information on the various triggers that can be used. The Scripts section below provides more information on the various triggers that can be used.
##### ManagingAuthority #### ManagingAuthority
Use ManagingAuthority when two versions of your package co-exist on the same machine, one deployed to App-V 4.6 and another deployed on App-V 5.0. To allow App-V vNext to take over App-V 4.6 extension points for the named package enter the following in the UserConfig file (where PackageName is the Package GUID in App-V 4.6: Use ManagingAuthority when two versions of your package co-exist on the same machine, one deployed to App-V 4.6 and another deployed on App-V 5.0. To allow App-V vNext to take over App-V 4.6 extension points for the named package enter the following in the UserConfig file (where PackageName is the Package GUID in App-V 4.6:
@ -595,7 +594,8 @@ Use ManagingAuthority when two versions of your package co-exist on the same mac
``` ```
### Dynamic Deployment Configuration file ## Deployment configuration file contents (DeploymentConfig.xml)
**Header** - The header of a Deployment Configuration file is as follows: **Header** - The header of a Deployment Configuration file is as follows: