Transcript © 2012 Microsoft Corporation. All rights reserved. System Center 2012 Configuration Manager Concepts & Administration Lesson 6: Deploying Applications Your Name Premier Field Engineer Microsoft.

© 2012 Microsoft Corporation. All rights reserved.
System Center 2012 Configuration Manager
Concepts & Administration
Lesson 6: Deploying Applications
Your Name
Premier Field Engineer
Microsoft
Conditions and Terms of Use
Microsoft Confidential
This training package is proprietary and confidential, and is intended only for uses described in the training materials. Content and software
is provided to you under a Non-Disclosure Agreement and cannot be distributed. Copying or disclosing all or any portion of the content
and/or software included in such packages is strictly prohibited.
The contents of this package are for informational and training purposes only and are provided "as is" without warranty of any kind,
whether express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and noninfringement.
Training package content, including URLs and other Internet Web site references, is subject to change without notice. Because Microsoft
must respond to changing market conditions, the content should not be interpreted to be a commitment on the part of Microsoft, and
Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Unless otherwise noted, the companies,
organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no
association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should
be inferred.
Copyright and Trademarks
© 2012 Microsoft Corporation. All rights reserved.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this
document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
For more information, see Use of Microsoft Copyrighted Content at
http://www.microsoft.com/about/legal/permissions/
Microsoft®, Internet Explorer®, and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries. Other Microsoft products mentioned herein may be either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.
Overview
High level overview of legacy Software Distribution
Introduction to Application Deployment
3
Objective
After completing this lesson, you will be able to:
Understand Distribution Points
Understand legacy Software Distribution
Understand Application deployment
Understand Software Center and Application Catalog
LAB: Configure Software Distribution and Application
Deployment
4
Microsoft Confidential
What’s new in Application Deployment?
Application Model
Incorporates all supported
software types
Greatly improved dependency
handling
Installation requirement rules
User Device Affinity
Unified deployment process
Unified monitoring experience
End user experience
Application Catalog
Software Center
Content management
State based distribution
point groups
Single instance content store
5
Boundary Groups
Boundary Groups are used for:
Site assignment
Content Location
Boundary Groups contains one or more boundaries
Boundary Groups can associate with the following roles for
Content Location:
Distribution Point
State Migration Point
Overlapping boundary configurations are supported for
content location only
Each referenced server within a Boundary Group can be
configured as a slow or fast connection
6
Distribution Point and Distribution Point groups
Microsoft Confidential
Distribution Point
One Distribution Point role
Merges Standard, Branch and Server Share DP
Requires Windows Vista SP2 and later
Requires Windows Server 2003 SP2 and later
Requires IIS and BITS
Defaults to BITS download for clients
Client Operating Systems configured as Distribution Points
do not support PXE and multicast
PXE Service point is now an option of the Distribution Point
Scheduling and throttling options for content distribution
to Distribution Point are like sender scheduling between
sites
8
Distribution Point Content
Ability to prestage content on Distribution Points
Prestaged Distribution Point settings per package
Automatically download content when packages are assigned
Download only content changes
Manually copy the content in this package
Ability to validate content on the Distribution Point
Content validation can be scheduled
Content validation can be triggered by an Administrator
Content status can be reviewed in the Monitoring workspace
Content status will only be reported – not fixed
Administrator will have to manually fix any problem
9
Distribution Point Content Library
Content Library is the new file repository for content on
site servers and Distribution Points
Common repository for all object types (applications,
updates, packages, etc…)
Contains three main components
Data Library – stores information about each file in the
file library
File Library – stores the actual files (files are renamed
and stored based on their hash values)
Content
Package Library – stores information
Library
about the content in each package
Data
Library
10
File
Library
Package
Library
Distribution Point Content Library (continued)
Replaces compressed content on the site server
Eliminates multiple instances of files and older data that
would remain on the server
Snapshot taken each time package version is updated
Replaces SMSPKGX$ as default package store on
distribution points
Not enabled by default, still available for most objects (except
applications and software updates)
Requires additional disk space to store packages
SMSPKG still exists for generating compressed copy and
while sending content from site to site
Single instance storage of files on site server and
distribution point
11
Distribution Point Content Library (continued)
Single instance distribution of files to a Distribution Point
from a site server
New component PkgXferMgr performs the distribution
Distribution Manager still processes the distribution jobs
Compressed copy from site server to site server or
secondary site
Still uses senders (same as Configuration Manager 2007)
Compressed copy format updated for single instance file
storage
Easier to configure storage location on the Distribution
Point
Specify the drives to use during role installation
Drives will have a priority for file storage, instead of a drive
with the most space
Support to move a file library to a new drive through the SDK
12
Distribution Point Groups
One Distribution Point can be added to multiple
Distribution Point groups
Distribution Point groups are state based
Content added to a group will be copied to all Distribution Points
Automatic distribution of content for Distribution Points are added
to the group at a later point
Distribution Point groups can be associated with
Collections
Content will be automatically assigned to the Distribution Point
group if the application is targeted to the Collection
13
Classic Package Deployment Model
Microsoft Confidential
Legacy Software Distribution
Same software distribution principles as Configuration
Manager 2007
Legacy Software Distribution consists of the following
parts:
Collection
Package
Program
Deployment
Legacy Software Distribution no longer supports App-V
deployments. App-V deployments must use the new
Application Deployment model
15
What has Changed Since Configuration
Manager 2007?
16
Microsoft Confidential
Classic Package Deployment Model
What?
How?
When?
SMS_Package, SMS_Program
SMS_Package
Where?
(also when)
SMS_Collection
Collection A
Package source files
`
Advertisement
Advertisement Start Time
+
List of programs
Schedule 1
`
`
`
Schedule 2
Advertisement Expiration Time
Execution strategy
Program 1: TypicalSetup
setup.exe /q INSTALLDIR=C:\LOB\ABCComp
...
Program 2: Minimum Setup
setup.exe /q COMPONENTS=UI,DBClient INSTAL...
Advertisement
Advertisement Start Time
Program 3: Custom Setup
Schedule 1
setup.exe
+
List of distribution point
Schedule 2
Advertisement Expiration Time
Execution strategy
...
17
Microsoft Confidential
Collection B
`
Application Model
Microsoft Confidential
Application Model Diagram
General information about the
software application
19
General Application Information
Administrator information about applications
Manufacturer
Version
Administrative categories
Contact information for the application
Application Catalog information
Information is displayed about application in localized language of
user
Information consists of:
Localized application name
User categories
Documentation
Localized description
20
Deployment Types
Contains details about the files, commands and programs
to install the Application
Application can contain multiple Deployment Types
Only one Deployment Type will be installed on a client
The following standard Deployment Types are available:
Windows Installer(MSI)
Script ( Commandline )
Microsoft Application Virtualization
Windows Mobile Cabinet
Nokia SIS file
21
Deployment Type: Detection Method
Detection Methods enable systems to determine
whether or not an application is already present on a
system (discovery)
In Software Updates, this is known as IsInstalled
Built-in Detection Methods available for Windows Installer
and Microsoft Application Virtualization
Detection is the key to any state based software
distribution system
22
Deployment Type: Detection Method
Some Deployment Types allow custom detection methods
to be configured and these methods can use registry
information, file versions, MSI database, WMI or a custom
script (Powershell, VBScript, Jscript)
Any combination of the previously mentioned rules can be
used to select the Deployment Type for deployment
Rules can be grouped
Logical operators AND/OR used to create complex rule sets
23
Deployment Type: User Experience
Installation behavior
Install for user
Install for system
Install for system if resource is Device; otherwise install for user
Logon requirement
Only when a user is logged on
Whether or not a user is logged on
Only when no user is logged on
Program visibility behavior
Restart behavior
Determine behavior based on Return Codes
No Specific Action
The software install program might force a device restart
Configuration Manager client will force a mandatory device restart.
24
Deployment Type: Requirements
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
Evaluated before installation
Custom requirement rule can use the same information
sources as Compliance Settings, for example:
File System
Registry key and value
WQL query
SQL query
Script
25
Deployment Type: Requirements (continued)
Default requirements:
26
Deployment Type: Return Codes
Return Codes can be used to change behaviour of the
Configuration Manager client after installing application
Administrator can add custom return codes
Administrator can add the following action to a custom
return code:
Success (no reboot)
Failure (no reboot)
Hard Reboot
Soft Reboot
Fast Retry
27
Deployment Type: Dependencies
Other Deployment Types that must be present in order for
the current application Deployment Type to be installed
One or more Dependencies
{x} AND {y} AND {z} OR {a}
.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
28
Multiple Deployment Types
Flexible way to deliver different installation format based
on requirements
No restrictions on the number and types of Deployment
Types
Five of the same type of Deployment Types could be added to an
application each representing a different flavor or transform
Virtual application might go to a guest logged into a kiosk,
Windows Installer to a users primary desktop machine
First Deployment Type with requirement met will be started
29
Deployment
Microsoft Confidential
Deployment
Replaces “Advertisement” from Configuration Manager 2007
Created when an Application is deployed to a Collection
You can only deploy an Application to a Collection once
Deployment settings
Action
Install , Uninstall
Purpose
Required
Available
Available with approval
Scheduling
User Experience
Software Center notifications
Allow Computer Restart or Install/Uninstall outside of Maintenance
window
Alerts
31
Simulate Deployment
Goal – build customer trust in moving to state based dynamic
applications
Did I do Detection Method right? Did I get rules/relationships right?
What will my Deployment Type mix be?
What it does - runs application as required in “rules only” mode
No content download, no execution of Deployment Type
Results – what would the system have done?
Processes Detection Method, requirement rules, dependencies and
supersedence
Does NOT simulate the install!
Guidance
Create simulation for an app, then delete Deployment after results
These rules are processed ongoing and will impact scale/performance
It’s a REAL piece of policy – so may collide with other policies
Simulate deploy a superseding application – may have impact on user
experience and compliance reporting
32
Deployment Monitoring
Used to monitor the deployment of all software (software
updates, compliance settings, applications, task sequences,
packages and programs) by using the Monitoring workspace in
the Configuration Manager console
Applications in Configuration Manager support state-based
monitoring
An application deployment state has one of the following
compliance states:
Success
In progress
Unknown
Requirements not met
Error
33
Application Installation
evaluation flow
34
Microsoft Confidential
Application Uninstall
Goals
Consistent, reliable and predictable experience across all deployment
technologies/deployment types (MSI, EXE, App-V, etc.)
Ensure that state-based application deployment includes state-based
removal of software in addition to installation
Admin creates an Uninstall Deployment
Uninstall is a deployment action
The App Model defines an uninstall method for each Deployment Type
of an Application.
Autocreated for AppV Deployment Type
Autocreated for MSI Deployment Type Example - msiexec /x “setup.msi”.
Manual actions for other Deployment Types
An admin defines a specific Collection to target the Uninstall
Deployment to (either users or machines)
If a user or device is the recipient of both an install and uninstall
Deployment, then install wins and the app will not be removed
35
Microsoft Confidential
Application Supersedence
The ability for the admin to create a relationship and declare one
application newer than another previous application. Ultimately
resulting in the newer application replacing the older application
for a user on a device.
Overall goals
Utilize supersedence conceptual models from Software Updates and
Windows Update
Allow the admin to test/pilot newer application, prior to production
release. While permitting the older application to continue to exist for
the majority of users
Allow the admin to eventually halt installations of the older application
and move users to the newer application
Provides the ability in one process to migrate users from one
application version to another version/application
Ability to offer users only the latest release of an app in the application
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
36
Microsoft Confidential
Supersedence Details
Supersedence relationship is defined at both Application and
Deployment Type
Admin first defines the relationship at an application level
Secondly admin maps each Deployment Type of both applications
Supports non-mapped Deployment Types for both the superseded
and superseding application
Supports both upgrade and uninstall of superseded Applications
Relationship Viewer shows supersedence relationships
End User Experience:
User only sees latest application version in Application Catalog (by
default)
Required Applications are always the enterprise’s latest version
Available Applications installed by user can be automatically
updated
37
Microsoft Confidential
Application Catalog
Self-Service Application portal
Shows only applications which are made available not required
For applications deployed to Users
Browse and search for software
Fully localized for site and applications
Search via category or name
Install Software
Direct self-installation from application catalog
Leverages full infrastructure for content and status
Automatic installation upon approval
Request Applications
Request approval for software
View request history
38
Microsoft Confidential
Installation from Application Catalog
1
2
3
4
5
6
39
• User clicks “install” on Catalog item
• Web site checks user’s permissions to install
• Web site requests Client ID from Configuration
Manager client agent and passes it to Site server
• Server creates policy for the specified client and
app and passes it to client
• Client agent evaluates requirements from the
policy and initiates installation
Melissa
• Client agent completes installation process and
reports status
Microsoft Confidential
5
Software Center
Replaces “Run Advertised Programs” Control Panel
Applet
Allows users to run and see the status of Application
Deployment, Software Updates and Operating System
Deployment
Allows users to change behavior of the Configuration
Manager Client
Business hours
Power Management
Computer Maintenance
Remote Control
Remote Control and Power Management settings can be
overridden by the Client agent settings in the
Administrator Console
40
Microsoft Confidential
Software Center (continued)
41
Microsoft Confidential
New in Configuration Manager 2012 Sp1
Application Catalog – If the Client Policy client settings
“Enable user policy on clients” is set to No then users can
no longer install applications from the Application Catalog.
Software Update Randomization – Disable deadline
randomization option under Computer Agent settings to
remove 2 hour randomization for required Software
Updates and Applications.
App-V – Enable virtual applications to share the same file
system and registry on client computers. This will allow
applications that are in the same virtual environment to
share data.
42
Microsoft Confidential
New in Configuration Manager 2012 Sp1
New Deployment types
For Windows 8 applications (support of .appx files) and links to the
Windows Store.
To deploy virtual applications that you have created by using App-V
5.0.
To deploy applications to Mac computers that run the
Configuration Manager client.
For mobile devices when you use the Windows Intune connector
and users download the apps from the new self-service portal for
mobile devices.
Windows Phone 8
Windows RT
iOS/Android
43
Microsoft Confidential
New in Configuration Manager 2012 Sp1
Windows Embedded devices
You can control the behavior of the write filter* when you
deploy applications and packages/programs using the new
feature “Commit changes at deadline or during a
maintenance windows (requires restarts)”.
44
Microsoft Confidential
Server Log Files
Distmgr.log: primary log file for creation, modification,
deletion and distribution of content
Pkgxfermgr.log: Package transfer manager sends/copies
bits from primary site to remote distribution point
Sender.log: sends/copies content bits between sites
Despooler.log: receives content bits from another site
45
Microsoft Confidential
Useful Client Log Files
Software Center: SC*.log
Policy Retrieval from site: Policyagent.log
High level info about DCM Baselines
DCMAgent.log
Info about download, store and accesing baselines
CIAgent.log
High level info about applicability of Application / Deployment
Type
AppIntentEval.log, Appenforce.log
Check Maintenance Windows
MaintenanceCoordinator.log
Info Detection Methods and install/uninstall specific failures
AppProvider.log
ContentTransferManager.log, Locationservices.log and CAS.log
46
Microsoft Confidential
Module Review
1. Name two new features of Application Development.
2. What is the Distribution Point Content Library?
•
What are the three main components?
3. Does Legacy Software Distribution support App-V
deplyments?
4. How many times can you deploy a collection?
5. Software Center allows users take what action(s)?
47
Microsoft Confidential
Module Summary
In this module, you learned:
Distribution Point concepts
Legacy Software distribution concepts
Application Deployment concepts
About the Software Center and Application Catalog
How to configure Software Distribution and Application
Deployment
48
Microsoft Confidential
Lab: Legacy Software Distribution and Application
Deployment
Scenario
This lab will provide you handson experience with Legacy
Software Distribution and
Application Deployment.
Goals
Create a legacy Software Distribution
Create an Application Deployment
Required/available
Install/uninstall intent
Simulated deployment
Review Software Center
Review Application Catalog
49
Microsoft Confidential