Hi,
I would appreciate your input on a design question on App-V 5 on SCCM 2012 R2.
Where we are:
- We have Terminal Servers running with App-V 4.6 Clients for some years. The users on these Terminal Servers could only receive the App-v 4.6 packages (since the terminal server only had the App-V client)
- Some time ago we started the rollout of App-V 5.0 packages to Terminal servers via SCCM 2012 R2.
- In parallel we rolled out some App-V 5.0 clients to Windows 7 machines.
What’s happening:
- Users get App-V package meant for TS (licensed applications which should not end on clients) and they should not
What we want:
- deploy App-V packages (via SCCM) to W7 computers only, later we will deploy to users but for now our administration system doesn’t cover that
- select which App-V packages to deploy to Windows 10 (when it’s there)
- select which App-V packages to deploy to terminal servers (WKX)
- uninstall of users/computers not in collections anymore
ð TTo achieve this we would create different deployment types of an App-v package with each a prereq “W7, Windows 10, Windows terminal services”. Then also we would create an uninstall mechanism (like this http://blogs.technet.com/b/configmgrdogs/archive/2014/11/03/managing-app-v-deployments-in-configmgr-2012.aspx)
Guess that would work, but wonder if you would see any flaws/issuesin/with this setup?
Thanks for your input.
J.
Jan Hoedt
Update: then also I wonder the supersedence within the application (with different deployment types), f.e. 7-Zip on terminal servers should be replaced but not for Windows 7. Would that work?
