Hi Trevor, Possible Scenario:
User1 needs App1 User1 has Primary device PC1 User1 needs App1 for LOB User1 "roams" User2 does not need App1 User2 needs App2 which does not coexist well with App1 User2 works from PC2 User2 has App2 installed on PC2 User1 logs onto PC2 App1 is delivered on per User basis but because machine is not User1's primary device an App-V version is deployed. All (both) users are happy. (Which is the main objective, therefore compelling :)) * Is this something that you practice when building ConfigMgr Application Deployment Types? o I don't use User-Centric App Deployment at my current customer but it is something I would implement. * Can you provide an example of an application that you used this for? o A financial Application like SAP - two different financial departments in the same company that have different versions of the financial software, with different, probably java, dependencies * Why is this setting configurable on Script Deployment Types? o In order to use script based deployments, not sure I understand the question. To implement proper user-centric computing you have to allow the various deployment types. * Isn't per-user installation a Windows Installer exclusive concept? o Not in my opinion. And I don't believe MS would lay any such restrictions on User-Centric computing. Without Per-User installation: User1 must order App1 for each PC they log onto. This doesn't make sense for users who roam. Think also on BYOD. User1 needs App1 but it can't be deployed to their BYOD device, for policy or licensing reasons. But they are allowed access to an App-V version. One killer for User-Centric is lack of a sustainable Asset Register. In terms of process you need to make sure you can define relationships between users and primary devices. Hope this helps, I'd be interested to hear others' views on it. Andrew Von: [email protected] [mailto:[email protected]] Im Auftrag von Trevor Sullivan Gesendet: Dienstag, 19. November 2013 19:26 An: [email protected] Betreff: [mssms] ConfigMgr 2012: Application Deployment Type: Installation Behavior: Per-User Installation Hey folks, Can anyone provide a compelling scenario where a "per-user" installation would be appropriate? Cheers, Trevor Sullivan [cid:[email protected]]
<<inline: image001.png>>
