Deep Application Management with Microsoft System Center 2012 Configuration Manager

1. MGT312 Deep Application Management with Microsoft System Center 2012 Configuration Manager Bryan Keller Lead Program Manager Microsoft Corporation

2. Session Agenda • Overview of Software Distribution (SWD) in Configuration Manager 2012 • Create, Deploy and Monitor Applications • User Device Affinity • Simple apps. More complex rules • Content, Applications and Operating System Deployment

3. Need For New Application Model Your end-users are changing the way they do work • Ultra mobility • Lots of devices • New generation with new expectations Your apps are changing • AppV • SaaS • Datacenter hosted (VDI, remote/seamless apps) • Mobile apps/catalogs What’d we do? • Rewrote our definition of an app from package/program • DON’T JUMP OFF A CLIFF – Packages/Programs still there! Traditional Model User Centric Model Management Server

4. User-centric Application DeliveryNew Application Model General Information • Administrator Properties • End User Metadata Application “Package” Keep your apps organized and managed < > The “friendly” information for your users (appears in Catalog) Deployment Type • Detection Method • Install Command • Requirement Rules • Dependencies • Supersedence Is app installed? App-V Windows Script Command line and options Windows Installer Can/cannot install app CAB Apps that must be present Application version control

5. ConfigMgr 2007 to 2012 Comparison – App Model

6. State-based Application Management In ConfigMgr 2007 • Collection rule targeting and status messages • Fire and forget software deployment model • Run once or on a schedule • Not smart, will download content and run program even if software is already there In ConfigMgr 2012, Application management is state-based • Detection method determines if any action should take place • Install/Uninstall • Regular evaluation to check for and enforce compliance • Rules determine applicability of software • Rules are per deployment type • Evaluated in real time on the client • If present or not applicable, don’t download content Key takeaway: Detection method - Not historically done by admins, key new area to familiarize yourself with. Rules – historically done server-side with collections, not in real time – key new area as well

7. Requirement Rules in 2012State-based Application Management • Properties of users and/or devices that makes delivering software appropriate • Rules are per deployment type • Evaluated in real time on the client • Evaluated before content is downloaded to the client

8. Global Conditions • Foundation of Requirement Rules • Properties of users and/or devices that make delivering software appropriate • Global conditions are system artifacts • Default Global condition = Memory is greater than 512MB • Custom Global condition = Machine is Corporate Device • “Machine is Corporate Device” maps to a registry key attribute • Global Expressions • Enables the application author or administrator to create logical groupings of global conditions and assign values. These expressions can be reused for applications • Example: • An expression such as “Corporate Primary Device” consists of the following rules: • Memory = 1 gig • and Free Disk Space = 500 MB • and Operating System = Windows 7 • CorporateDevice= True

9. Rich Application RelationshipsDependencies and Supersedence • Dependencies • Other deployment types that must be present in order for the current application deployment type to be installed • 1 to n Dependencies • This AND this AND this OR this • .NET Framework either 3.5 or 4.0 and • Browser either IE7 or IE8, install IE8 if none present • Dependencies are modeled as applications and can also be deployed independently • Supersedence: • Admin declares one application newer than another previous application • Provide the ability to uninstall OR upgrade previous version • Ability to offer users only the latest release of an app in the software catalog or software center • Ability to create new application or version and make sure we do not get in a “race condition” between conflicting detection methods

10. DEMO Create an Application

11. Content Distribution Distribution Point Groups • Can be linked to Collections for workflow optimization • Automatic distribution of content for distribution points added to the group Distribute Content Wizard • Send multiple packages to multiple distribution points or groups at once • Detect Application dependencies and add them to the distribution • Select a task sequence and distribute all related content Content Library • Files will be stored once, even if they are used across multiple applications, packages, update packages, etc. • Only files required by the distribution point are distributed over the network Bandwidth Control • Customize time and bandwidth utilization on distribution points

12. Content Monitoring • Compliance of content distributed in multiple views • Application, package, etc. level • Distribution point group level • Distribution point level • Ability to validate content on a distribution point • Available as a set schedule or on demand • Updates package compliance in the monitoring node

13. Application Deployment • Replaces “Advertisement” from Configuration Manager 2007 • Created when an Application is deployed to a Collection • Due to applications being state based, only deploy to a collection once • 2 types of deployment purposes • Required (like mandatory in Configuration Manager 2007) • Available (like optional in Configuration Manager 2007) • Available for User targeted displayed in the Software Catalog • Available for Device targeted displayed in Software Center on client • 2 types of actions • Install • Uninstall Provides setting for “Pre-deployment” feature when targeting user or user security group collections

14. Application Evaluation Flow New Policy App Install Schedule No Requirements met? Yes Yes Is installed? No No Install dependencies Dependencies installed? Yes Install Application Dependencies installed

15. What is User Device Affinity (UDA)? • Key feature to help move to User Centric Application Deployment • Provides the ability to define a relationship between a user and a device, then leverage this in app deployment • Ensure the application is not installed everywhere the user logs on • Change the “deployment type” based on UDA • Predeploy to systems when the user is not logged in for workgroup and after-hours deployments • Configuration Manager 2012 supports: • Single primary user to primary device • Multiple primary devices per user • Multiple primary users per device < Windows Embedded

16. How Can User Device Affinity Be Set? • User device affinity relationships are defined: • Based on a usage threshold on client • Using import file from external system • As part of Operating System Deployment • Can be set from PXE, Bootable and Prestaged Media • UDA relationship can be configured to: • Auto Approve, Pending Approval and Do Not Allow • During Mobile Device enrollment • By end-user through Software Catalog • Manually by administrator • Client Agent Settings • Define user device affinity configuration at collection level • Usage and User based user device affinity can be enabled and configured using client agent settings

17. Application Catalog • Administrators publish software titles to catalog, complete with meta data to enable search • Deliver best user experience on each device IT • Users can browse, select and install directly from Catalog • Application model determines format and policies for delivery User

18. On Demand Installation Process Flow User clicks “Install” on Catalog item Web site checks Melissa’s install permissions Web site gets Client ID from Agent, hands to server Policy created for Client ID & app, hands to agent Client agent evaluates requirements from policy Web site initiates installation Agent completes installation process & status 1 WEB SITE SITE SERVER 2 3 4 5 6 MELISSA 7 AGENT

19. DEMO Make an Application Available in the Catalog

20. Benefits of Multiple Deployment Types • Flexible way to deliver different installation formats based on rules • Many of the same type of deployment types could be added to an application each representing a different transform • Same app – different installs for different architectures (x86/x64) • App-V deployment type for a guest logged into a kiosk or VDI session, full MSI to a users primary desktop machine • Built-in deployment types • MSI • Script • App-V • Windows Mobile 6.x • Nokia • Citrix XenApp connector for ConfigMgr 2012 under development

21. App-V in Configmgr 2012: What’s Changing? • New Application Model, User Centric features • Enable support for application dependencies • Improved update behaviors • Selective publishing of components • Dynamic Suite Support • Instant icon gratification for unlock events • Integration with Remote Desktop Services (RDS) to target user sessions on RDS servers • Content Improvements • Streaming improvements • Reduce virtual app footprint when using Download and Execute • Integration requires App-V 4.6 client

22. Coming in SP1! Windows 8 Metro Style Applications • New Deployment Type for Metro Style Applications

23. Coming in SP1! Deep links • New Deployment Type • Reference from ConfigMgr’s Application Catalog to Windows Store • End Users have one location for all Enterprise Applications • Administrators do not need to repackage

24. Microsoft NDA Confidential Coming in SP1! Support for Mac OS X Applications • Push required software to Mac OS X systems using built-in Deployment Type • Support for Apps with the following file formats: • DMG • MPKG • PKG • .APP • Uses custom tool CMAppUtil on Mac: • Extracts detection info and makes it consumable by ConfigMgr • Outputs file in .cmmac format that includes the application binaries and detection methods

25. DEMO Applications with Multiple Deployment Types

26. Coming in SP1! Microsoft Application Virtualizationin Configuration Manager SP1 • App-V 4.6 SP2 support: • Needed for Windows 8 • Same feature functionality • App-V 5.0: • New Deployment Type for App-V 5.0 applications • Main new feature compared to 4.6 is composition

27. Coming in SP1! App-V 5.0 Connection Groups • ConfigMgradministrator and packager don’t need to be in sync • Only need to use ConfigMgr console create relationships • Optional relationships did not work well with Dynamic Suite Composition in 4.6: • Examples: • Lyncand Office • Excel and Visual Studio • In 4.6 the sequencer would need to know about these relationships, and both applications would be required

28. Coming in SP1! PowerShell • PowerShell Provider • Cmdlets: • Scope: Tasks exposed in the Administration Console • How: • Suitable experience for administrator (not the SDK) • Align with PowerShell general conventions

29. DEMO Powershell

30. Summary Software Distribution in Configuration Manager 2012 • Application Model • Deployment Types: MSI, Script, App-V, Mobile CAB • Greatly improved dependency handling • Installation requirement rules • Installation detection methods • Application supersedence • Application uninstall • Simulate Application Deployment • User Device Affinity • Unified monitoring experience • End user experience • Software Catalog • Software Center • Content management • Distribution point groups • Improved monitoring experience • Content validation New in Configuration Manager 2012 SP1 • App-V 4.6 SP2 • App-V 5.0 • New Deployment Types: • Windows 8 apps • Deep links • Mac OS X

31. Related Content • Breakout Sessions • MGT309 | Microsoft System Center 2012 Configuration Manager Overview • MGT310 | Microsoft System Center 2012 Endpoint Protection Overview • MGT311 | Microsoft System Center 2012 Configuration Manager Deployment and Infrastructure Technical Overview • MGT313 | Microsoft System Center 2012 Configuration Manager: Plan, Deploy, and Migrate from Configuration Manager 2007 to 2012 • MGT318 | Patch and Settings Management in Microsoft System Center 2012 Configuration Manager • WCL388 | Client Management Scenarios in the Windows 8 Timeframe

32. Related Content • Hands-on Labs: • MGT23-HOL | Deploying Windows 7 to Bare Metal Systems with Microsoft System Center 2012 Configuration Manager • MGT24-HOL | Implementing Endpoint Protection 2012 in Microsoft System Center 2012 Configuration Manager • MGT12-HOL | Compliance and Settings Management in Microsoft System Center 2012 Configuration Manager • MGT25-HOL | Deep Dive: Microsoft System Center 2012 Configuration Manager SQL Replication Labs • MGT21-HOL | Basic Software Distribution in Microsoft System Center 2012 Configuration Manager • MGT16-HOL | Migrating from Microsoft System Center Configuration Manager 2007 to System Center 2012 Configuration Manager • MGT14-HOL | Implementing Role Based Administration in Microsoft System Center 2012 Configuration Manager • MGT15-HOL | Deploying a Microsoft System Center 2012 Configuration Manager Hierarchy • MGT11-HOL | Introduction to Microsoft System Center 2012 Configuration Manager

33. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://northamerica.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

34. Complete an evaluation on CommNet and enter to win!

35. MS Tag Scan the Tag to evaluate this session now on myTechEd Mobile

36. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.