Hi,
Currently we are using two types of applications and make also two applications for that.
F.e.
7-Zip-AppV and 7-Zip-Application.
*7-Zip-AppV contains 2 deployment types: 1 for AppV on Windows 7 (prereq W7), one for Windows Server (prereq os WKX).
We deploy this to a machine collection as well as a computer collection which both have a query to an ad group (AD GROUP "7-Zip-AppV" which has computer as well as user groups in it).
*7-Zip-Application contains also 2 deployment types: again 1 for Windows 7 and one for Windows Server
We deploy it again to 2 collection which are based upon AD group "7-Zip-Application", which has user as well as computer groups).
---
=> My question: what about having 1 application "7-Zip", have 4 deployment types: 2 for App-V, 2 for applications and possibly more in the future (Windows 10 etc)?
Think this is the most flexible way to use applications but wonder if there would be a scenario in which this could cause issues (dependency, supersedence). Better to figure that out now, so I'd appreciate your input on that. Do you use this setup (1 application
with different deployment types)? Why or why not?
J.
Jan Hoedt