Skip to content

Commit 34a2aae

Browse files
ofrancChangelog botbene2k1jcirinosclwyldecarvalho-doc
authored
feat(changelog): instances-changed-windows-images-network-configuration- 2025-08-25 (#5457)
* feat(changelog): add new entry * docs(ins): update changelog content * docs(ins): fix typo * Apply suggestions from code review Co-authored-by: Jessica <[email protected]> Co-authored-by: ldecarvalho-doc <[email protected]> * feat(ins): move content * Update pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx Co-authored-by: Jessica <[email protected]> * Change the note location and msg to indicate that a reboot is mandatory * feat(ins): minor updates * fix(ins): typo --------- Co-authored-by: Changelog bot <[email protected]> Co-authored-by: Benedikt Rollik <[email protected]> Co-authored-by: Benedikt Rollik <[email protected]> Co-authored-by: Jessica <[email protected]> Co-authored-by: ldecarvalho-doc <[email protected]> Co-authored-by: Louis Bouchard <[email protected]>
1 parent 0e42940 commit 34a2aae

File tree

3 files changed

+197
-0
lines changed

3 files changed

+197
-0
lines changed

‎changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Windows Images - Network configuration now uses DHCP. Serial console enabled
3+
status: changed
4+
date: 2025-08-25
5+
category: compute
6+
product: instances
7+
---
8+
9+
Windows Server 2022 and Windows Server 2022 Core images now use DHCP for network configuration by default, consistent with all existing Instance OS images.
10+
11+
For running Instances, no network configuration changes are needed unless you modify the public IPv4 address.
12+
13+
If you change the public IPv4 address, the Instance will retain its existing static configuration and continue using the previous address. To enable DHCP for your Instance, follow our [dedicated documentation](/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022/) before updating the public IPv4 address.

‎menu/navigation.json‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1661,6 +1661,10 @@
16611661
{
16621662
"label": "Compatibility between Scaleway OS Images and Flexible IPs",
16631663
"slug": "comaptibility-scw-os-images-flexible-ip"
1664+
},
1665+
{
1666+
"label": "Enabling DHCP network configuration for Windows Server 2022 Instances",
1667+
"slug": "enabling-dhcp-network-configuration-windows-server-2022"
16641668
}
16651669
],
16661670
"label": "Additional Content",

‎pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx‎

Lines changed: 180 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,180 @@
1+
---
2+
title: Enabling DHCP network configuration for Windows Server 2022 Instances
3+
description: This page helps you to enable DHCP network configuration for Windows Server 2022 Instances
4+
tags: windows instance dhcp console
5+
dates:
6+
validation: 2025-08-25
7+
posted: 2023-08-25
8+
---
9+
import Requirements from '@macros/iam/requirements.mdx'
10+
11+
12+
The latest Windows Server 2022 and Windows Server 2022 Core images on Scaleway Instances now use DHCP for network configuration by default. This aligns with the standard mechanism used across all Scaleway Instance OS images.
13+
14+
For existing running Instances, no changes to network configuration are necessary unless you plan to update the public IPv4 address. In such cases, the Instance may retain its static network configuration, continuing to use the previous public IPv4 address.
15+
Follow the steps below to switch to DHCP, ensure the new address is applied correctly, and enable DHCP before assigning the new IP.
16+
17+
<Message type="important">
18+
These steps involve modifying network settings, which carry a risk of losing network connectivity (e.g., SSH or RDP access). To avoid this, enable and configure Serial Console access on your Instance beforehand. This allows you to maintain access via the Scaleway console even if standard network connections fail.
19+
</Message>
20+
21+
<Requirements />
22+
23+
- A Scaleway account logged into the [console](https://console.scaleway.com)
24+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
25+
- An [Instance](/instances/how-to/create-an-instance/) running on Windows Server 2022
26+
27+
28+
## Enabling Serial Console access
29+
30+
Scaleway provides a Serial Console (TTY) for Instances, which is essential for troubleshooting network issues.
31+
For Windows Server Instances, you must configure the OS to enable the Special Administration Console (SAC) for serial access.
32+
33+
### Enabling SAC on Windows (OS configuration)
34+
35+
Connect to your Windows Instance via RDP or another method and run the following commands in an elevated Command Prompt (Administrator) or PowerShell:
36+
37+
1. Enable Emergency Management Services (EMS):
38+
```
39+
bcdedit /emssettings EMSPORT:1
40+
bcdedit /ems {current} on
41+
```
42+
43+
2. (Optional, but recommended) Enable the boot menu in the Serial Console:
44+
```
45+
bcdedit /set {bootmgr} displaybootmenu yes
46+
bcdedit /set {bootmgr} timeout 10
47+
bcdedit /set {bootmgr} bootems yes
48+
```
49+
50+
3. Reboot the Instance to apply the changes:
51+
```
52+
shutdown /r /t 0
53+
```
54+
55+
For more details, refer to [Microsoft's Azure Serial Console for Windows](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/serial-console-windows) documentation on enabling Serial Console for Windows VMs.
56+
57+
### Accessing the Serial Console via Scaleway console
58+
59+
1. Log in to the [Scaleway console](https://console.scaleway.com/).
60+
2. Navigate to **Compute** > **CPU & GPU Instances**.
61+
3. Click on the Instance you want to configure.
62+
4. On the Instance **Overview** page, click **Console** to open the Serial Console in a pop-up window.
63+
5. Once connected, you should see the SAC prompt. Use commands like `cmd` to start a command channel, then `ch -si 1` to switch to it.
64+
65+
For more information on using the Scaleway Serial Console, see [How to use the Serial Console to connect to an Instance](/instances/how-to/use-serial-console/).
66+
67+
## Steps to enable DHCP configuration
68+
69+
Once Serial Console access is confirmed, configure DHCP using the Server Configuration tool (sconfig) on your Windows Instance. You can access sconfig via RDP, PowerShell, or the Serial Console.
70+
71+
<Message type="note">
72+
The reboot of the Instance is required for full activation.
73+
</Message>
74+
75+
1. Open an elevated Command Prompt (Administrator) or PowerShell and run:
76+
```
77+
sconfig
78+
```
79+
80+
2. In the sconfig menu, select option **8** (Network settings).
81+
82+
3. Select the network adapter index (usually **1** for the primary adapter).
83+
84+
4. Select option **1** (Set network adapter address).
85+
86+
5. Choose **D** for DHCP.
87+
88+
6. The system will apply the changes and release any existing DHCP lease.
89+
90+
7. Return to the main menu and select option **13** (Restart server) to reboot and activate the configuration.
91+
92+
Below is an example interaction for reference:
93+
94+
```sh
95+
===============================================================================
96+
Welcome to Windows Server 2022 Datacenter
97+
===============================================================================
98+
99+
1) Domain/workgroup: Workgroup: WORKGROUP
100+
2) Computer name: WIN-010DQB68HIR
101+
3) Add local administrator
102+
4) Remote management: Enabled
103+
104+
5) Update setting: Download only
105+
6) Install updates
106+
7) Remote desktop: Enabled (all clients)
107+
108+
8) Network settings
109+
9) Date and time
110+
10) Telemetry setting: Required
111+
11) Windows activation
112+
113+
12) Log off user
114+
13) Restart server
115+
14) Shut down server
116+
15) Exit to command line (PowerShell)
117+
118+
Enter number to select an option: 8
119+
===============================================================================
120+
Network settings
121+
===============================================================================
122+
123+
Available network adapters:
124+
125+
Index # | IP address | Description
126+
1 | 1.1.1.1 | Red Hat VirtIO Ethernet Adapter
127+
128+
Select network adapter index # (Blank=Cancel): 1
129+
===============================================================================
130+
Network adapter settings
131+
===============================================================================
132+
133+
NIC index: 1
134+
Description: Red Hat VirtIO Ethernet Adapter
135+
IP address: 1.1.1.1,
136+
fe80::dc00:ff:ff:ff:ff:ff
137+
Subnet mask: 255.255.255.255
138+
DHCP enabled: False
139+
140+
Default gateway: 62.210.0.1
141+
Preferred DNS server:
142+
Alternate DNS server:
143+
144+
1) Set network adapter address
145+
2) Set DNS servers
146+
3) Clear DNS server settings
147+
148+
Enter selection (Blank=Cancel): 1
149+
Select (D)HCP or (S)tatic IP address (Blank=Cancel): D
150+
Setting NIC to use DHCP...
151+
Successfully set gateway.
152+
Successfully enabled DHCP.
153+
Successfully released DHCP lease.. : 00-01-00-01-30-3E-73-36-DE-00-00-84-DB-2B
154+
(Press ENTER to continue):
155+
===============================================================================
156+
Welcome to Windows Server 2022 Datacenter
157+
===============================================================================
158+
159+
1) Domain/workgroup: Workgroup: WORKGROUP
160+
2) Computer name: WIN-010DQB68HIR
161+
3) Add local administrator
162+
4) Remote management: Enabled
163+
164+
5) Update setting: Download only
165+
6) Install updates
166+
7) Remote desktop: Enabled (all clients)
167+
168+
8) Network settings
169+
9) Date and time
170+
10) Telemetry setting: Required
171+
11) Windows activation
172+
173+
12) Log off user
174+
13) Restart server
175+
14) Shut down server
176+
15) Exit to command line (PowerShell)
177+
178+
Enter number to select an option: 13
179+
Are you sure you want to restart? (Y)es or (N)o: Y
180+
```

0 commit comments

Comments
 (0)