server/user-documentation
10
3
Fork 8
Code Issues Pull requests 2 Projects Activity

Completed document by installing w/o a terminal

Browse source
This commit is contained in:
pboy 2026-05-02 13:03:51 +02:00
commit cf7e83191b
1 changed files with 80 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

101
modules/ROOT/pages/installation/interactive-remote.adoc
View file

@ -1,21 +1,22 @@
= Fedora Server remote interactive installation guide
Peter Boy; Kevin Fenzi; Jan Kuparinen; Jiri Konecny
:page-authors: {author}, {author_2}, {author_3}, {author_4}
:revnumber: F42
:revdate: 2024-12-16
:revnumber: F44
:revdate: 2026-04-28
:numbered:
:page-aliases: pages/installation-interactive-remote.adoc
// [NOTE]
// ====
// **Status:** In sync with released version.
// ====
:page-aliases: pages/installation-interactive-remote.ado
[abstract]
With this method, the server is usually residing in a remote location, such as a data center. It boots from a prepared installation media into the Anaconda installation program configured to start and use a "remote desktop protocol" (RDP) server instead of a local physical console. The system administrator connects using a RDP client on a local desktop to the server and runs through the Anaconda graphical installer. This method is best suited for servers without any or just cumbersome available direct console access.
This method is best suited to servers with limited or no direct console access, but which still have the option of connecting and booting from a USB flash drive. It boots from the prepared installation media into Anaconda and starts a Remote Desktop Protocol (RDP) server instead of a local physical console. The system administrator then connects using an RDP client and runs the Anaconda graphical installer.
[NOTE]
Updated, not yet fully reviewed
== Prerequisites
@ -26,20 +27,22 @@ You need one of the installation media variants ready to use as described in x
RDP client::
Performing an RDP installation requires an RDP client running on your workstation or another terminal computer. RDP clients are available in the repositories of most Linux distributions; free RDP clients are also available for other operating systems, such as Windows. On Linux systems, use your package manager to search for a RDP for your distribution.
+
The following RDP clients are available in Fedora:
The following RDP clients are available in __Fedora__:
+
* GNOME Connections - Connections is a remote desktop client for the GNOME desktop environment.
* freerdp - Free implementation of the Remote Desktop Protocol (RDP)
--
* __GNOME Connections__ – a remote desktop client for the GNOME desktop environment.
* __freerdp__ – Free implementation of the Remote Desktop Protocol (RDP)
--
+
To install any of the clients listed above, execute the following command as root:
Use your desktop software installation program to install any of the clients listed above.
+
[source,]
----
[...]# dnf install PACKAGE_NAME
----
For MacOS you may use one of the following options:
+
Replace package with the package name of the client you want to use (for example, freerdp).
--
* __Windows App__ – provided by Microsoft for free via App Store
* __Jump Desktop__ – commercial application via App Store
* __freerdp__ – Free implementation of the Remote Desktop Protocol installable via homebrew or macport
--
== Booting the server
There are several options to boot the server, depending on the ethernet connection method and availability of at least some, maybe cumbersome and short living local console access.
@ -91,8 +94,64 @@ The system will initialize the installation program and start the necessary serv
----
Continue with __3.2. Connecting to the server__.
=== No Console access available – provide a kickstart medium
You will need two usable USB ports or DVD drives on the server, one for the installation medium, one for a kickstart flash drive.
. On your desktop, connect an USB stick and format as FAT and with label OEMDRV. In Fedora use the graphical tool of the desktop UI or a terminal window.
+
List the connected devices and identify the USB stick
+
[source,bash]
----
[…]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 596.2G 0 disk
├─sda1 8:1 0 600M 0 part /boot/efi
├─sda2 8:2 0 1G 0 part /boot
├─sda3 8:3 0 80G 0 part
│ ├─fedora_fedora-root 253:0 0 15G 0 lvm /
│ └─fedora_fedora-var_log 253:2 0 5G 0 lvm /var/log
└─sda4 8:4 0 514.6G 0 part ├─fedora_user-libvirt 253:3 0 120G 0 lvm /var/lib/libvirt
└─fedora_user-machines 253:4 0 80G 0 lvm /var/lib/machines
sdb 8:16 1 1001.5M 0 disk
└─sdb1 8:17 1 1001.5M 0 part
zram0 252:0 0 8G 0 disk [SWAP]
----
+
In the example above, the USB stick is sdb. Just in case it is mounted, unmount and then format and mount it at e.g. /mnt
+
[source,bash]
----
[…]$ sudo umount /dev/sdb1
[…]$ sudo mkfs.vfat -n 'OEMDRV' /dev/sdb1
[…]$ sudo mount /dev/sdb1 /mnt
----
. Create and edit a kickstart file _ks.cfg_ in the root directory of the USB flash drive.
+
If possible, you should provide a static network configuration, so you'll know the IP address. If that isn't possible and DHCP is available, you can omit the “network” line. Anaconda will then use DHCP and display the address it receives.
+
[source,bash]
----
[…]$ sudo vim /mnt/ks.cfg
<INSERT>
network --bootproto=static --ip=ww.xx.yy.zz --netmask=255.255.255.0 --gateway=ww.xx.yy.gg --ipv6='aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh/nnn' --hostname='myhost.mydomain.tld' --nameserver=10.0.2.1
rdp --user='SOME_NAME' --password=PASSWORD
<SAVE&QUIT>
----
+
If the network configuration does not allow or enable static interface configuration, omit the 'network …' line either completely or just add the --hostname parameter. It uses DHCP by default. And if your DHCP server provides dynamic DNS as well, you can easy access your server to be installed.
. On your server, connect the installation medium as well as the OEMDRV medium and boot. The server will use the OEMDRV stick, configure the interface and start VNC. Just in case you have at least a monitor without keyboard and mouse, you will see the corresponding message. Otherwise, trust your configuration.
With _Fedora 44_ you get some Python error messages you can ignore. It works anyway.
Continue with __3.2. Connecting to the server__.
=== No console access available – patch installation medium
==== No console access available – patch installation medium
If none of the above options work with your server and network configuration, you could patch the installation media as a last resort. As an example, you can change the grub boot lines in /isolinux/grub.conf. You would need to add the RDP parameter and remove the integrity test, as this is the default line but would fail after patching.
We won't go into this matter any further here. This is really the very last resort and is not recommended.
@ -131,7 +190,7 @@ Nmap done: 256 IP addresses (12 hosts up) scanned in 2.38 seconds
+
Look for an entry with open state of port 3389 and no hostname or unknown hostname. Among them you will probably find the device you are looking for. In the example above it is 192.168.158.200.
. On the desktop start the GNOME connections, add new connection with a plus symbol, enter the IP address obtained in the previous step. You will be asked to confirm certificates. These are generated by Anaconda and they are different for each installation.
. On the desktop start the RDP client, add new connection with a plus symbol, enter the IP address obtained in the previous step. You will be asked to confirm certificates. These are generated by Anaconda and they are different for each installation.
+
Alternatively, use freerdp client with
+