Forum Discussion
b26085 - Windows Server 2025 Domain Controller fail to deploy via DSC
- For the benefit of the community - we confirmed that Preview build 26296 has the fixes for this issue. You can use 26296 as a guest OS in MSLab and you should not encounter the issues described in this thread. Several of us have tested this image to confirm. The fixes should reach the production version of Windows Server 2025 in approximately another month, considering the usual deployment schedule.
Many thanks to Karl-WE for being a great partner and helping us to debug this!
MicrosoftI retried this scenario with the Windows Server 2025 Public Preview ISO from the Eval Center:
MSLab version 24.04.1
Host OS - en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso
Guest OS - en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso
I was able to get all the way through the scenario and did not see any error messages.
MSBernstein
Tested Scenarios:
Test 1 - FAILED:
MSLab version 24.04.1
Host OS: Windows Server 2025 build 26085
Guest OS - en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso WS 2025 build 26100
Result: 2_CreateParentDisks.ps1,
OK - VHDX Creation
FAILED - DC creation
Test 2- FAILED:
MSLab version 24.04.1
Host OS: Windows Server 2025 build 26085
Guest OS - en-us_Windows_InsiderPreview_Server_vNext_en-us_26227 WS 2025 build 26227
Result: 2_CreateParentDisks.ps1,
OK - VHDX Creation
FAILED - DC creation
Test 3 - FAILED:
MSLab version 24.04.1
Host OS: , en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso, Windows Server 2025 build 26100
Guest OS - en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso WS 2025 build 26100
Result: 2_CreateParentDisks.ps1,
OK - VHDX Creation
FAILED - DC creation and boot
Test 4 - OK:
MSLab version 24.04.1
Host OS: en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso, Windows Server 2025 build 26100,
Guest OS - en-us_Windows_InsiderPreview_Server_vNext_en-us_26227 WS 2025 build 26227
Result: 2_CreateParentDisks.ps1,
OK - VHDX Creation
OK - DC creation
MSBernstein unfortunately I cannot exactly repro the results with the newer release.
Good news though that 26277 as guest on 26100 works. Afterall it seems that the Host OS plays a role, too.
Repeated Test 3 using MSlab 24.05.01 doesn't change anything here.
Test 5 - FAILED:
MSLab version 24.04.1
Host OS: , Windows Server 2025 build 26277
Guest OS - en-us_windows_server_2025_preview_x64_dvd_ce9eb1a5.iso WS 2025 build 26100
Result: 2_CreateParentDisks.ps1,
OK - VHDX Creation
FAILED - DC creation and boot
Test 4 - OK:
MSLab version 24.04.1
Host OS: Windows Server 2025 build 26277
Guest OS - en-us_Windows_InsiderPreview_Server_vNext_en-us_26227 WS 2025 build 26227
Result: 2_CreateParentDisks.ps1,
OK - VHDX Creation
OK - DC creation
- There were some subsequent issues in the DC creation and even Azure Stack HCI VM creation.
These all should be fixed if the Host OS is b26311 and the DC for MSlab is created with b26311 aswell. See note in
https://github.com/microsoft/MSLab/issues/588 MSBernstein thank you in return for the great expierence and cooperation in this regard. Looking forward to see this fix coming for Windows Server 2025.
Agreed b26296 works as guest OS for mslab (Domain Controller).
For mslab users: the parent / host OS should be WS 2019, 2022, 2025 b26100 as for now to avoid further complications when using mslab.- MSBernsteinFor the benefit of the community - we confirmed that Preview build 26296 has the fixes for this issue. You can use 26296 as a guest OS in MSLab and you should not encounter the issues described in this thread. Several of us have tested this image to confirm. The fixes should reach the production version of Windows Server 2025 in approximately another month, considering the usual deployment schedule.
Many thanks to Karl-WE for being a great partner and helping us to debug this! - MSBernstein
Karl-WE It should be a servicing fix to 26100, which will come out in one of the Patch Tuesday releases. Assuming all goes well, etc. 🙂
I appreciate the compliment - it is very motivating!
Michael - Cannot thank you enough for all the efforts. It will give mslab a rewind when it's becoming fully compatible with Windows Server 2025.
Is this fix in the works for 26100 and later or limited to this build? - MSBernsteinI wanted to update this discussion. We have found the issue that we believe is the root cause here and are developing the fix. The issue is triggered when a Domain Controller VM is 'dehydrated' and then re-imported. This is uncommon in production environments but is important to how MSLab works. Thus, we're working on a fix. It takes us some time to get a fix out to the world with appropriate testing, so please be patient while we roll it out. Thanks.
- MSBernsteinOn the MSLab side, I put together a script change that can help workaorund the issue, and I'm working with the maintainer to see about incorporating the change into the main build.
We're continuing to investigate this on the OS side.