From 132064c178ba9029c52df57cc90cc845e84747f5 Mon Sep 17 00:00:00 2001 From: Changelog bot Date: Mon, 25 Aug 2025 13:23:56 +0000 Subject: [PATCH 1/9] feat(changelog): add new entry --- ...-windows-images-network-configuration-.mdx | 109 ++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx diff --git a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx new file mode 100644 index 0000000000..b53718a022 --- /dev/null +++ b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx @@ -0,0 +1,109 @@ +--- +title: Windows Images - Network configuration now uses DHCP. Serial console enabled +status: changed +date: 2025-08-25 +category: compute +product: instances +--- + +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. + +For currently running instances, no specific network configuration is required unless you decide to change the public IPv4 address of your instance. + +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. + + 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) + +Not that the last step reboots your instance. This step may be delayed until a reboot is possible : +``` + ================================================================================ + Welcome to Windows Server 2022 Datacenter + ================================================================================ + + 1) Domain/workgroup: Workgroup: WORKGROUP + 2) Computer name: WIN-010DQB68HIR + 3) Add local administrator + 4) Remote management: Enabled + + 5) Update setting: Download only + 6) Install updates + 7) Remote desktop: Enabled (all clients) + + 8) Network settings + 9) Date and time + 10) Telemetry setting: Required + 11) Windows activation + + 12) Log off user + 13) Restart server + 14) Shut down server + 15) Exit to command line (PowerShell) + +Enter number to select an option: 8 + ================================================================================ + Network settings + ================================================================================ + + Available network adapters: + + Index # | IP address | Description + 1 | 1.1.1.1 | Red Hat VirtIO Ethernet Adapter + + Select network adapter index # (Blank=Cancel): 1 + ================================================================================ + Network adapter settings + ================================================================================ + + NIC index: 1 + Description: Red Hat VirtIO Ethernet Adapter + IP address: 1.1.1.1, + fe80::dc00:ff:ff:ff:ff:ff + Subnet mask: 255.255.255.255 + DHCP enabled: False + + Default gateway: 62.210.0.1 + Preferred DNS server: + Alternate DNS server: + + 1) Set network adapter address + 2) Set DNS servers + 3) Clear DNS server settings + + Enter selection (Blank=Cancel): 1 +Select (D)HCP or (S)tatic IP address (Blank=Cancel): D + Setting NIC to use DHCP... + Successfully set gateway. + Successfully enabled DHCP. + Successfully released DHCP lease.. : 00-01-00-01-30-3E-73-36-DE-00-00-84-DB-2B + (Press ENTER to continue): + ================================================================================ + Welcome to Windows Server 2022 Datacenter + ================================================================================ + + 1) Domain/workgroup: Workgroup: WORKGROUP + 2) Computer name: WIN-010DQB68HIR + 3) Add local administrator + 4) Remote management: Enabled + + 5) Update setting: Download only + 6) Install updates + 7) Remote desktop: Enabled (all clients) + + 8) Network settings + 9) Date and time + 10) Telemetry setting: Required + 11) Windows activation + + 12) Log off user + 13) Restart server + 14) Shut down server + 15) Exit to command line (PowerShell) + + Enter number to select an option:.8: 13 +Are you sure you want to restart? (Y)es or (N)o: Y + +``` +This will ensure that DHCP network configuration is properly configured and activated in your windows instance. + + + From 976ae139a946ec1ea390673f074cf3385ed433ed Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:00:44 +0200 Subject: [PATCH 2/9] docs(ins): update changelog content --- ...-windows-images-network-configuration-.mdx | 99 +--------- menu/navigation.json | 4 + ...work-configuration-windows-server-2022.mdx | 178 ++++++++++++++++++ 3 files changed, 185 insertions(+), 96 deletions(-) create mode 100644 pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx diff --git a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx index b53718a022..01fc4560d5 100644 --- a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx +++ b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx @@ -6,104 +6,11 @@ category: compute product: instances --- -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. +Windows Server 2022 and Windows Server 2022 Core images now use DHCP for network configuration by default, consistent with all existing Instance OS images. -For currently running instances, no specific network configuration is required unless you decide to change the public IPv4 address of your instance. +For running Instances, no network configuration changes are needed unless you modify the public IPv4 address. -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. - - 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) - -Not that the last step reboots your instance. This step may be delayed until a reboot is possible : -``` - ================================================================================ - Welcome to Windows Server 2022 Datacenter - ================================================================================ - - 1) Domain/workgroup: Workgroup: WORKGROUP - 2) Computer name: WIN-010DQB68HIR - 3) Add local administrator - 4) Remote management: Enabled - - 5) Update setting: Download only - 6) Install updates - 7) Remote desktop: Enabled (all clients) - - 8) Network settings - 9) Date and time - 10) Telemetry setting: Required - 11) Windows activation - - 12) Log off user - 13) Restart server - 14) Shut down server - 15) Exit to command line (PowerShell) - -Enter number to select an option: 8 - ================================================================================ - Network settings - ================================================================================ - - Available network adapters: - - Index # | IP address | Description - 1 | 1.1.1.1 | Red Hat VirtIO Ethernet Adapter - - Select network adapter index # (Blank=Cancel): 1 - ================================================================================ - Network adapter settings - ================================================================================ - - NIC index: 1 - Description: Red Hat VirtIO Ethernet Adapter - IP address: 1.1.1.1, - fe80::dc00:ff:ff:ff:ff:ff - Subnet mask: 255.255.255.255 - DHCP enabled: False - - Default gateway: 62.210.0.1 - Preferred DNS server: - Alternate DNS server: - - 1) Set network adapter address - 2) Set DNS servers - 3) Clear DNS server settings - - Enter selection (Blank=Cancel): 1 -Select (D)HCP or (S)tatic IP address (Blank=Cancel): D - Setting NIC to use DHCP... - Successfully set gateway. - Successfully enabled DHCP. - Successfully released DHCP lease.. : 00-01-00-01-30-3E-73-36-DE-00-00-84-DB-2B - (Press ENTER to continue): - ================================================================================ - Welcome to Windows Server 2022 Datacenter - ================================================================================ - - 1) Domain/workgroup: Workgroup: WORKGROUP - 2) Computer name: WIN-010DQB68HIR - 3) Add local administrator - 4) Remote management: Enabled - - 5) Update setting: Download only - 6) Install updates - 7) Remote desktop: Enabled (all clients) - - 8) Network settings - 9) Date and time - 10) Telemetry setting: Required - 11) Windows activation - - 12) Log off user - 13) Restart server - 14) Shut down server - 15) Exit to command line (PowerShell) - - Enter number to select an option:.8: 13 -Are you sure you want to restart? (Y)es or (N)o: Y - -``` -This will ensure that DHCP network configuration is properly configured and activated in your windows instance. +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. diff --git a/menu/navigation.json b/menu/navigation.json index 9adb842ca4..77c3520f75 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -1661,6 +1661,10 @@ { "label": "Compatibility between Scaleway OS Images and Flexible IPs", "slug": "comaptibility-scw-os-images-flexible-ip" + }, + { + "label": "Enabling DHCP network configuration for Windows Server 2022 Instances", + "slug": "enabling-dhcp-network-configuration-windows-server-2022" } ], "label": "Additional Content", diff --git a/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx new file mode 100644 index 0000000000..e41f3f8e25 --- /dev/null +++ b/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -0,0 +1,178 @@ +--- +title: Enabling DHCP Network Configuration for Windows Server 2022 Instances +description: This page helps you to enable DHCP network configuration for Windows Server 2022 Instances +tags: windows instance dhcp console +dates: + validation: 2025-08-25 + posted: 2023-08-25 +--- +import Requirements from '@macros/iam/requirements.mdx' + + +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. + +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. + + + 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. + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) running Windows Server 2O22 + + +## Enabling serial console access + +Scaleway provides a serial console (TTY) for Instances, which is essential for troubleshooting network issues. +For Windows Server Instances, you must configure the OS to enable the Special Administration Console (SAC) for serial access. + +### Enabling SAC in Windows (OS Configuration) + +Connect to your Windows Instance via RDP or another method and run the following commands in an elevated Command Prompt (Administrator) or PowerShell: + +1. Enable Emergency Management Services (EMS): + ``` + bcdedit /emssettings EMSPORT:1 + bcdedit /ems {current} on + ``` + +2. (Optional but recommended) Enable the boot menu in serial console: + ``` + bcdedit /set {bootmgr} displaybootmenu yes + bcdedit /set {bootmgr} timeout 10 + bcdedit /set {bootmgr} bootems yes + ``` + +3. Reboot the Instance for changes to take effect: + ``` + shutdown /r /t 0 + ``` + +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. + +### Accesing the serial console via Scaleway console + +1. Log in to the [Scaleway console](https://console.scaleway.com/). +2. Navigate to **Compute** > **CPU & GPU Instances**. +3. Click on the Instance your want to configure. +4. On the Instance **Overview** page, click **Console** to open the serial console in a pop-up window. +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. + +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/). + +## Steps to enable DHCP configuration + +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. + +1. Open an elevated Command Prompt (Administrator) or PowerShell and run: + ``` + sconfig + ``` + +2. In the sconfig menu, select option **8** (Network settings). + +3. Select the network adapter index (usually **1** for the primary adapter). + +4. Select option **1** (Set network adapter address). + +5. Choose **D** for DHCP. + +6. The system will apply the changes and release any existing DHCP lease. + +7. Return to the main menu and select option **13** (Restart server) to reboot and activate the configuration. + + The reboot can be delayed if immediate downtime is not feasible, but it is required for full activation. + + +Below is an example interaction for reference: + +```sh +=============================================================================== + Welcome to Windows Server 2022 Datacenter +=============================================================================== + + 1) Domain/workgroup: Workgroup: WORKGROUP + 2) Computer name: WIN-010DQB68HIR + 3) Add local administrator + 4) Remote management: Enabled + + 5) Update setting: Download only + 6) Install updates + 7) Remote desktop: Enabled (all clients) + + 8) Network settings + 9) Date and time + 10) Telemetry setting: Required + 11) Windows activation + + 12) Log off user + 13) Restart server + 14) Shut down server + 15) Exit to command line (PowerShell) + +Enter number to select an option: 8 +=============================================================================== + Network settings +=============================================================================== + +Available network adapters: + +Index # | IP address | Description +1 | 1.1.1.1 | Red Hat VirtIO Ethernet Adapter + +Select network adapter index # (Blank=Cancel): 1 +=============================================================================== + Network adapter settings +=============================================================================== + +NIC index: 1 +Description: Red Hat VirtIO Ethernet Adapter +IP address: 1.1.1.1, + fe80::dc00:ff:ff:ff:ff:ff +Subnet mask: 255.255.255.255 +DHCP enabled: False + +Default gateway: 62.210.0.1 +Preferred DNS server: +Alternate DNS server: + + 1) Set network adapter address + 2) Set DNS servers + 3) Clear DNS server settings + +Enter selection (Blank=Cancel): 1 +Select (D)HCP or (S)tatic IP address (Blank=Cancel): D +Setting NIC to use DHCP... +Successfully set gateway. +Successfully enabled DHCP. +Successfully released DHCP lease.. : 00-01-00-01-30-3E-73-36-DE-00-00-84-DB-2B +(Press ENTER to continue): +=============================================================================== + Welcome to Windows Server 2022 Datacenter +=============================================================================== + + 1) Domain/workgroup: Workgroup: WORKGROUP + 2) Computer name: WIN-010DQB68HIR + 3) Add local administrator + 4) Remote management: Enabled + + 5) Update setting: Download only + 6) Install updates + 7) Remote desktop: Enabled (all clients) + + 8) Network settings + 9) Date and time + 10) Telemetry setting: Required + 11) Windows activation + + 12) Log off user + 13) Restart server + 14) Shut down server + 15) Exit to command line (PowerShell) + +Enter number to select an option: 13 +Are you sure you want to restart? (Y)es or (N)o: Y +``` From 39d5da93fd2424e61d2783a79a74e09a187c74a0 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:02:54 +0200 Subject: [PATCH 3/9] docs(ins): fix typo --- ...stances-changed-windows-images-network-configuration-.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx index 01fc4560d5..ff5b42ce98 100644 --- a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx +++ b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx @@ -10,7 +10,4 @@ Windows Server 2022 and Windows Server 2022 Core images now use DHCP for network For running Instances, no network configuration changes are needed unless you modify the public IPv4 address. -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. - - - +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. From c7091b0c6e37f1f35e4f76026179dea94127d678 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:12:55 +0200 Subject: [PATCH 4/9] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> Co-authored-by: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> --- ...ing-dhcp-network-configuration-windows-server-2022.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx index e41f3f8e25..c582ee2064 100644 --- a/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx +++ b/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -1,5 +1,5 @@ --- -title: Enabling DHCP Network Configuration for Windows Server 2022 Instances +title: Enabling DHCP network configuration for Windows Server 2022 Instances description: This page helps you to enable DHCP network configuration for Windows Server 2022 Instances tags: windows instance dhcp console dates: @@ -39,7 +39,7 @@ Connect to your Windows Instance via RDP or another method and run the following bcdedit /ems {current} on ``` -2. (Optional but recommended) Enable the boot menu in serial console: +2. (Optional but recommended) Enable the boot menu in the serial console: ``` bcdedit /set {bootmgr} displaybootmenu yes bcdedit /set {bootmgr} timeout 10 @@ -53,11 +53,11 @@ Connect to your Windows Instance via RDP or another method and run the following 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. -### Accesing the serial console via Scaleway console +### Accessing the serial console via Scaleway console 1. Log in to the [Scaleway console](https://console.scaleway.com/). 2. Navigate to **Compute** > **CPU & GPU Instances**. -3. Click on the Instance your want to configure. +3. Click on the Instance you want to configure. 4. On the Instance **Overview** page, click **Console** to open the serial console in a pop-up window. 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. From ca0bac740264d740388e9b19f12dd9f8769b87db Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:14:24 +0200 Subject: [PATCH 5/9] feat(ins): move content --- ...-instances-changed-windows-images-network-configuration-.mdx | 2 +- .../enabling-dhcp-network-configuration-windows-server-2022.mdx | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename pages/instances/{troubleshooting => reference-content}/enabling-dhcp-network-configuration-windows-server-2022.mdx (100%) diff --git a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx index ff5b42ce98..42165d16d8 100644 --- a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx +++ b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx @@ -10,4 +10,4 @@ Windows Server 2022 and Windows Server 2022 Core images now use DHCP for network For running Instances, no network configuration changes are needed unless you modify the public IPv4 address. -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. +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. diff --git a/pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx similarity index 100% rename from pages/instances/troubleshooting/enabling-dhcp-network-configuration-windows-server-2022.mdx rename to pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx From d5d3046999715d0fca7bc5e6d2f219179a30bcf1 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:20:12 +0200 Subject: [PATCH 6/9] Update pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- .../enabling-dhcp-network-configuration-windows-server-2022.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx index c582ee2064..7283205cba 100644 --- a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx +++ b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -21,7 +21,7 @@ For existing running Instances, no changes to network configuration are necessar - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/instances/how-to/create-an-instance/) running Windows Server 2O22 +- An [Instance](/instances/how-to/create-an-instance/) running on Windows Server 2022 ## Enabling serial console access From a97ee5aa45510eefef44bf0b3403faa259dc1452 Mon Sep 17 00:00:00 2001 From: Louis Bouchard Date: Mon, 25 Aug 2025 16:35:55 +0200 Subject: [PATCH 7/9] Change the note location and msg to indicate that a reboot is mandatory --- ...ling-dhcp-network-configuration-windows-server-2022.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx index 7283205cba..02005ea0a7 100644 --- a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx +++ b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -67,6 +67,10 @@ For more on using the Scaleway serial console, see [How to use the serial consol 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. + + The reboot of the instance is required for full activation. + + 1. Open an elevated Command Prompt (Administrator) or PowerShell and run: ``` sconfig @@ -83,9 +87,6 @@ Once serial console access is confirmed, proceed to configure DHCP using the Ser 6. The system will apply the changes and release any existing DHCP lease. 7. Return to the main menu and select option **13** (Restart server) to reboot and activate the configuration. - - The reboot can be delayed if immediate downtime is not feasible, but it is required for full activation. - Below is an example interaction for reference: From 331139747f29cd780637b86c9c75aac6b9e4e051 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:40:48 +0200 Subject: [PATCH 8/9] feat(ins): minor updates --- ...work-configuration-windows-server-2022.mdx | 29 ++++++++++--------- 1 file changed, 15 insertions(+), 14 deletions(-) diff --git a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx index 02005ea0a7..95094b0d79 100644 --- a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx +++ b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -11,10 +11,11 @@ import Requirements from '@macros/iam/requirements.mdx' 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. -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. +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. +Follow the steps below to switch to DHCP, ensure the new address is applied correctly, and enable DHCP before assigning the new IP. - 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. + 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. @@ -24,12 +25,12 @@ For existing running Instances, no changes to network configuration are necessar - An [Instance](/instances/how-to/create-an-instance/) running on Windows Server 2022 -## Enabling serial console access +## Enabling Serial Console access -Scaleway provides a serial console (TTY) for Instances, which is essential for troubleshooting network issues. +Scaleway provides a Serial Console (TTY) for Instances, which is essential for troubleshooting network issues. For Windows Server Instances, you must configure the OS to enable the Special Administration Console (SAC) for serial access. -### Enabling SAC in Windows (OS Configuration) +### Enabling SAC on Windows (OS configuration) Connect to your Windows Instance via RDP or another method and run the following commands in an elevated Command Prompt (Administrator) or PowerShell: @@ -39,36 +40,36 @@ Connect to your Windows Instance via RDP or another method and run the following bcdedit /ems {current} on ``` -2. (Optional but recommended) Enable the boot menu in the serial console: +2. (Optional, but recommended) Enable the boot menu in the Serial Console: ``` bcdedit /set {bootmgr} displaybootmenu yes bcdedit /set {bootmgr} timeout 10 bcdedit /set {bootmgr} bootems yes ``` -3. Reboot the Instance for changes to take effect: +3. Reboot the Instance to apply the changes: ``` shutdown /r /t 0 ``` -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. +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. -### Accessing the serial console via Scaleway console +### Accessing the Serial Console via Scaleway console 1. Log in to the [Scaleway console](https://console.scaleway.com/). 2. Navigate to **Compute** > **CPU & GPU Instances**. 3. Click on the Instance you want to configure. -4. On the Instance **Overview** page, click **Console** to open the serial console in a pop-up window. -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. +4. On the Instance **Overview** page, click **Console** to open the Serial Console in a pop-up window. +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. -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/). +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/). ## Steps to enable DHCP configuration -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. +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. - The reboot of the instance is required for full activation. + The reboot of the Instance is required for full activation. 1. Open an elevated Command Prompt (Administrator) or PowerShell and run: From db3b35b200dbd2fcc8719d0fbd3bb425520fd00c Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 25 Aug 2025 16:42:09 +0200 Subject: [PATCH 9/9] fix(ins): typo --- .../enabling-dhcp-network-configuration-windows-server-2022.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx index 95094b0d79..15ba4cbfb0 100644 --- a/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx +++ b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -66,7 +66,7 @@ For more information on using the Scaleway Serial Console, see [How to use the S ## Steps to enable DHCP configuration -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. +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. The reboot of the Instance is required for full activation.