Infrastructure at your Service

In my previous Blog I wrote how to install and configure SUSE Manager. In this Blog I will go more in the deep like repository management and PXE boot configuration.

Configuring repository

To syncronize products from SUSE repository, you need configure first the Organization Credentials.

To get your username and password for repository you need to go: Login with your SUSE Account


Admin -> Setup Wizard -> Organization Credentials -> Add a new credential

After you successfully added the Organization Credentials, you need to refresh it.


PXE Boot

Preboot Execution Environment can make your system installation and deployment easier. You can prepare multiple profiles/systems and boot your client directly from the image to install it.
Before we start with profiles, we need configure our DHCP Server to enable PXE boot.

if your DHCP Server runs on Linux:

You need open /etc/dhcp/dchpd.conf and add next-server and filename to your subnet.

[[email protected] dhcp]# vi dhcpd.conf

# DHCP Server Configuration file.
#   see /usr/share/doc/dhcp-server/dhcpd.conf.example
#   see dhcpd.conf(5) man page

default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
allow booting;
allow bootp;

subnet netmask {
 option routers;
 option subnet-mask;
 option domain-name-servers,;
 filename "pxelinux.0";

save the file and restart your dhcp server:

systemctl restart dhcpd

if your DHCP Server runs on Windows Server:

Open DHCP configuration -> IPv4 -> Scope -> Server Options You need to add new options 066 and 067

066: FQDN or IP for your SUMA Server 067: pxelinux.0

Boot from PXE

After you configured your DHCP Server, you can boot your client from LAN. You should see following screen:

As we did not configured any system images, the list is empty.

Copying ISO files to Server

To be able to make installation over network, you need to download iso files and put it on SUMA Server. Go to and download the iso file.

Create needed folders:

mkdir -p /srv/www/htdocs/pub/isos
mkdir -p /srv/www/htdocs/pub/distros/SLES-15-SP2-DVD-x86_64

Copy the files to SUMA Server: /srv/www/htdocs/pub/isos and mount it

scp sles15-sp2-x86_64.iso [email protected]:/srv/www/htdocs/pub/isos
mount -o loop /srv/www/htdocs/pub/isos/sles15-sp2-x86_64.iso /srv/www/htdocs/pub/distros/SLES-15-SP2-DVD-x86_64

After you copied all your isos and mounted, you need to define tree path in SUSE Manager. Open your SUMA Server -> Systems -> Autoinstallation -> Distributions.

Make sure that you synced down your products which you want to deploy!

If you configured correctly, you will see on the right side a green checkmark.

Create your AutoYast file

The AutoYaST profile in this section installs a SUSE Linux Enterprise Server system with all default installation options including a default network configuration using DHCP. After the installation is finished, a bootstrap script located on the SUSE Manager server is executed in order to register the freshly installed system with SUSE Manager. You need to adjust the IP address of the SUSE Manager server, the name of the bootstrap script, and the root password according to your environment:

All possible Attributes you can find under:

Basic AutoYast file:

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns=""
<confirm config:type="boolean">false</confirm>
<keep_install_network config:type="boolean">true</keep_install_network>
<install_recommended config:type="boolean">true</install_recommended>
<patterns config:type="list">
<users config:type="list">
<encrypted config:type="boolean">false</encrypted>
<init-scripts config:type="list">

After you prepared and modifed your AutoYast file, you need to upload it to SUMA Server. Systems -> Autoinstallation -> Profiles -> Upload Kickstart/Autoyast File and past the content fo file contents.

Now let’s boot client again from the PXE:


SUSE Manager can for beginners little bit complicated. But once you understand the main concept your learning curve will growth fast.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Open source Team
Open source Team