MICROSOFT APP-V CLIENT 5.1 Preparation and Installation

Preparing for your App-V client distribution? Here is a quick run down of some things to consider for new installation and upgrades as well as installation steps.

 

 

Client Supported Configurations

Client system requirements

The following table lists the operating systems that are supported for the App-V 5.1 Client installation

Operating system Service pack System architecture
Microsoft Windows Server 2012 R2 64-bit
Microsoft Windows Server 2012 64-bit
Microsoft Windows Server 2008 R2 SP1 64-bit
Microsoft Windows 10 32-bit and 64-bit
Microsoft Windows 8.1 32-bit and 64-bit
Microsoft Windows 8 32-bit and 64-bit
Microsoft Windows 7 SP1 32-bit and 64-bit

 

The following App-V client installation scenarios are not supported, except as noted:

  • Computers that run Windows Server
  • Computers that run App-V 4.6 SP1 or earlier versions
  • The App-V 5.1 Remote Desktop services client is supported only for RDS-enabled servers
App-V client hardware requirements

The following list displays the supported hardware configuration for the App-V 5.1 client installation.

  • Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
  • RAM— 1 GB (32-bit) or 2 GB (64-bit)
  • Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
Remote Desktop Services client system requirements

The following table lists the operating systems that are supported for App-V 5.1 Remote Desktop Services (RDS) client installation.

 

Operating system Service Pack System architecture
Microsoft Windows Server 2012 R2 64-bit
Microsoft Windows Server 2012 64-bit
Microsoft Windows Server 2008 R2 SP1 64-bit

 

Remote Desktop Services client hardware requirements

 

App-V adds no additional requirements beyond those of Windows Server.

  • Processor—1.4 GHz or faster, 64-bit (x64) processor
  • RAM—2 GB RAM (64-bit)
  • Disk space—200 MB available hard disk space

Upgrading the Client to App-V 5.1

You can upgrade to App-V 5.1 directly from any of the following versions:

  • App-V 5.0
  • App-V 5.0 SP1
  • App-V 5.0 SP2
  • App-V 5.0 SP3

Packages and connection groups will continue to work with App-V 5.1 as they currently do

 

Client Pre-requisites

The following table indicates the software that is already installed for different operating systems.

Operating system Prerequisite description
Windows 10 All of the prerequisite software is already installed.
Windows 8.1 All of the prerequisite software is already installed.

Note
If you are running Windows 8, upgrade to Windows 8.1 before using App-V 5.1.
Windows Server 2012 The following prerequisite software is already installed:

  • Microsoft .NET Framework 4.5.1
  • Windows PowerShell 3.0
Note
Installing PowerShell 3.0 requires a restart.
Windows 7 The prerequisite software is not already installed. You must install it before you can install App-V.

 

What to know before installing the prerequisites:
  • Best practice: The computer that runs the Client should have the same hardware and software configurations as the computers that will run the virtual applications.
  • The sequencing process is resource intensive, so make sure that the computer that runs the Client has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Client.
Desktop Client and Remote Desktop Services Client Pre-requisites

Install the following prerequisite software for the App-V client.

Prerequisite Details
Microsoft .NET Framework 4.5.1 (Web Installer)
Windows PowerShell 3.0 Installing PowerShell 3.0 requires a restart.
KB2533623 Applies to Windows 7 only: Download and install the KB.
Visual C++ Redistributable Packages for Visual Studio 2013

 

Upgrading the Pre-requisites from App-V 5.0

App-V 5.0 Pre-Reqs App-V 5.1 Pre-Reqs Details
Microsoft.NET Framework 4 (Full Package) Microsoft .NET Framework 4.5.1 (Web Installer) Upgrade Required to .NET 4.5.1 version

Note: Before implementing change ensure business Natively installed and virtual applications dependant on version 4.0 are sociability tested with 4.5.1

Windows PowerShell 3.0 Windows PowerShell 3.0 No change required
KB2533623 KB2533623 No change required. Applies to Windows 7 only: Download and install the KB.
Visual C++ Redistributable Packages for Visual Studio 2013 Visual C++ Redistributable Packages for Visual Studio 2013 No change required.
The Microsoft Visual C++ 2010 Redistributable No change required
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) No change required

 

App-V 5.1 Co-existence with App-V 4.6

The 4.6 version of App-V has reached the end of life support stage. Although co-existence is still available, It is recommended that for existing 4.6 packages, you gradually or completely migrate them to the App-V 5.1 format. This can be achieved using the built app-v package converter for a majority of your application portfolio.

Improvements in the App-V package converter include being able to use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.

You can also use the –OSDsToIncludeInPackage parameter with the ConvertFrom-AppvLegacyPackage cmdlet to specify which .osd files’ information is converted and placed within the new package.

 

Client Installation steps

The App-V 5.1 client Installers are available in two formats

The App-V 5.1 client Installers are available in two formats

Client Type File Name
Standard version appv_client_setup.exe
Remote Desktop Services version appv_client_setup_rds.exe

 

After having reviewed that the pre-requisites exist on your chosen OS proceed with the following steps

 

Run the exe you will be presented with the first dialog to begin the installation. Click on Install link.

Next select I accept the license terms, and then click Next

The next option allows you to choose whether to opt for Microsoft Updates. It is recommended that Updates to the client are managed via WSUS/Group Policy or a third party software distribution system. Select your choice and then click Install.

The next dialogue asks you to choose to be involved in the “Customer Experience Improvement program”. Make your selection and click on Install.

If no errors appear during the installation the client will be ready for you to launch and start loading and publishing applications.

To verify your installation just check of the client entry in the “Programs and features” panel.

 

Advanced Install using command lines

Creating an unattended installation package is simplified by using supported command line parameters to answer the dialog prompts and configure the client with standalone or Publishing server connection settings. See the supported command – line settings below.

/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.
/UNINSTALL Uninstalls the client.
/ACCEPTEULA Accepts the license agreement. This is required for an unattended installation. Example usage: /ACCEPTEULA or /ACCEPTEULA=1.
/?, /h, /help Requests help about the previous installation parameters.

 

App-V 5.1 Visual C++ Redistributable Management

App-V 5.0 has been able to successfully virtualise Visual C++ Runtimes since the release of SP2. In the case of whether to manage redistributables separate to the virtualised package, that is to install them natively on the App-v client OS. There is no definitive rule to state the recommended management methodology. For the administrator looking for best practice recommendations and new to application virtualisation.

Natively installed on the Sequencer and Client –        Requires management of application client builds

–        Requires management of the applications client builds

–        Minimise potential SXS conflicts of Grouped Virtual apps with VisualC++ data running on clients with native instances of the same Visual C++ components.

–        Managed Visual runtimes allows you to easily transition or deploy Virtual Packages from one Windows OS to Another. Win7, 8, 10, server 2008, 2012 cutting down rework and testing.

–        Avoid mismatch of Visual C++ Components between Sequencer and Client.

Included with the Virtualised Applications –        Less management of application client builds

–        Less management of application client builds

–        In conjunction with heavy connection group usage of virtual apps a relaxed management approach of app components can potentially open up more instances of issues/conflicts to resolve as virtual application portfolios grow over time.

–        Incorporating Visual Runtimes into virtual packages still allows for easy package transition and deployment across different operating systems, so long as there is a consistent methodology applied to incorporating visual C++ components and other pre-requisites into virtual packages.

–        Higher chance of mismatch of runtimes between the sequencer and client.

 

Leave a Reply

Your email address will not be published. Required fields are marked *