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

Continued fixing up dynamic configuration article

Browse Source
This commit is contained in:
Heidi Lohr
2018-08-27 16:54:40 -07:00
parent 531c2664fc
commit b3726b9ba3
1 changed files with 20 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -456,9 +456,11 @@ The following section displays the various subsystems and usage samples.
### Extensions
Some subsystems (Extension Subsystems) control Extensions which can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section.
Some subsystems (Extension Subsystems) control extensions that can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section.
**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.:
#### Application Capabilities
Used by default programs in the Windows OS interface, the Application Capabilities extension allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, and 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">
@ -496,11 +498,11 @@ Some subsystems (Extension Subsystems) control Extensions which can only apply t
</ApplicationCapabilities>
```
**Other Settings**:
#### Other Settings
In addition to Extensions, other subsystems can be edited:
You can edit other subsystems in addition to Extensions:
**Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine
* Machine-wide Virtual Registry: use this when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine.
```xml
<Registry>
@ -514,7 +516,7 @@ In addition to Extensions, other subsystems can be edited:
</Registry>
```
**Machine Wide Virtual Kernel Objects**
* Machine-wide Virtual Kernel Objects
```xml
<Objects>
@ -524,7 +526,7 @@ In addition to Extensions, other subsystems can be edited:
</Objects>
```
**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.
* 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>
@ -534,9 +536,9 @@ In addition to Extensions, other subsystems can be edited:
</MachineConfiguration>
```
**MachineScripts** – Package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used
* MachineScripts: The package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used
**TerminateChildProcess**:- An application executable can be specified, whose child processes will be terminated when the application exe process is terminated.
* TerminateChildProcess: an application executable can be specified whose child processes will be terminated when the application exe process is terminated.
```xml
<MachineConfiguration>
@ -681,6 +683,15 @@ Using the following example file and table, modify the deployment or user config
</MachineScripts>
```
|Parameter in the example file|Description|
|---|---|
|||
|||
|||
|||
<table>
<colgroup>
<col width="50%" />