App V v5 Client Deployment within SCCM 2012

AppV v5 Sp1 is the newest release of Microsoft’s Application virtualization software.

 

The below will walk through the needed prerequisites for installing the AppV Client and also screen shot the needed steps to deploy AppV 5 within SCCM.

 

Microsoft .NET Framework 4 (Full Package) (http://www.microsoft.com/en-us/download/details.aspx?id=17718)

 

Windows PowerShell 3.0 (http://www.microsoft.com/en-us/download/details.aspx?id=34595)

 

NOTE Installing PowerShell 3.0 requires a restart.

 

For computers running the 32-bit version of Microsoft Windows 7 or Microsoft Windows 7 SP1, download and install KB2533623 (http://go.microsoft.com/fwlink/?LinkId=286100)

 

For computers running the 64-bit version of Microsoft Windows 7 or Microsoft Windows 7 SP1, download and install KB2533623 (http://go.microsoft.com/fwlink/?LinkId=286101)

 

Also the client installer will detect if it is necessary to install the following prerequisites, and it will do so accordingly:

 

The Microsoft Visual C++ 2010 Redistributable(http://go.microsoft.com/fwlink/?LinkId=26999)

 

The Microsoft Visual C++ 2005 SP1 Redistributable

 

To sum up:

 

· .dotnet 4

· PowerShell v3

· Windows6.1-KB2533623-x86.msu (http://support.microsoft.com/kb/2533623)

 

Because of the need for 1-2 reboots (at the least for PowerShell) I highly recommend deploying the prereqs prior to deploying the AppV 5 client – Ideally adding the updates to your most current patch cycle.

 

clip_image002

 

Below is a TS for deploying the prereqs – but if you run this “as is” you will experience multiple reboots.

 

AppV 5 client TS AppV 5 client TS

 

clip_image004

 

clip_image006

 

clip_image008

 

For the Client install:

 

clip_image010

 

Setting up the package within SCCM requires some consideration.

 

1. Are you managing the client with App V IIS or SCCM 2012

 

Note the built in switches if you were managing the AppV Client with AppV IIS:

 

clip_image012

 

clip_image014

 

clip_image016

 

Note also that the AppV install file – appv_client_setup.exe allows for the MSI files to be “extracted” is you want to import the MSI for use within the SCCM “Application Model”

Refer to this blog:

 

http://blogs.technet.com/b/gladiatormsft/archive/2013/04/24/mdop-2013-embeds-app-v-msi-s-inside-of-exe-files.aspx

 

appv_client_setup.exe /Layout /LayoutDir="D:\temp"

 

Which extracts the following files:

 

clip_image018

 

For this example I am deploying the AppV Client EXE to be managed within SCCM 2012:

 

Using the Package/Program methodology

 

clip_image019

 

 

clip_image020

 

clip_image022

 

clip_image023

 

appv_client_setup.exe /q /ACCEPTEULA

 

clip_image024

 

clip_image025

 

After the above is done deploy the Program to a collection:

 

clip_image027

 

Ensure the package has been distributed to a Distribution Point:

 

clip_image029

 

Making is “available” so the advertisement shows up in Software center:

 

clip_image031

 

Next, Next, next

 

clip_image033

 

On the Client Machine:

 

clip_image035

 

clip_image037

 

Note the download location and all the needed files – including the “extracted” MSI’s (not needed for this example but I kept them in the Package folder for future deployments)

 

clip_image039

 

clip_image041

 

clip_image043

 

WORKING

 

clip_image045

 

Reasons the client will not install:

 

1. You have NOT installed all the Prereqs

2. You have NOT added the /ACCEPTEULA

Leave a Reply