37
Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Embed Size (px)

Citation preview

Page 1: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin University Deakin Desktop Project Nov 1 - 2011

David Schwarz Technical Architect

Page 2: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Presentation Structure

• History of the Managed Operating Environment

Core Principles• Issues and Constraints• The Deakin Approach• Lessons Learned• The End product

Page 3: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Terminology / Versions

Phoenix Desktop• Windows 2K• XP • Radia• Kix (login script)

Deakin Desktop • Windows 7 x64• App-V• SCCM• Software deployment solution for PC and Mac!

– App-V• Microsoft Application Virtualization 4.6

– SCCM• Microsoft System Centre Configuration Manager 2007

R3

Page 4: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

SOE/MOEs @ Deakin• Phoenix Desktop first deployed 1999• Operating System

Nt 4.01999-2000

Win2k2000-2004

WinXP2002-2012

Win72011-?

Page 5: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

MOEs @ Deakin

Deployment Method

Ghost Image1995-2000

Novadigm EDM 4.02000-2001

Radia 2001-2011

SCCM / App-V2011-?

Page 6: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Current State

• University highly centralized• Distributed support staff supportive of

MOE• Considerable expertise in desktop

management.• Long-term senior management support

of the MOE.• Central and consistent AD domain.• Central SMB file storage

Page 7: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Core Principles

• Ensure all solutions are designed to address valid business needs or issues.

• Use best practice for all infrastructure decisions.

• Reduce complexity in the infrastructure.

• Virtualize where clear benefits exist.

Page 8: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Issues

• Phoenix Desktop Aging– Designed in 2000 – best practice has

changed.– Users ran as Power User, Not Admin– 4% of fleet were laptops – Now 40%

• 25,000 line login script– Printing was peer-to-peer

• HP bought Radia, lost focus for ~4 years on desktops.

Page 9: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Total lifecycle management map

Doesn’t do this

Issues - Radia limitations

Page 10: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Drivers for change

• Reduce costs / Increase efficiency• Better user experience• Increase flexibility of staff, especially

those on Laptops.

Page 11: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

• Strategic decision to move to full PC lifecycle management

Deakin Desktop Project Approach

Page 12: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Pre-Project AnalysisMid 2009• Small project to:-– Request a solution that manages entire

PC life-cycle.– Compare HP with Microsoft.– Made a clear decision as to the way

forward.• Microsoft won – clearly, on cost and

business benefits.• Budget bid for 2010-2011 project

Page 13: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Late 2009 – Early 2010Five-day engagement with Microsoft.• Integration of Microsoft technology

with Deakin infrastructure.• Investigation of technology options.• Deliverable of “Configuration Manager

Conceptual Design and Discussion Paper”

Page 14: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect
Page 15: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Any Questions ?

• Next Section is much more technical

Page 16: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Early 2010• Using output from Microsoft

engagement and local staff knowledge.• Created:-– Project brief,– PID– Technical Specification

• Started looking for staff with appropriate skills

Page 17: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Early 2010Visited UTas and Tasmanian Polytechnic• Tas Poly extremely positive experience

of App-V• Decided to change App-V to not be

integrated with SCCM.• Re-wrote significant part of TechSpec

Page 18: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Mid 2010• Designed and built:-– SCCM servers• Investigated using Isilons as distribution

points– PXE booting • University wide network reconfiguration

– Windows 7 core image• Certified workstations that would run

Windows 7 (and made a mistake, more later)

Page 19: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Mid 2010• Deployed SCCM client to all University

workstations.– Turned on hardware and software

inventory– Got a BA to start analyzing data.– Had heart attack as software inventory

identified 4000 different versions of apps.

Page 20: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Mid 2010• Designed and built:-• App-V servers

• Investigated using Isilons as streaming servers

• Naming schemes for:-• SCCM

• Packages• Collections• Advertisements

• App-V• Packages

Page 21: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Mid – Late 2010• Built interface between App-V and

Identity and Access management system to allow user and group based software provisioning.

• Designed new printer management infrastructure.

Page 22: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Mid-Late 2010• Designed a new five-stage packaging

process– Sourcing– Packaging– QA– UAT– Deployment

• Identified all core software and packaged using new process into SCCM.

Page 23: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Mid-Late 2010• Packaged ~100 labs apps into App-V as

a test.– Vast majority worked as expected– Significantly faster than Radia to

package.– Worked as advertised

Page 24: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Late 2010• Load tested– SCCM Servers• Couldn’t overload the SCCM servers

– App-V servers• Worst case scenario, 1500 workstations

stream SPSS 17 (870 MB package)(That’s 1.3 TB of data to move)• Deployed to all workstations in under 10

minutes (Isilons peaked at 8Gb/s)

Page 25: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Late 2010• Infrastructure build finished, and

signed off by board.• What did we end up with?

Page 26: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect
Page 27: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

Started 2011 Teaching spaces build• Ran for four months Nov -> Feb• One month requirements gathering• Three months packaging• One month debug and performance

tuning

Page 28: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

2011 Labs• Requests for ~160 teaching packages– ~80 App-V– ~80 SCCM

• Upgraded – 2124 lab workstations– 317 presentation workstations

• Win7 deployment over two weekends– ~50% per weekend

Page 29: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Stage 3: Faculty, Institutes and Other Areas DeploymentOriginally planned each deployment to the Faculties, Institutes and Other Areas to be run as a project:• Project Brief• Project Board (Executive, Senior User & Supplier),

Project Assurance and Project Team with detailed roles and responsibilities

• Project Plan• Configuration Document• Training Plan• Communication Plan• Sign-off for each phase, go/no-go point and checkpoint

Page 30: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Stage 3: Faculty, Institutes and Other Areas Deployment• Staff project had deliverables changes– Zero data loss demanded– Project had to review and change

migration process• Realised that we don’t have budget to

deploy to FOIA’s using original plan high touch plan.

• Moved to a pull methodology, pending more budget made available

Page 31: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Stage 3: Faculty, Institutes and Other Areas Deployment• New Process– Pre qualify FOIA by ensuring• On Exchange 2010• All Software is available• Printers configured & tested• Shares identified and setup in GP• Early adopters have run the

environment– Then staff schedule there own

deployment via a webpage.

Page 32: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Deakin Desktop Project Approach

• Now onto rollout for Staff……..• Jimmy you can go here…..

Page 33: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Lessons Learned

• Acer Veriton 1000’s do not run Windows 7– Not supported by Acer– Passed the MS hardware compatibility

test– Caused massive pain, when they

randomly hit 100% processor time.• Vmware ESX is good– Much faster packaging (high disk IO)– Quicker to reset to a known state– Multiple tasks on the go at once

(well….)

Page 34: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Lessons Learned

• Test all driver packages thoroughly, work driver packages into a regular maintenance schedule.

• Contractors are magnificent.• Be adaptive as possible or you will be

left behind

Page 35: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Things to keep in mind

• Ensure that your first major deployment doesn’t have a hard deadline like our Labs rollout.

• Don’t complicate the deployment with non-mandatory additions (ie. 802.1x).

• Only deploy to Windows 7 certified hardware.

• Create master plan at the beginning and stick to it.

Page 36: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

And a demo of it all working together• App-V launch• SCCM deployment• Allocating software for App-V• Folder redirection• Etc,etc

Page 37: Deakin University Deakin Desktop Project Nov 1 - 2011 David Schwarz Technical Architect

Contact details

• David Schwarz – Ph 03 52278938– Email: [email protected]