Transcript Bryan Keller Lead Program Manager Microsoft Corporation Traditional User Centric Model Model Management Server New Application Model General Information Application “Package” Administrator Properties End User Metadata Deployment Type App-V Detection Method Windows Script Install Command Windows Installer Requirement Rules CAB Dependencies Supersedence.

Bryan Keller
Lead Program Manager
Microsoft Corporation
Traditional
User
Centric
Model
Model
Management
Server
New Application Model
General Information
Application
“Package”
< >
Administrator Properties
End User Metadata
Deployment Type
App-V
Detection Method
Windows Script
Install Command
Windows Installer
Requirement Rules
CAB
Dependencies
Supersedence
Feature
Configuration Manager 2007
Configuration 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
Targeting
Who gets it AND where can it run
Collections – 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
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
State-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
Provides setting for “Pre-deployment” feature when targeting user
or user security group collections
<
Windows
Embedded
IT
User
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 delivery
Process Flow
WEB SITE
SITE SERVER
MELISSA
AGENT
1
User clicks “Install” on Catalog item
2
Web site checks Melissa’s install permissions
3
Web site gets Client ID from Agent, hands to server
4
Policy created for Client ID & app, hands to agent
5
Client agent evaluates requirements from policy
6
Web site initiates installation
7
Agent completes installation process & status
Coming in SP1!
Coming in SP1!
Coming in SP1!
Microsoft NDA Confidential
Coming in SP1!
Coming in SP1!
Coming in SP1!
http://northamerica.msteched.com
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn