Skip to content

Commit 976ae13

Browse files
committed
docs(ins): update changelog content
1 parent 132064c commit 976ae13

File tree

3 files changed

+185
-96
lines changed

3 files changed

+185
-96
lines changed

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

Lines changed: 3 additions & 96 deletions
Original file line numberDiff line numberDiff line change
@@ -6,104 +6,11 @@ category: compute
66
product: instances
77
---
88

9-
The newly released Windows server 2022 and Windows server 2022 core images now use DHCP for network configuration. This is the default mechanism for all existing Instances O/S Images.
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.
1010

11-
For currently running instances, no specific network configuration is required unless you decide to change the public IPv4 address of your instance.
11+
For running Instances, no network configuration changes are needed unless you modify the public IPv4 address.
1212

13-
In this case, the existing static configuration will remain and your instance will keep using the previous public IPv4 address. To enable DHCP configuration for your instance do the following prior to setting a new public IPv4 address.
14-
15-
<Message type=important> There is a risk of loosing network connectivity while doing the following steps. It is advisable to enable the serial console prior to run those steps so you keep serial access to your instance. The method is described in the document [Azure Serial Console for Windows](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/serial-console-windows)</Message>
16-
17-
Not that the last step reboots your instance. This step may be delayed until a reboot is possible :
18-
```
19-
================================================================================
20-
Welcome to Windows Server 2022 Datacenter
21-
================================================================================
22-
23-
1) Domain/workgroup: Workgroup: WORKGROUP
24-
2) Computer name: WIN-010DQB68HIR
25-
3) Add local administrator
26-
4) Remote management: Enabled
27-
28-
5) Update setting: Download only
29-
6) Install updates
30-
7) Remote desktop: Enabled (all clients)
31-
32-
8) Network settings
33-
9) Date and time
34-
10) Telemetry setting: Required
35-
11) Windows activation
36-
37-
12) Log off user
38-
13) Restart server
39-
14) Shut down server
40-
15) Exit to command line (PowerShell)
41-
42-
Enter number to select an option: 8
43-
================================================================================
44-
Network settings
45-
================================================================================
46-
47-
Available network adapters:
48-
49-
Index # | IP address | Description
50-
1 | 1.1.1.1 | Red Hat VirtIO Ethernet Adapter
51-
52-
Select network adapter index # (Blank=Cancel): 1
53-
================================================================================
54-
Network adapter settings
55-
================================================================================
56-
57-
NIC index: 1
58-
Description: Red Hat VirtIO Ethernet Adapter
59-
IP address: 1.1.1.1,
60-
fe80::dc00:ff:ff:ff:ff:ff
61-
Subnet mask: 255.255.255.255
62-
DHCP enabled: False
63-
64-
Default gateway: 62.210.0.1
65-
Preferred DNS server:
66-
Alternate DNS server:
67-
68-
1) Set network adapter address
69-
2) Set DNS servers
70-
3) Clear DNS server settings
71-
72-
Enter selection (Blank=Cancel): 1
73-
Select (D)HCP or (S)tatic IP address (Blank=Cancel): D
74-
Setting NIC to use DHCP...
75-
Successfully set gateway.
76-
Successfully enabled DHCP.
77-
Successfully released DHCP lease.. : 00-01-00-01-30-3E-73-36-DE-00-00-84-DB-2B
78-
(Press ENTER to continue):
79-
================================================================================
80-
Welcome to Windows Server 2022 Datacenter
81-
================================================================================
82-
83-
1) Domain/workgroup: Workgroup: WORKGROUP
84-
2) Computer name: WIN-010DQB68HIR
85-
3) Add local administrator
86-
4) Remote management: Enabled
87-
88-
5) Update setting: Download only
89-
6) Install updates
90-
7) Remote desktop: Enabled (all clients)
91-
92-
8) Network settings
93-
9) Date and time
94-
10) Telemetry setting: Required
95-
11) Windows activation
96-
97-
12) Log off user
98-
13) Restart server
99-
14) Shut down server
100-
15) Exit to command line (PowerShell)
101-
102-
Enter number to select an option:.8: 13
103-
Are you sure you want to restart? (Y)es or (N)o: Y
104-
105-
```
106-
This will ensure that DHCP network configuration is properly configured and activated in your windows instance.
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/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022/) before updating the public IPv4 address.
10714

10815

10916

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

0 commit comments

Comments
 (0)