deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 02:13:43 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
Files
c08231e70fd97426c6919adc63ebe39b37b9742f
windows-itpro-docs/mdop/appv-v5/how-to-deploy-the-app-v-client-gb18030.md
Nicole Turner faf3d0006e Update how-to-deploy-the-app-v-client-gb18030.md 
Removed table formatting and added L2 headings, fixes https://github.com/MicrosoftDocs/windows-itpro-docs/issues/2036
2019-06-18 15:11:48 +02:00

174 lines
22 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: How to Deploy the App-V Client
description: How to Deploy the App-V Client
ms.author: dansimp
author: dansimp
ms.assetid: 9c4e67ae-ddaf-4e23-8c16-72d029a74a27
ms.reviewer:
manager: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 11/05/2018
---
# How to Deploy the App-V Client
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.0 client and Remote Desktop Services client. You must install the version of the client that matches the operating system of the target computer.
<a href="" id="bkmk-clt-install-prereqs"></a>**What to do before you start**
1. Review and install the software prerequisites:
Install the prerequisite software that corresponds to the version of App-V that you are installing:
- [About App-V 5.0 SP3](about-app-v-50-sp3.md)
- App-V 5.0 SP1 and App-V 5.0 SP2 – no new prerequisites in these versions
- [App-V 5.0 Prerequisites](app-v-50-prerequisites.md)
2. Review the client coexistence and unsupported scenarios, as applicable to your installation:
| | |
|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
| Deploying coexisting App-V clients | [Planning for the App-V 5.0 Sequencer and Client Deployment](planning-for-the-app-v-50-sequencer-and-client-deployment.md) |
| Unsupported or limited installation scenarios | [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md) |
---
3. Review the locations for client registry, log, and troubleshooting information:
#### Client registry information
<ul><li>By default, after you install the App-V 5.0 client, the client information is stored in the registry in the following registry key:<p><p><code>HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\APPV\CLIENT</code></li><li>When you deploy a virtualized package to a computer that is running the App-V client, the associated package data is stored in the following location:<p><p><code>C:\ProgramData\App-V</code><p><p>However, you can reconfigure this location with the following registry key:<p><p><code>HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\SOFTWARE\MICROSOFT\APPV\CLIENT\STREAMING\PACKAGEINSTALLATIONROOT</code></li></ul>
#### Client log files
<ul><li>For log file information that is associated with the App-V 5.0 Client, search in the following log:<p><p><code>Event logs/Applications and Services Logs/Microsoft/AppV</code></li><li>In App-V 5.0 SP3, some logs have been consolidated and moved to the following location:<p><p><code>Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog</code><p><p>For a list of the moved logs, see [About App-V 5.0 SP3](about-app-v-50-sp3.md#bkmk-event-logs-moved).</li><li>Packages that are currently stored on computers that run the App-V 5.0 Client are saved to the following location:<p><p><code>C:\ProgramData\App-V\<<em>package id</em>>\<<em>version id</em>></code></li></ul>
#### Client installation troubleshooting information
- See the error log in the **%temp%** folder.
- To review the log files, click **Start**, type **%temp%**, and then look for the **appv_ log**.
## To install the App-V 5.0 Client
1. Copy the App-V 5.0 client installation file to the computer on which it will be installed.<p><p>Choose from the following client types:
| Client type | File to use |
|-----------------------------------------------|-------------------------------|
| Standard version of the client | **appv_client_setup.exe** |
| Remote Desktop Services version of the client | **appv_client_setup_rds.exe** |
---
2. Double-click the installation file, and click **Install**. Before the installation begins, the installer checks the computer for any missing [App-V 5.0 Prerequisites](app-v-50-prerequisites.md).
3. Review and accept the Software License Terms, choose whether to use Microsoft Update and whether to participate in the Microsoft Customer Experience Improvement Program, and click **Install**.
4. On the **Setup completed successfully** page, click **Close**.
The installation creates the following entries for the App-V client in **Programs**:
- **.exe**
- **.msi**
- **language pack**
>[!NOTE]
>After the installation, only the .exe file can be uninstalled.
## To install the App-V 5.0 client using a script
1. Install all of the required prerequisite software on the target computers. See [What to do before you start](#bkmk-clt-install-prereqs). If you install the client by using an .msi file, the installation will fail if any prerequisites are missing.
2. To use a script to install the App-V 5.0 client, use the following parameters with **appv\_client\_setup.exe**.
>[!NOTE]
>The client Windows Installer (.msi) supports the same set of switches, except for the **/LOG** parameter.
| | |
|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| /INSTALLDIR | Specifies the installation directory. Example usage:<p><p>**/INSTALLDIR=C:\Program Files\AppV Client** |
| /CEIPOPTIN | Enables participation in the Customer Experience Improvement Program. Example usage:<p><p>**/CEIPOPTIN=[0\|1\]** |
| /MUOPTIN | Enables Microsoft Update. Example usage:<p><p>**/MUOPTIN=[0\|1\]** |
| /PACKAGEINSTALLATIONROOT | Specifies the directory in which to install all new applications and updates. Example usage: <p><p>**/PACKAGEINSTALLATIONROOT='C:\App-V Packages'** |
| /PACKAGESOURCEROOT | Overrides the source location for downloading package content. Example usage:<p><p>**/PACKAGESOURCEROOT='<http://packageStore>'** |
| /AUTOLOAD | Specifies how new packages will be loaded by App-V 5.0 on a specific computer. The following options are enabled: [1]; automatically load all packages [2]; or automatically load no packages [0]. Example usage:<p><p>**/AUTOLOAD=[0\|1\|2\]** |
| /SHAREDCONTENTSTOREMODE | Specifies that streamed package contents will be not be saved to the local hard disk. Example usage: <p><p>**/SHAREDCONTENTSTOREMODE=[0\|1\]** |
| /MIGRATIONMODE | Allows the App-V 5.0 client to modify the shortcuts and FTAs that are associated with the packages that are created with a previous version. Example usage:<p><p>**/MIGRATIONMODE=[0\|1\]** |
| /ENABLEPACKAGESCRIPTS | Enables the scripts that are defined in the package manifest file or configuration files that should run. Example usage:<p><p>**/ENABLEPACKAGESCRIPTS=[0\|1\]** |
| /ROAMINGREGISTRYEXCLUSIONS | Specifies the registry paths that will not roam with a user profile. Example usage:<p><p>**/ROAMINGREGISTRYEXCLUSIONS=software\classes;software\clients** |
| /ROAMINGFILEEXCLUSIONS | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: <p><p>**/ROAMINGFILEEXCLUSIONS 'desktop;my pictures'** |
| /S[1-5]PUBLISHINGSERVERNAME | Displays the name of the publishing server. Example usage:<p><p>**/S2PUBLISHINGSERVERNAME=MyPublishingServer** |
| /S[1-5]PUBLISHINGSERVERURL | Displays the URL of the publishing server. Example usage:<p><p>**/S2PUBLISHINGSERVERURL=\\pubserver** |
| /S[1-5]GLOBALREFRESHENABLED | Enables a global publishing refresh. Example usage:<p><p>**/S2GLOBALREFRESHENABLED=[0\|1\]** |
| /S[1-5]GLOBALREFRESHONLOGON | Initiates a global publishing refresh when a user logs on. Example usage:<p><p>**/S2LOGONREFRESH=[0\|1\]** |
| /S[1-5]GLOBALREFRESHINTERVAL | Specifies the publishing refresh interval, where **0** indicates do not periodically refresh. Example usage: **/S2PERIODICREFRESHINTERVAL=[0-744]** |
| /S[1-5]GLOBALREFRESHINTERVALUNIT | Specifies the interval unit (Hours[0], Days[1]). Example usage:<p><p>**/S2GLOBALREFRESHINTERVALUNIT=[0\|1\]** |
| /S[1-5]USERREFRESHENABLED | Enables user publishing refresh. Example usage: **/S2USERREFRESHENABLED=[0\|1\]** |
| /S[1-5]USERREFRESHONLOGON | Initiates a user publishing refresh when a user logs on. Example usage:<p><p>**/S2LOGONREFRESH=[0\|1\]** |
| /S[1-5]USERREFRESHINTERVAL | Specifies the publishing refresh interval, where **0** indicates do not periodically refresh. Example usage: **/S2PERIODICREFRESHINTERVAL=[0-744]** |
| /S[1-5]USERREFRESHINTERVALUNIT | Specifies the interval unit (Hours[0], Days[1]). Example usage:<p><p>**/S2USERREFRESHINTERVALUNIT=[0\|1\]** |
| /Log | Specifies a location where the log information is saved. The default location is %Temp%. Example usage:<p><p>**/log C:\logs\log.log** |
| /q | Specifies an unattended installation. |
| /REPAIR | Repairs a previous client installation. |
| /NORESTART | Prevents the computer from rebooting after the client installation.<p><p>The parameter prevents the end-user computer from rebooting after each update is installed and lets you schedule the reboot at your convenience. For example, you can install App-V 5.0 SPX and then install Hotfix Package Y without rebooting after the Service Pack installation. After the installation, you must reboot before you start using App-V. |
| /UNINSTALL | Uninstalls the client. |
| /ACCEPTEULA | Accepts the license agreement. This is required for an unattended installation. Example usage:<p><p>**/ACCEPTEULA** or **/ACCEPTEULA=1** |
| /LAYOUT | Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V 5.0. No value is expected. |
| /LAYOUTDIR | Specifies the layout directory. Requires a string value. Example usage:<p><p>**/LAYOUTDIR=”C:\Application Virtualization Client”** |
| /?, /h, /help | Requests help about the previous installation parameters. |
---
## To install the App-V 5.0 client by using the Windows Installer (.msi) file
1. Install the required prerequisites on the target computers. See [What to do before you start](#bkmk-clt-install-prereqs). If any prerequisites are not met, the installation will fail.
2. Ensure that the target computers do not have any pending restarts before you install the client using the App-V 5.0 Windows Installer (.msi) files. The Windows Installer files do not flag a pending restart.
3. Deploy one of the following Windows Installer files to the target computer. The file that you specify must match the configuration of the target computer.
| Type of deployment | Deploy this file |
|-----------------------------------------------------------------|-----------------------------|
| Computer is running a 32-bit Microsoft Windows operating system | appv_client_MSI_x86.msi |
| Computer is running a 64-bit Microsoft Windows operating system | appv_client_MSI_x64.msi |
| You are deploying the App-V 5.0 Remote Desktop Services client | appv_client_rds_MSI_x64.msi |
---
4. Using the information in the following table, select the appropriate language pack **.msi** to install, based on the desired language for the target computer. The **xxxx** in the table refers to the target locale of the language pack.
**What to know before you start:**
- The language packs are common to both the standard App-V 5.0 client and the Remote Desktop Services version of the App-V 5.0 client.
- If you install the App-V 5.0 client using the **.exe**, the installer will deploy only the language pack that matches the operating system running on the target computer.
- To deploy additional language packs on a target computer, use the procedure **To install the App-V 5.0 client by using Windows Installer (.msi) file**.
| Type of deployment | Deploy this file |
|-----------------------------------------------------------------|------------------------------|
| Computer is running a 32-bit Microsoft Windows operating system | appv_client_LP_xxxx_ x86.msi |
| Computer is running a 64-bit Microsoft Windows operating system | appv_client_LP_xxxx_ x64.msi |
---
**Got a suggestion for App-V**? Add or vote on [suggestions](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). <p><p>**Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
## Related topics
[Deploying App-V 5.0](deploying-app-v-50.md)
[About Client Configuration Settings](about-client-configuration-settings.md)
[How to Uninstall the App-V 5.0 Client](how-to-uninstall-the-app-v-50-client.md)
Reference in New Issue View Git Blame Copy Permalink