mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
Merge pull request #118 from JanKeller1/8442312
Link fixes, plus a few fixes to typos
This commit is contained in:
Brian Lich
GitHub
commit
34ac2be8d2
@ -58,10 +58,9 @@
|
||||
##### [Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md)
|
||||
#### [App-V Planning Checklist](appv-planning-checklist.md)
|
||||
### [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)
|
||||
##### [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
##### [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)
|
||||
##### [How to Install the Sequencer](appv-install-the-sequencer.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)
|
||||
#### [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
@ -1059,7 +1059,7 @@ For situations where there is more than one application that could register the
|
||||
|
||||
The AppPath extension point supports calling App-V applications directly from the operating system. This is typically accomplished from the Run or Start Screen, depending on the operating system, which enables administrators to provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing.
|
||||
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths ? A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/).
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/).
|
||||
|
||||
### Virtual application
|
||||
|
||||
|
||||
@ -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)
|
||||
|
||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V Server (new installataion)
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
|
||||
>**Important**<br>If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -72,9 +72,9 @@ Sequencing Office 2010 is one of the main methods for creating an Office 2010 pa
|
||||
|
||||
Office 2010 App-V packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10, Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator:
|
||||
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](http://go.microsoft.com/fwlink/p/?LinkId=330677)
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](https://gallery.technet.microsoft.com/App-V-50-Package-a29410db)
|
||||
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](http://go.microsoft.com/fwlink/p/?LinkId=330678)
|
||||
- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](https://gallery.technet.microsoft.com/App-V-50-Package-e7ef536b)
|
||||
|
||||
For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md).
|
||||
|
||||
|
||||
@ -133,7 +133,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
<td align="left"><p>Use the <strong>ExcludeApp</strong> setting when you create the package by using the Office Deployment Tool.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.</p></li>
|
||||
<li><p>For more information, see [ExcludeApp element](http://technet.microsoft.com/library/jj219426.aspx#bkmk-excludeappelement).</p></li>
|
||||
<li><p>For more information, see [ExcludeApp element](https://technet.microsoft.com/library/jj219426.aspx#BKMK_ExcludeAppElement).</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -205,7 +205,7 @@ Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the
|
||||
|
||||
Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
|
||||
|
||||
1. Download the [Office Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778).
|
||||
1. Download the [Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778).
|
||||
|
||||
2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
|
||||
|
||||
@ -810,7 +810,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<tr class="odd">
|
||||
<td align="left"><p>How do I package and publish Visio 2013 and Project 2013 with Office?</p></td>
|
||||
<td align="left"><p>You must include Visio 2013 and Project 2013 in the same package with Office.</p>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](https://technet.microsoft.com/en-us/itpro/mdop/solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions#bkmk-pkg-pub-reqs).</p></td>
|
||||
<p>If you aren’t deploying Office, you can create a package that contains Visio and/or Project.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>How can I deploy Visio 2013 and Project 2013 to specific users?</p></td>
|
||||
@ -841,7 +841,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
<ol>
|
||||
<li><p>Create a package that contains Office, Visio, and Project.</p></li>
|
||||
<li><p>Deploy the package to all users.</p></li>
|
||||
<li><p>Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project.</p></li>
|
||||
<li><p>Use [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.</p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -858,13 +858,13 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
|
||||
**Office 2013 App-V Packages Additional Resources**
|
||||
|
||||
[Office Deployment Tool for Click-to-Run](http://go.microsoft.com/fwlink/p/?LinkID=330672)
|
||||
[Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778)
|
||||
|
||||
[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/en-us/kb/2772509)
|
||||
|
||||
**Office 2010 App-V Packages**
|
||||
|
||||
[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/en-us/download/details.aspx?id=38399)
|
||||
[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/download/details.aspx?id=38399)
|
||||
|
||||
[Known issues when you create or use an App-V 5.0 Office 2010 package](https://support.microsoft.com/en-us/kb/2828619)
|
||||
|
||||
@ -882,14 +882,4 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
|
||||
## 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).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ To deploy App-V packages with Microsoft System Center 2012 Configuration Manage
|
||||
## How to deploy virtualized packages using an ESD
|
||||
|
||||
|
||||
Describes the methods you can use to deploy App-V packages by using an ESD
|
||||
Describes the methods you can use to deploy App-V packages by using an ESD.
|
||||
|
||||
[How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
|
||||
@ -207,46 +207,9 @@ It is recommended that you use the App-V sequencer for converting critical appli
|
||||
|
||||
If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer.
|
||||
|
||||
|
||||
|
||||
[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 Clients
|
||||
|
||||
|
||||
The following table displays the recommended method for upgrading clients.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Task</th>
|
||||
<th align="left">More Information</th>
|
||||
</tr>
|
||||
</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>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
<td align="left"><p>[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
You must be running the latest version of App-V 4.6 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
@ -264,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>
|
||||
@ -60,13 +60,13 @@ This checklist can be used to help you plan for preparing your organization for
|
||||
<tr class="odd">
|
||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
||||
<td align="left"><p>If applicable, review the options and steps for migrating from a previous version of App-V.</p></td>
|
||||
<td align="left"><p>[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)</p></td>
|
||||
<td align="left"><p>[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</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)
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning to Deploy App-V for Windows 0
|
||||
# Planning to Deploy App-V for Windows 10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
@ -55,7 +55,7 @@ Describes the planning considerations for the App-V Client and for the Sequencer
|
||||
|
||||
Describes the recommended path for migrating from previous versions of App-V, while ensuring that existing server configurations, packages and clients continue to work in your new App-V environment.
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
|
||||
[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
|
||||
## Planning for using App-V with Office
|
||||
|
||||
|
||||
@ -13,10 +13,10 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The following is a known issue in Application Virtualization (App-V) for 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**
|
||||
The following are known issues in Application Virtualization (App-V) for 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
|
||||
|
||||
MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
|
||||
|
||||
**Workaround**:
|
||||
@ -41,6 +41,123 @@ MSI packages that were generated using an App-V sequencer from previous versions
|
||||
|
||||
By default, the path to the Windows SDK installation will be:<br>**C:\Program Files (x86)\Windows Kits\10**
|
||||
|
||||
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
|
||||
|
||||
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10. This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier.
|
||||
|
||||
**Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
|
||||
|
||||
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
|
||||
|
||||
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration.
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
|
||||
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration will be stored in each user’s profile and will be applied correctly.
|
||||
|
||||
- Create a custom deployment configuration file and apply it to the package on the client using the Add-AppvClientPackage cmdlet with the –DynamicDeploymentConfiguration parameter. See [About App-V Dynamic Configuration](appv-dynamic-configuration.md) for more information.
|
||||
|
||||
- Create a new package with the custom configuration using the App-V Sequencer.
|
||||
|
||||
## Server files not deleted after new App-V Server installation
|
||||
|
||||
If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files are not being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation.
|
||||
|
||||
**Workaround**: Delete this registry key before you start installing App-V:
|
||||
|
||||
Under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall, locate and delete the installation GUID key that contains the DWORD value "DisplayName" with value data "Microsoft Application Virtualization (App-V) Server". This is the only key that should be deleted.
|
||||
|
||||
## File type associations added manually are not saved correctly
|
||||
|
||||
File type associations added to an application package manually using the Shortcuts and FTAs tab at the end of the application upgrade wizard are not saved correctly. They will not be available to the App-V Client or to the Sequencer when updating the saved package again.
|
||||
|
||||
**Workaround**: To add a file type association, open the package for modification and run the update wizard. During the Installation step, add the new file type association through the operating system. The sequencer will detect the new association in the system registry and add it to the package’s virtual registry, where it will be available to the client.
|
||||
|
||||
## When streaming packages in Shared Content Store (SCS) mode to a client that is also managed with AppLocker, additional data is written to the local disk.
|
||||
|
||||
To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V Client to stream the contents of a package on demand. However, if AppLocker manages an application within the package, some data might be written to the client’s local disk that would not otherwise be written.
|
||||
|
||||
**Workaround**: None
|
||||
|
||||
## In the Management Console Add Package dialog box, the Browse button is not available when using Chrome or Firefox
|
||||
|
||||
On the Packages page of the Management Console, if you click **Add or Upgrade** in the lower-right corner, the **Add Package** dialog box appears. If you are accessing the Management Console using Chrome or Firefox as your browser, you will not be able to browse to the location of the package.
|
||||
|
||||
**Workaround**: Type or copy and paste the path to the package into the **Add Package** input field. If the Management Console has access to this path, you will be able to add the package. If the package is on a network share, you can browse to the location using File Explorer by doing these steps:
|
||||
|
||||
1. While pressing **Shift**, right-click on the package file
|
||||
|
||||
2. Select **Copy as path**
|
||||
|
||||
3. Paste the path into the **Add Package** dialog box input field
|
||||
|
||||
## <a href="" id="upgrading-app-v-management-server-to-5-1-sometimes-fails-with-the-message--a-database-error-occurred-"></a>Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
|
||||
|
||||
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”
|
||||
|
||||
**Workaround**: Run this command on your SQL database:
|
||||
|
||||
`ALTER TABLE AppVManagement.dbo.PackageGroupMembers ADD PackageOptional bit NOT NULL DEFAULT 0, VersionOptional bit NOT NULL DEFAULT 0`
|
||||
|
||||
where “AppVManagement” is the name of the database.
|
||||
|
||||
## Users cannot open a package in a user-published connection group if you add or remove an optional package
|
||||
|
||||
In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group.
|
||||
|
||||
**Workaround**: Have users log out and then log back in.
|
||||
|
||||
## Error message is erroneously displayed when the connection group is published only to the user
|
||||
|
||||
|
||||
When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.”
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
|
||||
- Publish all packages in a connection group.
|
||||
|
||||
The problem arises when the connection group being repaired has packages that are missing or not available to the user (that is, not published globally or to the user). However, the repair will work if all of the connection group’s packages are available, so ensure that all packages are published.
|
||||
|
||||
- Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-AppvClientConnectionGroup command.
|
||||
|
||||
Determine which packages are available to users and then run the Repair-AppvClientPackage command once for each package. Use PowerShell cmdlets to do the following:
|
||||
|
||||
1. Get all the packages in a connection group.
|
||||
|
||||
2. Check to see if each package is currently published.
|
||||
|
||||
3. If the package is currently published, run Repair-AppvClientPackage on that package.
|
||||
|
||||
## Icons not displayed properly in Sequencer
|
||||
|
||||
Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32.
|
||||
|
||||
**Workaround**: Only use icons that are 16x16 or 32x32.
|
||||
|
||||
## InsertVersionInfo.sql script no longer required for the Management Database
|
||||
|
||||
|
||||
The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
|
||||
|
||||
The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340).
|
||||
|
||||
**Important**
|
||||
**Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
|
||||
|
||||
|
||||
## Microsoft Visual Studio 2012 not supported
|
||||
|
||||
|
||||
App-V does not support Visual Studio 2012.
|
||||
|
||||
**Workaround**: None
|
||||
|
||||
## Application filename restrictions for App-V Sequencer
|
||||
|
||||
|
||||
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**Workaround**: Use a different filename
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -38,22 +38,26 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
|
||||
|
||||
|
||||
4. After importing the App-V Windows PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample Windows 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.
|
||||
|
||||
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
|
||||
|
||||
>**Note**
|
||||
By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache. If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
|
||||
|
||||
|
||||
|
||||
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
|
||||
### <a href="" id="-------------app-v-reporting-server-frequently-asked-questions"></a> App-V reporting server frequently asked questions
|
||||
|
||||
@ -98,10 +102,10 @@ 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 Windows PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
|
||||
<p>Set-AppvClientConfiguration -ReportingEnabled 1 - ReportingServerURL http://any.com/appv-reporting</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>
|
||||
<p></p></li>
|
||||
@ -123,44 +127,38 @@ 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** Windows 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 Windows 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 Windows PowerShell
|
||||
|
||||
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).
|
||||
|
||||
|
||||
|
||||
**To enable reporting and to initiate data collection on the computer running the App-V client**:
|
||||
|
||||
```syntax
|
||||
Set-AppVClientConfiguration –ReportingEnabled 1
|
||||
```
|
||||
`Set-AppVClientConfiguration –ReportingEnabled 1`
|
||||
|
||||
**To configure the client to automatically send data to a specific reporting server**:
|
||||
|
||||
``` syntax
|
||||
Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30 -ReportingInterval 1 -ReportingRandomDelay 30
|
||||
Set-AppVClientConfiguration -ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -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**:
|
||||
|
||||
```syntax
|
||||
Set-AppvClientConfiguration –ReportingDataCacheLimit 100
|
||||
```
|
||||
`Set-AppvClientConfiguration –ReportingDataCacheLimit 100`
|
||||
|
||||
Configures the maximum size of the reporting cache on the computer running the App-V client to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
|
||||
|
||||
**To configure the data block size transmitted across the network between the client and the server**:
|
||||
|
||||
```syntax
|
||||
Set-AppvClientConfiguration –ReportingDataBlockSize 10240
|
||||
```
|
||||
`Set-AppvClientConfiguration –ReportingDataBlockSize 10240`
|
||||
|
||||
Specifies the maximum data block that the client sends to 10240 MB.
|
||||
|
||||
@ -240,9 +238,7 @@ You can configure the computer that is running the App-V client to automatically
|
||||
|
||||
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:
|
||||
|
||||
```syntax
|
||||
Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess
|
||||
```
|
||||
`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
|
||||
|
||||
If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
|
||||
|
||||
|
||||
@ -31,9 +31,9 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa
|
||||
|
||||
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
|
||||
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (<http://go.microsoft.com/fwlink/p/?LinkId=28819>).
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/en-us/security/bb291012).
|
||||
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet (<http://go.microsoft.com/fwlink/p/?LinkId=30009>).
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://technet.microsoft.com/library/hh994572.aspx).
|
||||
|
||||
## Accounts and groups in App-V
|
||||
|
||||
|
||||
@ -53,11 +53,9 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!NOTE]
|
||||
> If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
|
||||
|
||||
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **Next**.
|
||||
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
@ -66,8 +64,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
|
||||
|
||||
|
||||
Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
|
||||
|
||||
8. On the **Installation** page, wait while the sequencer configures the virtualized application package.
|
||||
@ -76,8 +73,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
> [!NOTE]
|
||||
> To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
|
||||
|
||||
|
||||
Click **Next**.
|
||||
|
||||
10. On the **Installation Report** page, you can review information about the virtualized application package you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**.
|
||||
@ -109,9 +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.
|
||||
@ -179,9 +173,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**.
|
||||
|
||||
**To sequence a middleware application**
|
||||
@ -218,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.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user