mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Removd mentions of installing or deploying client, redirected a file, updated links to match
This commit is contained in:
JanKeller1
@ -47,18 +47,10 @@ Before you design the App-V infrastructure, determine the project’s scope. The
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Determine Which App-V Infrastructure is Required
|
||||
|
||||
|
||||
>**Important**
|
||||
Both of the following models require the App-V client to be installed on the computer where you plan to run virtual applications.
|
||||
|
||||
You can also manage your App-V environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
|
||||
|
||||
- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
|
||||
|
||||
- With disconnected remote users who cannot connect to the App-V infrastructure.
|
||||
|
||||
@ -108,6 +108,6 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
|
||||
@ -15,7 +15,7 @@ App-V supports a number of different deployment options. Review this topic for i
|
||||
## App-V Deployment Information
|
||||
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
This section describes how to install the App-V sequencer, which is used to virtualize applications, and how to enable the App-V client, which runs on target computers to facilitate virtualized packages.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploy the App-V Sequencer and Client (Windows 10)
|
||||
description: Deploying the App-V Sequencer and Client
|
||||
title: Deploying the App-V Sequencer and Configuring the Client (Windows 10)
|
||||
description: Deploying the App-V Sequencer and Configuring the Client
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,13 +9,12 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Deploying the App-V Sequencer and Client
|
||||
# Deploying the App-V Sequencer and Configuring the Client
|
||||
|
||||
The App-V Sequencer and client enable administrators to virtualize and run virtualized applications.
|
||||
|
||||
## Enable the client
|
||||
|
||||
|
||||
The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
|
||||
|
||||
> [!NOTE]
|
||||
@ -25,7 +24,6 @@ The App-V client is the component that runs a virtualized application on a targe
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
@ -34,7 +32,6 @@ The App-V client stores its configuration in the registry. You can gather some u
|
||||
|
||||
You can use Group Policy to configure the client settings for the App-V client and the Remote Desktop Services client.
|
||||
|
||||
|
||||
Perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller.
|
||||
|
||||
1. Save the **.admx** file to the following directory: **Windows \\ PolicyDefinitions**
|
||||
@ -43,11 +40,9 @@ Perform the following steps on the computer that you will use to manage Group Po
|
||||
|
||||
After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console.
|
||||
|
||||
The App-V client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
|
||||
## Deploy the client by using the Shared Content Store mode
|
||||
## Understanding Shared Content Store mode for App-V clients
|
||||
|
||||
The App-V Shared Content Store (SCS) mode enables the SCS App-V clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V client are supported with SCS mode.
|
||||
|
||||
@ -62,15 +57,25 @@ The SCS mode is helpful in the following scenarios:
|
||||
|
||||
- Remote Desktop Services deployments
|
||||
|
||||
To use SCS in your environment, you must enable the App-V client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V client to run in SCS mode by entering the following Windows PowerShell command on the computer that runs the App-V client:
|
||||
|
||||
```
|
||||
set-AppvClientConfiguration -SharedContentStoreMode 1
|
||||
```
|
||||
To use SCS in your environment, you must configure the App-V client to run in SCS mode (it will not use SCS mode by default).
|
||||
|
||||
There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V client in SCS mode. This can be accomplished with Windows PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using Windows PowerShell commands. The package would not stream across the network because it would be locally stored.
|
||||
|
||||
[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
### Configure the Group Policy setting for the SCS Mode for App-V clients
|
||||
|
||||
Use the following steps to locate and configure the Group Policy setting for the SCS Mode for App-V clients.
|
||||
|
||||
1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
|
||||
|
||||
2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
|
||||
|
||||
### Configure an individual client to use the SCS mode
|
||||
|
||||
To configure the App-V client to run in SCS mode, on the client, enter the following Windows PowerShell command:
|
||||
|
||||
```
|
||||
Set-AppvClientConfiguration -SharedContentStoreMode 1
|
||||
```
|
||||
|
||||
## Deploy the Sequencer
|
||||
|
||||
@ -87,11 +92,6 @@ You can use the App-V Sequencer log information to help troubleshoot the Sequenc
|
||||
|
||||
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**. Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**.
|
||||
|
||||
## Other resources for deploying the Sequencer and client
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
## Have 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/en-US/home?forum=mdopappv).
|
||||
|
||||
@ -74,7 +74,7 @@ The distributed deployment topology can support a large App-V client base and it
|
||||
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md)
|
||||
|
||||
## Using an Enterprise Software Distribution (ESD) solution and App-V
|
||||
You can also deploy the App-V clients and packages by using an ESD without having to deploy App-V. The full capabilities for integration will vary depending on the ESD that you use.
|
||||
You can also deploy packages by using an ESD. The full capabilities for integration will vary depending on the ESD that you use.
|
||||
|
||||
>**Note**<br>The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ This checklist outlines the recommended steps and items to consider when deployi
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Review the App-V supported configurations information to make sure selected client and server computers are supported for App-V feature installation.</p></td>
|
||||
<td align="left"><p>Review the App-V supported configurations information.</p></td>
|
||||
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
|
||||
@ -636,7 +636,7 @@ The following table describes the various script events and the context under wh
|
||||
|
||||
### Using multiple scripts on a single event trigger
|
||||
|
||||
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.
|
||||
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client.
|
||||
|
||||
**How to use multiple scripts on a single event trigger:**
|
||||
|
||||
@ -683,10 +683,10 @@ Using the following example file and table, modify the deployment or user config
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><code><Path>ScriptRunner.exe</Path></code></p></td>
|
||||
<td align="left"><p>The script launcher application that is installed as part of the App-V client installation.</p>
|
||||
<td align="left"><p>The script launcher application that is included in the App-V client.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>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:\Program Files\Microsoft Application Virtualization\Client folder.</p>
|
||||
<p>Although ScriptRunner.exe is included in 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:\Program Files\Microsoft Application Virtualization\Client folder.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ The topics in this section provide information and step-by-step procedures to he
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [App-V Deployment Checklist](appv-deployment-checklist.md)
|
||||
- [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
|
||||
@ -1,29 +1,4 @@
|
||||
---
|
||||
title: How to Install the App-V Client for Shared Content Store Mode (Windows 10)
|
||||
description: How to Install the App-V Client for Shared Content Store Mode
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client
|
||||
---
|
||||
|
||||
|
||||
# How to Install the App-V Client for Shared Content Store Mode
|
||||
|
||||
|
||||
Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode.
|
||||
|
||||
**Enable the App-V client for SCS mode**
|
||||
|
||||
1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
|
||||
|
||||
2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
@ -14,7 +14,7 @@ ms.prod: w10
|
||||
|
||||
An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group.
|
||||
|
||||
A connection group XML file defines the connection group that runs on the computer where you’ve installed the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
A connection group XML file defines the connection group for the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
|
||||
|
||||
This topic explains the following procedures:
|
||||
|
||||
|
||||
@ -209,7 +209,7 @@ If a converted package does not open after you convert it, it is also recommende
|
||||
|
||||
[How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
|
||||
|
||||
## Migrating the App-V server Server Full Infrastructure
|
||||
## Migrating the App-V Server Full Infrastructure
|
||||
|
||||
|
||||
There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
|
||||
@ -227,20 +227,20 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to the latest version of App-V 4.6.</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
|
||||
<td align="left"><p>Review prerequisites.</p></td>
|
||||
<td align="left"><p>[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Deploy App-V version of the client.</p></td>
|
||||
<td align="left"><p>Enable the App-V client.</p></td>
|
||||
<td align="left"><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Install App-V server server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V server Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
<td align="left"><p>Install App-V Server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Migrate existing packages.</p></td>
|
||||
<td align="left"><p>See Converting packages created using a prior version of App-V earlier in this topic.</p></td>
|
||||
<td align="left"><p>See [Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this topic.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@ -171,9 +171,9 @@ The following table displays the required steps to prepare the base image and th
|
||||
<tr class="odd">
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Install the App-V client version of the client.</p></li>
|
||||
<li><p>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).</p></li>
|
||||
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
|
||||
<li><p>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).</p></li>
|
||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
||||
<li><p>Pre-configure all user- and global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
||||
<li><p>Pre-configure all user- and global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
||||
@ -191,9 +191,9 @@ The following table displays the required steps to prepare the base image and th
|
||||
</ul></td>
|
||||
<td align="left"><p></p>
|
||||
<ul>
|
||||
<li><p>Install the App-V client version of the client.</p></li>
|
||||
<li><p>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).</p></li>
|
||||
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
|
||||
<li><p>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).</p></li>
|
||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
||||
<li><p>Pre-configure all global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
||||
<li><p>Pre-configure all global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
||||
@ -225,8 +225,7 @@ The following table displays the required steps to prepare the base image and th
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Shared Content Store (SCS) Mode</p>
|
||||
<ul>
|
||||
<li><p>Configurable in PowerShell using <strong>Set- AppvClientConfiguration</strong> –<strong>SharedContentStoreMode</strong>, or</p></li>
|
||||
<li><p>During installation of the App-V client.</p></li>
|
||||
<li><p>Configurable in Windows PowerShell with `Set-AppvClientConfiguration -SharedContentStoreMode 1`<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).</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p>When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).</p>
|
||||
<p>This helps to conserve local storage and minimize disk I/O per second (IOPS).</p></td>
|
||||
|
||||
@ -41,7 +41,7 @@ This checklist can be used to help you plan for preparing your organization for
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Plan for App-V 1.0 Deployment Prerequisites and prepare your computing environment.</p></td>
|
||||
<td align="left"><p>Plan for App-V deployment prerequisites and prepare your computing environment.</p></td>
|
||||
<td align="left"><p>[App-V Prerequisites](appv-prerequisites.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
@ -65,8 +65,8 @@ This checklist can be used to help you plan for preparing your organization for
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>Plan for running App-V clients using in shared content store mode.</p></td>
|
||||
<td align="left"><p>[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)</p></td>
|
||||
<td align="left"><p>Decide whether to configure App-V clients in Shared Content Store mode.</p></td>
|
||||
<td align="left"><p>[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -21,7 +21,7 @@ Use this information to plan how to deploy App-V so that it does not disrupt you
|
||||
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
This section describes the minimum hardware and software requirements necessary for App-V client, sequencer and server feature installations. Additionally, associated feature planning information is also displayed.
|
||||
This section describes the minimum hardware and software requirements and other planning information for the App-V sequencer and App-V server components.
|
||||
|
||||
- [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
|
||||
|
||||
@ -54,11 +54,11 @@ Review the following for more information about configuring IIS and Network Load
|
||||
|
||||
## <a href="" id="bkmk-clusterscsmode"></a>Support for clustered file servers when running SCS mode
|
||||
|
||||
Running App-V Server in Share Content Store (SCS) mode with clustered file servers is supported.
|
||||
Running App-V Server in Shared Content Store (SCS) mode with clustered file servers is supported.
|
||||
|
||||
The following steps can be used to enable this configuration:
|
||||
|
||||
- Configure App-V to run in client SCS mode. For more information about configuring App-V SCS mode, see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
|
||||
- Configure the App-V client to run in Shared Content Store mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
||||
|
||||
- Configure the file server cluster, configured in either the scale out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.
|
||||
|
||||
|
||||
@ -66,4 +66,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
- [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
@ -38,15 +38,15 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
|
||||
|
||||
|
||||
4. After importing the App-V PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample PowerShell cmdlet enables App-V reporting:
|
||||
4. After importing the App-V Windows PowerShell module using `Import-Module AppvClient` as administrator, enable App-V client reporting. This sample Windows PowerShell command enables App-V reporting:
|
||||
|
||||
``` syntax
|
||||
Set-AppvClientConfiguration –reportingserverurl <url>:<port> -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
|
||||
Set-AppvClientConfiguration -ReportingServerURL <url>:<port> -ReportingEnabled 1 -ReportingStartTime <0-23> -ReportingRandomDelay <#min>
|
||||
```
|
||||
|
||||
To immediately send App-V report data, run `Send-AppvClientReport` on the App-V client.
|
||||
|
||||
For more information about installing the App-V client with reporting enabled see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
For more information about configuring reporting on the App-V client, see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
|
||||
|
||||
5. After the reporting server receives the data from the App-V client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server and then a notification is sent to the App-V client.
|
||||
|
||||
@ -102,9 +102,9 @@ The following table displays answers to common questions about App-V reporting
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Can reporting be scheduled?</p></td>
|
||||
<td align="left"><p>Yes. Besides manually sending reporting using PowerShell Cmdlets (<strong>Send-AppvClientReport</strong>), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:</p>
|
||||
<td align="left"><p>Yes. Besides manually sending reporting using Windows PowerShell cmdlets (<strong>Send-AppvClientReport</strong>), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:</p>
|
||||
<ol>
|
||||
<li><p>Using PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
|
||||
<li><p>Using Windows PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
|
||||
<p>Set-AppvClientConfiguration -ReportingEnabled 1 - ReportingServerURL http://any.com/appv-reporting</p>
|
||||
<p></p>
|
||||
<p>For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: <strong>ReportingEnabled</strong>, <strong>ReportingServerURL</strong>, <strong>ReportingDataCacheLimit</strong>, <strong>ReportingDataBlockSize</strong>, <strong>ReportingStartTime</strong>, <strong>ReportingRandomDelay</strong>, <strong>ReportingInterval</strong>.</p>
|
||||
@ -112,7 +112,7 @@ The following table displays answers to common questions about App-V reporting
|
||||
<li><p>By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Group Policy settings override local settings configured using PowerShell.</p>
|
||||
<p>Group Policy settings override local settings configured using Windows PowerShell.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -127,14 +127,14 @@ The following table displays answers to common questions about App-V reporting
|
||||
## <a href="" id="---------app-v-client-reporting"></a> App-V Client Reporting
|
||||
|
||||
|
||||
To use App-V reporting you must enable and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using PowerShell.
|
||||
To use App-V reporting you must enable and configure the App-V client. To configure reporting on the client, use the Windows PowerShell cmdlet **Set-AppVClientConfiguration**, or the Group Policy **ADMX Template**. For more information about the Windows PowerShell cmdlets, see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of Windows PowerShell commands for configuring App-V client reporting.
|
||||
|
||||
### Configuring App-V Client reporting using PowerShell
|
||||
### Configuring App-V Client reporting using Windows PowerShell
|
||||
|
||||
The following examples show how PowerShell parameters can configure the reporting features of the App-V client.
|
||||
The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
|
||||
|
||||
**Note**
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
|
||||
|
||||
|
||||
|
||||
@ -148,9 +148,7 @@ The following configuration task can also be configured using Group Policy setti
|
||||
Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
|
||||
```
|
||||
|
||||
`-ReportingInterval 1 -ReportingRandomDelay 30`
|
||||
|
||||
This example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
|
||||
The preceding example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
|
||||
|
||||
**To limit the size of the data cache on the client**:
|
||||
|
||||
@ -238,7 +236,7 @@ You can configure the computer that is running the App-V client to automatically
|
||||
|
||||
- ReportingRandomDelay
|
||||
|
||||
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
|
||||
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following Windows PowerShell cmdlet:
|
||||
|
||||
`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
|
||||
|
||||
|
||||
@ -105,7 +105,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in **Comments** and **Descriptions**.
|
||||
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
15. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory where the package was created.
|
||||
@ -210,8 +210,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
|
||||
|
||||
Reference in New Issue
Block a user