

Loading kickstart files over the network from the kernel line during an install only supports NFS, HTTP, and FTP. Rootpw -iscrypted $6$CXxBapbzNlScWzBU$45c4bxK9/pDVls/aJcaT/9kENR0OFxMhohBf7k8RrBWtzTs42ljw4SER0AqYTDEdWHlDWE4BTTnQX8vkMWJ6l1īootloader -append=" crashkernel=auto" -location=mbr -boot-drive=sda Network -bootproto=dhcp -device=enp0s8 -onboot=off -noipv6 -activate For this article I will use kickstart file /root/nf with below content. I have written another article which contains a sample kickstart configuration file which you can use for reference. Since we plan to automate our installation using kickstart and network boot PXE server so we will need a working kickstart file. Follow the official CentOS page to get the various options with this tool. You can also use system-config-kickstart tool on the GUI to create your own kickstart file. It is a good starting point if you want to try out an automated Kickstart installation. This file contains most settings that were used while installing your computer. When you install a Red Hat system, a file with the name anaconda-ks.cfg is created in the home directory of the root user. Typically for a Linux client, this file is called pxelinux.0.ĪLSO READ: Configure kickstart server | PXE boot server | RHEL/CentOS 8

But to configure PXE boot server on RHEL you need an active subscription to be able to download the required rpms or you can also download these rpms by creating a local repository using the RHEL vanilla DVD image.

The same list of steps will work on RHEL 7 as well.

In this article I will share the steps to configure PXE boot server using HTTP, Kickstart and DHCP / DNSMASQ service on a CentOS 7 node.
