Installing a New Operating System on Your Colocated Server (PXE Boot) Print

Overview

If your colocated server has been onboarded to the Qilak Tenantos control panel, you can perform network-based (PXE) OS installations without needing remote hands. This uses our provisioning network to deliver the installer to your hardware.

Important: Because you own the hardware in colocation, a few things work differently than on a leased dedicated server. Read the prerequisites section carefully before your first PXE install.

Warning: A reinstall wipes all disks. Back up all data before proceeding. This cannot be undone.

Prerequisites for PXE Boot on Colocated Hardware

PXE boot on colocated equipment requires one-time setup. Confirm each of the following before attempting a reinstall:

1. The NIC MAC address is registered with Qilak. Our provisioning system will only PXE boot MAC addresses that have been authorized on the switch port serving your rack unit. This is normally captured during colocation onboarding, but if you swap a NIC, replace a motherboard, or add a second server, the new MAC must be registered before it can PXE boot.
2. The correct NIC is patched to our provisioning VLAN. Only one NIC per server is connected to the provisioning network. If you re-cabled the server, PXE will only work from the originally patched interface.
3. PXE boot is enabled in BIOS/UEFI on the correct NIC, and network boot is either the first boot option or accessible via a one-time boot menu.
4. IPMI/BMC access is configured so you can watch the install and recover from boot issues remotely. If you have not set this up, request assistance during business hours.
5. Your disk layout is compatible with our installer templates. Hardware RAID controllers should have the array pre-configured; software RAID will be built by the installer.

Step-by-Step: Reinstalling Your Colocated Server

1. Log in to the Qilak client area and open Services → My Services.
2. Click on your colocation service to open the management page.
3. Click Reinstall in the sidebar.
4. Select the OS template you want to install.
5. Choose a disk layout. If your server has a hardware RAID controller, select the layout that matches the array you have pre-built.
6. Set the root or Administrator password. Optionally paste an SSH public key.
7. Open the IPMI console in a second tab so you can watch the install run.
8. Click Confirm Reinstall. The server will reboot, PXE boot, and install unattended.

Reinstalls on colocated hardware typically take 20–60 minutes depending on OS, disk speed, and RAID configuration.

Troubleshooting

The server will not PXE boot

This is the most common issue for colocation and almost always comes down to one of the following:

1. The MAC address is not registered or has changed

If you replaced a NIC, replaced the motherboard, or added a new server, the MAC address our provisioning system expects will not match what the hardware is presenting. The server will attempt PXE, get no response, and fall through to the next boot device.

To fix this:

1. Reboot the server via IPMI and watch the console during POST.
2. Note the MAC address shown by the PXE ROM as the NIC initializes (usually displayed as CLIENT MAC ADDR: XX:XX:XX:XX:XX:XX).
3. Open a support ticket at qilak.ca with:
   • Your service ID
   • The observed MAC address
   • Which NIC it is (onboard NIC1, add-in card, etc.) if you know
   • A brief reason (replaced NIC, new build, etc.)
4. We will verify the change, update the MAC registration in Tenantos, and confirm when you can retry.

For security reasons we cannot update MAC registrations without a client area ticket — an email alone is not sufficient.

2. The wrong NIC is patched or being used for PXE

Only the NIC connected to our provisioning network can PXE boot. If you have multiple NICs and PXE is enabled on all of them, the server may attempt to boot from a disconnected or wrong port first.

• In BIOS, disable PXE on all NICs except the one patched to our provisioning VLAN.
• If you are not sure which NIC is patched, open a ticket — we can confirm from our switch which port is active for your service.

3. PXE is disabled in BIOS/UEFI

Firmware updates can reset boot settings. Enter BIOS/UEFI setup via IPMI and confirm:

• Network boot / PXE is enabled on the correct NIC
• Boot order includes the network interface
• Secure Boot is configured appropriately for your chosen OS (some Linux templates require it disabled)

4. UEFI vs Legacy BIOS mismatch

Some templates require UEFI; others require Legacy. If PXE downloads the loader but the installer never starts, the boot mode is likely wrong. Open a ticket for confirmation of the correct mode for your chosen OS.

The installer starts but fails during partitioning

• Confirm your hardware RAID array is healthy and initialized before installing.
• If disks were previously part of a different array, request a "zero disks" from support so leftover RAID metadata is cleared before retrying.
• Check IPMI console for the specific error and include it in your ticket.

I cannot log in after install

• Use the password set during reinstall, not the original welcome email password.
• Linux: log in as root. Windows Server: log in as Administrator.
• Wait 3–5 minutes after the panel shows "Active" for services to finish starting.
• If SSH or RDP does not respond, open the IPMI console to check whether networking came up correctly.

I want to install an OS that is not in the template list

Because colocation clients often have specific software requirements, we can add custom OS templates on request. Open a ticket with the distribution, version, and any specific kickstart or preseed options you need.

Physical Hardware Changes

Any time you change hardware in your colocated server that affects the primary NIC — replacing the NIC, replacing the motherboard, or moving to a new chassis — you must notify Qilak so we can update the MAC registration. Failing to do this will cause PXE boot to stop working. If the change was made during a remote hands request performed by Qilak, we update the registration automatically.

Need Help?

Open a ticket through the Qilak client area or email support@qilak.ca. For PXE and MAC-related issues, please include your service ID, the observed MAC from IPMI console, and a screenshot of the boot sequence.