Forum Discussion
WithinRafael
Jun 11, 2024Copper Contributor
WS2025 Preview (26100.1) fails to boot after joining WS2016 forest
I installed WS2025 Preview (Datacenter, 26100.1) in a virtual machine and after joining the domain, the box is rendered unbootable (boot loops). I can reinstall and do other tasks as a standalone ser...
Val-Thunder
Jan 27, 2025Copper Contributor
Hello,
Same problem with forest in 2012.
We found that the problem does not occur with AMD-based instances, only with Intel EC2 instances.
An Intel instance such as m5.xlarge can join the domain but after a manual reboot, the instance blocks at boot without visible log and AWS displays a status of 2/3 valid checks.
If we transform the instance into m5a.xlarge the instance can boot and operate in the domain again.
We have not really found an explanation for this behavior, as if joining a domain with Intel CPU blocked the instance from booting when no GPO is applied.
With WS 2022, we have no problem, only 2025 with Intel CPU...
- acdciFeb 13, 2025Copper Contributor
Confirmed the instance type change works! Went from t3 to t3a, success. Wow. Great catch!