Linux | Sysprep For

Linux system preparation is achieved through distribution-specific tools (e.g., virt-sysprep , cloud-init , systemd-machine-id-setup ) and manual shell scripts. The goal is to produce a "golden image" that can be deployed without conflicts. When cloning a Linux VM or disk image, several artifacts remain that cause issues if not reset:

| Artifact | Consequence if not reset | |----------|--------------------------| | ( /etc/machine-id ) | Duplicate IDs break systemd-journald, DHCP leases, and some licensing | | SSH host keys ( /etc/ssh/ssh_host_* ) | All clones share same keys – a critical security risk (man-in-the-middle) | | Network interfaces ( /etc/udev/rules.d/70-persistent-net.rules ) | Naming conflicts or missing interfaces on new hardware | | Hostname ( /etc/hostname ) | Duplicate hostnames on the network | | Log files & temp data | Wasted space and potential information leakage | 3. Primary Tools for Linux Sysprep 3.1 virt-sysprep (Cross-distribution, most common) Part of libguestfs-tools . Works offline on disk images or VMs. sysprep for linux

virt-sysprep -a centos8.qcow2 --operations defaults,-ssh-hostkeys --hostname generic-vm | Distribution | Tool | Command | |--------------|------|---------| | RHEL / CentOS / Fedora | sys-unconfig (legacy), now virt-sysprep or cloud-init | rm -f /etc/machine-id | | Ubuntu / Debian | cloud-init (clean) | cloud-init clean --logs | | SUSE Linux | zypper with custom scripts | rm -f /var/lib/systemd/machine-id | 3.3 Manual Scripting (universal fallback) A simple bash script run before shutdown: Primary Tools for Linux Sysprep 3

| Platform | Mechanism | |----------|------------| | | Linux images run cloud-init at startup – regenerates SSH keys, sets unique hostnames, resets machine ID. | | VMware | Use virt-sysprep before converting to template, or enable guestinfo with cloud-init. | | Proxmox | pve-container templates use built-in cleanup; for VMs, run virt-sysprep . | | OpenStack | Glance images should be cloud-init ready – no manual Sysprep required. | | | VMware | Use virt-sysprep before converting

#!/bin/bash # Linux Sysprep script sudo rm -f /etc/machine-id /var/lib/dbus/machine-id Remove SSH host keys sudo rm -f /etc/ssh/ssh_host_* Clear logs sudo find /var/log -type f -exec truncate -s 0 {} ; Reset hostname echo "localhost" | sudo tee /etc/hostname sudo hostnamectl set-hostname localhost Clean package manager cache sudo apt clean # Debian/Ubuntu sudo yum clean all # RHEL/CentOS Remove udev network rules sudo rm -f /etc/udev/rules.d/70-persistent-net.rules Disable DHCP leases sudo truncate -s 0 /var/lib/dhcp/dhclient.leases 4. Integration with Cloud & Virtualization Platforms Modern deployments no longer rely on static golden images but use cloud-init to perform the "Sysprep" role at first boot.

1. Executive Summary Unlike Windows, Linux does not have a single, built-in tool named "Sysprep." However, the concept—generalizing a system image by removing unique identifiers (hostnames, SSH keys, network configurations, machine IDs) before cloning—is standard practice.