Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 164

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 167

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 170

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 173

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 176

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 178

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 180

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 202

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 206

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 224

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 225

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 227

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/includes/class.layout.php on line 321

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 56

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 56

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 56

Warning: Creating default object from empty value in /home/content/84/11844684/html/wp-content/themes/platform/admin/class.options.metapanel.php on line 49
App-V 5.0 Client Deployment in System Center Configuration Manager 2012 | Trailing Reboot

This guide discusses packaging the App-V 5.0 client for use on Windows 7 64 bit SP1, Windows Server 2008 SP2 64bit & Windows Server 2008 R2 SP1 64 bit Operating Systems.

First off, if you’re looking to test App-V 5.0 you’ll need to have at minimum SP1 of ConfigMgr 2012 since the App-V 5.0 client requires Powershell 3.0

Speaking of requirements, lets take a look at the prerequisites for installing the App-V 5.0 client:

*The app-v client installer will take care of these.

The first order of business is to prepare the prerequisites.

 

.NET Framework 4.0

Download the install code and create a script installer.

1. In Software Library, Applications, Create Application. Choose to manually specify the application information. Click next.

1_appv

2. Enter the application information and click next.

 2_appv

3. Enter Application Catalog details and click next

3__appv

 4. At Deployment Types, click Add.

5. Choose Script Installer and click next.

4_appv

6. Name the deployment type and click next.

5_appv

7. Use the following install and uninstall command line options, click next.

6__appv

 8. For Detection Method use the registry key HKLM/Software/Microsoft/NET Framework Setup/NDP/v4/Full and the registry value “Install” with a Data Type “Integer”. Click OK, and next.

 7__appv

9. Choose whether to install for user or system and click next.

 8_appv

10. Click Next, accepting defaults through the remainder of the deployment type wizard and close.

11. Click Next, accepting defaults through the remainder of the create application wizard and close.

 

Windows Management Framework 3.0

 Download the WMF 3.0 install code into a shared location before beginning the application build.

1. Create a new application, choose manually specify the application information and click next.

 9_appv

 2. Specify the application information and click next.

 10_appv

3. Enter Application Catalog information and click next.

4. At the deployment types window, click Add. Choose script installer and click next.

 11_appv

5. Specify a name for the deployment type and click next.

 12_appv

6. Specify the content location and install/uninstall parameters. Click Next.

For the installation use the following

Install: c:\windows\system32\wusa.exe “Windows6.1-KB2506143-x64.msu” /quiet /norestart

Uninstall: c:\windows\system32\wusa.exe /uninstall “Windows6.1-KB2506143-x64.msu”

 

I chose to place these two command line install options inside a batch script:

13__appv

7. Check the “Use a custom script to detect the presence of this deployment type” radio button.

8. Click Edit and choose script type Powershell. Copy and paste the following code into content area:

 $osresult = $null 

$os = (Get-WmiObject Win32_OperatingSystem).Name
if ($os -like “*Windows 8*”) {$osresult = “True”}
if ($os -like “*Server 2012*”) {$osresult = “True”}
$hfchk = Get-WmiObject -Query “select HotFixID from Win32_QuickFixEngineering where HotFixID like ‘KB2506143′” | foreach-object{Write-Host $_.HotfixID}
$osresult

 9. Click OK, and then next. Choose user experience settings and click next.

 14_appv

10. At the requirements screen. Add a device category with the condition OS and an operator: one of, and select Windows 7 SP1 64bit and Server 2008 SP2 64bit and Server 2008 R2 SP1 64bit. These are the only supported OS versions that Windows Management Framework 3.0 will install too. Click OK twice.

 15_appv

11. Click through the rest of the create deployment type wizard accepting defaults. Click Close when prompted.

12. Click through the remainder of the Create Application Wizard, accepting defaults. Click close when prompted.

 

App-V 5.0 Client Package

Download the MDOP 2012 suite and extract the App-V client folder and executables to a shared location.

1. In Software Library, Applications. Create a new application. Choose manually specify and click next.

16__appv

 2. Specify application information and click next.

 17_appv

 3. Enter Application Catalog information and click next.

4. At the deployment types window, choose Add. Choose script installer and click next.

18_appv

5. Enter Deployment Type information and click next.

19_appv

6. Enter your content location and the following install and uninstall commands. Click next.

20_appv

7. Click Add Clause, type Windows installer and the following product code for the 64 bit App-V Client.

{7DAB7C80-5E5A-4924-8F9F-B9C2BE53DFF7}

Click OK, and next.

 21_appv

 8. At the user experience. Choose your install behavior and click next.

9. At the requirements page, choose Add. Category device, Condition Operating System, Operator One Of. the value should be Windows 7 64bit (all)

22_appv

 10. Click next

11. At the dependencies page add .NET Framework and WMF 3.0 as separate dependency groups.

 23__appv

 24_appv

 *The dependencies must be in separate groups in order to have the “AND” operation take place when App-V Client is installed. If you add .NET and WMF as a single group they will use an OR operation.

25_appv

 12. Click next through the remainder of the deployment type wizard and click close when prompted.

13. Click next through the remainder of the create application wizard and click close when prompted.

14. Right click on your newly created App-V package and click view relationships / dependency

26_appv

 15. You should observe the following

 27_appv

16. Lastly, highlight your WMF 3.0 package, right click and go to properties.

17. Click the deployment tab. Highlight the deployment you created and click edit

18. Go to the dependency tab and add a dependency for .NET 4.0

 28_appv

 This is done to ensure that .NET Framework 4.0 installs first when deploying the App-V  Client. WMF 3.0 requires .NET 4.0 in order to run. I had issues when testing the App-V client deployment where WMF would try to install first.

19 .Click OK twice.

 

Deploy App-V Client

Wow, that was a lot of work just to deploy a simple App-V client but we are finally ready to test. Rest assured, your hard work will pay off when you never have to install this version of the client manually again.

Deploy the App-V client to a collection and log into your client to observe the installation in Software Center:

29_appv

 I would recommend testing each of WMF 3.0, and .NET 4.0 separately before trying the App-V Client package. This way if there are any issues you are looking at one application instead of 3.

 

As always, the logs are your best friend for troubleshooting.

Helpful logs :

AppEnforce.log

AppDiscovery.log

30_appv

Leave a Reply

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