-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mslab 24.04 Hydration of DC fails after first reboot when Parent OS and VM (mslab DC) OS is Windows Server 2025 #588
Comments
This issue is under Investigation by Microsoft. Thank you @michbern-ms. |
@jaromirk I put together a new 'NoDCHydrate' feature which enables one to work around this for now: Take a look and let me know if you want me to set up a PR. The investigation on the OS side continues, but I wanted to offer the feature as a workaround. |
Oh, that's sweet! @machv what do you think? |
Today, tested with Windows_InsiderPreview_Server_vNext_en-us_26296.iso. No change in behaviour. Waiting for fix on OS level. |
@Karl-WE That's unexpected. Version 26296 has the two fixes necessary to resolve this scenario. I ran the full scenario this morning with 26296, downloaded from the Preview center: And it worked well. I did not need to use the 'NoDehydrateDC' feature - it all just worked. @jaromirk , @machv - would it be possible for one of you to test with 26296 and see if you can reproduce what Karl is seeing? |
Hi @michbern-ms Hyper-V Host OS was the same build as the DC VM OS version. I will try this again on Windows 11 24H2 as Hyper-V host OS. |
It's killing me softly as I thought I could finally come back to a new lab and have fun. I am eager to help Michael. As always. |
This issue is remediated with b26311. See also #607, #604 I am closing this with a workaroud remark: Note Users that seek to evaluate mslab based on Windows Server 2025 please consider the following instructions:
fyi: @michbern-ms Thank you everyone for their huge efforts!
|
The entire issue is described here
https://techcommunity.microsoft.com/t5/windows-server-insiders/b26085-windows-server-2025-domain-controller-fail-to-deploy-via/m-p/4119469
Scenario:
Host OS (Hyper-V): b26085 Windows Server 2025
Guest OS (DC): b26085 Windows Server 2025
Issue:
Application of DSC fails after the first reboot while hydrating the DC VM
Repro
Workaround:
Do not use WS 2025 as a guest VM OS at the moment, for CreateParentDisks (DC) until solved.
Using WS 2025 for usual VMs, such as Management, WAC etc are not affected.
The text was updated successfully, but these errors were encountered: