Trevor, I was thinking along the same lines about putting the version after the name in the Name field. I agree that it's dumb the Name has to be unique like that. Thanks!
Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Wednesday, November 27, 2013 10:34 AM To: [email protected] Subject: RE: [mssms] Managing applications Mark, Only one Deployment Type will execute for each Application, so if you were to have many versions of an application (eg. Google Chrome), it could get very confusing with all the various Deployment Types. I would suggest creating a different Application object for each version of the application (Google Chrome). Since the Application objects cannot share the same value in the Name field - which I think is pretty dumb, since they're all referenced by unique IDs anyway - you can just include the application's major version number in the Name field. That is what I've had to do for things like Microsoft Internet Explorer 10 and Microsoft Internet Explorer 11, or the .NET Framework 4.0, 4.5, 4.5.1. Cheers, Trevor Sullivan [cid:[email protected]] [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Wednesday, November 27, 2013 9:14 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Managing applications I am looking for a little feedback/guidance in regards to managing applications that update frequently, using the new App model. For example, Google Chrome seems to update to a new version every 3-4 weeks. Should I make an Application for say 30, and then a new one for 31? Or do I make a generic Application for Chrome (skipping the version box), and then make Deployment Types for 30, 31 and so on? We are just getting ready to migrate to SCCM2012 so I am curious as to how others are handling this. Thanks! Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State
<<inline: image001.png>>
<<inline: image002.png>>
