Hi,
To start with, let me explain how my App-V applications setup is, by example, f.e. Z-Zip.
Application naming:
--------------------------
Application 7-Zip 4.65 (1.0)
*Deployment types:
7-Zip 4.65 – W7 ‘requirement Windows 7
7-Zip 4.65 – WK8R2 ‘requirement Windows 2008 R2
Application 7-Zip 9.20 (1.0)
*Deployment types: ... ‘same as above => supersedence on “7-Zip 4.65 (1.0)”
Application 7-Zip 9.20 (2.0)
*Deployment types: ... ‘same as above => supersedence on “7-Zip 9.20 (1.0)”
User groups:
------------------
7-Zip-Install (query AD-group with users who should have 7-Zip) => install deploy of 7-Zip
7-Zip-Uninstall (query users who have 7-Zip installed, based upon a query on “7-Zip 4.65 (1.0”) minus collection “Z-Zip-Install”) => uninstall deploy of 7-Zip
Now this setup complicates the User group uninstall collection, since it contains the query of the application AND version (7-Zip 4.65 (1.0)). Iow, each time a new version comes, I’d need to change the uninstall query.
---
Then I read this:
https://softomaticca.wordpress.com/2014/07/18/deploy-a-revised-appv-package-in-a-snap-using-configmgr12-sccm2012/which makes me want to rethink my setup. But since I do have a lot of applications, I want to have the design right in one go.
So my question is: what’s the most flexible setup?
----------------------------------------------------------------
*Deploying applications without any version number, f.e. 7-Zip, then deployment types “7-Zip 4.65 (1.0)”,
“7-Zip 9.20 (1.0)”, “7-Zip 9.20 (2.0)”, giving the latest version the highest priority
But in this setup the enduser won’t see the new version number (only 7-Zip)
*Deploying, as the article mentions, f.e. 7-Zip 9.20, then deployment types “7-Zip 9.20 (1.0) – W7”, “7-Zip 9.20 (2.0) – W7” and giving version 2.0 a higher priority?
Using supersedence on application level for major updates (f.e. 4.65, 9.20 etc)
This looks the best option but then, each time a new version is released, I need to adapt my query for the uninstall collection.
Please advise.
J.
Jan Hoedt