0
System Center ConfigurationManager 2012
The application model in real lifeKim OppalfensSenior consultant | InovativCo-Founder System Center user group Belgium
Disclaimers1. NOT an overview session2. NOT a sales pitch3. No, I do NOT have an answer to all scenarios (yet).
Agenda•   Vision behind the app model•   The app model overview in record time•   User device affinity•   Content library•...
Vision behind the app model  Lifecycle                  •   Install                  •   Upgrade                  •   Unin...
Vision behind the app model                                                         Application Installation        Applic...
The app model overview
Requirement Rules in 2012State-based Application Management Properties of users and/or devices that     Rules are per     ...
Detection MethodsState-based Application ManagementDetection is the key to any state based softwaredistribution system    ...
Application evaluation flow
Application Supersedence                                                                  But, Allows admins to Definition...
Supersedence and the end-user UX                  User only sees latest application                  version in Software C...
Supersedence examples (1) SimpleScenario and Assumptions 2 applications:   Adobe Reader X supersedes    Adobe Reader 9 ...
Supersedence examples (2) Conflict 2 applications:  Adobe Reader X supersedes Adobe Reader 9 Accounting App (AA1) depen...
Application Uninstalls                                          • Uninstall is a deployment action     Admin creates an Un...
Troubleshooting & monitoring                               The deployment What logfiles?                               mon...
Sharing our experiences / challengesApplications installed                          User targeted installs                ...
Challenges and potential workarounds   Required app to                                                   Automatically   u...
The application model in real life
Upcoming SlideShare
Loading in...5
×

The application model in real life

669

Published on

More info on http://techdays.be.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
669
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • (http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_LogLocation)AppIntentEval.logAppDiscovery.logAppEnforce.logCcmExec.logCcmsdkprovider.logConfigMgrSoftwareCatalog.logDataTransferService.logExecMgr.logPolicyAgent.logSoftwareCatalogUpdateEndpoint.logSoftwareCenterSystemTasks.logStateMessage.logVirtualApp.log
  • Global conditions vs Collection rulesWhentouseanapp
  • Transcript of "The application model in real life"

    1. 1. System Center ConfigurationManager 2012
    2. 2. The application model in real lifeKim OppalfensSenior consultant | InovativCo-Founder System Center user group Belgium
    3. 3. Disclaimers1. NOT an overview session2. NOT a sales pitch3. No, I do NOT have an answer to all scenarios (yet).
    4. 4. Agenda• Vision behind the app model• The app model overview in record time• User device affinity• Content library• Application Supersedence• Application Uninstalls• Challenges and potential workarounds• Troubleshooting & Monitoring• Questions?
    5. 5. Vision behind the app model Lifecycle • Install • Upgrade • Uninstall management • • Retire Versioning and history User centric • Deliver applications to users not computers deployment
    6. 6. Vision behind the app model Application Installation Application Uninstall Application Revision Application Retirement Application Supersedence
    7. 7. The app model overview
    8. 8. Requirement Rules in 2012State-based Application Management Properties of users and/or devices that Rules are per Evaluated in real- makes delivering deployment type time on the clientsoftware appropriate Evaluated before content is Re-evaluated on a downloaded to the schedule client
    9. 9. Detection MethodsState-based Application ManagementDetection is the key to any state based softwaredistribution system Detection methods enable systems to determine whether or not an application is already present on a system (Discovery) Detection methods are also used to determine the success or failure of a deployment Important to get these right!
    10. 10. Application evaluation flow
    11. 11. Application Supersedence But, Allows admins to Definition: The ability for testpilot newer the admin to create a This ultimately results in the application, prior to relationship and declare newer application replacing production release. Whileone application newer than the older application for a permitting the older another previous user on a device application to continue to application. exist for the majority of users
    12. 12. Supersedence and the end-user UX User only sees latest application version in Software Catalog (by default) Required applications are always the enterprise’s latest version. When the user or computer receives a policy that targets it with BOTH policies Available Applications installed by user can be automatically updated
    13. 13. Supersedence examples (1) SimpleScenario and Assumptions 2 applications:  Adobe Reader X supersedes Adobe Reader 9 Both applications deployed to same deviceIf client has Adobe Reader 9 alreadyinstalled assuming requirements are met for Reader X, Reader 9 will be replaced with Reader X (either uninstalled or updated)If client has Adobe Reader X alreadyinstalled evaluates both 9 and X detection methods, X is present, 9 is not – but since X supersedes, it doesn’t try to install 9If neither are installed, only AdobeReader X will be installed
    14. 14. Supersedence examples (2) Conflict 2 applications:  Adobe Reader X supersedes Adobe Reader 9 Accounting App (AA1) depends on Reader 9Case 1: Client receives all policies No applications have been previously installed Assuming requirements for all Deployment Types are met, Reader X will be installed on device AA1 is not installed on client, and conflict requirements not met messageCase 2: AA1 policy received prior to supersedence relationship defined. AA1 and Reader 9 will be installed (assuming requirements are met), When Reader X is deployed, a conflict for Reader X will be provided to user and admin
    15. 15. Application Uninstalls • Uninstall is a deployment action Admin creates an Uninstall Deployment • The App Model defines an uninstall method for each Deployment Type of an Application.An admin defines a specific collectionto target the Uninstall Deployment to (either users or machines)If a user or device is the recipient of both an install and uninstallpolicy, then install wins and the app will not be removed
    16. 16. Troubleshooting & monitoring The deployment What logfiles? monitoring tool
    17. 17. Sharing our experiences / challengesApplications installed User targeted installs Application Uninstallsduring a tasksequence Roaming user logging and computer targeted do not validate the generate an install in to my workstation uninstalls requirements policy
    18. 18. Challenges and potential workarounds Required app to Automatically user on primary Required appv with upgrade available device, available on roaming profiles applications non-primary Uninstall an application from a machine that is still targetted to users
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×