How to Deploy the Client
Updated: November 1, 2012
Applies To: Application Virtualization 5.0
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.
Running the App-V 5.0 client on computers running App-V 4.6 SP1 or prior versions is not supported. Additionally, installing the client on a computer that runs Windows Server is not supported.
Important |
|---|
| The computer on which you plan to install the App-V 5.0 client must be running Microsoft .NET 4 Framework (Full) and Microsoft KB 2533623, and PowerShell 3.0. Otherwise, the installation will fail. |
To install the App-V 5.0 client
-
Copy the App-V 5.0 client installation files to the computer on which it will be installed. To install the standard version of the client, double-click appv_client_setup.exe and click Install. To install the Remote Desktop Services version of the client, double-click appv_client_setup_rds.exe and click Install. Before the installation begins, the installer will evaluate the computer for any missing App-V 5.0 Prerequisites.
-
On the Software License Terms page, review the license terms. To accept the license terms, select I accept the license terms. Click Next.
-
On the Use Microsoft Update to help keep your computer secure and up-to-date page, to enable Microsoft updates, select Use Microsoft Update when I check for updates (recommended). To disable Microsoft updates, select I don’t want to use Microsoft Update. Click Next.
-
On the Customer Experience Improvement Program page, to participate in the program, select Join the Customer Experience Improvement Program. This will allow information to be collected about how you use App-V 5.0. If you don’t want to participate in the program, select I don’t want to join the program at this time. Click Install.
-
On the Setup completed successfully page, click Close. After you complete the installation there will be multiple entries in Programs for the App-V 5.0 client. There will be an instance for the associated exe, .msi, and for the language pack. Only the .exe entry can be uninstalled.
Note When you uninstall the App-V 5.0 client by using Programs / Uninstall a program, all virtualized packages will also be removed.
Troubleshoot the App-V 5.0 client installation
-
For more information about how to troubleshoot the client installation, you can view 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 using a script
-
To use a script to install the App-V 5.0 client, use the following parameters with appv_client_setup.exe. When you install the client using an .msi file, if any prerequisites are missing, the installation will fail.
Note The client Windows Installer (.msi) supports the same set of switches except for the /LOG parameter. /INSTALLDIR
Specifies the installation directory. Example usage: /INSTALLDIR=C:\Program Files\AppV Client
/CEIPOPTIN
Enables participation in the Customer Experience Improvement Program. Example usage: /CEIPOPTIN=[0|1]
/MUOPTIN
Enables Microsoft Update. Example usage: /MUOPTIN=[0|1]
/PACKAGEINSTALLATIONROOT
Specifies the directory in which to install all new applications and updates. Example usage: /PACKAGEINSTALLATIONROOT='C:\App-V Packages'
/PACKAGESOURCEROOT
Overrides the source location for downloading package content. Example usage: /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: /AUTOLOAD=[0|1|2]
/SHAREDCONTENTSTOREMODE
Specifies that streamed package contents will be not be saved to the local hard disk. Example usage: /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: /MIGRATIONMODE=[0|1]
/ENABLEPACKAGESCRIPTS
Enables the scripts that are defined in the package manifest file or configuration files that should run. Example usage: /ENABLEPACKAGESCRIPTS=[0|1]
/ROAMINGREGISTRYEXCLUSIONS
Specifies the registry paths that will not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\classes;software\clients
/ROAMINGFILEEXCLUSIONS
Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS 'desktop;my pictures'
/S[1-5]PUBLISHINGSERVERNAME
Displays the name of the publishing server. Example usage: /S2PUBLISHINGSERVERNAME=MyPublishingServer
/S[1-5]PUBLISHINGSERVERURL
Displays the URL of the publishing server. Example usage: /S2PUBLISHINGSERVERURL=\\pubserver
/S[1-5]GLOBALREFRESHENABLED -
Enables a global publishing refresh. Example usage: /S2GLOBALREFRESHENABLED=[0|1]
/S[1-5]GLOBALREFRESHONLOGON
Initiates a global publishing refresh when a user logs on. Example usage: /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: /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: /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: /S2USERREFRESHINTERVALUNIT=[0|1]
/Log
Specifies a location where the log information is saved. The default location is %Temp%. Example usage: /log C:\logs\log.log
/q
Specifies an unattended installation.
/REPAIR
Repairs a previous client installation.
/NORESTART
Disallows the computer to restart after the client installation.
/UNINSTALL
Uninstalls the client.
/ACCEPTEULA
Accepts the license agreement. This is required for an unattended installation. Example usage: /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: /LAYOUTDIR=”C:\Application Virtualization Client”.
/?, /h, /help
Requests help about the previous installation parameters.
To install the App-V 5.0 client Windows Installer (.msi) file
-
Before you start this procedure, you should ensure that all the target computers have been configured with the App-V 5.0 Prerequisites. If any of the prerequisites are not met the installation will fail.
Note You should also 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. Deploy one of the following Windows Installer files to the target computer. The Windows Installer file you specify must match the configuration of the target computer.
-
If the target computer is running a 32-bit Microsoft Windows operating system, deploy the appv_client_MSI_x86.msi.
-
If the target computer is running a 64-bit Microsoft Windows operating system, deploy the appv_client_MSI_x64.msi.
-
If you are deploying the App-V 5.0 Remote Desktop Services client, deploy the appv_client_rds_MSI_x64.msi.
You must also specify and deploy an associated language pack. Select the appropriate language pack .msi, based on the desired set of languages required for the target computer:
-
If the target computer is running a 32-bit operating system, deploy the appv_client_LP_xxxx_ x86.msi.
-
If the target computer is running a 64-bit operating system, deploy the appv_client_LP_xxxx_ x64.msi.
Note Where xxxx refers to the target locale of the language pack. 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 only deploy the language pack that matches the operating system running on the target computer. To deploy additional language packs on a target computer, you should use the preceding To install the App-V 5.0 client Windows Installer (.msi) file procedure to deploy the additional language packs (.msi).
-
If the target computer is running a 32-bit Microsoft Windows operating system, deploy the appv_client_MSI_x86.msi.
-
You must also specify and deploy an associated language pack. Select the appropriate language pack .msi, based on the desired set of languages required for the target computer:
-
If the target computer is running a 32-bit operating system, deploy the appv_client_LP_xxxx_ x86.msi.
-
If the target computer is running a 64-bit operating system, deploy the appv_client_LP_xxxx_ x64.msi.
Note Where xxxx refers to the target locale of the language pack. 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 only deploy the language pack that matches the operating system running on the target computer. To deploy additional language packs on a target computer, you should use the preceding To install the App-V 5.0 client Windows Installer (.msi) file procedure to deploy the additional language packs (.msi).
-
If the target computer is running a 32-bit operating system, deploy the appv_client_LP_xxxx_ x86.msi.
See Also
Tasks
How to Uninstall the App-V 5.0 ClientConcepts
About Client Configuration SettingsOther Resources
Deploying App-V 5.0-----
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.
-----
