Hey everyone! I'm supposed to upgrade about 600 devices from Windows 10 Pro 22H2 to Windows 11 Pro 24H2 since support for Windows 10 is running out soon. However, I'm hitting a snag while doing an in-place upgrade on a test machine. I'm getting a "Not enough resources to complete the operation" error right after login. The thing is, storage and memory aren't the issue, which makes this error really frustrating because it would force me to format the device, completely ruining the point of an automated upgrade.
Here's a bit more about the setup:
- Devices: Dell Latitude 3400-3450 laptops and OptiPlex 3020-3090 desktops.
- Some devices are on-site while others are remote (using Check Point VPN).
- Everything is AD domain-joined.
- We use ManageEngine Endpoint Central, but my permissions are quite limited.
- Access to the Domain Controller and firewall rules is also restricted.
With all these constraints, I'm looking for the best approach to resolve this. Should I dive deeper into the resource error (like checking drivers, BIOS updates, or TPM/Secure Boot)? Is there a more efficient way to roll out Windows 11 at scale given my limited infrastructure access? Any workarounds or strategies you experienced sysadmins can share would be super helpful!
4 Answers
First off, make sure all your drivers and firmware are updated. It might also help to run the DISM /restorehealth command and the SFC /scannow command to check for other issues. When it comes to deploying the upgrade, you can easily set it up through GPO. Just configure the Target Feature Update version in the Windows Update for Business policy to Windows 11, version 24H2. That should streamline the process!
I found that there's an inventory report in ManageEngine called "Windows 11 Readiness". It can show you what components are missing for the upgrade on each workstation. It might help identify problems before you push the upgrade.
I remember encountering a similar issue with early 24H2 installations linked to encryption types when contacting the domain controller. You might want to check if you're using older encryption standards like RC4, as they might have been disabled in 24H2 updates.
There should be logs generated during the upgrade attempts that can give you more detailed insight into what's going wrong. You can check the log files for more information. Here's a link with details: [Microsoft Log Files](https://learn.microsoft.com/en-us/windows/deployment/upgrade/log-files).
Good call on using GPO! That really simplifies things for mass updates.