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

Merge pull request #9611 from aczechowski/cz-20240214-topic

Browse Source 
bulk add default ms.topic to appv articles
This commit is contained in:
Gary Moore 2024-02-14 14:00:18 -08:00 committed by GitHub
commit f9d33c8699
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
21 changed files with 106 additions and 85 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
windows/application-management/app-v/appv-evaluating-appv.md
View File

@ -4,11 +4,12 @@ description: Learn how to evaluate App-V for Windows 10/11 in a lab environment
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Evaluating App-V # Evaluating App-V

13
windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
View File

@ -4,11 +4,12 @@ description: How to Install the App-V Databases and Convert the Associated Secur
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
@ -79,14 +80,14 @@ Before attempting this procedure, you should read and understand the information
               "  Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" +                "  Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" +
               "  The output is written to the console in the format 'Account name    SID as string   SID as hexadecimal'{0}" +                "  The output is written to the console in the format 'Account name    SID as string   SID as hexadecimal'{0}" +
               "  And can be written out to a file using standard Windows PowerShell redirection{0}" +                "  And can be written out to a file using standard Windows PowerShell redirection{0}" +
               "  Please specify user accounts in the format 'DOMAIN\username'{0}" +                "  Please specify user accounts in the format 'DOMAIN\username'{0}" +
               "  Please specify machine accounts in the format 'DOMAIN\machinename$'{0}" +                "  Please specify machine accounts in the format 'DOMAIN\machinename$'{0}" +
               "  For more help content, please run 'Get-Help ConvertToSID.ps1'{0}" +                "  For more help content, please run 'Get-Help ConvertToSID.ps1'{0}" +
               "{0}====== Arguments ======{0}" +                "{0}====== Arguments ======{0}" +
               "{0}  /?    Show this help message", [Environment]::NewLine)                "{0}  /?    Show this help message", [Environment]::NewLine)
{ {
else else
{  { 
    #If an array was passed in, try to split it     #If an array was passed in, try to split it
    if($myArgs.Length -eq 1)     if($myArgs.Length -eq 1)
    {     {
@ -95,7 +96,7 @@ Before attempting this procedure, you should read and understand the information
    #Parse the arguments for account names     #Parse the arguments for account names
    foreach($accountName in $myArgs)     foreach($accountName in $myArgs)
    {        {   
        [string[]] $splitString = $accountName.Split('\')  # We're looking for the format "DOMAIN\Account" so anything that does not match, we reject         [string[]] $splitString = $accountName.Split('\')  # We're looking for the format "DOMAIN\Account" so anything that does not match, we reject
        if($splitString.Length -ne 2)         if($splitString.Length -ne 2)
        {         {

3
windows/application-management/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
View File

@ -4,11 +4,12 @@ description: How to Manage Connection Groups on a Stand-alone Computer by Using
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell # How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell

9
windows/application-management/app-v/appv-managing-connection-groups.md
View File

@ -4,11 +4,12 @@ description: Connection groups can allow administrators to manage packages indep
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Managing Connection Groups # Managing Connection Groups
@ -40,9 +41,9 @@ In some previous versions of App-V, connection groups were referred to as Dynami
- [Operations for App-V](appv-operations.md) - [Operations for App-V](appv-operations.md)

9
windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version.md
View File

@ -4,18 +4,19 @@ description: Learn how to migrate to Microsoft Application Virtualization (App-V
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Migrating to App-V from previous versions # Migrating to App-V from previous versions
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)] [!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
To migrate from App-V 4.x to App-V for Windows 10/11, you must upgrade to App-V 5.x first. To migrate from App-V 4.x to App-V for Windows 10/11, you must upgrade to App-V 5.x first.
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter ## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
@ -51,7 +52,7 @@ To understand the new process, review the following example `ConvertFrom-AppvLeg
**And you run this command:** **And you run this command:**
``` syntax ``` syntax
ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\ ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
-DestinationPath \\NewPkgStore\ContosoApp\ -DestinationPath \\NewPkgStore\ContosoApp\
-OSDsToIncludeInPackage X.osd,Y.osd -OSDsToIncludeInPackage X.osd,Y.osd
``` ```
@ -88,7 +89,7 @@ Use the package converter utility to upgrade virtual application packages create
**Important**   **Important**  
After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful. After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful.
**What to know before you convert existing packages** **What to know before you convert existing packages**

3
windows/application-management/app-v/appv-modify-an-existing-virtual-application-package.md
View File

@ -4,11 +4,12 @@ description: Learn how to modify an existing virtual application package and add
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to Modify an Existing Virtual Application Package # How to Modify an Existing Virtual Application Package

7
windows/application-management/app-v/appv-modify-client-configuration-with-powershell.md
View File

@ -4,11 +4,12 @@ description: Learn how to modify the Application Virtualization (App-V) client c
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to Modify Client Configuration by Using Windows PowerShell # How to Modify Client Configuration by Using Windows PowerShell
@ -28,8 +29,8 @@ Use the following procedure to configure the App-V client configuration.
`Set-AppVClientConfiguration –Name1 MyConfig –Name2 "xyz"` `Set-AppVClientConfiguration –Name1 MyConfig –Name2 "xyz"`
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). <br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related articles ## Related articles

3
windows/application-management/app-v/appv-move-the-appv-server-to-another-computer.md
View File

@ -4,11 +4,12 @@ description: Learn how to create a new management server console in your environ
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to move the App-V server to another computer # How to move the App-V server to another computer

51
windows/application-management/app-v/appv-performance-guidance.md
View File

@ -4,11 +4,12 @@ description: Learn how to configure App-V for optimal performance, optimize virt
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Performance Guidance for Application Virtualization # Performance Guidance for Application Virtualization
@ -16,7 +17,7 @@ ms.subservice: itpro-apps
**Applies to**: **Applies to**:
- Windows 7 SP1 - Windows 7 SP1
- Windows 10 - Windows 10
- Windows 11 - Windows 11
- Server 2012 R2 - Server 2012 R2
- Server 2016 - Server 2016
@ -103,7 +104,7 @@ The following information displays the required steps to prepare the base image
#### Prepare the Base Image #### Prepare the Base Image
- **Performance**: - **Performance**:
- Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md). - Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
- Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps. - Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
@ -120,7 +121,7 @@ The following information displays the required steps to prepare the base image
- `AppData\Local\Microsoft\AppV\Client\VFS` - `AppData\Local\Microsoft\AppV\Client\VFS`
- `AppData\Roaming\Microsoft\AppV\Client\VFS` - `AppData\Roaming\Microsoft\AppV\Client\VFS`
- **Storage**: - **Storage**:
- Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md). - Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
- Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps. - Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
@ -144,7 +145,7 @@ For critical App-V Client configurations and for a little more context and how-t
- **PreserveUserIntegrationsOnLogin**: If you have not pre-configured (**Add-AppvClientPackage**) a specific package and this setting isn't configured, the App-V Client will de-integrate* the persisted user integrations, then reintegrate*. - **PreserveUserIntegrationsOnLogin**: If you have not pre-configured (**Add-AppvClientPackage**) a specific package and this setting isn't configured, the App-V Client will de-integrate* the persisted user integrations, then reintegrate*.
For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh. For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh.
If you don't plan to pre-configure every available user package in the base image, use this setting. If you don't plan to pre-configure every available user package in the base image, use this setting.
- Configure in the Registry under `HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Integration`. - Configure in the Registry under `HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Integration`.
@ -181,7 +182,7 @@ UE-V will only support removing the .lnk file type from the exclusion list in th
- If a user has an application installed on one device but not another with .lnk files enabled. - If a user has an application installed on one device but not another with .lnk files enabled.
> [!Important] > [!Important]
> This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk. > This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
Using the Microsoft Registry Editor (regedit.exe), navigate to `HKEY\_LOCAL\_MACHINE\Software\Microsoft\UEV\Agent\Configuration\ExcludedFileTypes` and remove `.lnk` from the excluded file types. Using the Microsoft Registry Editor (regedit.exe), navigate to `HKEY\_LOCAL\_MACHINE\Software\Microsoft\UEV\Agent\Configuration\ExcludedFileTypes` and remove `.lnk` from the excluded file types.
@ -200,10 +201,10 @@ To enable an optimized sign-in experience, for example the App-V approach for th
- Attaching and detaching a user profile disk (UPD) or similar technology that contains the user integrations. - Attaching and detaching a user profile disk (UPD) or similar technology that contains the user integrations.
> [!Note] > [!Note]
> >
> App-V is supported when using UPD only when the entire profile is stored on the user profile disk. > App-V is supported when using UPD only when the entire profile is stored on the user profile disk.
> >
> App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver doesn't handle UPD selected folders. > App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver doesn't handle UPD selected folders.
- Capturing changes to the locations, which constitute the user integrations, prior to session sign out. - Capturing changes to the locations, which constitute the user integrations, prior to session sign out.
@ -246,50 +247,50 @@ Registry – HKEY\_CURRENT\_USER
This following process is a step-by-step walk-through of the App-V and UPM operations, and the users' expectations. This following process is a step-by-step walk-through of the App-V and UPM operations, and the users' expectations.
- **Performance**: After implementing this approach in the VDI/RDSH environment, on first login, - **Performance**: After implementing this approach in the VDI/RDSH environment, on first login,
- (Operation) A user-publishing/refresh is initiated. - (Operation) A user-publishing/refresh is initiated.
(Expectation) If it's the first time that a user has published virtual applications (for example, non-persistent), this operation will take the usual duration of a publishing/refresh. (Expectation) If it's the first time that a user has published virtual applications (for example, non-persistent), this operation will take the usual duration of a publishing/refresh.
- (Operation) After the publishing/refresh, the UPM solution captures the user integrations. - (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
(Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-out process. This result will incur the same/similar overhead as persisting the user state. (Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-out process. This result will incur the same/similar overhead as persisting the user state.
**On subsequent logins**: **On subsequent logins**:
- (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh. - (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
(Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (that is, package entitlements change), some may go away. (Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (that is, package entitlements change), some may go away.
- (Operation) Publishing/refresh will process unpublish and publish operations for changes in user package entitlements. - (Operation) Publishing/refresh will process unpublish and publish operations for changes in user package entitlements.
(Expectation) If there are no entitlement changes, publishing will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity of virtual applications (Expectation) If there are no entitlement changes, publishing will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity of virtual applications
The publishing operation (**Publish-AppVClientPackage**) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps. The publishing operation (**Publish-AppVClientPackage**) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.
- (Operation) UPM solution will capture user integrations again at sign off. - (Operation) UPM solution will capture user integrations again at sign off.
(Expectation) Same as previous. (Expectation) Same as previous.
**Outcome**: **Outcome**:
- Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of sign in. - Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of sign in.
- The publishing/refresh will process changes to the users-entitled virtual applications, which impacts the experience. - The publishing/refresh will process changes to the users-entitled virtual applications, which impacts the experience.
- **Storage**: After implementing this approach in the VDI/RDSH environment, on first login - **Storage**: After implementing this approach in the VDI/RDSH environment, on first login
- (Operation) A user-publishing/refresh is initiated. - (Operation) A user-publishing/refresh is initiated.
(Expectation): (Expectation):
- If this instance is the first time a user has published virtual applications (for example, non-persistent), this will take the usual duration of a publishing/refresh. - If this instance is the first time a user has published virtual applications (for example, non-persistent), this will take the usual duration of a publishing/refresh.
- First and subsequent logins will be impacted by pre-configuring of packages (add/refresh). - First and subsequent logins will be impacted by pre-configuring of packages (add/refresh).
- (Operation) After the publishing/refresh, the UPM solution captures the user integrations. - (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
(Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-off process. This result will incur the same/similar overhead as persisting the user state. (Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-off process. This result will incur the same/similar overhead as persisting the user state.
**On subsequent logins**: **On subsequent logins**:
- (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh. - (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
- (Operation) Add/refresh must pre-configure all user targeted applications. - (Operation) Add/refresh must pre-configure all user targeted applications.
@ -300,7 +301,7 @@ This following process is a step-by-step walk-through of the App-V and UPM opera
- (Operation) Publishing/refresh will process unpublish and publish operations for changes to user package entitlements. - (Operation) Publishing/refresh will process unpublish and publish operations for changes to user package entitlements.
**Outcome**: Because the add/refresh must reconfigure all the virtual applications to the VM, the publishing refresh time on every login will be extended. **Outcome**: Because the add/refresh must reconfigure all the virtual applications to the VM, the publishing refresh time on every login will be extended.
### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle ### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle
Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (unpublished) virtual application packages, it's recommended you update the base image to reflect these changes. To understand why review the following section: Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (unpublished) virtual application packages, it's recommended you update the base image to reflect these changes. To understand why review the following section:
@ -380,7 +381,7 @@ Removing FB1 doesn't require the original application installer. After completin
"C:\\UpgradedPackages" "C:\\UpgradedPackages"
> [!Note] > [!Note]
> This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file. > This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file.
|Step|Considerations|Benefits|Tradeoffs| |Step|Considerations|Benefits|Tradeoffs|
|--- |--- |--- |--- | |--- |--- |--- |--- |
@ -398,7 +399,7 @@ When publishing a virtual application package, the App-V Client will detect if a
|Step|Considerations|Benefits|Tradeoffs| |Step|Considerations|Benefits|Tradeoffs|
|--- |--- |--- |--- | |--- |--- |--- |--- |
|Selectively Employ Dynamic Configuration files|The App-V client must parse and process these Dynamic Configuration files. <br> <br>Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.<br> <br>Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.|Publishing times will improve if these files are used selectively or not at all.|Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files.| |Selectively Employ Dynamic Configuration files|The App-V client must parse and process these Dynamic Configuration files. <br> <br>Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.<br> <br>Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.|Publishing times will improve if these files are used selectively or not at all.|Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files.|
### Disabling a Dynamic Configuration by using Windows PowerShell ### Disabling a Dynamic Configuration by using Windows PowerShell

3
windows/application-management/app-v/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
View File

@ -4,11 +4,12 @@ description: How to Register and Unregister a Publishing Server by Using the Man
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to Register and Unregister a Publishing Server by Using the Management Console # How to Register and Unregister a Publishing Server by Using the Management Console

3
windows/application-management/app-v/appv-release-notes-for-appv-for-windows-1703.md
View File

@ -4,11 +4,12 @@ description: A list of known issues and workarounds for App-V running on Windows
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Release Notes for App-V for Windows 10 version 1703 and later # Release Notes for App-V for Windows 10 version 1703 and later

15
windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md
View File

@ -4,11 +4,12 @@ description: A list of known issues and workarounds for App-V running on Windows
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Release Notes for App-V for Windows 10, version 1607 # Release Notes for App-V for Windows 10, version 1607
@ -17,7 +18,7 @@ ms.subservice: itpro-apps
- Windows 10, version 1607 - Windows 10, version 1607
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1607. The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1607.
## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client ## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client
There are MSI packages generated by an App-V sequencer from previous versions of App-V (Versions 5.1 and earlier). These packages include a check to validate whether the App-V client is installed on client devices, before allowing the MSI package to be installed. As the App-V client gets installed automatically when you upgrade user devices to Windows 10, version 1607, the prerequisite check fails and causes the MSI to fail. There are MSI packages generated by an App-V sequencer from previous versions of App-V (Versions 5.1 and earlier). These packages include a check to validate whether the App-V client is installed on client devices, before allowing the MSI package to be installed. As the App-V client gets installed automatically when you upgrade user devices to Windows 10, version 1607, the prerequisite check fails and causes the MSI to fail.
@ -28,20 +29,20 @@ There are MSI packages generated by an App-V sequencer from previous versions of
2. Ensure that you've installed the **MSI Tools** included in the Windows 10 SDK, available as follows: 2. Ensure that you've installed the **MSI Tools** included in the Windows 10 SDK, available as follows:
- For the **Visual Studio Community 2015 with Update 3** client, which includes the latest Windows 10 SDK and developer tools, see [Downloads and tools for Windows 10](https://developer.microsoft.com/windows/downloads). - For the **Visual Studio Community 2015 with Update 3** client, which includes the latest Windows 10 SDK and developer tools, see [Downloads and tools for Windows 10](https://developer.microsoft.com/windows/downloads).
- For the standalone Windows 10 SDK without other tools, see [Standalone Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk). - For the standalone Windows 10 SDK without other tools, see [Standalone Windows SDK](https://developer.microsoft.com/windows/downloads/windows-sdk).
3. Copy msidb.exe from the default path of the Windows SDK installation (**C:\Program Files (x86)\Windows Kits\10**) to a different directory. For example: **C:\MyMsiTools\bin** 3. Copy msidb.exe from the default path of the Windows SDK installation (**C:\Program Files (x86)\Windows Kits\10**) to a different directory. For example: **C:\MyMsiTools\bin**
4. From an elevated Windows PowerShell prompt, navigate to the following folder: 4. From an elevated Windows PowerShell prompt, navigate to the following folder:
&lt;Windows Kits 10 installation folder&gt;**\Microsoft Application Virtualization\Sequencer\\**
By default, this path is:<br>**C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer** &lt;Windows Kits 10 installation folder&gt;**\Microsoft Application Virtualization\Sequencer\\**
By default, this path is:<br>**C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer**
5. Run the following command: 5. Run the following command:
`Update-AppvPackageMsi -MsiPackage "<path to App-V Package .msi file>" -MsSdkPath "<path>"` `Update-AppvPackageMsi -MsiPackage "<path to App-V Package .msi file>" -MsSdkPath "<path>"`
where the path is to the new directory (**C:\MyMsiTools\ for this example**). where the path is to the new directory (**C:\MyMsiTools\ for this example**).

11
windows/application-management/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md
View File

@ -4,11 +4,12 @@ description: Running a Locally Installed Application Inside a Virtual Environmen
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 03/08/2018 ms.date: 03/08/2018
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications # Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
@ -81,10 +82,10 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
The application in the previous example would produce a registry export file (.reg file) like the following example: The application in the previous example would produce a registry export file (.reg file) like the following example:
```registry ```registry
Windows Registry Editor Version 5.00 Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual]
@="" @=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe]
@="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555 @="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555
``` ```

9
windows/application-management/app-v/appv-sequence-a-package-with-powershell.md
View File

@ -4,11 +4,12 @@ description: Learn how to sequence a new Microsoft Application Virtualization (A
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to Sequence a Package by using Windows PowerShell # How to Sequence a Package by using Windows PowerShell
@ -20,7 +21,7 @@ Use the following procedure to create a new App-V package using Windows PowerShe
> [!NOTE] > [!NOTE]
> Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). > Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
**To create a new virtual application by using Windows PowerShell** **To create a new virtual application by using Windows PowerShell**
1. Install the App-V sequencer. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md). 1. Install the App-V sequencer. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
@ -60,10 +61,10 @@ The following list displays additional optional parameters that can be used with
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened. - FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
Starting with Windows 10 version 1703, the `new-appvsequencerpackage` or the `update-appvsequencepackage` cmdlets automatically capture and store all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. Starting with Windows 10 version 1703, the `new-appvsequencerpackage` or the `update-appvsequencepackage` cmdlets automatically capture and store all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
> [!IMPORTANT] > [!IMPORTANT]
> If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template. > If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
## Related articles ## Related articles

3
windows/application-management/app-v/appv-technical-reference.md
View File

@ -4,11 +4,12 @@ description: Learn strategy and context for many performance optimization practi
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Technical Reference for App-V # Technical Reference for App-V

3
windows/application-management/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
View File

@ -4,11 +4,12 @@ description: How to Transfer Access and Configurations to Another Version of a P
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console # How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console

3
windows/application-management/app-v/appv-troubleshooting.md
View File

@ -4,11 +4,12 @@ description: Learn how to find information about troubleshooting Application Vir
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Troubleshooting App-V # Troubleshooting App-V

29
windows/application-management/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md
View File

@ -4,18 +4,19 @@ description: Learn about upgrading to Application Virtualization (App-V) for Win
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Upgrading to App-V for Windows client from an existing installation # Upgrading to App-V for Windows client from an existing installation
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)] [!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10/11, you need to make only the following few adjustments to your existing environment to start using App-V for Windows client. If you’re already using App-V and you’re planning to upgrade user devices to Windows 10/11, you need to make only the following few adjustments to your existing environment to start using App-V for Windows client.
1. [Upgrade user devices to Windows 10/11](#upgrade-user-devices-to-windows-1011). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. 1. [Upgrade user devices to Windows 10/11](#upgrade-user-devices-to-windows-1011). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
@ -31,11 +32,11 @@ These steps are explained in more detail below.
## Upgrade user devices to Windows 10/11 ## Upgrade user devices to Windows 10/11
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows document set](/windows/windows-10/) for information about upgrading user devices. Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows document set](/windows/windows-10/) for information about upgrading user devices.
## Verify that App-V applications and settings were migrated correctly ## Verify that App-V applications and settings were migrated correctly
After upgrading a user device, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade. After upgrading a user device, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade.
To verify that the user’s App-V application packages were migrated correctly, type `Get-AppvClientPackage` in Windows PowerShell. To verify that the user’s App-V application packages were migrated correctly, type `Get-AppvClientPackage` in Windows PowerShell.
@ -43,13 +44,13 @@ To verify that the user’s App-V settings were migrated correctly, type `Get-Ap
## Enable the in-box App-V client ## Enable the in-box App-V client
With Windows 10/11, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell. With Windows 10/11, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
**To enable the App-V client with Group Policy** **To enable the App-V client with Group Policy**
1. Open the device’s **Group Policy Editor**. 1. Open the device’s **Group Policy Editor**.
2. Navigate to **Computer Configuration > Administrative Templates > System > App-V**. 2. Navigate to **Computer Configuration > Administrative Templates > System > App-V**.
3. Run **Enables App-V Client** and then select **Enabled** on the screen that appears. 3. Run **Enables App-V Client** and then select **Enabled** on the screen that appears.
@ -71,27 +72,27 @@ Once you’ve enabled the in-box App-V client, you need to configure it to point
**To modify client settings to point to an existing App-V publishing server with Windows PowerShell** **To modify client settings to point to an existing App-V publishing server with Windows PowerShell**
Type the following cmdlet in a Windows PowerShell window: Type the following cmdlet in a Windows PowerShell window:
`Add-AppvPublishingServer -Name AppVServer -URL https:// appvserver:2222` `Add-AppvPublishingServer -Name AppVServer -URL https:// appvserver:2222`
**To modify client settings to point to an existing App-V publishing server with Group Policy** **To modify client settings to point to an existing App-V publishing server with Group Policy**
1. Open the device’s **Local Group Policy Editor**. 1. Open the device’s **Local Group Policy Editor**.
2. Navigate to **Computer Configuration > Administrative Templates > System > App-V > Publishing**. 2. Navigate to **Computer Configuration > Administrative Templates > System > App-V > Publishing**.
3. Enter your existing App-V publishing server’s details in **Options** and then click or press **Apply**. 3. Enter your existing App-V publishing server’s details in **Options** and then click or press **Apply**.
## Verify that the in-box App-V client can receive and launch .appv packages ## Verify that the in-box App-V client can receive and launch .appv packages
1. Add and publish a package using the following Windows PowerShell cmdlets: 1. Add and publish a package using the following Windows PowerShell cmdlets:
`Add-AppvClientPackage \\path\to\appv\package.appv | Publish-AppvClientPackage` `Add-AppvClientPackage \\path\to\appv\package.appv | Publish-AppvClientPackage`
2. Launch the published package. 2. Launch the published package.
3. Unpublish an existing package use the following cmdlet: 3. Unpublish an existing package use the following cmdlet:
`Unpublish-AppvClientPackage "ContosoApplication"` `Unpublish-AppvClientPackage "ContosoApplication"`

5
windows/application-management/app-v/appv-using-the-client-management-console.md
View File

@ -4,11 +4,12 @@ description: Learn how to use the Application Virtualization (App-V) client mana
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Using the App-V Client Management Console # Using the App-V Client Management Console
@ -25,7 +26,7 @@ The App-V client has associated settings that can be configured to determine how
- [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md) - [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md) - [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
## <a href="" id="the-app-v-5-1-client-management-console-"></a>The App-V client management console ## <a href="" id="the-app-v-5-1-client-management-console-"></a>The App-V client management console

3
windows/application-management/app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
View File

@ -4,11 +4,12 @@ description: How to View and Configure Applications and Default Virtual Applicat
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console # How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console

3
windows/application-management/app-v/appv-viewing-appv-server-publishing-metadata.md
View File

@ -4,11 +4,12 @@ description: Use this procedure to view App-V Server publishing metadata, which
author: aczechowski author: aczechowski
ms.service: windows-client ms.service: windows-client
ms.date: 04/19/2017 ms.date: 04/19/2017
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: aaroncz ms.author: aaroncz
ms.collection: must-keep ms.collection: must-keep
ms.subservice: itpro-apps ms.subservice: itpro-apps
ms.topic: article
--- ---
# Viewing App-V Server Publishing Metadata # Viewing App-V Server Publishing Metadata