top of page

Deploy App-V Package with ConfigMgr​ (Part 2)

This is the warning to everyone new to administering ConfigMgr. I've seen and heard many horror stories of accidental deployments destroying Enterprise environments. From deploying Windows Client to all Servers to deploying a new version of Office breaking all the Enterprise add-ins.

Never deploy anything to any collection without double, and triple-checking that the collection is correct. Right click on the target Collection and 'Update Membership', wait a few seconds and then 'Refresh' the Collection.

Don't ever update a Collection query whilst a Deployment is active against the Collection. 

That's the warnings done, now let's complete the deployment.

The initial deployment will be to a test client, which will be a direct member of a Collection.

From ConfigMgr Console, navigate to 'Assets and Compliance', 'Device Collections', then right click and 'Create Device Collection'

Add a meaningful name and filter to 'All Workstations' or something containing the test client

Click 'Add Rule' and then 'Direct Rule'

Click Next

In the value use the '%' as a wildcard to search for a client name

Complete the 'Create Device Collection Wizard

Now repeat the process for an 'UnInstall' collection.

Open the 2 Collections and confirm that the correct client is listed.

With the collections complete, the MS Edge App-V package can now be deployed.

Click on 'Software Library', right click on 'Edge Browser' application and 'Distribute Content'

Start the 'Distribute Content Wizard'

Click 'Add' and select either a DP or DP Group

Refresh the Application after a few moments and confirm that the 'Content Status' is green

Click on 'Software Library', right click on 'Edge Browser' application and 'Deploy'

Browse to the 'SW_AV_MS_Edge_Install' collection

Click next at the 'Content' page

Select 'Install' and 'Required', 

Go with the default for the 'Installation Deadline', 'As soon as possible after the available time'

Select 'Hide in Software Center and all notifications', the users are not to be aware of the installation.

Check the 'Software Installation' box.

Take the defaults for SCOM alerts

Complete the wizard and confirm deployment wizard completes successfully.

Now repeat, select 'Deploy' for the MS Edge Application, select 'SW_AV_MS_Edge_UnInstall' collection. 

Add the same client to the collection.

This time, select the 'Uninstall' action.

An installation deployment will take precedence over and uninstall, whilst an active installation deployment is set against the collection with that client the uninstall will not run.

Logon to the client, Control Panel, Configuration Manager, Actions tab and then 'Machine Policy Retrieval & Evaluation Cycle'

Initially the application will download to 'C:\Windows\CCMCache\', the Powershell script will then publish the the App-V package to 'C:\ProgramData\App-V\'

Run 'Get-AppvClientPackage' from powershell to confirm that the App-V package has correctly published.

No shortcuts will be created and the users will be unaware.

Its possible to browse further down App-V path to 'msedge.exe' and manually execute, MS Edge Browser will lunch

Finally 'Deploy' the App-V package to all Windows 10 X64 clients.

Next we'll create the GPO Preference, that will create Start Menu shortcuts to approved users. (here)

bottom of page