Configuration of DHCP role fails when using non-English Windows Server iso
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Description
The script looks for an interface with an alias Ethernet while configuring the DHCP role, but will fail if you use an non-English Windows Server iso. In my case I was using 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_JA-JP.ISO for the iso and the interface alias was イーサネット.
https://github.com/microsoft/WSLab/blob/95408e80df8587b445af9b0e21078d8b5779b53c/Scripts/2_CreateParentDisks.ps1#L735
As an workaround, I had to logon and rename the interface to Ethernet to proceed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at Scripts/2_CreateParentDisks.ps1 around line 735, where the DHCP role configuration looks for the Ethernet interface alias. Reproduce the setup with the Japanese Windows Server ISO or inspect how the interface alias is obtained, then verify that DHCP configuration succeeds without manually renaming the localized interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100