Windows on dedicated, without pretending it is Linux

A Windows dedicated server is a physical machine running Windows Server, not Linux with a different desktop. You manage it through IPMI for console access, a valid Windows license, and Remote Desktop instead of SSH. Updates can reboot the box on their own schedule, so you plan for that from the first hour rather than treating the chassis like a Linux VPS with a GUI.

IPMI console and network cards

Until Remote Desktop is listening, the screen you need is IPMI or iKVM. Confirm that console works before you lock yourself out of RDP. The public NIC and the IPMI NIC are separate paths with separate jobs, so one firewall rule should not cut you off from both. Linux rescue images will not repair a Windows boot the way many people expect. Use the Windows installer media through IPMI when the OS will not start. If RDP fails, open a ticket with a console screenshot rather than only the words “server down.”

Remote Desktop and account hygiene

Leaving RDP on port 3389 open to the whole internet with an old Administrator password is how incidents start. Allow-list your office or VPN first, enable Network Level Authentication, and use a password manager. Fail2ban is not a Windows product; use whatever lockout or firewall tooling you actually installed on the server. The Administrator account is not “root with a GUI.” Rotate that password and never paste it into a support ticket.

Updates, IIS, and one clear role

Patch Tuesday and forced reboots are normal on Windows. Schedule maintenance windows so unattended updates do not take IIS down during business hours. A sudden reboot after updates is not a DDoS. Keep one primary role on the metal when you can. Mixing IIS with unrelated services on the same chassis is how a Windows Update reboot interrupts work you thought was separate. Defender should stay on unless a real replacement is installed and running.

First-hour checklist

Bring the server up in this order: IPMI works, the OS is installed, the license is valid, RDP is limited to an allow-list, and updates follow a schedule you chose. Only then install the application and design backups you control, such as a disk image, a SQL dump, and an off-box copy. Dedicated servers do not include a hypervisor snapshot button, so backup design is yours. If you wanted Linux instead, say so before the ISO, not after a week of fighting IIS with nginx habits. When you write in, include the chassis id, what IPMI shows, and whether the issue is RDP, IIS, or updates. The dedicated servers product page lists the SKUs; this article is the practical first hour on Windows metal.