/
The Changing Face of Deployment The Changing Face of Deployment

The Changing Face of Deployment - PowerPoint Presentation

celsa-spraggs
celsa-spraggs . @celsa-spraggs
Follow
359 views
Uploaded On 2018-10-30

The Changing Face of Deployment - PPT Presentation

CSM Event 22 nd April 2008 Keith Baker Deployment Specialist Microsoft UK Session agenda Customer goals and challenges Current status Changing Perspectives How does this relate to you ID: 703618

microsoft deployment processes management deployment microsoft management processes bau cost infrastructure image costs build user installation tools server clients

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "The Changing Face of Deployment" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1
Slide2

The Changing Face of Deployment CSM Event 22nd April 2008

Keith BakerDeployment SpecialistMicrosoft UKSlide3

Session agendaCustomer goals and challenges

Current statusChanging PerspectivesHow does this relate to you?

What’s changed ?

Available Resources

Deployment

processes and best

practices

QuestionsSlide4

Customer goals and challengesSlide5

Key Environmental GoalsWhat customers want…

Increase Operational Agility

Growth

Competitive edge

Customer service

Regulatory compliance

Device management

Varying skill sets

Mobility

Reduce Costs and Complexity

Improve Security

PC maintenance

Server sprawl

Legacy platforms

Deployment and maintenance

Identity management

Software updates

Malicious attacks, viruses, spam, etc.

Evolving threats

Patch management, virtual private network, etc.

Secure accessSlide6

Customer challenges What customers are experiencing…

Applications

Operating System Compatibility

Inter Application Contention

Testing overhead

Inconsistent and ad hoc user installations

High Cost

of administration

Local User Data and Settings

Deployment Processes

Data Loss

Extended

rebuild

times

Inconsistent manual backup

/ restore

processes

Regulatory compliance issues

I

nfrastructure and tools not implemented

Difficult to maintain and update when things change

Inconsistency and variationsSlide7

Current statusSlide8

Where to focus ?Slide9

Source: IDC 2002, Microsoft Primary Quantitative Research. 400 30-minute phone surveys of IT professionals in data centers with 25 or more servers

More than 60% of

TCO

over a 5-year period is driven by people costs.

0

10

20

30

40

50

60

70

Staff Costs

Downtime

Training

Software

Hardware

The Manual Reality

People and processes make the biggest differenceSlide10

Changing PerspectivesSlide11

Microsoft WIM imaging technologyBasis for current Microsoft platform’s installation – common to Client and Server, applicable to recent legacy platforms

Removes need for third party imaging toolsSmall footprint, network efficientFile based and so non destructiveAbility to modify elements of the build at the point of delivery – speed and flexibility

WinPE

2.1

Replacement for DOS Boot environment.

New tool set

Single configuration file for install and build, image manipulation tools etc.

Things have changed

Technology EnablersSlide12

So I need some tools then...Well, yes and noThe old adage is still true, a tool is only as good as the overall process in which you use

itNew tool sets bring new possibilities, so don’t just look for ways to fit them in to the old processes.Step back, look at best practice guidance, market trends, see what leaders are doing or planning to do. They may be bigger, have more resources, or smaller and more agile etc, but you can still cherry pick the best concepts and adapt

.

The key point is to avoid traditional short term deployment focused decisions. Examine where your real costs lie over the life of a machine and focus decisions on those.Slide13

Traditional Deployment ObjectivesAre they still the right choices?Speed - what’s the quickest way to put the operating system and a core group of applications on to a machine

Cost – Deployment is expensive. Having the fastest build time means more machines in a given timeframe so the cost are lower. This is the primary goal.Build – the “corporate build” has to be extensively engineered as it will form the platform for a number of years and so be designed to cope with all of the needs during this period. (In essence, making many of the decisions for this whole period, today). Slide14

Business As Usual ObjectivesWhat are the priorities here?Managing Change – that image you started deploying last week – two of the apps need changing to new versions and there is another app to add

Patching – we spend longer installing all the current patches than it takes to do the install in the first placeCost – sending a engineer out each time we need to rebuild a machine is very expensive.New machines – drivers and hardware support is part of the image so we need a new one when machines types are added/updated Build – There are things the business require which aren’t in the build and some things need changing

Testing overhead – changes take too long and cost too much Slide15

Current thinkingMany companies are now focusing on the whole life costs of machines, often in line with a 3 or 5 year refresh cycleDeployment has a cost associated with it, but taken out of the constraints of single financial years budget, it becomes clear that the traditional basis for deployment objectives can lead to substantially greater costs in terms of on going BAU support and maintenance

Focus is now being placed on cost effective BAU processes which encompass the ability to implement deployment of the “Corporate Build” and applications Slide16

How does this relate to you?Slide17

Deployment Vs BAU Management

3-5yrs

BAU

BAU

NT4 Domain

NT4 - 9x Clients

AD

W2K Clients

Point Solution

£

Point Solution

£

Point Solution

£

AD 2003

XP/SP2 Clients

Vista Clients

Office 2007

BAU

3-5yrs

Point Solution

£

Traditional Deployment Approach:

Blinkered A to B solution. Requirement for change will result in........

70 %

of IT Spend

3-5yrsSlide18

Deployment Vs BAU Management

continued...

BAU

BAU

NT4 Domain

NT4 - 9x Clients

AD

W2K Clients

£

£

£

AD 2003

XP/SP2 Clients

Vista Clients

Office 2007

BAU

£

Traditional Deployment Approach

Managed Desktop Environment:

Long term view. Focused on reusability of investment and flexibility

AD 2003

Managed Desktop

BAU

Vista/Office 2007 implementation project utilising reusable

Managed

Desktop Infrastructure componentsSlide19

Build Architectures

User

Applications

Office

Core

Utils

O/S

Monolithic

(

Thick image)

Image

Dynamic Delivery

Advantages

Quick installation times

Minimal Infrastructure

Fast skills acquisition

Well known approach

Disadvantages

High propensity for change

High testing overhead

Inflexible

Large no of images

Does not scale easilySlide20

Build Architectures

Modular

(Thin image)

Image

Dynamic Delivery

Advantages

Flexible

Manageable

Testing overhead reduced

Fewer images required

Disadvantages

Increases build times

Initial set up more complex

Infrastructure requirementsSlide21

Desktop Deployment Cost

Basic

Manual

Deployment

$1,300

per PC

USMT, ACT, WinPE, WDS, ImageX, WIM

Standardised

Light

Touch Deployment

~

$580

per PC

Deployment automation with Zero Touch

(SCCM, SCOM

)

Rationalised

Zero

Touch Based Deployment

$230

per PC

Source:

“Core Infrastructure Optimization Research, Survey of Findings

,”

IDC,

June 2007Slide22

Zero-Touch

Heavy-Touch

x

Limited best practices - steep deployment learning curves

Basic infrastructure and limited compatibility inventory

Repetitive manual processes result in high labour costs and inconsistent results

Manual Processes

Light-Touch

Semi-Automated Processes

Best practices and end-to-end prescriptive guidance enable “light-touch” deployments

Standardised

infrastructure and central HW/SW inventory for more predictable and reliable deployments

Semi-automated processes deliver lower

BAU

and support

costs reducing ongoing

TCO

Automated Processes

Best

practices and lifecycle management guidance enable ‘zero touch’ deployment, even in remote

locations

Rationalised

infrastructure and dynamic inventory allows IT to align with business

needs

Automated

processes deliver lowest

BAU

and IT labour costs and highest long term TCO savings

Cost: <

$230/PC

*

Cost: >

$1300/PC

*

Cost: ~

$580/PC

*

Reducing

Deployment Cost And Complexity

*

Source:

“Core Infrastructure Optimization Research, Survey of Findings

,”

IDC,

June 2007Slide23

Basic

Standardised

Rationalised

Dynamic

Cost Center

More Efficient Cost Center

Managed IT

infrastructure

with limited

automation

Request driven management

Managed and

Consolidated IT

infrastructure

with maximum

Automation

SLA accountability,

change management

Fully automated

management,

dynamic resource

usage, business-

linked service level agreements (SLAs)

Business Enabler

Strategic Asset

Uncoordinated, manual infrastructure

Problem driven management

Structured approach:

Not trying to run before you can walk

Core Infrastructure Optimization ModelSlide24

What’s Changed ?Slide25

New ToolsSYSPREPSETUP

IMAGEXWindows System Image ManagerPEIMGWindows Deployment ServicesOCSETUPPNPUTIL

WAIK

Bitlocker

Configuration Tools

PKGMGR

BCDEDIT

Application Compatibility

Toolkit 5.0

User State Migration Tool 3.0

Volume Activation ToolsSlide26

Client and Server O/S delivery Single SolutionClient deployment

O/S - Vista (32 and 64 bit), XP (32 and 64 bit)Configuration and settingsApplication installationUser data and settings

Server deployment

O/S – Server 2008, Server 2008 Core, Server 2003

Hardware config (raid, NIC teaming etc.)

Server roles

Application installation

Common tool setSlide27

Tools Replaced For New O/S’sWINNT.EXE and WINNT32.EXE

Replaced by SETUP and imagesMS-DOS boot floppiesUse Windows PE!Setup Manager / NotepadUse Windows System Image Manager for editing XML files

SYSOCMGR

Replaced by OCSETUP, PKGMGR

Remote Installation Services

Replaced by Windows Deployment Services

(retains “legacy support”)

RIPREP and RISETUPSlide28

ChallengesSteep learning curveUnderstand use and capabilities of individual tools, their roles and how they can be used

Current practices may no longer be a good fitMuch of the deployment processes required for new O/S’s can be utilised for their predecessors Opportunity to re evaluate current practicesHow can the best use of this opportunity be made and also minimise the overhead in doing so

Microsoft Deployment Toolkit (MDT) 2008 Solution Accelerator provides help and

guidanceSlide29

Available Resources Slide30

What is MDT2008 ?

A free Solution Accelerator

Download from:

http://www.microsoft.com/deployment

End-to-end guidance, best practices, and tools for efficient planning, building, and deploying

Microsoft

Windows, Office and other apps

Based on real-world experience

Increases automation

Decreases costsSlide31

Detailed Project Guidance and Job Aids

Deployment

Workbench MMC

TechNet Deployment Center

Microsoft Deployment Toolkit 2008

MDT

2008

simplifies

Windows

operating systems and Office deployment, configuration and application installation, includes

comprehensive process guidance, job aids and

tools corresponding

with

each phase

of

the

project

.Slide32

Microsoft Deployment Toolkit:Deployment Scenarios

New ComputerA new installation of the standard platform and pertinent applications are

deployed to a new computer where there is no user data or profile to preserve.

Refresh Computer

Re-image a currently managed machine to

bring it to the current standard platform and including delivery of the pertinent applications or rebuild to

address

an issue.

This scenario includes ability to preserve existing user data and profile(s) on

the

computer.

Replacement Compu

ter

A new installation of the standard

environment

is

deployed to a new or re

provisioned computer, along with pertinent applications plus apply

user data and profile(s) migrated from an existing computer. Slide33

Microsoft Deployment Toolkit:Deployment Methods

Lite Touch Installation (LTI)Deployment without management infrastructureManually initiatedUses network share, Windows Deployment Services, CD/DVD, or USB

Refresh, upgrade, replace, new

computer

Zero Touch Installation

(ZTI)

Uses SMS 2003 OS Deployment Feature

Pack or integrates with SCCM native OS deployment

Scheduled via

SMS or SCCM and is completely

automated

Centrally monitored with Microsoft Operations Manager (MOM) 2005

or System Center Operations Manager (SCOM) Management

Pack

Refresh, replace, new computerSlide34

Microsoft Deployment Toolkit: Advantages

Dynamic driver injection at point of deliveryReduces number of builds requiredFlexibility to cope with new hardware

Reduces management overhead

Build changes at point of delivery based on:

Hardware, Network Location, Mac Address, Machine Name or BIOS Asset

tag using

a Database Lookup

Non

destructive delivery

User state and data never needs

to

leave the machine –

reduces migration time, network load and storage requirements Slide35

BenefitsAutomated builds reduce costs and increase reliabilityDynamic Driver injection based on PnP ids reduces number of builds required for XP and Vista

Vista HAL independence makes a single corporate image a realityStandardisation and consistency reduce support incidents and raise end user satisfactionReduced complexity decreases patching and update cycle times through lower testing overheads

Change management simplified and more responsive to business requirements

SCCM Task

Sequencing

engine provides extensive automation of

LTI

processes enhancing

standardisationSlide36

RoadmapSlide37

Microsoft Deployment ToolkitRoadmapSlide38

QuestionsSlide39
Slide40

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