wiki.smarken.dk

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Client Deployment ======


(Klient udrulning)

For at installere en klient maskine, i virksomhedssammenhæng, benyttes ofte en PXE server til at hente installationen som et fuldt standardiseret disk-image, eller en automatiseret installation. Principperne er nogenlunde de samme for både Linux og windows.  

Der er fordele og ulemper ved både installation og image procedurerne.

===== Image =====

Fordelene ved image er f.eks. at når ens workplace gruppe har godkendt opsætningen, kan der nemt laves et image af en godkendt maskine, som så bare lægges op til download/deploy.
En teknisk ulempe er så at det nemt kan forkomme at image er fastlåst til de harware drivere der er lagt ind i image, og hvis der på klienten er harwareafvigelser skal drivere og opsætning så laves efterfølgende.

===== Automatiseret installation =====

Ved automatiseret installation hentes distro, drivere og apps, fra et repository, som kan være lokalt eller eksternt på internettet.

Ved lokalt repository kan IT/sikkerhedsafdelingen lettere begrænse apps til (sikkerheds-)godkendte apps og tilføre restriktioner efter behov. Ved lokal respository kan brugeren nemt se hvad der er godkendt på forhånd, og evt. anmode om godkendelse af en given app, hvis den ikke er i repository.

Ved både lokal og ekstern repository kan installationen styres ved scripting meget specifikt til både generel, gruppe og bruger profiler. 

===== Alternativer til (normal) PXE  =====

----



===== iPXE =====
[[https://ipxe.org/start]]

**iPXE** er open source network boot firmware. iPxe understøtter en __fulD PXE__ implementation forbedret med yderligere funktionaliteter så som:

  * boot fra en web server via HTTP
  * boot fra et iSCSI SAN
  * boot fra et Fibre Channel SAN via FCoE
  * boot fra et AoE SAN
  * boot fra et wireless network
  * boot fra et wide-area network
  * boot fra et Infiniband network
  * at kontrolere og styre boot processen gennem scripting\\ 

Du kan bruge iPXE to at erstatte PXE ROM på dit netkort eller du kan chainload'e ind i iPXE for at opnå iPXE's yderligere features uden besværligheden ved at skulle re-flash'e dit netværkskort.

iPXE er frit, open-source software licenseret under GNU GPL (med visse dele under GPL-kompatible licencer), og iPXE er inkluderet i produkter fra flere producenter af netværkskort og OEM'er.

----

===== FOG =====

[[https://docs.fogproject.org/en/latest/introduction/]]

FOG is a Linux-based, free and open source computer imaging solution for
various versions of Windows (XP, Vista, 7, 8/8.1, 10), Linux and Mac OS
X. It ties together a few open source tools with a PHP-based web
interface.

FOG doesn't use any boot disks, or CDs; everything is done via TFTP and
PXE. Your PCs boot via PXE and automatically downloads a small linux
client doing all the hard work of imaging your machine.

Also with FOG many network drivers are built into the client's kernel
(vanilla linux), so you don't really need to worry about network
drivers (unless there isn't kernel support for it yet).

FOG also supports putting an image that came from a computer with a 80GB
partition onto a machine with a 40GB hard drive as long as the data is
less than 40GB.

FOG supports multi-casting, meaning that you can image many PCs from the
same stream. So it should be as fast whether you are imaging 1 PC or 20
PCs.


----
====== Externe guides og dokumentation af PXE ======
----



===== Setting Up a PXE Boot Server =====

**(SUSE SLES 16)**\\ 
Publication Date: 07 Aug 2026\\ 
Preboot Execution Environment (PXE) is a network boot standard that enables systems to boot and install an operating system over the network instead of using local installation media. A PXE boot server simplifies and automates operating system deployment across multiple machines, reducing manual effort and improving consistency. On SUSE Linux Enterprise Server 16.0, you can configure a PXE boot server with support for UEFI Secure Boot and the Agama installer to create a scalable, network-based installation environment.

**Prerequisites**:

  * A SUSE Linux Enterprise Server 16.0 system with administrative privileges
  * Internet connection to fetch ISO images
  * Static IP configuration for the PXE server

**Note: Limitations and features of your chosen method**\\ 

**Use Kea**—the new DHCP server from **ISC**—as a modern replacement for **ISC DHCP**. For more information on Kea, refer to [[https://www.isc.org/kea/]].\\ 
//For the ISC DHCP **EOL notice**//, see https://www.isc.org/dhcp/.\\ 
 Kea is a DHCP server and requires separate TFTP server software. The Kea DHCP server supports options for TFTP/PXE boot over IPv4 and IPv6 as well as for HTTP boot via IPv4. The HTTP boot via IPv6 requires that the DHCPv6 server can send the Vendor Class Option (see RFC3315, Section 22.16), //supposed// to be used “by a client to identify the vendor,” back to the client and is **currently not supported**.

**dnsmasq** is a combination of a DNS server, a DHCP server and a TFTP server. You can use it to serve the boot loader, kernel, initrd (and other files) over TFTP.\\ 
For more information on dnsmasq, refer to [[https://thekelleys.org.uk/dnsmasq/doc.html]].\\ 
The dnsmasq DHCP server supports options for TFTP/PXE boot over IPv4 and IPv6 as well as for HTTP boot via IPv4. The HTTP boot via IPv6 requires that the DHCPv6 server can send the Vendor Class Option (see RFC3315, Section 22.16), //supposed// to be used “by a client to identify the vendor,” back to the client and is **currently not supported**.

[[https://documentation.suse.com/sles/16.0/html/SLES-PXE-server/|SUSE dokumentation]]

NB! Dokumentationen er lavet for SLES, men dækker langt hen ad vejen også for OpenSUSE, og begge frit kan downloades downloades. Den primære forskel mellem SLES og OpenSUSE er at til SLES kan der tilkøbes support, og for openSUSE leveres support af OpenSUSE Community.

----

===== RHEL PXE server =====

[[https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/6/html/installation_guide/s1-netboot-pxe-config |Network Boot Configuration]]


----

===== Multi-boot for USB, iso, PXE - Netboot.xyz =====


[[https://netboot.xyz/]]

**1**
Grab the image
Pick the format that matches how you boot — ISO for VMs and IPMI, .img for USB, .kpxe for TFTP.\\ 

curl -O https://boot.netboot.xyz/ipxe/netboot.xyz.iso\\ 
**2**
Boot from it
Plug in the stick, attach the ISO, or point your DHCP server at the bootloader file.

dhcp-boot=netboot.xyz.kpxe\\ 

**3**
Pick your OS
The menu loads. Navigate with the arrow keys, press enter, and it streams the kernel from the upstream mirror.\\ 

----