Running a Successful Linux Desktop Pilot

Ginny Roth

Mike Friesenegger

Network and Systems Specialists

Novell, Inc

What Are We Here For?

After this session you will come away with a plan to successfully design and implement a Novell Linux Desktop pilot.

So, You Wanna Be a Rock Star…

Should We Really Be Doing This?

Assessing Organizational Requirements

Executive Sponsorship

How Do We Pull This Off?

Fear of the Unknown

Feature Set Mapping

Determining Pilot Users

Shall We Get Started?

Planning

Tools

Steps

Should We Really Be Doing This?

Why Linux Desktops in the Enterprise?

Enhanced control and vendor flexibility

Lower cost for software and manageability

Improved security

Assessment is Critical to Success

Today, Linux can fit into target areas

Organizational assessment considerations:

Application needs

Hardware requirements

Network services

File formats

General categories emerging

Kiosks

Special function workstations

Engineering workstations

Verticals (Government, Education)

Assess At An Organizational Level

Applications

Critical Business Apps (i.e. ERP, HR, CRM, Collaboration)

Office Productivity (i.e. MSOffice)

Virus protection

One-offs (ex. MSAccess)

Hardware

Aging Unix Workstations

x86 Refresh Cycles

Network Services

File and Print

Directory Services

Authentication/Authorization

Infrastructure (i.e. cabling, wireless)

Backup

File Formats

Interoperability Standards (i.e XML, PDF, HTML, MSOffice)

Organizational Matrix

Executive Sponsorship

An executive sponsor must be identified prior to the planning and implementation of a successful pilot. Failure to do so will only delay or permanently derail the project.

Benefits of an Executive Sponsor

Project funding

Supports timeframes

Supports key pilot initiatives

Alleviates possible internal resistance

Check out session BUS132, “Selling Your Boss and Your Boss' Boss on Novell Linux Desktop”, for details on ROI and business rational for the Linux desktop.

How Do We Pull This Off?

Administrator Fear of the Unknown

Managing the Desktop

Remote Control

Application Distribution

Patch Management

Provisioning

Help Desk Support

Proactive Documentation and Training

FAQ's

Interoperability

With Existing Infrastructure

Printing

“Mapped Drives”

Authentication

User Fear of the Unknown

Learn Something New

Brainstorm Quickstart Cards, CBT, Classroom Instruction

Linux Desktop Mimics Windows (set expectations ;-) )

Can I Do My Job Like I Do In Windows?

Office Productivity

Email/PDA Sync

Shortcut Keys

Where Are My Files and Printers?

How Do I Share Information with My Co-Workers?

Sharing Documents (file formats)

User Fear of the Unknown

Communication is Key

What are the company goals in regards to Linux

Why are we making this switch now

How do I get support and help

Will my desktop be secure

Feature Set Mapping

Desktop Look and Feel

Drive Mapping

Printers

Office

Email/IM

Control Panel

Software Update

Burning CD's

Authentication

Determining Pilot Users

Who Are My Users

Remote

Office Workers

Power Users

Fixed Function Workers

What Does Their Work Day Look Like

What Apps Do They Use

Who Do They Work/Share Information With

What Is Their Skill Level

Impacts Training

Self Motivated/Early Adopters

Committed to Providing Feedback

Avoid Users with Heavy MSOffice Requirements

Macros, OLE, Pivot Tables

Pilot Gap Analysis

Shall We Get Started?

Planning

Determine Level of Effort

Determine Goals for Success

Can come from several different sources

Classify and Inventory Apps

Apps that require Terminal Services

Apps that can run native Linux

Apps that need replaced

Apps that can be retired

Apps requiring WINE

Assign Project Roles and Workload Percentage

Project manager

Desktop/Help Desk support

Engineer

Sponsor

More Planning

Determine Level of Effort, continued

Determine Size of Pilot Group

Impacts manual vs automated processes

Establish Timeline

Timeline will affect sample group

Aggressive timeline will affect resources required

Develop Milestones for Pilot Phases

Determine Training Requirements (users, engineers, help desk)

Different requirements for users, engineers and help desk

Consider outside organizations

Quickstart

Should be provided for all users regardless of previous training

Classroom/Lab

CBT

....And More Planning

Determine Level of Effort, continued

Determine Choice of Windows Manager

Gnome (Closely mimics Windows)

KDE (KIOSK Mode)

Both – Consider support implications

Develop Fallback Strategy

Dual Boot

Images

Terminal Server

Document, Document, Document

Formulate Best Practices

Avoids Re-inventing the Wheel

Committed to Providing Feedback

Can Contribute to Training Materials

Tools

YaST Is Your Friend

Provides Graphical Interface for Workstation Configs

Used to configure AutoYast functionality

AutoYast

Provisioning of initial workstations

Re-deployment or upgrades

ZLM

Update Services

Incremental Software Distribution

VNC

Can Assist Help Desk in User Support/Training

Steps

Lab Setup

Provides testing environment for rollout

Allows for training and testing with early adopter users and help desk

Hardware reflects user environment

Decide if you want connected or isolated (will impact work effort)

Lab Infrastructure

Mimics Production Infrastructure

eDirectory, AD, OpenLDAP

PAM, Kerberos, LDAP

OES/NetWare, Windows, Samba

iPrint, Windows, CUPS, Jetdirect

Steps

Lab Infrastructure, continued

Apps

Terminal Server if needed

WINE is an addition to NLD

SLES 9 Server

DNS

DHCP

Distribution Method

AutoYast (PXE/TFTP/HTTP)

Pre-configured CD's

Cloned Hardware Configurations

Use Yast to create repeatable installation

ZLM Server (optional)

Provides automation for updates and patches

Steps

Rollout

Should flow directly from planning and lab implementation

Don't introduce new technologies or apps

Support

Provide multiple channels

Email, phone, IM, Web support pages (example)

Training

Use lab if possible

Be prepared to have help desk provide supplemental training

Communicate, Communicate, Communicate

Company goals

Don't assume everyone has received the message

I Could Use a Little Help Here!

IBM Redpaper

www.redbooks.ibm.com/redbooks/SG246380

Novell Linux Migration Study

www.novell.com/coolsolutions/feature/2294.html

The Future is Open: What OpenDocument Is...

www.groklaw.net/article.php?story=20050130002908154

NLD Pilot

2003-12-08T12:43:39