--- title: "How to install and configure Windows Server on a dedicated server" description: "Find out how to install Windows Server on an OVHcloud Dedicated Server and configure it to work with Additional IP, vRack, IPv6, Backup Storage and Backup Agent" url: https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/configure-windows-dedicated-server lang: en lastUpdated: 2026-07-17 --- # How to install and configure Windows Server on a dedicated server ## Objective Windows Server is a supported operating system on OVHcloud Dedicated Servers. Once installed, you must configure the Windows system so that it can use the OVHcloud network and storage services attached to the server. This guide walks you through installing Windows Server from the OVHcloud Control Panel, connecting to it, and then performing the Windows-side configuration needed to interact with the main OVHcloud services bound to a dedicated server. **In this guide, you will learn how to:** - Install Windows Server from the Control Panel - Connect to the server with Remote Desktop and complete the initial setup - Configure Windows to use an Additional IP - Configure Windows to use the vRack private network - Configure Windows to use the IPv6 block delivered with the server - Access OVHcloud Backup Storage from Windows - Protect the server with managed backups using OVHcloud Backup Agent :::warning Reinstalling an operating system erases all data on the server disks. Back up any data you want to keep before starting. ::: ## Requirements - A [Dedicated Server](https://www.ovhcloud.com/en-gb/bare-metal/) in your OVHcloud account - A valid Windows Server licence. Licences can be ordered through OVHcloud or applied from an external reseller — refer to the [Managing your OVHcloud licences](/en/guides/bare-metal-cloud/dedicated-servers/windows-key.md) guide. - A Remote Desktop Protocol (RDP) client on your local machine (the Remote Desktop Connection client is included with Windows) *** ### OVHcloud Control Panel Access - **Direct link:** Dedicated Servers - **Navigation path:** Bare Metal Cloud > Dedicated servers > Select your server *** ## Introduction A dedicated server is a physical ("bare metal") server hosted in an OVHcloud data centre. OVHcloud provides the hardware, the public network connection, an optional vRack private network, and a complimentary Backup Storage space. You are responsible for administering the operating system installed on the server, including all network and storage configuration inside Windows. The services a Windows dedicated server commonly interacts with are summarised below. | OVHcloud service | Purpose | Where it is enabled | | ---------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Additional IP | Extra public IP addresses bound to the server | Control Panel — Network menu, IP section | | vRack | Private layer-2 network between OVHcloud services | Control Panel — Network menu, vRack section | | IPv6 | The /64 IPv6 block delivered with every server | Delivered automatically | | Backup Storage | Complimentary FTP/CIFS (SMB)/NFS backup space | Control Panel — Dedicated Servers > Select your server, Backup storage tab | | Backup Agent | Managed daily backups to an isolated, immutable Object Storage vault | Control Panel — Dedicated Servers > Select your server, General information tab, Service status section | ## Instructions **Contents:** - [Step 1 — Install Windows Server from the Control Panel](#install) - [Step 2 — Connect to your server](#connect) - [Step 3 — Complete the initial Windows configuration](#initial-config) - [Step 4 — Configure Windows to interact with OVHcloud services](#services) - [Step 5 — Verify the configuration](#verify) - [Troubleshooting](#troubleshooting) ### Step 1 — Install Windows Server from the Control Panel [](#) In this step, you install (or reinstall) Windows Server on your dedicated server. The installation is driven entirely from the Control Panel. On the `General information ` tab, next to `Operating system (OS) `, open the actions menu and click `Reinstall my server `. The `Installation from an OVHcloud template ` window opens and walks you through 4 steps. :::info Windows Server requires a licence, which generates additional fees. Without a Windows Server licence attached to the server, the Windows templates are not offered in the operating-system list. You can order a licence through OVHcloud or supply your own. Manage your licences under **Bare Metal Cloud** > **Licences**. For more information, refer to the [Managing your OVHcloud licences](/en/guides/bare-metal-cloud/dedicated-servers/windows-key.md) guide. ::: :::warning This action is irreversible. All data on the disks will be permanently deleted. ::: 1. **Type of OS** — set Type of OS and select the Windows Server template you want. Templates are grouped by category (Linux, Windows, and so on). The Windows templates only appear if a Windows Server licence is attached to your dedicated server (see the note above). 2. **Target disk group** — choose the Target disk group on which Windows will be installed. To define your own array or layout, enable Customise the hardware RAID configuration or Customise the partition configuration. For Soft RAID details on Windows, refer to the [Configuring software RAID on a Windows server](/en/guides/bare-metal-cloud/dedicated-servers/raid-soft-windows.md) guide. 3. Click Next and follow the remaining steps of the wizard to review your choices, then confirm to start the installation. The server reboots into the installer and the process completes automatically. ### Step 2 — Connect to your server [](#) Once the installation is complete, OVHcloud sends an email containing the administrator username and password for your Windows server. On your local Windows machine, open the `Remote Desktop Connection ` client. Enter the IPv4 address of your server, then your username and password. A certificate warning usually appears the first time you connect — click `Yes ` to continue. You can use any third-party RDP-compatible client if your local device does not run Windows. :::tip If RDP is unavailable — for example after a network misconfiguration — connect through the [Intelligent Platform Management Interface (IPMI) console](/en/guides/bare-metal-cloud/dedicated-servers/ipmi.md) from the `IPMI/KVM ` tab in the Control Panel. The IPMI console works regardless of the operating system's connectivity state. ::: After your first connection, change the administrator password from within Windows (in the RDP session, press `Ctrl` + `Alt` + `End` > `Change a password `). ### Step 3 — Complete the initial Windows configuration [](#) Before connecting the server to other OVHcloud services, complete the basic Windows setup. - Run Windows Update and install the latest updates. - Set the server host name, time zone and keyboard layout. - Configure the Windows Firewall to allow the services you intend to run. For a Windows-specific firewall walkthrough, refer to the [Activating the firewall on a Windows server](/en/guides/bare-metal-cloud/dedicated-servers/activate-port-firewall-soft-win.md) guide. :::warning OVHcloud provides you with services for which you are responsible for the configuration and management. If you need assistance, contact a [specialist service provider](https://partner.ovhcloud.com/en-gb/directory/). ::: ### Step 4 — Configure Windows to interact with OVHcloud services [](#) This section covers the Windows-side configuration for the OVHcloud services most commonly attached to a dedicated server. Each sub-section is independent — follow only the ones relevant to your setup. In each one, the first part is done in the OVHcloud Control Panel and the second part inside Windows Server. #### 4a — Additional IP An Additional IP is an extra public IP address routed to your server. After ordering it, you must declare it inside Windows for the server to answer on that address. **In the OVHcloud Control Panel** Order the Additional IP from the `Network ` menu of the Control Panel, in the `IP ` section: click `Order IPs `. For more information, see the [Additional IP](https://www.ovhcloud.com/en-gb/bare-metal/ip/) page. **In Windows Server** 1. Open Control Panel > Network and Sharing Center > Change adapter settings, then open the properties of your network adapter. 2. Select Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced, and add the Additional IP address. On the OVHcloud network, an Additional IP is routed individually to the server. Use the netmask and gateway that match your server's main IP configuration. :::tip If you intend to assign the Additional IP to a virtual machine rather than the host, refer to the [Configuring an IP block in a vRack](/en/guides/bare-metal-cloud/dedicated-servers/configuring-an-ip-block-in-a-vrack.md) guide. ::: #### 4b — vRack private network The vRack is a private layer-2 network that lets your dedicated server communicate privately with other OVHcloud services (other dedicated servers, Public Cloud instances, and so on). **In the OVHcloud Control Panel** From the `Network ` menu of the Control Panel, open the `vRack ` section, select your vRack and add this server to it. **In Windows Server** 1. Open the properties of the **private** network adapter (the second interface, dedicated to the vRack). 2. Assign a static private IPv4 address from your vRack addressing plan. Leave the default gateway empty — the vRack is a layer-2 network with no OVHcloud-provided gateway. For the full procedure, including OVHcloud Link Aggregation (OLA) considerations, refer to the [Configuring the vRack on a dedicated server](/en/guides/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md) guide. #### 4c — IPv6 Every OVHcloud dedicated server is delivered with a /64 IPv6 block. The address is not configured automatically in Windows and must be added manually. **In the OVHcloud Control Panel** Retrieve your IPv6 address, prefix and gateway from the `General information ` tab of your server: the `Network ` section shows `IPv6 ` and `IPv6 Gateway `. **In Windows Server** 1. Open the properties of your network adapter and select Internet Protocol Version 6 (TCP/IPv6) > Properties. 2. Enter the IPv6 address, the prefix length, and the IPv6 default gateway. For the addressing details and the gateway configuration specific to OVHcloud, refer to the [IPv6 configuration](/en/guides/bare-metal-cloud/dedicated-servers/network-ipv6.md) guide. #### 4d — Backup Storage Backup Storage is a complimentary storage space included with your dedicated server. It can be accessed over FTP, CIFS (SMB) or NFS and is best used as a complementary backup target. **In the OVHcloud Control Panel** 1. In the Backup storage tab of your server, click Enable backup storage. Once active, the tab shows the FTP server address and username, and lets you set the password for the space. 2. Authorise your server's IP address to access the space. **In Windows Server** Access the space using one of the supported protocols: - **CIFS (SMB)** — map it as a network drive (This PC > Map network drive). - **FTP** — connect with any FTP client, using the connection details from the Control Panel and the password you set. For activation and protocol details, refer to the [Backup Storage on dedicated servers](/en/guides/bare-metal-cloud/dedicated-servers/services-backup-storage.md) guide and the [Backup Storage](https://www.ovhcloud.com/en-gb/bare-metal/backup-storage/) page. #### 4e — Backup Agent Backup Storage is a passive storage space — it does not back up your data by itself. For managed, automated protection, OVHcloud offers **Backup Agent**, a separate backup service for Bare Metal servers. Once ordered, you deploy a lightweight agent on your Windows server, which then performs daily incremental, encrypted and immutable backups to an isolated Object Storage vault located in a different region from the server. **In the OVHcloud Control Panel** On the `General information ` tab, in the `Service status ` section, use the `Backup Agent ` entry and click `Manage Backup Agent `. You can also enable it during the OS reinstallation. **In Windows Server** Once the agent is deployed, configure your first backup (source data, schedule and retention). For the full procedure, refer to the [Backup Agent overview](/en/guides/storage-and-backup/backup-agent/overview.md) and the [How to configure your first backup](/en/guides/storage-and-backup/backup-agent/first-configuration.md) guide. ### Step 5 — Verify the configuration [](#) Confirm that each configured service works as expected. | Check | How | Expected result | | -------------- | --------------------------------------------------------------------------------------- | ----------------------------- | | RDP access | Connect with Remote Desktop Connection to the main IPv4 | Windows desktop loads | | Additional IP | From an external host, `ping` the Additional IP | The server replies | | vRack | From another vRack member, `ping` the private IP | The server replies | | IPv6 | Run `ping -6 ipv6.google.com` from the server | Replies are received | | Backup Storage | Open the mapped CIFS (SMB) drive or connect over FTP | Files can be read and written | ### Troubleshooting [](#) | Issue | Possible cause | Solution | | ----------------------------- | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | RDP connection fails | Firewall rules or network restrictions on the local device | Verify local firewall and network settings; connect through the [IPMI console](/en/guides/bare-metal-cloud/dedicated-servers/ipmi.md) as a fallback. | | Additional IP not reachable | Incorrect mask or gateway in Windows | Re-check the values entered in the advanced TCP/IPv4 settings. | | vRack peer unreachable | Wrong private subnet or a gateway set on the private adapter | Confirm the private addressing plan and leave the gateway empty. | | Server offline after a change | Misconfiguration during setup | Boot into [rescue mode](/en/guides/bare-metal-cloud/dedicated-servers/rescue-customer-windows.md) to inspect and repair the configuration. | ## Go further [Activating the firewall on a Windows server](/en/guides/bare-metal-cloud/dedicated-servers/activate-port-firewall-soft-win.md) [Configuring software RAID on a Windows server](/en/guides/bare-metal-cloud/dedicated-servers/raid-soft-windows.md) [Using rescue mode on a Windows server](/en/guides/bare-metal-cloud/dedicated-servers/rescue-customer-windows.md) [Backup Agent overview](/en/guides/storage-and-backup/backup-agent/overview.md) [Using the IPMI console with dedicated servers](/en/guides/bare-metal-cloud/dedicated-servers/ipmi.md) [Managing your OVHcloud licences](/en/guides/bare-metal-cloud/dedicated-servers/windows-key.md) [OVHcloud API and OS installation](/en/guides/bare-metal-cloud/dedicated-servers/api-os-installation.md) Join our [community of users](https://community.ovhcloud.com/).