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

Fixed acrolinx and build issue

Browse Source
This commit is contained in:
Alekhya Jupudi 2021-11-10 11:58:04 +05:30
parent 6f8104efdb
commit 5c6259d9f5
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -40,11 +40,11 @@ Some terms used in this document may have different meanings depending on extern
Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI). Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
To help determine what information is relevant to your environment you should review each section’s brief overview and applicability checklist. To help determine what information is relevant to your environment, you should review each section’s brief overview and applicability checklist.
## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V in stateful\* non-persistent deployments ## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V in stateful\* non-persistent deployments
This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. A number of conditions must be met and steps followed to provide the optimal user experience. This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. Many conditions must be met and steps followed to provide the optimal user experience.
Use the information in the following section for more information: Use the information in the following section for more information:
@ -70,7 +70,7 @@ Use the information in the following section for more information:
[Enhancing the VDI Experience through Performance Optimization/Tuning](#bkmk-evdi) [Enhancing the VDI Experience through Performance Optimization/Tuning](#bkmk-evdi)
### Applicability Checklist ### <a href="" id="applicability-checklist-"></a>Applicability Checklist
|Checklist|Deployment Environment| |Checklist|Deployment Environment|
|--- |--- | |--- |--- |
@ -87,15 +87,15 @@ Use the information in the following section for more information:
|--- |--- | |--- |--- |
|![Checklist box](images/checklistbox.gif)|Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups.| |![Checklist box](images/checklistbox.gif)|Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups.|
### Usage Scenarios ### <a href="" id="bkmk-us"></a>Usage Scenarios
As you review the two scenarios, keep in mind that these approach the extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users, virtual application packages, or both. As you review the two scenarios, keep in mind that these approach the extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users, virtual application packages, or both.
|Optimized for Performance|Optimized for Storage| |Optimized for Performance|Optimized for Storage|
|--- |--- | |--- |--- |
|To provide the most optimal user experience, this approach leverages the capabilities of a UPM solution and requires additional image preparation and can incur some additional image management overhead.<br> <br>The following describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) later in this topic.|The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in very costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image.<br> <br>The impact of this alteration is detailed in the [User Experience Walk-through](#bkmk-uewt) section of this document.| |To provide the most optimal user experience, this approach uses the capabilities of a UPM solution and requires extra image preparation and can incur some more image management overhead.<br> <br>The following describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) later in this topic.|The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image.<br> <br>The impact of this alteration is detailed in the [User Experience Walk-through](#bkmk-uewt) section of this document.|
### Preparing your Environment ### <a href="" id="bkmk-pe"></a>Preparing your Environment
The following table displays the required steps to prepare the base image and the UE-V or another UPM solution for the approach. The following table displays the required steps to prepare the base image and the UE-V or another UPM solution for the approach.
@ -103,14 +103,14 @@ The following table displays the required steps to prepare the base image and th
|Optimized for Performance|Optimized for Storage| |Optimized for Performance|Optimized for Storage|
|--- |--- | |--- |--- |
|<li>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).<li>Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.<li>Configure for Shared Content Store (SCS) mode. For more information see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).<li>Configure Preserve User Integrations on Login Registry DWORD.<li>Pre-configure all user- and global-targeted packages for example, **Add-AppvClientPackage**.<li>Pre-configure all user- and global-targeted connection groups for example, **Add-AppvClientConnectionGroup**.<li>Pre-publish all global-targeted packages.<br>Alternatively,<li>Perform a global publishing/refresh.<li>Perform a user publishing/refresh.<li>Un-publish all user-targeted packages.<li>Delete the following user-Virtual File System (VFS) entries<br><code>AppData\Local\Microsoft\AppV\Client\VFS</code><br><code>AppData\Roaming\Microsoft\AppV\Client\VFS</code>|<li>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).<li>Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.<li>Configure for Shared Content Store (SCS) mode. For more information see Deploying the<li>App-V Sequencer and Configuring the Client.<li>Configure Preserve User Integrations on Login Registry DWORD.<li>Pre-configure all global-targeted packages for example,** Add-AppvClientPackage**.<li>Pre-configure all global-targeted connection groups for example, **Add-AppvClientConnectionGroup**.<li>Pre-publish all global-targeted packages.| |<li>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).<li>Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.<li>Configure for Shared Content Store (SCS) mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).<li>Configure Preserve User Integrations on Login Registry DWORD.<li>Pre-configure all user- and global-targeted packages, for example, **Add-AppvClientPackage**.<li>Pre-configure all user- and global-targeted connection groups, for example, **Add-AppvClientConnectionGroup**.<li>Pre-publish all global-targeted packages.<br>Alternatively,<li>Perform a global publishing/refresh.<li>Perform a user publishing/refresh.<li>Unpublish all user-targeted packages.<li>Delete the following user-Virtual File System (VFS) entries<br><code>AppData\Local\Microsoft\AppV\Client\VFS</code><br><code>AppData\Roaming\Microsoft\AppV\Client\VFS</code>|<li>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).<li>Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.<li>Configure for Shared Content Store (SCS) mode. For more information, see Deploying the<li>App-V Sequencer and Configuring the Client.<li>Configure Preserve User Integrations on Login Registry DWORD.<li>Pre-configure all global-targeted packages, for example,** Add-AppvClientPackage**.<li>Pre-configure all global-targeted connection groups, for example, **Add-AppvClientConnectionGroup**.<li>Pre-publish all global-targeted packages.|
**Configurations** - For critical App-V Client configurations and for a little more context and how-to, review the following information: **Configurations** - For critical App-V Client configurations and for a little more context and how-to, review the following information:
|Configuration Setting|What does this do?|How should I use it?| |Configuration Setting|What does this do?|How should I use it?|
|--- |--- |--- | |--- |--- |--- |
|Shared Content Store (SCS) Mode<br> <li>Configurable in Windows PowerShell with <code>Set-AppvClientConfiguration -SharedContentStoreMode 1</code> <br>or configurable with Group Policy, as described in [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).|When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).<br>This helps to conserve local storage and minimize disk I/O per second (IOPS).|This is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN.| |Shared Content Store (SCS) Mode<br> <li>Configurable in Windows PowerShell with <code>Set-AppvClientConfiguration -SharedContentStoreMode 1</code> <br>Or configurable with Group Policy, as described in [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).|When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).<br>This helps to conserve local storage and minimize disk I/O per second (IOPS).|This is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN.|
|PreserveUserIntegrationsOnLogin<li>Configure in the Registry under **HKEY_LOCAL_MACHINE \ Software \ Microsoft \ AppV \ Client \ Integration**.<li>Create the DWORD value **PreserveUserIntegrationsOnLogin** with a value of 1.<li>Restart the App-V client service or restart the computer running the App-V Client.|If you have not pre-configured (**Add-AppvClientPackage**) a specific package and this setting is not configured, the App-V Client will de-integrate* the persisted user integrations, then re-integrate*.<br>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.| |PreserveUserIntegrationsOnLogin<li>Configure in the Registry under **HKEY_LOCAL_MACHINE \ Software \ Microsoft \ AppV \ Client \ Integration**.<li>Create the DWORD value **PreserveUserIntegrationsOnLogin** with a value of 1.<li>Restart the App-V client service or restart the computer running the App-V Client.|If you have not pre-configured (**Add-AppvClientPackage**) a specific package and this setting is not configured, the App-V Client will de-integrate* the persisted user integrations, then reintegrate*.<br>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.|
|MaxConcurrentPublishingRefresh<li>Configure in the Registry under **HKEY_LOCAL_MACHINE \ Software \ Microsoft \ AppV \ Client \ Publishing**.<li>Create the DWORD value **MaxConcurrentPublishingrefresh** with the desired maximum number of concurrent publishing refreshes.<li>The App-V client service and computer do not need to be restarted.|This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit.|Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync.<br>If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they log in could take an indeterminate amount of time.| |MaxConcurrentPublishingRefresh<li>Configure in the Registry under **HKEY_LOCAL_MACHINE \ Software \ Microsoft \ AppV \ Client \ Publishing**.<li>Create the DWORD value **MaxConcurrentPublishingrefresh** with the desired maximum number of concurrent publishing refreshes.<li>The App-V client service and computer do not need to be restarted.|This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit.|Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync.<br>If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they log in could take an indeterminate amount of time.|
### Configure UE-V solution for App-V Approach ### Configure UE-V solution for App-V Approach