Deep Application Management with Microsoft System Center 2012 Configuration Manager

MGT312

Adwait JoshiSenior Product Marketing ManagerMicrosoft Corporation

Hassen KaraaSenior Program ManagerMicrosoft Corporation

Session Agenda

Overview of Software Distribution (SWD) in Configuration Manager 2012

Create, Deploy and Monitor ApplicationsUser Device Affinity

Simple apps. More complex rulesContent, Applications and Operating System Deployment

Need For New Application Model

Your end-users are changing the way they do work

Ultra mobilityLots of devicesNew generation with new expectations

Your apps are changingAppVSaaSDatacenter hosted (VDI, remote/seamless apps)Mobile apps/catalogs

What’d we do?Rewrote our definition of an app from package/programDON’T JUMP OFF A CLIFF – Packages/Programs still there!

Management Server

Traditional Model User Centric Model

Application “Package”

User-centric Application DeliveryNew Application Model

Keep your apps organized and managed

App-V

Windows Script

CAB

Windows Installer

General Information

Administrator Properties

End User Metadata The “friendly” information for your users (appears in Catalog)

Is app installed?

Deployment Type

Detection Method

Install Command

Requirement Rules

Dependencies

Supersedence

Command line and options

Can/cannot install app

Apps that must be present

Application version control

< >

ConfigMgr 2007 to 2012 Comparison – App Model

Feature Configuration Manager 2007Configuration Manager 2012

Create Application Package and Program Application, Deployment Types, Requirement Rules

Deploy Application Advertisement Deploy

Compliance “Did I execute correctly?”Install Status

“Is the app there?”State based with detection method

TargetingWho gets it AND where can it runCollections – Users or devices, inventory

Who gets it? Collections – Users or devices

User-targeting Users or devices Users or devices with User Device Affinity

Client User Experience Run Advertised Programs Software Catalog and Software Center

Content Management None or limited Content library and monitoring

State-based Application ManagementIn ConfigMgr 2007

Collection rule targeting and status messagesFire and forget software deployment modelRun once or on a scheduleNot 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 placeInstall/UninstallRegular evaluation to check for and enforce complianceRules determine applicability of software

Rules are per deployment typeEvaluated 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

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

Global ConditionsFoundation of Requirement RulesProperties of users and/or devices that make delivering software appropriateGlobal conditions are system artifacts

Default Global condition = Memory is greater than 512MBCustom Global condition = Machine is Corporate Device

“Machine is Corporate Device” maps to a registry key attribute

Global ExpressionsEnables the application author or administrator to create logical groupings of global conditions and assign values. These expressions can be reused for applicationsExample:

An expression such as “Corporate Primary Device” consists of the following rules:Memory = 1 gig and Free Disk Space = 500 MBand Operating System = Windows 7CorporateDevice = True

Rich Application RelationshipsDependencies and Supersedence

DependenciesOther deployment types that must be present in order for the current application deployment type to be installed1 to n DependenciesThis AND this AND this OR this

.NET Framework either 3.5 or 4.0 andBrowser 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 applicationProvide the ability to uninstall OR upgrade previous versionAbility 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

Create an Application

DEMO

Content Distribution

Distribution Point GroupsCan be linked to Collections for workflow optimizationAutomatic distribution of content for distribution points added to the group

Distribute Content WizardSend multiple packages to multiple distribution points or groups at onceDetect Application dependencies and add them to the distributionSelect 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

Content Monitoring

Compliance of content distributed in multiple views

Application, package, etc. levelDistribution point group levelDistribution point level

Ability to validate content on a distribution point

Available as a set schedule or on demandUpdates package compliance in the monitoring node

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 purposesRequired (like mandatory in Configuration Manager 2007)Available (like optional in Configuration Manager 2007)Available for User targeted displayed in the Software CatalogAvailable 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

Application Evaluation Flow

Requirements met?

New Policy App Install Schedule

Dependencies installed?

Yes

Install dependenciesNo

No

Yes

Install Application

Is installed?

No

Yes

Dependencies installed

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 onChange the “deployment type” based on UDAPredeploy to systems when the user is not logged in for workgroup and after-hours deployments

Configuration Manager 2012 supports:Single primary user to primary deviceMultiple primary devices per userMultiple primary users per device

<

Windows Embedded

How Can User Device Affinity Be Set?

User device affinity relationships are defined:

Based on a usage threshold on clientUsing import file from external systemAs part of Operating System Deployment

Can be set from PXE, Bootable and Prestaged MediaUDA relationship can be configured to:

Auto Approve, Pending Approval and Do Not Allow

During Mobile Device enrollmentBy end-user through Software CatalogManually by administrator

Client Agent SettingsDefine user device affinity configuration at collection levelUsage and User based user device affinity can be enabled and configured using client agent settings

Application Catalog

IT

Administrators publish software titles to catalog, complete with meta data to enable search Deliver best user experience

on each device

Users can browse, select and install directly from Catalog Application model determines

format and policies for deliveryUse

r

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

On Demand Installation

WEB SITE

AGENT

1

2

3

4

5

Process Flow

6

7

SITE SERVER

MELISSA

Make an Application Available in the Catalog

DEMO

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 transformSame 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 typesMSI ScriptApp-VWindows Mobile 6.xNokia

Citrix XenApp connector for ConfigMgr 2012 under development

App-V in Configmgr 2012: What’s Changing?

New Application Model, User Centric featuresEnable support for application dependenciesImproved update behaviors Selective publishing of componentsDynamic Suite Support

Instant icon gratification for unlock eventsIntegration with Remote Desktop Services (RDS) to target user sessions on RDS servers

Content ImprovementsStreaming improvementsReduce virtual app footprint when using Download and Execute

Integration requires App-V 4.6 client

Windows 8 Apps

New Deployment Type for Windows 8 Apps

Coming in SP1!

Deep links

New Deployment TypeReference from ConfigMgr’s Application Catalog to Windows StoreEnd Users have one location for all Enterprise ApplicationsAdministrators do not need to repackage

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:

DMGMPKGPKG.APP

Uses custom tool CMAppUtil on Mac:

Extracts detection info and makes it consumable by ConfigMgrOutputs file in .cmmac format that includes the application binaries and detection methods

Microsoft NDA Confidential

Coming in SP1!

Applications with Multiple Deployment Types

DEMO

Microsoft Application Virtualizationin Configuration Manager SP1

App-V 4.6 SP2 support:Needed for Windows 8Same feature functionality

App-V 5.0:New Deployment Type for App-V 5.0 applicationsMain new feature compared to 4.6 is composition

Coming in SP1!

App-V 5.0 Connection Groups

ConfigMgr administrator and packager don’t need to be in sync

Only need to use ConfigMgr console create relationshipsOptional relationships did not work well with Dynamic Suite Composition in 4.6:

Examples:Lync and OfficeExcel and Visual Studio

In 4.6 the sequencer would need to know about these relationships, and both applications would be required

Coming in SP1!

PowerShell

PowerShell ProviderCmdlets:

Scope: Tasks exposed in the Administration ConsoleHow:

Suitable experience for administrator (not the SDK)Align with PowerShell general conventions

Coming in SP1!

App-V 5.0 Connection Groups and Powershell

DEMO

Summary

Application ModelDeployment Types: MSI, Script, App-V, Mobile CAB

Greatly improved dependency handlingInstallation requirement rules Installation detection methodsApplication supersedenceApplication uninstallSimulate Application Deployment

User Device Affinity

Unified monitoring experienceEnd user experience

Software CatalogSoftware Center

Content managementDistribution point groupsImproved monitoring experienceContent validation

Software Distribution in Configuration Manager 2012

New in Configuration Manager 2012 SP1New Deployment Types:

Windows 8 appsDeep linksMac OS X

App-V 4.6 SP2App-V 5.0

Related Content

Breakout SessionsMGT309 | Microsoft System Center 2012 Configuration Manager OverviewMGT310 | Microsoft System Center 2012 Endpoint Protection OverviewMGT311 | Microsoft System Center 2012 Configuration Manager Deployment and Infrastructure Technical OverviewMGT313 | Microsoft System Center 2012 Configuration Manager: Plan, Deploy, and Migrate from Configuration Manager 2007 to 2012MGT318 | Patch and Settings Management in Microsoft System Center 2012 Configuration ManagerWCL388 | Client Management Scenarios in the Windows 8 Timeframe

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

MGT Track Resources

DOWNLOAD System Center 2012 SP1 CTP

microsoft.com/systemcenter

#TEMGT312 DOWNLOAD System Center 2012 Evaluation

microsoft.com/systemcenterHands-On Labs

Talk to our Experts at the TLC

Resources

Connect. Share. Discuss.

http://europe.msteched.com

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Resources for Developers

http://microsoft.com/msdn

Evaluations

http://europe.msteched.com/sessions

Submit your evals online

© 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.