This manual is protected under Novell intellectual property rights. By reproducing, duplicating or
distributing this manual you explicitly agree to conform to the terms and conditions of this license
agreement.
This manual may be freely reproduced, duplicated and distributed either as such or as part of a bundled
package in electronic and/or printed format, provided however that the following conditions are fullled:
That this copyright notice and the names of authors and contributors appear clearly and distinctively
on all reproduced, duplicated and distributed copies. That this manual, specically for the printed
format, is reproduced and/or distributed for noncommercial use only. The express authorization of
Novell, Inc must be obtained prior to any other use of any manual or part thereof.
For Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell
.com/company/legal/trademarks/tmlist.html. * Linux is a registered trademark of
Linus Torvalds. All other third party trademarks are the property of their respective owners. A trademark
symbol (®, ™ etc.) denotes a Novell trademark; an asterisk (*) denotes a third party trademark.
All information found in this book has been compiled with utmost attention to detail. However, this
does not guarantee completeaccuracy. Neither Novell, Inc., SUSE LINUX Products GmbH, the authors,
nor the translators shall be held liable for possible errors or the consequences thereof.
This guide is intended for use by professional network and system administrators during
the actual planning, deployment, conguration, and operation of SUSE Linux Enterprise®. As such, it is solely concerned with ensuring that SUSE Linux Enterprise is
properly congured and that the required services on the network are available to allow
it to function properly as initially installed. This guide does not cover the process of
ensuring that SUSE Linux Enterprise offers proper compatibility with your enterprise's
application software or that its core functionality meets those requirements. It assumes
that a full requirements audit has been done and the installation has been requested or
that a test installation, for the purpose of such an audit, has been requested.
This guide contains the following:
Deployment
Before you install SUSE Linux Enterprise, choose the deployment strategy and
disk setup that is best suited for your scenario. Learn how to install your system
manually, how to use network installation setups, and how to perform an autoinstallation. Congure the installed system with YaST to adapt it to your requirements.
Administration
SUSE Linux Enterprise offers a wide range of tools to customize various aspects
of the system. This part introduces a few of them.
System
Learn more about the underlying operating system by studying this part. SUSE
Linux Enterprise supports a number of hardware architectures and you can use this
to adapt your own applications to run on SUSE Linux Enterprise. The boot loader
and boot procedure information assists you in understanding how your Linux system
works and how your own custom scripts and applications may blend in with it.
Services
SUSE Linux Enterprise is designed to be a network operating system. SUSE®
Linux Enterprise Desktop includes client support for many network services. It
integrates well into heterogeneous environments including MS Windows clients
and servers.
Security
This edition of SUSE Linux Enterprise includes several security-related features.
It ships with Novell® AppArmor, which enables you to protect your applications
by restricting privileges. Secure login, rewalling, and le system encryption are
covered as well.
Troubleshooting
SUSE Linux Enterprise includes a wealth of applications, tools, and documentation
should you need them in case of trouble. Some of the most common problems that
can occur with SUSE Linux Enterprise and their solutions are discussed in detail.
1Feedback
We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the
bottom of each page of the online documentation and enter your comments there.
2Documentation Updates
For the latest version of this documentation, see the SUSE Linux Enterprise Desktop
Web site [http://www.novell.com/documentation/sled10/index
.html].
3Additional Documentation
For additional documentation on this product, refer to http://www.novell.com/
documentation/sled10/index.html:
GNOME User Guide
A comprehensive guide to the GNOME desktop and its most important applications.
KDE User Guide
A comprehensive guide to the KDE desktop and its most important applications.
xivDeployment Guide
Novell AppArmor Administration Guide
An in-depth administration guide to Novell AppArmor that introduces application
connement for heightened security in your environment.
For a documentation overview on the SUSE® Linux Enterprise Server product, refer
to http://www.novell.com/documentation/sles10/index.html. The
following manuals are exclusively available for SUSE Linux Enterprise Server:
Start-Up Guide
Basic information about installation types and work ows.
Architecture-Specic Information
Architecture-specic information needed to prepare a SUSE Linux Enterprise
Server target for installation.
Installation and Administration
In-depth installation and administration for SUSE Linux Enterprise Server.
Novell AppArmor Administration Guide
An in-depth administration guide to Novell AppArmor that introduces application
connement for heightened security in your environment.
Storage Administration Guide
An introduction to managing various types of storage devices on SUSE Linux Enterprise.
Heartbeat Guide
An in-depth administration guide to setting up high availability scenarios with
Heartbeat.
Novell Virtualization Technology User Guide
An introduction to virtualization solutions based on SUSE Linux Enterprise and
the Xen* virtualization technology.
Many chapters in this manual contain links to additional documentationresources. This
includes additional documentation that is available on the system as well as documentation available on the Internet.
About This Guidexv
4Documentation Conventions
The following typographical conventions are used in this manual:
• /etc/passwd: lenames and directory names
• placeholder: replace placeholder with the actual value
• PATH: the environment variable PATH
• ls, --help: commands, options, and parameters
• user: users or groups
•
Alt, Alt + F1: a key to press or a key combination; keys are shown in uppercase as
on a keyboard
•
File, File > Save As: menu items, buttons
•
Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a
chapter in another manual.
xviDeployment Guide
Part I. Deployment
Planning for SUSE Linux
Enterprise Desktop
This chapter is addressed mainly to corporate system administrators who face the task
of having to deploy SUSE® Linux Enterprise Desktop at their site. Rolling out SUSE
Linux Enterprise Desktop to an entire site should involve careful planning and consideration of the following questions:
For which purpose will the SUSE Linux Enterprise Desktop workstations be used?
Determine the purpose for which SUSE Linux Enterprise Desktop should be used
and make sure that hardware and software able to match these requirements are
used. Consider testing your setup on a single machine before rolling it out to the
entire site.
How many workstations should be installed?
Determine the scope of your deployment of SUSE Linux Enterprise Desktop. Depending on the number of installation planned, consider different approaches to
the installation or even a mass installation using SUSE Linux Enterprises unique
AutoYaST technology. For more information about this subject, refer to Chapter 2,
Deployment Strategies (page 7).
How do you get software updates for your deployment?
All patches provided by Novell for your product are available for download to
registered users. Register and nd the patch support database at http://www
.novell.com/suselinuxportal.
1
Do you need help for your local deployment?
Novell provides training, support, and consulting for all topics around SUSE Linux
Enterprise Desktop. Find more information about this at http://www.novell
.com/products/desktop/.
Planning for SUSE Linux Enterprise Desktop3
1.1Hardware Requirements
SUSE Linux Enterprise Desktop requires certain minimum hardware requirements to
be met before you can successfully install and run SUSE Linux Enterprise Desktop. A
minimum installation of SUSE Linux Enterprise Desktop containing the most basic,
essential software and a very minimalistic graphical user interface requires at least:
• Intel* Pentium* III, 500 MHz
• 256 MB of physical RAM
• 800 MB of available disk space
• 800 x 600 display resolution
For a standard installation of SUSE Linux Enterprise Desktop including the desktop
environment of your choice (GNOME or KDE) and a wealth of applications, the following conguration is recommended:
• Intel Pentium IV, 2.4 GHz or higher or any AMD64 or Intel 64 processor
• 1–2 physical CPUs
• 512 MB physical RAM or higher
• 1024 x 768 display resolution (or higher)
1.2Reasons to Use SUSE Linux
Enterprise Desktop
Let the following items guide you in your selection of SUSE Linux Enterprise Desktop
and while determining the purpose of the installed systems:
Wealth of Applications
SUSE Linux Enterprise Desktop's broad offer of software makes it appeal to both
professional users in a corporate environment and to home users or users in smaller
networks.
4Deployment Guide
Ease of Use
SUSE Linux Enterprise Desktop comes with two enterprise-ready desktop environments, GNOME and KDE. Both enable users to comfortably adjust to a Linux
system while maintaining their efciency and productivity. To explore the desktops
in detail, refer to GNOME User Guide and KDE User Guide.
Support for Mobile Users
With the NetworkManager technology fully integrated into SUSE Linux Enterprise
Desktop and its two desktop environments, mobile users will enjoy the freedom
of easily joining and switching wired and wireless networks.
Seamless Integration into Existing Networks
SUSE Linux Enterprise Desktop was designed to be a versatile network citizen. It
cooperates with various different network types:
Pure Linux NetworksSUSE Linux Enterprise Desktop is a complete Linux
client and supports all the protocols used in traditional Linux and Unix* environments. It integrates well with networks consisting of other SUSE Linux or SUSE
Linux Enterprise machines. LDAP, NIS, and local authentication are supported.
Windows NetworksSUSE Linux Enterprise Desktop supports Active Directory
as an authentication source. It offers you all the advantages of a secure and stable
Linux operating system plus convenient interaction with other Windows clients
and means to manipulate your Windows user data from a Linux client. Explore
this feature in detail in Chapter 12, Active Directory Support (page 303).
Windows and Novell NetworksBeing backed by Novell and their networking
expertise, SUSE Linux Enterprise Desktop naturally offers you support for Novell
technologies, like GroupWise, Novell Client for Linux, and iPrint, and it also offers
authentication support for Novell eDirectory services.
Application Security with Novell AppArmor
SUSE Linux Enterprise Desktop enables you to secure your applications by enforcing security proles tailor-made for your applications. To learn more about Novell
AppArmor, refer to http://www.novell.com/documentation/
apparmor/.
Planning for SUSE Linux Enterprise Desktop5
Deployment Strategies
There are several different ways to deploy SUSE® Linux Enterprise. Choose from
various approaches ranging from a local installation using physical media or a network
installation server to a mass deployment using a remote-controlled, highly-customized,
and automated installation technique. Select the method that best matches your requirements.
TIP: Using Xen Virtualization with SLED
You may use the Xen virtualization technology to test virtual instances of SUSE
Linux Enterprise Desktop prior to rolling it out to real hardware. You could also
experiment with basic Windows*-in-SLED setups. For more information about
the virtualization technology available with SUSE Linux Enterprise, refer to
If your deployment of SUSE Linux Enterprise only involves 1 to 10 workstations, the
easiest and least complex way of deploying SUSE Linux Enterprise is a plain manual
installation as featured in Chapter 3, Installation with YaST (page 17). Manual installa-
tion can be done in several different ways depending on your requirements:
2
Installing from the SUSE Linux Enterprise Media (page 8)
Consider this approach if you want to install a single, disconnected workstation.
Deployment Strategies7
Installing from a Network Server Using SLP (page 8)
Consider this approach if you have a single workstation or a small number of
workstations and if a network installation server announced via SLP is available.
Installing from a Network Server (page 9)
Consider this approach if you have a single workstation or a small number of
workstations and if a network installation server is available.
Table 2.1
Tasks Requiring Manual Interaction
Details
Table 2.2
Installation Source
Installing from the SUSE Linux Enterprise Media
Installing from a Network Server Using SLP
SUSE Linux Enterprise media kitInstallation Source
• Inserting the installation media
• Booting the installation target
• Changing media
• Determining the YaST installation scope
• Conguring the system with YaST system
NoneRemotely Controlled Tasks
Section 3.1.2, “Installing from the SUSE Linux Enterprise Media” (page 18)
Network installation server holding the SUSE Linux
Enterprise installation media
Tasks Requiring Manual
Interaction
8Deployment Guide
• Inserting the boot disk
• Booting installation target
• Determining the YaST installation scope
• Conguring the system with YaST
None, but this method can be combined with VNCRemotely Controlled Tasks
Details
Table 2.3
Installation Source
Tasks Requiring Manual
Interaction
Details
Installing from a Network Server
Section 3.1.3, “Installing from a Network Server Using
SLP” (page 19)
Network installation server holding the SUSE Linux
Enterprise installation media
• Inserting the boot disk
• Providing boot options
• Booting the installation target
• Determining the YaST installation scope
• Conguring the system with YaST
None, but method can be combined with VNCRemotely Controlled Tasks
Section 3.1.4, “Installing from a Network Source without SLP” (page 19)
2.2Deploying up to 100 Workstations
With a growing numbers of workstations to install, you certainly do not want to install
and congure each one of them manually. There are many automated or semiautomated
approaches as well as several options to perform an installation with minimal to no
physical user interaction.
Before considering a fully-automated approach, take into account that the more complex
the scenario gets the longer it takes to set up. If a time limit is associated with your deployment, it might be a good idea to select a less complex approach that can be carried
out much more quickly. Automation makes sense for huge deployments and those that
need to be carried out remotely.
Deployment Strategies9
Choose from the following options:
Simple Remote Installation via VNC—Static Network Conguration (page 11)
Consider this approach in a small to medium scenario with a static network setup.
A network, network installation server, and VNC viewer application are required.
Simple Remote Installation via VNC—Dynamic Network Conguration (page 11)
Consider this approach in a small to medium scenario with dynamic network setup
through DHCP. A network, network installation server, and VNC viewer application
are required.
Remote Installation via VNC—PXE Boot and Wake on LAN (page 12)
Consider this approach in a small to medium scenario that should be installed via
network and without physical interaction with the installation targets. A network,
a network installation server, network boot images, network bootable target hardware, and a VNC viewer application are required.
Simple Remote Installation via SSH—Static Network Conguration (page 12)
Consider this approach in a small to medium scenario with static network setup.
A network, network installation server, and SSH client application are required.
Remote Installation via SSH—Dynamic Network Conguration (page 13)
Consider this approach in a small to medium scenario with dynamic network setup
through DHCP. A network, network installation server, and SSH client application
are required.
Remote Installation via SSH—PXE Boot and Wake on LAN (page 14)
Consider this approach in a small to medium scenario that should be installed via
network and without physical interaction with the installation targets. A network,
a network installation server, network boot images, network bootable target hardware, and an SSH client application are required.
Simple Mass Installation (page 14)
Consider this approach for large deployments to identical machines. If congured
to use network booting, physical interaction with the target systems is not needed
at all. A network, a network installation server, a remote controlling application
such as a VNC viewer or an SSH client, and an AutoYaST conguration prole
are required. If using network boot, a network boot image and network bootable
hardware are required as well.
10Deployment Guide
Rule-Based Autoinstallation (page 15)
Consider this approach for large deployments to various types of hardware. If
congured to use network booting, physical interaction with the target systems is
not needed at all. A network, a network installation server, a remote controlling
application such as a VNC viewer or an SSH client, and several AutoYaST conguration proles as well as a rule setup for AutoYaST are required. If using network
boot, a network boot image and network bootable hardware are required as well.
Table 2.4
Preparations• Setting up an installation source
Drawbacks• Each machine must be set up individually
Details
Table 2.5
Simple Remote Installation via VNC—Static Network Conguration
NetworkInstallation Source
• Booting from the installation media
Remote: VNCControl and Monitoring
small to medium scenarios with varying hardwareBest Suited For