Deploy App-V Package with ConfigMgr (Part1)

 

To recap, the instructions for creating a client to sequence App-V packages is here and sequencing Microsoft Edge, here.

The easiest method to deploy an App-V package via ConfigMgr is to treat it similar to an MSI Application deployment. The package is copied to CCMCache and Published 'C:\ProgramData\App-V' on the Client, shortcuts etc are automatically created. The downside of this is that every user will get the access to the package regardless. Publishing only to the user in hot-desk environment results in potential delays whilst the App-V package is either installed or streamed to the user.

To allow a targeted deployment to named users whilst removing the delay from the installation, MS Edge will be deployed to all the clients without publishing the Start Menu shortcuts. GPO Preferences will be used then create shortcuts for the approved users. 

Before deploying or testing any App-V package deployment from ConfigMgr ensure that App-V is enabled on the clients.

 

From Windows 10 1607 App-V is an in-built feature and not installed from the MDOP suit. To enable App-V run the following command from Powershell. This can be deployed as a script from ConfigMgr, not sure the following instructions will help.

Enable-Appv

Copy the MS Edge App-V package to the content source share of the ConfigMgr Server, mines SMSSource.

I've renamed the folder package root folder 'Microsoft Edge Browser.1.3' as I've other Edge deployments.

Open 'Powershell_ise', 2 scripts are needed, 'InstallEdge.ps1' and 'RemoveEdge.ps1'.

InstallEdge.ps1

Add-AppvClientPackage -Path '.\Microsoft Edge Browser.appv' -DynamicDeploymentConfiguration '.\Microsoft Edge Browser_DeploymentConfig.xml' | Publish-AppvClientPackage -Global | Mount-AppvClientPackage

RemoveEdge.ps1

#Open Microsoft Edge Browser_DeploymentConfig.xml for PackageID
Get-AppvClientPackage -all -PackageId '87266c50-0da9-4bde-9b46-24ad96d6404b' |  Remove-AppvClientPackage 

Save both scripts with the MS Edge Package

Edit 'Microsoft Edge Browser_DeploymentConfig.xml', amending the '<Shortcuts Enabled="true">' to 'false'

From 'Software Library' in the ConfigMgr Console, right click and 'Create Application'

Add the package information

Select 'Manually specify the application infromation'

Select 'Manually specify the application infromation'

Click 'Add' 

Select 'Script Installer' as Type and 'Manually specify the deployment type information'

Select 'Manually specify the application infromation'

Specify the following information, the unc path to the App-V package and the powershell commands.

\\ConfigMgr01\SMSSource\AppV\Microsoft Edge Browser.1.3\

UNC Path

Installation Program:

powershell.exe -executionpolicy bypass -file InstallEdge.ps1

powershell.exe -executionpolicy bypass -file RemoveEdge.ps1

Uninstall Program

Select 'Use a custom script to detect the presence of this type' and click 'Edit...'

Select 'Powershell' from 'Script type:'

Add the following to test for the path of the App-V package.

$tp = test-path "C:\ProgramData\App-V\87266c50-0da9-4bde-9b46-24ad96d6404b\8F2E3D0D-1FB0-4ECD-8FD0-36ABC03FCAFA"

if ($tp -eq $true){write-output "true"}

Select  Windows 10 x64' only

Set the 'User Experience' to 'System' and 'Hidden'

Click past the 'Dependencies'

Complete the 'Deployment Type' settings

Click past 'Deployment Types' 

Complete the 'Application Wizard' by reviewing the following windows and closing.

Next up will be the Application Deployment and GPO Preferences (here)