mslab vNext - Support vNEXT Windows Server
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Description
Issue repro:
- Install Windows Server vNext on baremetal
- Add "Hyper-V" and reboot
- Terminal (Admin)
- winget install microsoft.Powershell (7.6.2)
- close and repopen
- Terminal (Admin)
- run 1_Prereq.ps1
- run 2_CreateParentDisks.ps1.
Choose en-us_Windows_InsiderPreview_Server_vNext_en-us_29595.iso
Results:
- the Domain controller behaviour is the same
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 by reviewing mslabver.txt, Prereq.log, and CreateParentDisks.log alongside 1_Prereq.ps1 and 2_CreateParentDisks.ps1. Reproduce the reported setup with Windows Server vNext and the specified ISO, then identify why the Domain Controller behavior is unchanged. Done means the lab scripts support this Windows Server version and the relevant reproduction completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100