mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Continued edits
This commit is contained in:
Heidi Lohr
@ -8,48 +8,27 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
# Deploying App-V Packages by Using Electronic Software Distribution (ESD)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
You can deploy App-V packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
You can deploy App-V packages using an electronic software distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
To deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to Application Management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv)
|
||||
To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv)
|
||||
|
||||
## How to deploy virtualized packages using an ESD
|
||||
|
||||
To learn more about how to deploy virtualized packages using an ESD, see [How to deploy App-V packages using electronic software distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
Describes the methods you can use to deploy App-V packages by using an ESD.
|
||||
## How to enable only administrators to publish packages by using an ESD
|
||||
|
||||
[How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
To learn how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD, see [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
## How to Enable Only Administrators to Publish Packages by Using an ESD
|
||||
## Related topics
|
||||
|
||||
|
||||
Explains how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD.
|
||||
|
||||
[How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
|
||||
- [App-V and Citrix integration](https://www.microsoft.com/en-us/download/details.aspx?id=40885)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Other resources for using an ESD and App-V
|
||||
|
||||
|
||||
Use the following link for more information about [App-V and Citrix Integration](https://www.microsoft.com/en-us/download/details.aspx?id=40885).
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
@ -8,37 +8,34 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
# About App-V dynamic configuration
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
# About App-V Dynamic Configuration
|
||||
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.
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
|
||||
You can use the dynamic configuration to customize an App-V package for a user. Use the following information 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 helps to provide a more convenient method for package customization by removing the need to re-sequence packages using the desired settings, and provides 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 providing a way to keep package content and custom settings independent.
|
||||
|
||||
## 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
|
||||
|
||||
The previous .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 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.
|
||||
|
||||
**Note**
|
||||
The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements.
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements.
|
||||
|
||||
### Dynamic Configuration file contents
|
||||
|
||||
All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following table:
|
||||
|
||||
1. User configuration .xml file.
|
||||
2. Deployment configuration .xml file.
|
||||
3. Package manifest.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="100%" />
|
||||
@ -56,7 +53,6 @@ All of the additions, deletions, and updates in the configuration files need to
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults.
|
||||
|
||||
@ -98,7 +94,7 @@ The structure of the App-V Dynamic Configuration file is explained in the follow
|
||||
|
||||
**Header** - the header of a dynamic user configuration file is as follows:
|
||||
|
||||
```
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<UserConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
|
||||
```
|
||||
@ -109,7 +105,7 @@ The **PackageId** is the same value as exists in the Manifest file.
|
||||
|
||||
**Applications** - All app-extensions that are contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored.
|
||||
|
||||
```
|
||||
```xml
|
||||
<UserConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
|
||||
<Applications>
|
||||
<!-- No new application can be defined in policy. AppV Client will ignore any application ID that is not also in the Manifest file -->
|
||||
@ -122,7 +118,7 @@ The **PackageId** is the same value as exists in the Manifest file.
|
||||
|
||||
**Subsystems** - AppExtensions and other subsystems are arranged as subnodes under the <Subsystems>:
|
||||
|
||||
```
|
||||
```xml
|
||||
<UserConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/userconfiguration">
|
||||
<Subsystems>
|
||||
..
|
||||
@ -143,7 +139,7 @@ Example using the shortcuts subsystem:
|
||||
|
||||
**Example 1**<br>If the user defined this in either the dynamic or deployment config file:
|
||||
|
||||
```
|
||||
```xml
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions
|
||||
...
|
||||
@ -161,7 +157,7 @@ Then the content in the Manifest will be integrated during publishing.
|
||||
|
||||
**Example 3**<br>If the user defines the following
|
||||
|
||||
```
|
||||
```xml
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions/>
|
||||
</Shortcuts>
|
||||
@ -173,7 +169,7 @@ The supported Extension Subsystems are:
|
||||
|
||||
**Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts:
|
||||
|
||||
```
|
||||
```xml
|
||||
<Subsystems>
|
||||
<Shortcuts Enabled="true">
|
||||
<Extensions>
|
||||
@ -211,7 +207,7 @@ The supported Extension Subsystems are:
|
||||
|
||||
**File-Type Associations:** Associates File-types with programs to open by default as well as setup the context menu. (MIME types can also be setup using this susbsystem). Sample File-type Association is below:
|
||||
|
||||
```
|
||||
```xml
|
||||
<FileTypeAssociations Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.FileTypeAssociation">
|
||||
@ -277,7 +273,7 @@ The supported Extension Subsystems are:
|
||||
|
||||
**URL Protocols**: This controls the URL Protocols that are integrated into the local registry of the client machine e.g. “mailto:”.
|
||||
|
||||
```
|
||||
```xml
|
||||
<URLProtocols Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.URLProtocol">
|
||||
@ -324,7 +320,7 @@ The supported Extension Subsystems are:
|
||||
|
||||
**Software Clients**: Allows the app to register as an Email client, news reader, media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases you should only need to enable and disable it. There is also a control to enable and disable the email client specifically if you want the other clients still enabled except for that client.
|
||||
|
||||
```
|
||||
```xml
|
||||
<SoftwareClients Enabled="true">
|
||||
<ClientConfiguration EmailEnabled="false" />
|
||||
</SoftwareClients>
|
||||
@ -332,7 +328,7 @@ The supported Extension Subsystems are:
|
||||
|
||||
**AppPaths**: If an application for example contoso.exe is registered with an apppath name of “myapp”, it allows you type “myapp” under the run menu and it will open contoso.exe.
|
||||
|
||||
```
|
||||
```xml
|
||||
<AppPaths Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.AppPath">
|
||||
@ -363,7 +359,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited:
|
||||
|
||||
**Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU
|
||||
|
||||
```
|
||||
```xml
|
||||
<Registry Enabled="true">
|
||||
<Include>
|
||||
<Key Path="\\REGISTRY\\USER\\\[{AppVCurrentUserSID}\]\\Software\\ABC">
|
||||
@ -385,7 +381,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited:
|
||||
|
||||
**Virtual Environment Variables**
|
||||
|
||||
```
|
||||
```xml
|
||||
<EnvironmentVariables Enabled="true">
|
||||
<Include>
|
||||
<Variable Name="UserPath" Value="%path%;%UserProfile%" />
|
||||
@ -407,7 +403,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited:
|
||||
|
||||
**Header** - The header of a Deployment Configuration file is as follows:
|
||||
|
||||
```
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?><DeploymentConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration">
|
||||
```
|
||||
|
||||
@ -419,7 +415,7 @@ The **PackageId** is the same value as exists in the manifest file.
|
||||
|
||||
- Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS.
|
||||
|
||||
```
|
||||
```xml
|
||||
<DeploymentConfiguration PackageId="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration">
|
||||
<UserConfiguration>
|
||||
..
|
||||
@ -438,7 +434,7 @@ Machine Configuration - the Machine configuration section of the Deployment Conf
|
||||
|
||||
1. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under <Subsystems>:
|
||||
|
||||
```
|
||||
```xml
|
||||
<MachineConfiguration>
|
||||
<Subsystems>
|
||||
..
|
||||
@ -455,7 +451,7 @@ Some subsystems (Extension Subsystems) control Extensions which can only apply t
|
||||
|
||||
**Application Capabilities**: Used by default programs in windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI.:
|
||||
|
||||
```
|
||||
```xml
|
||||
<ApplicationCapabilities Enabled="true">
|
||||
<Extensions>
|
||||
<Extension Category="AppV.ApplicationCapabilities">
|
||||
@ -497,7 +493,7 @@ In addition to Extensions, other subsystems can be edited:
|
||||
|
||||
**Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine
|
||||
|
||||
```
|
||||
```xml
|
||||
<Registry>
|
||||
<Include>
|
||||
<Key Path="\\REGISTRY\\Machine\\Software\\ABC">
|
||||
@ -511,7 +507,7 @@ In addition to Extensions, other subsystems can be edited:
|
||||
|
||||
**Machine Wide Virtual Kernel Objects**
|
||||
|
||||
```
|
||||
```xml
|
||||
<Objects>
|
||||
<NotIsolate>
|
||||
<Object Name="testObject" />
|
||||
@ -521,7 +517,7 @@ In addition to Extensions, other subsystems can be edited:
|
||||
|
||||
**ProductSourceURLOptOut**: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch.
|
||||
|
||||
```
|
||||
```xml
|
||||
<MachineConfiguration>
|
||||
..
|
||||
<ProductSourceURLOptOut Enabled="true" />
|
||||
@ -533,7 +529,7 @@ In addition to Extensions, other subsystems can be edited:
|
||||
|
||||
**TerminateChildProcess**:- An application executable can be specified, whose child processes will be terminated when the application exe process is terminated.
|
||||
|
||||
```
|
||||
```xml
|
||||
<MachineConfiguration>
|
||||
..
|
||||
<TerminateChildProcesses>
|
||||
@ -549,6 +545,17 @@ 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)|
|
||||
|---|---|---|---|---|---|
|
||||
|||||||
|
||||
|||||||
|
||||
|||||||
|
||||
|||||||
|
||||
|||||||
|
||||
|||||||
|
||||
|||||||
|
||||
|||||||
|
||||
|
||||
<table style="width:100%;">
|
||||
<colgroup>
|
||||
<col width="16%" />
|
||||
@ -655,7 +662,7 @@ We recommended that you run the multi-script line from a command prompt first to
|
||||
|
||||
Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<MachineScripts>
|
||||
<AddPackage>
|
||||
<Path>ScriptRunner.exe</Path>
|
||||
@ -735,12 +742,10 @@ To create the file manually, the information above in previous sections can be c
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
|
||||
## Related topics
|
||||
|
||||
[How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
|
||||
[How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
- [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
Reference in New Issue
Block a user