Configuration Manager.Next Application Management – Part 2 Bill Anderson & Mark Florida Lead Program Managers Microsoft Corporation Session Code: MGT304

Session Objectives And Takeaways Follow on to the first session Focus on advanced app mgmt scenarios App-V deployment type What is user device affinity and how it is used Multiple DTs with conditional delivery rules Define and manage App dependencies Lots of demo(s)!!!

Embracing User Centric Separate advertisements for different forms of the same application to a machine… ConfigMgr v.Next New Features: Application Model User Device Affinity Conditional Delivery Rules App-V Deployment Type User assigned an application, rules determine which form to deliver ConfigMgr 2007

Embracing User Centric ConfigMgr v.Next New Features: Application Dependencies Conditional Delivery Rules Software Catalog Reboot Management Relationships between applications, rather serialized tasks… Custom scripting and/or dependent programs to bundle multiple applications for a machine… ConfigMgr 2007

App-V Integration – What’s New Parity with native App-V solution – Instant icon gratification – Now coming in SCCM 07 SP2! Reduce virtual app footprint when using Download and Execute Selective publishing of components in a virtual application. Integration with Terminal Services – support for simultaneous users and non-console sessions.

App-V Integration – What’s New User-centric improvements, moving to new Application Model Improved admin, end user experience No need to enable streaming on Distribution Points, removed additional streaming store on DPs Enable support for app-dependencies. Enable streaming for dependent, dynamic suite composition apps Improved update behaviors – deployments are revision latest

Create Application with App-V Deployment Type Demo Create Application with App-V Deployment Type

Windows Mobile Deployment Type New Features Admin Work Flow Unified admin experience for deploying apps to desktop + mobile devices Conditional App Delivery Rules Phone Memory Device Locale Windows Mobile OS version WM Platform ( SP vs. PPC) Admin defined custom rules based on device registry and OMA URIs Dependencies Support for application dependencies Content Signing Application wizard supports mobile content signing Targeting Supports machine and user(includes user group) targeting Supports User/Device Affinity for required deployments

Create Application with Mobile Deployment Type Demo Create Application with Mobile Deployment Type

User Device Affinity It’s a mapped relationship between a user and a device Designed to solve 2 key user targeting problems: Users roam to >1 machine, and apps install everywhere Primary User Rule in Conditional Delivery Targeting users, when no one is present WoL, after hours, workgroup machines, mobile devices Can be created in lots of ways Asset Intelligence can populate with usage thresholds Automated, or admin approved Imported from static list (purchasing, OSD list) Pre Execution Hook in OSD End-User can set Relationship can be 1-1, 1-many, or many-1

Demo UDA Demo

What is Conditional Delivery? Conditional Delivery Rules represent business or technical conditions that can determine how an application is installed. Rules apply to a given Deployment Type If any rule is not met – that DT cannot be used If all DT’s fail rules, then nothing happens If one DT passes rules, then it installs If >1 DT pass rules, the highest priority DT installs

Key Concepts Global Conditions Exceptions Rules Requirement Rules Conditions to be used in delivery or requirement rules for any app. Machine (CPU, Memory, OS, Machine OU…) User (Primary Machine, User OU) Network (Slow/fast/On Internet boundaries) Custom conditions admin can create Exceptions Rules Application Exclusion rules defines when app should not be delivered. Deployment Type Deployment Type Requirement Rules Requirement rules are tied to a DT Defines the applicability of each DT Platform requirements Hardware requirements User and machine rules Using MSI Technology Using AppV Requirement Rules Requirement Rules

Requirement rules on the Deployment Type Requirement rules are defined for a DT using global conditions in system Defines the applicability of a DT If requirement rules are not met, DT is not applicable and can not be installed Composition: Global Condition + Operator + Value Examples of Requirement Rules Platform requirements: Operating System = x64 Vista Sp1 Hardware Requirements: Total Physical Memory =>3 GB Free Disk Space => 2GB Functionality: DT_Standard should be used by all users. DT_Sales Sales should be used by users in Sales OU. Remote vs Local: Working over fast network, use MSI DT. When On Internet use TS DT. Primary Device: If primary machine, do not install the fat client (MSI) and use TS instead.

Rules – Out of the box Type Global Condition Name Machine Machine OS and Architecture Machine OS Language Total Physical Memory, Free disk space (system, admin defined partitions or any), Machine AD OU Machine AD Site SCCM Site CPU frequency, # of processors Screen resolution User Primary Device Network (considering) Network Boundary = Fast Network Boundary = Slow or Unreliable Network Boundary = On Internet Custom Create new Simple conditions Complex conditions (expressions)

Custom Global Conditions ANYTHING can be a rule – wanted to give customers flexibility to author their own. Technology – uses DCM providers and UX structure to create settings and values for rules 2 types: Simple rule/condition Complex expression that combines other rules or expressions

Demo Conditional Delivery

Client Evaluation SCCM Client Local policy store SCCM Server Client downloads and stores CDR policy SCCM Server Local policy store Policy evaluation is triggered (User log on or schedule) CDR Policy is created by Admin Policy engine evaluates CDR policy CDR Policy: Name: AppaCDR Target: User IF “On Internet” DT1 (TS) IF “NOT On Internet” DT2 (MSI) Policy Engine DT2 is selected If multiple DT is applicable install “preferred” DT Call MSI provider for DT2 App provider Discover DT2 (If already installed) Install DT2 Report installation results

Dependencies vs. Dependent programs Dependencies are a relationship between Deployment Types Similar to requirement rules, but can be installed When an application is targeted, the dependencies are treated as a component of this application Content Download Installation Reboots can be suppressed

Application Dependencies demo Application Dependencies

Client Evaluation Evaluate Deployment Type requirements for the targeted Application Deployment Type not applicable Deadline Reached Has More Dependencies? Evaluate requirements for the dependency Check client for dependency Locate and Download Content for Application and missing dependencies Enforce Intent (Require)

Takeaways You’ll have questions now, you’ll have more after beta when you play with it! It’s built on the core fundamentals of DCM – so learn DCM today It’s really 3 things – 2 of which you know today: Policy is gotten from an MP for what to consider executing – you do that today Rules are processed for what to install, IF to install, or IF to reinstall – this is new Apps install – you do that today.

Related Content Breakout Sessions MGT303 Software Distribution in Microsoft System Center Configuration Manager V.next: Part 1 MGT304 Software Distribution in Microsoft System Center Configuration Manager V.next: Part 2 MGT305 Accelerating Windows 7 Deployments with MDOP, Microsoft System Center, and Virt MGT306 Microsoft System Center and the Green Client

Related Content Hands-on Labs MGT03-HOL Deploying Microsoft System Center Configuration Manager 2007 MGT05-HOL Device Management with Microsoft System Center Configuration Manager 2007 MGT10-HOL Introduction to Microsoft System Center Configuration Manager 2007 MGT12-HOL Managing Microsoft Updates with Microsoft System Center Configuration Manager 2007 MGT21-HOL Upgrading from Microsoft Systems Management Server 2003 to Microsoft System Center Configuration Manager 2007 MGT23-HOL Deploying Windows 7 with Microsoft System Center Configuration Manager 2007 MGT24-HOL Integrating Microsoft Application Virtualization into Microsoft System Center Configuration Manager 2007 R2 MGT25-HOL Utilizing SQL Server Reporting Services with Microsoft System Center Configuration Manager 2007 R2 MGT26-HOL Generating Asset Intelligence Data with Microsoft System Center Configuration Manager 2007 MGT27-HOL Determining Client Health in Microsoft System Center Configuration Manager 2007 R2

Related Content Interactive Session Product Demos MGT01-IS Microsoft System Center Configuration Manager V.next Overview MGT02-IS Microsoft System Center Configuration Manager R2 Upgrade and Architecture Product Demos MGT01-DEMO Microsoft System Center Configuration Manager V.next: End-to-End

Links and Resources System Center Nexus Team Blog - link What’s new SP2 TechNet Documentation Library- link Configuration Manager download ConfigMgr Product Homepage – link Configuration Manager Product Team Blog – link Windows MDOP – link Windows Server 2008 R2 Branch Cache overview – link Branch Cache ConfigMgr Deployment Guidance – link

Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

Required Slide © 2009 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.