Managing Novell Linux Desktop
with Novell ZENworks® Linux Management

Martin Buckley

Director of Product Management

Novell Resource Management

Ted Haeger

Director of Marketing

Novell Linux Desktop

Goal for this Session
Assuring Success for You and Your Organization

Understand how to ensure a successful deployment

Find or make packages for Novell Linux Desktop

This session will help you to:

1

Identify best-fit Scenarios for Novell Linux Desktop

Create pattern deployments of Novell Linux Desktop

Manage Updates with ZENworks Linux Management

Roll out desktop applications with ZENworks Linux Management

2

3

4

5

6

Introduction to
Novell Linux Desktop

Novell Linux Desktop 9
Overview

Novell Linux Desktop 9 is a desktop operating system and office-productivity environment that enables businesses to use Linux and open source with confidence.

Complete Business Productivity Suite
for the most important business tasks

Enterprise deployment and maintenance features
cut costs with pattern-based installs

Powered by SUSE LINUX
ensuring high performance, security and reliability

Backed by Novell
helping businesses deploy Linux with confidence

Enterprise Desktop User Profiles

Deployment Types

Fixed-
Function
Workstation

Call center

Shop floor

Trader
workstation

Engineering
Workstation

CAD, EDA

Animaiton

UNIX workstation
replacements

64 bit OS

Deskless
PC User

Infrequent PC
use

Shared PCs

Read-only
documents

IT
Professional

Developer

IT Administration

Webmaster

Corporate
Power
User

Content
contributors

Number cruncher

MS-Access user

Legal

Field sales

Linux desktop

future market

(2-5 years)
Linux desktop

maturing market

(< 2 years)

User Assessment is
critical:

Application

Hardware

Network services

File formats

Desktop OS

functionality and application need

Corporate
PC User

General purpose
desktop use

LOB application
user

Identifying Practical Uses
for Novell Linux Desktop

Winning with Novell Linux Desktop

To succeed in your organization focus on getting early wins:

Begin roll-outs as controlled pilots

Socialize reasoning behind Linux adoption and specific project objectives

Assess whether they have special application and hardware needs

Analyze your potential cost savings

Identify user groups that make best candidates for Novell Linux Desktop

General Knowledge Workers

Technical Workstations

CRM

Inventory Management

Point
of Sale

Shop Floor

Business Appliances

Engineering, CAD, EDA

Scientific Research

Desktops

Systems Administration

Development

Work with Customers
Assessment is Critical to Success

Linux desktops aren't for everyone

User assessment considerations:

Application needs

Hardware requirements

Network services

File formats

General categories emerging

Limited function workstations

Technical workstations

etc.

Novell Linux Desktop
Identify Target User Communities

Have minimal allegiance to Windows* / MS Office

Have limited dependence on IE

Do not rely on Windows-only applications

Do not present mutiny risk

Identify groups of users who

Novell Linux Desktop
Identify Target User Communities

Have minimal allegiance to Windows* / MS Office

Have limited dependence on IE

Do not rely on Windows-only applications

Do not present mutiny risk

Identify groups of users who

Novell Linux Desktop
Identify Target User Communities

Have minimal allegiance to Windows* / MS Office

Have limited dependence on IE

Do not rely on Windows-only applications

Do not present mutiny risk

Identify groups of users who

Novell Linux Desktop
Target User Type Recommendations

Transactional Workers (Structured Task Workers)

Require just two or three applications to perform their job duties (word processor, spreadsheet, email, browser)

Receptionist, Lower-level administrative personnel, call center agents, insurance claims processor, advanced data-entry worker, managerial task worker, etc.

UNIX* (Technical Workstation Replacement)

Technical workers whose current job functions are met using UNIX workstations

Software Developer, Computer-Aided Design (CAD), Electronic Design Automation (EDA), Other Compute-heavy Operations

Early Adopters (Linux* Supporters)

Typically technical individuals – often in IT or engineering organizations – who are interested in experimenting with Linux on the desktop

Novell Linux Desktop
Quantifying the Value Proposition

Hard ROI factors

Operating system cost savings

Office suite cost savings

Soft ROI factors

Focus: streamlined machines outfitted for getting work done provide fewer time-wasters and distractions (Instant messages or solitaire)

Assessment Criteria

What applications would be required? Do the right ISV's support it? Are there OSS alternatives?

What lock-downs work best?

Transactional Workers

Novell Linux Desktop
Quantifying the Value Proposition

Hard ROI factors

Hardware cost savings

Software cost savings (in cases of dual-machined desktops)

Soft ROI factors

UNIX-based workers are generally more independent, require less intrusive management; you can use ZENworks Linux Management to create a self-serve environment

Assessment Criteria

What applications would be required? Do the right ISV's support it? Are there OSS alternatives?

What lock-downs work best?

UNIX Workstations

Novell Linux Desktop
Quantifying the Value Proposition

Early Adopters

Hard ROI factors

Hardware cost savings

Software cost savings

Soft ROI factors

Employee participation

Creates departmental champions for next wave of deployments

Assessment Criteria

Users typically self-enroll in these skunkworks-style pilots

Review

In this section, we discussed:

The need for socializing the change and keeping pilots controlled to a winnable scope

Identifying the right target users

Determining where ROI can be achieved

Assessing user needs

Making Patterned Deployments with AutoYaST and ZENworks 7
Linux Management

Deploying for Success
Using Patterned Deployments

Once you have properly assessed your user needs, then you can tailor Novell Linux Desktop

Novell Linux Desktop
out of the box
is generalized

You want
Novell Linux Desktop
optimized
to your requirements

AutoYaST can help!

AutoYaST
Steps for Making a Patterned Deployment

Install Novell Linux Desktop on a target workstation

Install exactly the packages needed

Configure Novell Linux Desktop

Change and features to how you need them (wallpapers, menus, colors, icons, etc.)

Install any RPM packages that did not come with Novell Linux Desktop

Create patterned deployment (see next slide)

Tools > Create Reference Profile

Deploy! (with all usual care)

1

2

3

4

Test the patterned deployment

5

Screenshots for AutoYaST

1

2

3

4

ZENworks Imaging

ZENworks 7 Linux Management includes the ability to cleanly deliver Novell Linux Desktop to workstations

Policy Enabled AutoYaST

ZENworks Imaging

NLD

Policy Enabled AutoYaST

ZENworks Imaging

Novell Linux Desktop
and Novell Resource Management

Novell Linux Desktop
and Novell Resource Management

In this section we'll cover:

Getting updates for Novell Linux Desktop from Novell

Controlling desktop updates with ZENworks Linux Management

Deploying and updating applications using ZENworks Linux Management

Handling packages (RPM's)

Novell Linux Desktop
Getting Updates from Novell

Activated workstations get their updates from...

update.novell.com

Hosted

Server

update.novell.com

Novell Linux Desktop
As Scale Increases, Control Decreases

But too many workstations lead to issues

Each arrow shown represents a manual update

One package conflict hits whole deployment

Novell controls updates

update.novell.com

Hosted

Server

Three fundamental concepts have made ZENworks the industry leader:

The ZENworks experience

Policy-Driven Automation

Managing the complete desktop lifecycle

Enabling your #1 asset - PEOPLE

Linux lifecycle management
Birth to Retirement

ZENworks 7 Linux Management
architecture

database

TED

managed

devices

connectivity

ZENworks Linux Management
Provides Control for Muliple Workstations

update.novell.com

Hosted

Server

ZENworks

Linux

Management

Server

ZENworks Linux Management
Managing in-house Applications

Use ZENworks Linux Management to deploy applications

ZENworks

Linux

Management

Server

CAD

application

Finance

application

Anti-virus

application

ZENworks Linux Management
Configuration and lockdown by policy

ZENworks

Linux

Management

Server

Dallas design team

San Diego call center

Policy

Policy

Review

In this presentation, we have covered:

How to skin a cat

Old dog new tricks

Eight ways until Tuesday

As you begin to develop your plans for

As you begin to develop your plans for

As you begin to develop your plans for

Each arrow shown represents a manual update

that means a lot of sneakerwork to get an update done

Should you automate, or have end users do perform the updates?

No because...

One package conflict hits whole deployment

Rarely would a package conflict with the base install, but what about added packages, like your applications?

Novell controls updates

This model does not scale well...you need control over your own deployment

So what does ZENworks do? To answer that question, there are three fundamentals to understand.

Policy-Driven Automation

Enabling the Digital Identity

Managing the complete Workstation Lifecycle

Each of these represents significant business benefits; all together, they define why ZENworks for Desktops has come to lead the industry in Desktop Management

Each arrow shown represents a manual update

that means a lot of sneakerwork to get an update done

Should you automate, or have end users do perform the updates?

No because...

One package conflict hits whole deployment

Rarely would a package conflict with the base install, but what about added packages, like your applications?

Novell controls updates

This model does not scale well...you need control over your own deployment

Each arrow shown represents a manual update

that means a lot of sneakerwork to get an update done

Should you automate, or have end users do perform the updates?

No because...

One package conflict hits whole deployment

Rarely would a package conflict with the base install, but what about added packages, like your applications?

Novell controls updates

This model does not scale well...you need control over your own deployment

Each arrow shown represents a manual update

that means a lot of sneakerwork to get an update done

Should you automate, or have end users do perform the updates?

No because...

One package conflict hits whole deployment

Rarely would a package conflict with the base install, but what about added packages, like your applications?

Novell controls updates

This model does not scale well...you need control over your own deployment

Novell Corporate Presentation Template 2005

2003-12-08T12:43:39