Novell LINUX ENTERPRISE 11 - SUBSCRIPTION MANAGEMENT TOOL GUIDE... User manual

SUSE Linux Enterprise
Point of Service
www.novell.com11
October02,2009 SUSE Linux Enterprise Point of Service Guide

SUSE Linux Enterprise Point of Service Guide
All content is copyright © 2006- 2009 Novell, Inc.
Legal Notice
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 ful-
lled:
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, specically 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 complete accuracy. Neither Novell, Inc., SUSE LINUX Products GmbH, the authors,
nor the translators shall be held liable for possible errors or the consequences thereof.

Contents
About This Guide vii
1Product Overview 1
1.1 Architecture............................ 1
1.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 ServerTypes ........................... 5
1.4 Images ............................. 13
1.5 SUSE Linux Enterprise Point of Service Deployment . . . . . . . . . . 16
2SUSE Linux Enterprise Point of Service Installation 21
2.1 Installation During the Initial Installation Process . . . . . . . . . . . . 21
2.2 Installation On Top of an Already Installed System . . . . . . . . . . . 22
3Basic Conguration 25
3.1 Setting Up the Administration Server . . . . . . . . . . . . . . . . . 25
3.2 Setting Up the Branch Server . . . . . . . . . . . . . . . . . . . . 27
3.3 Adding a Point of Service Terminal . . . . . . . . . . . . . . . . . . 30
4Setting Up the Administration Server 35
4.1 Administration Server Conguration . . . . . . . . . . . . . . . . . 36
4.2 Initializing the LDAP Directory . . . . . . . . . . . . . . . . . . . 38
4.3 Creating An Ofine Installation Package . . . . . . . . . . . . . . . 40
4.4 Creating Point of Service Images . . . . . . . . . . . . . . . . . . 40
4.5 Copying the Boot Image Files . . . . . . . . . . . . . . . . . . . . 41
4.6 Copying the System Image Files . . . . . . . . . . . . . . . . . . . 43
4.7 What'sNext........................... 45

5Setting Up a Dedicated Image Building Server 47
6Setting Up a Branch Server 49
6.1 Conditions to Congure a Branch Server . . . . . . . . . . . . . . . 50
6.2 Online Branch Server Conguration . . . . . . . . . . . . . . . . . 51
6.3 Ofine Branch Server Conguration . . . . . . . . . . . . . . . . . 53
6.4 Creating Branch Server Objects in LDAP . . . . . . . . . . . . . . . 55
6.5 Downloading Images from the Administration Server . . . . . . . . . . 64
6.6 Starting the Core Script . . . . . . . . . . . . . . . . . . . . . . 65
7Deploying Point of Service Terminals 67
7.1 OperatingSystem......................... 67
7.2 Conditions to Add a Point of Service Terminal . . . . . . . . . . . . . 68
7.3 Creating Point of Service Images . . . . . . . . . . . . . . . . . . 72
7.4 Creating the Required LDAP Objects . . . . . . . . . . . . . . . . . 72
7.5 Distributing Images to Point of Service Terminals . . . . . . . . . . . . 89
7.6 Hardware............................ 92
7.7 Point of Service Conguration Files . . . . . . . . . . . . . . . . . 94
7.8 Booting the Point of Service Terminal . . . . . . . . . . . . . . . . 102
8Securing Your Setup 111
8.1 Physical Server Security . . . . . . . . . . . . . . . . . . . . . . 112
8.2 NetworkSecurity........................ 112
8.3 DataSecurity.......................... 113
8.4 Application Security . . . . . . . . . . . . . . . . . . . . . . . 115
9Testing Your SUSE Linux Enterprise Point of Service Environment 117
9.1 Monitoring the Terminal Bootup . . . . . . . . . . . . . . . . . . 117
9.2 Troubleshooting Terminal Bootup Problems . . . . . . . . . . . . . 120
10 The SUSE Linux Enterprise Point of Service LDAP Directory 121
10.1 Logical Structure of the LDAP Directory . . . . . . . . . . . . . . . 122
10.2 Using posAdmin to Manage the LDAP Directory . . . . . . . . . . . 128
10.3 LDAP Objects Reference . . . . . . . . . . . . . . . . . . . . . 136
11 Managing Image Source Files 151
11.1 POSCDTool Command Line Options . . . . . . . . . . . . . . . . . 151
11.2 POSCopyTool Command Line Options . . . . . . . . . . . . . . . . 156
11.3 Managing the Image Source Files . . . . . . . . . . . . . . . . . . 158

12 Building Images with the Image Creator Tool 163
12.1 Creating an Image Based on Template . . . . . . . . . . . . . . . . 165
12.2 Building Network Boot Images . . . . . . . . . . . . . . . . . . . 166
12.3 Building Bootable CD Images with a System Image . . . . . . . . . . 167
12.4 Building Bootable CD Images without a System Image . . . . . . . . . 168
12.5 Building USB Stick Images with a System Image . . . . . . . . . . . . 168
12.6 Adding Installable Documentation in RPM Format . . . . . . . . . . . 169
12.7 Image Conguration Settings . . . . . . . . . . . . . . . . . . . 170
13 Building Images with KIWI 173
13.1 Understanding the KIWI Conguration . . . . . . . . . . . . . . . 174
13.2 Preparing the Image Conguration . . . . . . . . . . . . . . . . . 178
13.3 Creating the KIWI Image . . . . . . . . . . . . . . . . . . . . . 180
13.4 Building Customized SUSE Linux Enterprise Point of Service Images . . . 181
13.5 Deploying KIWI Images . . . . . . . . . . . . . . . . . . . . . . 183
14 Remotely Managing Point of Service Terminals with admind and adminc
185
14.1 admind............................. 185
14.2 adminc............................. 187
14.3 posGetIP............................ 188
14.4 Installing admind on a Point of Service Terminal . . . . . . . . . . . 189
14.5 Installing the admind Client on Administration and Branch Servers . . . 191
15 Backup and Restore 193
15.1 Ofine Physical Backup . . . . . . . . . . . . . . . . . . . . . . 193
15.2 Ofine Logical Backup . . . . . . . . . . . . . . . . . . . . . . 194
15.3 OnlineBackup.......................... 194
15.4 RestoringData.......................... 195
16 Troubleshooting 197
16.1 Server Infrastructure . . . . . . . . . . . . . . . . . . . . . . . 197
16.2 Operation ........................... 199
AChanging the Server Language 203
A.1 Changing the Language Selection . . . . . . . . . . . . . . . . . . 203
A.2 Installing a Language RPMs . . . . . . . . . . . . . . . . . . . . 203

BPoint of Service Scripts 205
B.1 Overview............................ 205
B.2 Core Script Process . . . . . . . . . . . . . . . . . . . . . . . . 206
B.3 Script Quick Reference . . . . . . . . . . . . . . . . . . . . . . 208
CSUSE Linux Enterprise Point of Service Files and Directory Structure
219
C.1 Administration Server Directory Structure . . . . . . . . . . . . . . 219
C.2 Branch Server Directory Structure . . . . . . . . . . . . . . . . . 223
C.3 KIWI Files and Directory Structure . . . . . . . . . . . . . . . . . 226

About This Guide
This guide contains instructions on how to install, manage and deploy SUSE® Linux
Enterprise Point of Service. Learn which components constitute a SUSE Linux Enterprise
Point of Service environment and how to congure the individual servers and terminals.
The guide is intended mainly for system administrators.
Many chapters in this manual contain links to additional documentation resources.
These include additional documentation that is available on the system, as well as
documentation available on the Internet.
For an overview of the documentation available for your product (and the latest docu-
mentation updates), refer to http://www.novell.com/documentation or to
the following section.
1 Available Documentation
We provide HTML and PDF versions of our books in different languages.
Find HTML versions of most product manuals in your installed system under /usr/
share/doc/manual or in the help centers of your desktop. Find the latest documen-
tation updates at http://www.novell.com/documentation where you can
download PDF or HTML versions of the manuals for your product.
For more information on the underlying operating system, refer to the SUSE Linux
Enterprise Server documentation, available from http://www.novell.com/
documentation/sles11/.
For information on securing your applications using AppArmor, refer to the Security
Guide, available from http://www.novell.com/documentation/sles11/.
For an introduction to setting up High Availability environments with SUSE Linux
Enterprise, refer to the High Availability Guide, available from http://www.novell
.com/documentation/sles11/.

2 Feedback
Several feedback channels are available:
• To report bugs for a product component or to submit enhancement requests, please
use https://bugzilla.novell.com/. If you are new to Bugzilla, you
might nd the Bug Writing FAQs helpful, available from the Novell Bugzilla home
page.
• 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.
3 Documentation Conventions
The following typographical conventions are used in this manual:
•/etc/passwd: directory names and lenames
•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.
viii SUSE Linux Enterprise Point of Service Guide

1
Product Overview
SUSE® Linux Enterprise Point of Service is a secure and reliable Linux platform opti-
mized for enterprise retail organizations. Built on the solid foundation of SUSE® Linux
Enterprise, it is the only enterprise-class Linux operating system tailored specically
for retail Point of Service terminals, kiosks, self-service systems, and reverse-vending
systems.
This section provides an architectural overview of the SUSE Linux Enterprise Point of
Service product, along with an overview of server types, images, and the deployment
process.
1.1 Architecture
The SUSE Linux Enterprise Point of Service architecture consists of one centralized
Administration Server, one or more Branch Servers, and Point of Service terminals.
These can be standard PCs running retail check-out applications or specialized point-
of-sale machines such as cash registers and customer kiosks (see Figure 1.1, “SUSE
Linux Enterprise Point of Service System Architecture” (page 2)). Find a list of system
requirements for the individual components in Section 1.2, “System Requirements”
(page 3) and an overview of the different server types and their functions in Section 1.3,
“Server Types” (page 5).
Product Overview 1

Figure 1.1 SUSE Linux Enterprise Point of Service System Architecture
All system information (system structure, image information, the conguration and
deployment method for each Branch Server and Point of Service terminal, etc.) is stored
in an LDAP database on the Administration Server (which may be replicated on Branch
Servers). The Administration Server usually also holds the master repository for the
images required to boot and congure Point of Service terminals and provides the
utilities required to build those images.
NOTE: Creating a Dedicated Image Building Server
However, if you have a large system and want to ofoad the image building
function from the Administration Server, you can also set up a dedicated Image
Building Server. For more information, see Chapter 4, Setting Up the Adminis-
tration Server (page 35) or Chapter 5, Setting Up a Dedicated Image Building
Server (page 47).
Triggered by the possyncimages.pl script (see Section B.3.9, “possyncimages.pl”
(page 217), each Branch Server downloads the system information and images required
for its local Point of Service terminals from the Administration Server. The Point of
Service terminals, in turn, download their respective images from the Branch Server
when they boot.
2SUSE Linux Enterprise Point of Service Guide

WARNING: Protecting the Branch Servers
Because Branch Servers contain sensitive information, they must be secured
against unauthorized access. Close unused ports and allow only the root user
to have access to the server console. Refer to Chapter 8, Securing Your Setup
(page 111) for more details on how to protect your SUSE Linux Enterprise Point
of Service setup.
SUSE Linux Enterprise Point of Service is broadly scalable so that a small shop with
ve Point of Service terminals can be managed just as well as a large chain with a
thousand branches. For organizations with several Branch Servers, the link between
the branch and administrative servers is maintained over WAN. During execution of
administrative tasks, such as the installation of new Point of Service terminals in a
branch, steps must be taken to ensure that the WAN link to the Administration Server
is available.
The SUSE Linux Enterprise Point of Service architecture is highly centralized. However,
administrative tasks can also be performed on subunits for role-based administration.
The Branch Server provides all the services necessary for the operation and management
of the Point of Service terminals and the LDAP database can be replicated on the Branch
Server. Consequently, the Branch Server and Point of Service terminals can function
independently of the Administration Server in the event of server failure or downed
connection.
1.2 System Requirements
This section provides a list of minimal hardware requirements for SUSE Linux Enterprise
Point of Service 11.
1.2.1 Administration Server
The following list identies the system requirements for an Administration Server:
• One server with an x86 or x86-64 processor
• A minimum of 4 GB hard disk space; recommended 15 GB
Product Overview 3

The required space depends on the size of your images.
• A minimum of 512 MB RAM; recommended 512 MB - 3 GB (at least 512 MB per
CPU)
• One network card
1.2.2 Image Building Server
The following list identies the system requirements for a dedicated image building
server:
• One server with an x86 or x86-64 processor
• A minimum of 4 GB hard disk space; recommended 25 GB
The required space is dependent on the size of your images.
• A minimum of 512 MB RAM; recommended 512 MB - 3 GB (at least 512 MB per
CPU)
• One network card
1.2.3 Branch Server
The following list identies the system requirements for a Branch Server:
• One server with an x86 or x86-64 processor
• A minimum of 4 GB hard disk space; recommended 10 GB
The required space is dependent on the size of the images you distribute to your
Point of Service terminals.
• A minimum of 512 MB RAM; recommended 512 MB - 3 GB (at least 512 MB per
CPU)
• At least two network cards per server:
• One network card for the Administration Server's public network
4SUSE Linux Enterprise Point of Service Guide

• One network card for the Branch Server's private network
1.2.4 Administration/Branch Server
Combination
The following list identies the system requirements for an Administration/Branch
Server combination:
• One server with an x86 or x86-64 processor
• A minimum of 4 GB hard disk space; recommended 25 GB
The required space is dependent on the size of your images.
• A minimum of 512 MB RAM; recommended 512 MB - 3 GB (at least 512 MB per
CPU)
• One network card
1.3 Server Types
SUSE® Linux Enterprise Point of Service is based upon SUSE Linux Enterprise and
is installed as an add-on product. After installation and setup, your SUSE Linux Enter-
prise Point of Service system includes one centralized Administration Server, one or
more Branch Servers, and Point of Service terminals. This section focuses on the server
types used in SUSE Linux Enterprise Point of Service and gives an overview of the
tasks they run and the services they provide.
1.3.1 Administration Server
The Administration Server is the central administration point for SUSE® Linux Enter-
prise Point of Service. It is usually located in the main ofce and is used to manage the
Point of Service infrastructure, to host the LDAP database and to create images to send
to the Branch Servers. Whereas the LDAP server running on the Administration Server
stores the conguration of the Point of Service clients, the conguration of new Point
Product Overview 5

of Service terminals (and which images to deploy to the Point of Service terminal)
needs to be accepted in a YaST module.
The Administration Server provides the following functions:
• Maintains the master LDAP directory for the Branch Server systems. For more in-
formation on the LDAP directory, see Chapter 10, The SUSE Linux Enterprise
Point of Service LDAP Directory (page 121).
• Unless your SUSE Linux Enterprise Point of Service system includes a dedicated
Image Building Server, the Administration Server usually provides the tools to
create and customize system images and stores the system images for distribution
to the Branch Servers and Point of Service terminals. For more information, see
Chapter 12, Building Images with the Image Creator Tool (page 163) and Chapter 13,
Building Images with KIWI (page 173).
• Stores the conguration parameters for the Branch Servers.
• Provides an RSYNC server to distribute the system images and software updates
to the Branch Server systems.
• Supports NTP time synchronization for the Branch Servers.
• Consolidates the syslog output from the Branch Servers (optional).
For information on installing and conguring the Administration Server, see Chapter 4,
Setting Up the Administration Server (page 35). Find out more about the Administration
Server structure and functions in the following sections.
Services
The Administration Server provides two important services in your SUSE Linux Enter-
prise Point of Service system:
• LDAP is the protocol for accessing the SUSE Linux Enterprise Point of Service
directory, which stores all system information.
• RSYNC is a remote data synchronization service that is used to transfer images
from the Administration Server to the Branch Servers.
6SUSE Linux Enterprise Point of Service Guide

In order to provide services of the Administration Server, the rewall running on the
Administration Server needs to allow trafc on the ldap or ldaps ports (389 TCP/UDP
and 636 TCP/UDP, respectively) and the rsync port ((TCP/UDP 873). For more infor-
mation, refer to Section 4.2, “Initializing the LDAP Directory” (page 38).
1.3.2 Branch Server
The Branch Server provides the network boot and system management infrastructure
for the Point of Service terminals. It can also serve as a generic system platform for in-
store applications such as database systems and back-ends for Point of Service applica-
tions.
In your system, the Branch Server provides the following functions:
• Runs DNS services for the local network.
• May run DHCP to control the network boot process. Conversely, instead of setting
up the DHCP service on the Branch Server, an external DHCP server can be used.
For more information, refer to the list of attributes for scLocation elements in
Section 10.3.8, “scLocation” (page 142).
• Provides a multicast boot infrastructure for Point of Service terminals.
• Transfers system images from the Administration Server to the Point of Service
terminals.
The Branch Server uses a software distribution mechanism based on RSYNC to
pull new system images from the Administration Server. It then uses TFTP to
download system images and conguration les to the Point of Service terminals.
• Manages diskless and disk-based Point of Service terminals. Conguration data is
taken from the LDAP directory on the Administration Server.
• Provides system redundancy and failover. A pair of Branch Servers can be cong-
ured as a two-node high availability cluster with replicated data.
• Supports NTP for time synchronization from the Administration Server.
• Supports SNMP. Standard MIB2 monitoring is set up with net-snmp (optional).
Product Overview 7

• Logs syslog output from the Point of Service terminals (optional).
For information on installing and conguring the Branch Server, see Chapter 6, Setting
Up a Branch Server (page 49). Find out more about the Branch Server structure and
functions in the following sections.
LDAP Branch Server Object
Each Branch Server has a corresponding Branch Server object (scBranchServer)
in the LDAP directory. This object stores conguration information that is specic to
each Branch Server.
For more information on the scBranchServer object, see Chapter 10, The SUSE
Linux Enterprise Point of Service LDAP Directory (page 121).
LDAP Access
To complete its initial conguration and perform basic functions (such as registering
Point of Service terminals and downloading system images and conguration les),
the Branch Server must have administrator level access to the LDAP directory. This
admin account and password are created by the posInitAdminserver.sh script
during the initial conguration of the Administration Server. Once created, this account
is not accessible in the LDAP tree.
LDAP communications can be secured with SSL. When you run the
posInitAdminserver.sh script, you can enable or disable SSL communication.
Note that the rewall running on the Administration Server must allow trafc on the
ldap and ldaps ports, 389 TCP/UDP and 636 TCP/UDP, respectively. For more infor-
mation, refer to Section 4.2, “Initializing the LDAP Directory” (page 38).
Administrative Tasks
Other than emergency handling, no system administration is necessary on the Branch
Server. All administrative tasks are controlled from the central Administration Server
or are regularly executed by daemons running on the Branch Server. For emergencies
and debugging, all administrative functions can be triggered locally or via SSH login
by calling scripts with few or no command line parameters.
8SUSE Linux Enterprise Point of Service Guide

If you need to update the Point of Service images stored on the Branch Server, you can
run possyncimages.pl to manually trigger the RSYNC update process and
download new image les from the Administration Server. For more information, see
Section B.3.9, “possyncimages.pl” (page 217).
Similarly, if you need to update the Point of Service hardware conguration information
stored on the Branch Server, run either posldap2crconfig.pl --dumpall or
posAdmin --updateconfig. These commands regenerate the hardware congu-
ration and config.MAC les for all Point of Service terminals found in LDAP.
For more information on the posldap2crconfig.pl script, see Section B.3.4,
“posldap2crcong.pl” (page 212).
Services
In SUSE Linux Enterprise Point of Service, Branch Servers provide the services listed
in Table 1.1, “Branch Server Services” (page 9).
Table 1.1 Branch Server Services
DescriptionService
Every Branch Server runs a DNS master for that branch. The
posldap2dns script generates the zone les for the BIND name server
DNS
from the data in the LDAP directory and then reloads the zone les
on each Branch Server.
A DHCP server can be installed on the Branch Server. The
posldap2dhcp script generates the dhcpd.conf le from branch
data in the LDAP directory.
DHCP
The NTP service for the Branch Servers synchronizes with the Admin-
istration Server NTP, which must be congured to get the time from
a reliable source.
NTP
The TFTP service on the Branch Server is structured with boot, image,
Point of Service, and upload directories. There is a PXE default con-
TFTP
guration with which all the Point of Service terminals rst load the
Product Overview 9

DescriptionService
same initial initrd and the same kernel. For more information, see
Section “TFTP Server Directory Structure” (page 10).
If there is an error with a TFTP action, the service waits 60 seconds,
then restarts.
The Branch Server can dene syslog logging services for Point of
Service terminals. This service must be manually dened; the con-
Syslog
guration information is stored in the /etc/syslog-ng.conf le,
not in LDAP.
High Availability Conguration
For high availability, Branch Servers can be congured in two-node pairs. The primary
node runs all of the scripts and services required to download Branch Server congura-
tion information, synchronize time, and download system images from the Administra-
tion Server. The secondary node stays synchronized with the primary, ready to take
over and run the scripts and services if the primary fails.
For information on installing a high availability environment, refer to the general High
Availability Guide, available from http://www.novell.com/documentation/
sles11/.
TFTP Server Directory Structure
SUSE Linux Enterprise Point of Service uses /srv/tftpboot as the tftp_root
path for the TFTP server on the Branch Server. Table 1.2, “TFTP Directory Structure
on the Branch Server” (page 11) outlines the main areas into which the directory
structure is divided under the TFTP root directory.
10 SUSE Linux Enterprise Point of Service Guide

Table 1.2 TFTP Directory Structure on the Branch Server
ContentsDirectory
Contains config.MAC image conguration les for every
registered Point of Service terminal on the current Branch
Server.
/tftpboot/CR/
Contains system conguration les, such as xorg.conf, for
the individual Point of Service terminals.
/tftpboot/
CR/MAC/
Contains the following boot images and conguration les
for Point of Service terminals: initrd.gz,linux, the PXE
/tftpboot/
boot/
loader (pxelinux.0), and the PXE conguration folder
(pxelinux.cfg).
Contains system image les and their checksums.
/tftpboot/
image/
Serves as the destination directory to upload hwtype.MAC
les for newly registered Point of Service terminals. These
/tftpboot/
upload/
les are used to create the Point of Service terminal's worksta-
tion object in LDAP.
This directory also stores the bootversion.MAC les that
the posleases2ldap daemon uses to provide image install noti-
cation. When an image is successfully installed on a Point
of Service terminal, the linuxrc script creates a bootversion
.MAC le in the /tftpboot/upload directory on the
Branch Server. posleases2ldap then transfers the information
to the scNotifiedimage attribute in the
scWorkstation object in LDAP and deletes the
bootversion.MAC le.
An example of a Branch Server TFTP structure is shown below:
/tftpboot/CR
00:02:55:E8:FA:C9 config.00:02:55:E8:FA:C9
00:03:56:01:D5:5F config.00:03:56:01:D5:5F
Product Overview 11

00:09:6B:3B:01:07 config.00:09:6B:3B:01:07
00:02:55:23:F3:93 config.00:02:55:23:F3:93
/tftpboot/CR/00:02:55:E8:FA:C9
XF86Config
/tftpboot/CR/00:03:56:01:D5:5F
XF86Config
/tftpboot/CR/00:09:6B:3B:01:07
/tftpboot/boot
initrd.gz
linux
pxelinux.0
pxelinux.cfg
/tftpboot/boot/pxelinux.cfg
default
/tftpboot/image
minimal-2.0.4 minimal-2.0.4.md5
graphical-2.0.4 graphical-2.0.4.md5
/tftpboot/upload
hwtype.00:02:55:E8:FA:C9
NOTE: Deletion of Point of Service Control File
The Point of Service control le hwtype.00:02:55:E8:FA:C9 is deleted
after successful registration in LDAP. For more information, see Section 7.7.3,
“The hwtype.MAC File” (page 100).
1.3.3 Special Server Types
Apart from the default implementation shown in Figure 1.1, “SUSE Linux Enterprise
Point of Service System Architecture” (page 2), SUSE Linux Enterprise Point of
Service allows for a variety of different setups to match your individual requirements.
You can create special types of servers, like a dedicated Image Building Server taking
load from the Administration Server, or implement POSBranch Servers instead of fully-
edged Branch Servers as described in the following sections.
12 SUSE Linux Enterprise Point of Service Guide