diff --git a/mdop/appv-v5/about-app-v-51-dynamic-configuration.md b/mdop/appv-v5/about-app-v-51-dynamic-configuration.md index 66b00d229d..49fedbdd62 100644 --- a/mdop/appv-v5/about-app-v-51-dynamic-configuration.md +++ b/mdop/appv-v5/about-app-v-51-dynamic-configuration.md @@ -198,7 +198,7 @@ allowed in the body: 1. If the user defined this in either the dynamic or deployment config file: - - \`\`\` + - ``` **\** @@ -210,23 +210,23 @@ allowed in the body: **\** - \`\`\` + ``` Content in the manifest will be ignored.    1. If the user defined only the following: - - \`\`\` + - ``` **\** - \`\`\` + ``` Then the content in the Manifest gets integrated during publishing. 1. If the user defines the following: - - \`\`\` + - ``` **\** @@ -234,7 +234,7 @@ allowed in the body: **\** - **\`\`\`** + **```** Then all the shortcuts within the manifest will still be ignored. There will be no shortcuts integrated. @@ -244,7 +244,7 @@ allowed in the body: **Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts: - **\`\`\`** + **```** \ @@ -318,13 +318,13 @@ allowed in the body: \ - \`\`\` + ``` **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: - **\`\`\`** + **```** \ @@ -388,171 +388,171 @@ allowed in the body:         \[{Windows}]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\contosowordpadicon.exe,15\ -         \Blah Blah Blah\ +         Blah Blah Blah -         \[{FOLDERID_ProgramFilesX86}]\\Microsoft Contoso - 14\\res.dll,9182\ +         [{FOLDERID_ProgramFilesX86}]\Microsoft Contoso + 14\res.dll,9182 -         \[{FOLDERID_ProgramFilesX86}]\\Microsoft Contoso - 14\\res.dll,1424\ +         [{FOLDERID_ProgramFilesX86}]\Microsoft Contoso + 14\res.dll,1424 -         \0\ +         0 -         \ +          -           \Open\ +           Open -           \ +              -            \{e56fa627-c35f-4a01-9e79-7d36aed8225a}\ +            {e56fa627-c35f-4a01-9e79-7d36aed8225a} -              \Edit\ +              Edit -              \&Edit\ +              &Edit   -            \"[{PackageRoot}]\\Contoso\\WINcontosowordpad.EXE" - /vu "%1"\ +            "[{PackageRoot}]\Contoso\WINcontosowordpad.EXE" + /vu "%1" -           \ +            -           \ +              -           \{e56fa627-c35f-4a01-9e79-7d36aed8225a}\ +           {e56fa627-c35f-4a01-9e79-7d36aed8225a} -             \Open\ +             Open -             \&Open\ +             &Open -             \"[{PackageRoot}]\\Contoso\\WINcontosowordpad.EXE" - /n "%1"\ +             "[{PackageRoot}]\Contoso\WINcontosowordpad.EXE" + /n "%1" -             \ +              -             \ +              -               \mscontosowordpad\ +               mscontosowordpad -               \ShellSystem\ +               ShellSystem -               \[SHELLNOOP]\ +               [SHELLNOOP] -               \[SetForeground][ShellNewDatabase - "%1"]\ +               [SetForeground][ShellNewDatabase + "%1"] -             \ +              -           \ +            -         \ +          -       \ +        -      \ +       -    \ +     -   \ +   -   \ +   - \`\`\` + ``` **URL Protocols**: This controls the URL Protocols that are integrated into the local registry of the client machine e.g. “mailto:” - **\`\`\`** + ``` - \ + - \ + - \ + - \ + -   \mailto\ +   mailto -   \ +    -   \[{ProgramFilesX86}]\\Microsoft - Contoso\\Contoso\\contosomail.EXE,-9403\ +   [{ProgramFilesX86}]\Microsoft + Contoso\Contoso\contosomail.EXE,-9403 -   \2\ +   2 -   \ +   -   \ +   -   \ +   -   \ +   - \ + -   \ +   -   \ +   -   \2\ +   2 -   \ +   -   \ +    -   \open\ +   open -   \ +    -   \[{ProgramFilesX86}]\\Microsoft - Contoso\\Contoso\\contosomail.EXE\ +   [{ProgramFilesX86}]\Microsoft + Contoso\Contoso\contosomail.EXE -   \open\ +   open -   \[{ProgramFilesX86}\\Microsoft - Contoso\\Contoso\\contosomail.EXE" -c OEP.Note /m "%1"\ +   [{ProgramFilesX86}\Microsoft + Contoso\Contoso\contosomail.EXE" -c OEP.Note /m "%1" -   \ +   -   \ +   -   \0\ +   0 -   \0\ +   0 -   \2\ +   2 -    \ +     -   \ +   -   \contosomail\ +   contosomail -   \ShellSystem\ +   ShellSystem -   \[SHELLNOOP]\ +   [SHELLNOOP] -   \[SetForeground][ShellNewDatabase "%1"]\ +   [SetForeground][ShellNewDatabase "%1"] -   \ +   -   \ +   -   \ +   -   \ +   -   \ +   -   \ +   -   \ +   -   \ +   - \`\`\` + ``` **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 @@ -561,62 +561,61 @@ allowed in the body: specifically if you want the other clients still enabled except for that client. - **\`\`\`** + ``` - \ + -   \ +   - \ + - \`\`\` + ``` **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. - **\`\`\`** + ``` - \ + - \ + - \ + - \ + -   \[{ProgramFilesX86}]\\Microsoft - Contoso\\Contoso\\contosomail.EXE\ +   [{ProgramFilesX86}]\Microsoft + Contoso\Contoso\contosomail.EXE -   \contosomail.exe\ +   contosomail.exe -   \[{ProgramFilesX86}]\\Microsoft - Contoso\\Contoso\\contosomail.EXE\ +   [{ProgramFilesX86}]\Microsoft + Contoso\Contoso\contosomail.EXE -   \ +   -   \false\ +   false -   \ +   - \ + - \ + - \ + - \ + - \`\`\` + ``` - **COM**: Allows an Application register Local COM servers. Mode can be - Integration, Isolated or Off. When Isol. + **COM**: Allows an Application register Local COM servers. Mode can be Integration, Isolated or Off. When Isol. - **\`\`\`** + ``` - \ + - \`\`\` + ``` **Other Settings**: @@ -625,85 +624,84 @@ allowed in the body: **Virtual Kernel Objects**: - **\`\`\`** + **```** - \ + - \`\`\` + ``` - **Virtual Registry**: Used if you want to set a registry in the Virtual - Registry within HKCU + **Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU - **\`\`\`** + ``` - \ + - \ + - \ + - \ + -  \ +   -   \ +   -  \ +   - \ + -   \ +   - \`\`\` + ``` **Virtual File System** - **\`\`\`** + ```       \ - \`\`\` + ``` - **Virtual Fonts** + **Virtual Fonts** - **\`\`\`** + ``` -       \ +       - \`\`\` + ``` - **Virtual Environment Variables** + **Virtual Environment Variables** - **\`\`\`** + ``` - \ + - \ + -        \ +         -        \ +         -        \ +         -       \ +        -        \ +         -         \ +          -         \ +          - \`\`\` + ``` **Virtual services** - **\`\`\`** + ``` -       \ +       - \`\`\` + ``` 1. **UserScripts** – Scripts can be used to set up or alter the virtual environment as well as execute scripts at time of deployment or removal @@ -719,24 +717,24 @@ allowed in the body: points for the named package enter the following in the UserConfig file (where PackageName is the Package GUID in App-V 4.6: -- \`\`\` +- ``` - \ + - \`\`\` + ``` ### Dynamic Deployment Configuration file **Header** - The header of a Deployment Configuration file is as follows: -\`\`\` +``` -\\ + -\`\`\` +``` The **PackageId** is the same value as exists in the manifest file. @@ -756,31 +754,31 @@ The **PackageId** is the same value as exists in the manifest file. only for an entire machine, not for a specific user on the machine. For example, HKEY_LOCAL_MACHINE registry keys in the VFS. -\`\`\` +``` -\ +xmlns="http://schemas.microsoft.com/appv/2010/deploymentconfiguration"> -\ + ... -\ + -\ + ... -\ + ... -\ + -\ + -\`\`\` +``` **User Configuration** - use the previous **Dynamic User Configuration file** section for information on settings that are provided in the user configuration @@ -795,21 +793,21 @@ subsections allowed in under this element 1. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under \: -- \`\`\` +- ``` - \ + -   \ +     … -   \ +   … - \ + - \`\`\` + ``` The following section displays the various subsystems and usage samples. @@ -829,78 +827,78 @@ subsections allowed in under this element extension also makes the virtual application visible in the Set Default Programs UI.: - \`\`\` + ``` - \ + -   \ +   -    \ +     -     \ +        -    \[{PackageRoot}]\\LitView\\LitViewBrowser.exe\ +    [{PackageRoot}]\LitView\LitViewBrowser.exe -      \ +       -       \LitView Browser\ +       LitView Browser -       \SOFTWARE\\LitView\\Browser\\Capabilities\ +       SOFTWARE\LitView\Browser\Capabilities -      \ +       -    \ +     -     \ +        -    \\@[{ProgramFilesX86}]\\LitView\\LitViewBrowser.exe,-12345\ +    @[{ProgramFilesX86}]\LitView\LitViewBrowser.exe,-12345   -    \\@[{ProgramFilesX86}]\\LitView\\LitViewBrowser.exe,-12346\ +    @[{ProgramFilesX86}]\LitView\LitViewBrowser.exe,-12346 -      \0\ +      0 -      \Lit View E-Mail Client\ +      Lit View E-Mail Client -      \ +       -       \ +        -       \ +        -       \ +        -      \ +       -      \ +       -       \ +        -       \ +        -      \ +       -     \ +      -       \ +        -      \ +       -      \ +       -   \ +    -    \ +     -   \ +   - \ + - \ + - \`\`\` + ``` **Other Settings**: @@ -909,62 +907,62 @@ subsections allowed in under this element **Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY_Local_Machine. - **\`\`\`** + ``` - \ + - \ + -   \ +   -     \ +      -    \ +     -   \ +   -  \ +   - \ + - \ + - \`\`\` + ``` - **Machine Wide Virtual Kernel Objects** + **Machine Wide Virtual Kernel Objects** - **\`\`\`** + ``` - \ + - \ + -    \ +     -  \ +   - \ + - \`\`\` + ``` 1. **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.   -- \`\`\` +- ``` - \ + -   ..  +   ...  -   \ +    -   .. +   ... - \ + - \`\`\` + ``` 1. **MachineScripts** – Package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment @@ -976,28 +974,28 @@ subsections allowed in under this element whose child processes will be terminated when the application exe process is terminated. -- \`\`\` +- ``` - \ + -   ..    +   ...    -   \ +    -     \ +      -     \ +      -     \ +      -   \ +    -   .. +   ... - \ + - \`\`\` + ``` ### Scripts @@ -1030,9 +1028,9 @@ 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]** +>[!NOTE] -**\>**We recommended that you run the multi-script line from a command prompt +>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. @@ -1041,9 +1039,7 @@ the deployment configuration file. Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run. -\`\`\` - -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +``` ScriptRunner.exe @@ -1055,52 +1051,49 @@ configuration file to add the scripts that you want to run. -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``` -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Parameter in the example file -#### \\\ +#### \ Name of the event trigger for which you are running a script, such as adding a package or publishing a package. -#### \\\ScriptRunner.exe\\\ +#### \ScriptRunner.exe\ The script launcher application that is installed as part of the App-V client installation. -\>[!NOTE] +>[!NOTE] -\>Although ScriptRunner.exe is installed as part of the App-V client, the +>Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:FilesApplication Virtualizationfolder. -#### \\\ +#### \ -\`-appvscript\` - Token that represents the actual script that you want to run. +`-appvscript` - Token that represents the actual script that you want to run. -\`script1.exe\` – Name of the script that you want to run. +`script1.exe` – Name of the script that you want to run. -\`arg1 arg2\` – Arguments for the script that you want to run. +`arg1 arg2` – Arguments for the script that you want to run. -\`-appvscriptrunnerparameters\` – Token that represents the execution options +`-appvscriptrunnerparameters` – Token that represents the execution options for script1.exe -\`-wait\` – Token that informs ScriptRunner to wait for execution of script1.exe +`-wait` – Token that informs ScriptRunner to wait for execution of script1.exe to complete before proceeding to the next script. -\`-timeout=x\` – Token that informs ScriptRunner to stop running the current +`-timeout=x` – Token that informs ScriptRunner to stop running the current script after x number of seconds. All other specified scripts still runs. -\`-rollbackonerror\` – Token that informs ScriptRunner to stop running all +`-rollbackonerror` – Token that informs ScriptRunner to stop running all scripts that haven't yet run and to roll back an error to the App-V client. -#### \\\ +#### \ Waits for overall completion of ScriptRunner.exe. @@ -1117,34 +1110,23 @@ script does not run. ### Create a Dynamic Configuration file using an App-V 5.1 Manifest file -You can create the Dynamic Configuration file using one of three methods: either -manually, using the App-V 5.1 Management Console or sequencing a package, which -will be generated with 2 sample files. +You can create the Dynamic Configuration file using one of three methods: either manually, using the App-V 5.1 Management Console or sequencing a package, which will be generated with 2 sample files. -For more information about how to create the file using the App-V 5.1 Management -Console see, [How to Create a Custom Configuration File by Using the App-V 5.1 -Management -Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-51-management-console.md). +For more information about how to create the file using the App-V 5.1 Management Console see, [How to Create a Custom Configuration File by Using the App-V 5.1 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-51-management-console.md). To create the file manually, the information above in previous sections can be combined into a single file. We recommend you use files generated by the sequencer. -Got a suggestion for App-V? ---------------------------- +## Got a suggestion for App-V? -Add or vote on suggestions -[here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). -For App-V issues, use the [App-V TechNet -Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv). +- Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). +- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv). -Related topics --------------- +## Related topics -[How to Apply the Deployment Configuration File by Using -PowerShell](how-to-apply-the-deployment-configuration-file-by-using-powershell51.md) +- [How to Apply the Deployment Configuration File by Using PowerShell](how-to-apply-the-deployment-configuration-file-by-using-powershell51.md) -[How to Apply the User Configuration File by Using -PowerShell](how-to-apply-the-user-configuration-file-by-using-powershell51.md) +- [How to Apply the User Configuration File by Using PowerShell](how-to-apply-the-user-configuration-file-by-using-powershell51.md) -[Operations for App-V 5.1](operations-for-app-v-51.md) +- [Operations for App-V 5.1](operations-for-app-v-51.md)