What do User-Centric deployments mean for OSD NE Ohio System Center User Group February 2012 Jason Condo

Agenda General overview of 2012 console Creating a OS deployment task sequence Distributing content Deploying Creating boot media Adding an unknown device to ConfigMgr for deployment Kicking off the deployment

Agenda – Cont. While deployment runs… What is user-centric deployments Why does is matter to me Software Center Applications with “rules” Sample App to JoeUser Primary Desktop – full install Shared Desktop – App-V download or stream Term Server – App–V stream Completed deployment

2012 Console overview Similarities from 2007 to 2012 Collections Packages OS deployment DCM Reporting Differences All of the above Console is now function based instead of console tree New Applications Software Center Architecture (hierarchy, roles)

OSD in 2012 Good news, it’s pretty much the same Bad news, not everything is obvious and in central place MDT integration – requires MDT 2012 (will be released together) Basically the same some new logic for partitioning drives Application groups have 3 digits and must be converted to 2 digits for ConfigMgr (PACKAGES001 now PACKAGES01) Can deploy whole drive WIMs with multiple partitions

Creating a base image Minimum pre-reqs you need Operating System installation files ConfigMgr Client installation Network share for saving image to Credentials to write to share (service account) Additional Software Updates Applications and/or Packages

Importing an Image Demonstration Previously captured image from ConfigMgr TS Adding image Reviewing details in console

Creating a deployment task sequence Demonstration Creation Distribution Deployment

Creating boot media Adding OSDComputerName to make boot media prompt for PC name

Kicking off a deployment Demonstration Boot media Adding device resource Assigning primary user Initiating the deployment

User-Centric Paradigm Shift More and more the user is being “trained” by the connected world we live in to want to leverage all means possible to do what they need to do. This causes stress on sys admins and security policies who used heavy controls to standardize Survey – how many are being forced to adopt technology your staff, systems, or policies are not ready for?

How does this apply to you for OSD How do you handle reinstall of user apps? Manual Direct membership (goes to every PC) Deploy to user groups (goes to every PC) What kind of deployment type do you do more? REPLACE - prebuild on bench NEW - prebuild on bench REFRESH – in-place Do you do REPLACE instead of REFRESH? Refresh requires application and user mgmt. High level of trust in the solution

Infrastructure Optimization Basic Ad-Hoc Minimal systems Low implementation cost High Support Cost (actual or unseen) High Maintenance No Scalability Low skill level Standard Some Standard hardware Some Standardized Application Some Infrastructure Systems used but not connected Economy of scale Lower support cost Minimal implementation cost (evolution) Cost savings from standardization Not enough time or resources to integrate Minimal maintaining Low - medium skill level required Rationalized Leverage Infrastructure systems Standardization of apps, hardware, tools, users Scalable Low support cost Higher implementation cost Requires some maintenance of standardization Medium - high skill level Dynamic Leverage data/attributes to automate use of infrastructure systems Economies of scale Low support cost High implementation cost Economies of scale for system maintaining High skill level Skill Automation, Standardization Speed and Agility Administration

To leverage User-Centric Understand the User Experience Equation Users “Access Layers” (Devices) Applications State Data Assigning primary devices to users Similar to managing the hardware but enable dynamic changes Requires trust (with controls)

User Experience Equation In some instances these are combined User SCCM Device SCCM Application SCCM Metro State Local Roaming Profiles Web Apps Metro Data Local Folder Redirection Web Apps SharePoint Cloud Storage Private Public User Experience

What are devices? Tablet iPad Phone (Android/iPhone/Windows) Desktop Laptop Device VDI Citrix Terminal Services Laptop Desktop Access Layer App-V Web App Applications Client/Server App Are devices the physical end-point, or should we look deeper? Device concept blurs

Applications Packages Applications Deployment types Dynamics and rules

State Application Settings System Settings Things that apply to an object to make it unique Don’t confuse it with data Data when accessed by the Application + State (configuration of application) should become useful to the user.

Data Information that becomes useful when accessed by an application. Application, state, and access layer provide presentation of data to the user. Word document – following 3 scenarios the data doesn’t change, just the way it is accessed and used. SharePoint 2010 Wordviewer 2010 Microsoft Word 2010

Software Center in ConfigMgr 2012 Device driven installs in the console User applications in the web app Admin approvals Requests for software How does this tie into rumored Windows Store for Windows 8?

Sample Application Deployment JoeUser Computer Temp Workstation Newly Deployed workstation

Wrap up We covered some basics around OSD in ConfigMgr 2012 User Experience Equation Applications vs. packages Demonstrated New system deployment

Questions

Additional Resources OSD OSD Team blog Michael Niehaus blog (MDT, OSD) ConfigMgr 2012 Great Step by Step tutorial of basics at: manager-guides/ TechNet Other Blogs My blog Our User Group Bennett Adelson’s Infrastructure Blog