The Infamous Windows 10 22H2 to Windows 11 22H2 upgrade.
I'm new to this and struggling with this one. I have scoured page after page on Quest and IT Ninja but nothing seems to work for my issue. Could use some direction on this one as I'm under the gun to get this done to about 700 machines.
- Kace SMA version: 14.0.334
- Have subscribed to the Feature updates being used in the Catalog
Problem:
I'm trying to upgrade Windows 10 21H2, 20H2, and 22H2 machines to be on Windows 11 22H2. My method is to run an update through Windows Feature Update to move the 20H2 users to 21H2 via enablement package then move them through the same method to 22H2. 7/10 times this works without a hitch and sometimes nothing happens at all. I have ran as a Detect and then Detect and Deploy, a Detect and Deploy and as a Detect and Stage and then a Detect and Deploy. Really makes no difference from what I can see both in KACE and on the physical machine. This is the problem I'm seeing with the enablement upgrades for the machines.
Windows 11 issues:
Once all the machines are on Windows 10 22H2 I run a detect and deploy through Windows Features Update for Windows 11 22H2 x64 Business Editions and for testing purposes I leave the notifications one so I can see when it is trying to run it or do anything. This one falls flat on it's face 8 out of 10 times. And it is very sporadic at that. We have a mix of machines from Dell to HP's and VM's I have found no rhyme or reason as to why it doesn't work. But yet it will say success most of the time and not failure.
What I have tried so far:
- Verify that all machines are able to Upgrade to Windows 11
- Set both the Detect and the Deploy timeouts to 6 hours
- Maximum Deploy Attempts set to 3
- Have ran a patch schedule on the machine/s in question and verified that all Cumulative patches and Windows patches are installed.
- Adjusted GPO to not restrict the Version of Windows that can be installed
- Set the Agent process timeout to 2 Hours up from 1 Hour that it was currently set at.
- Agent inventories every 2 Hours
- Have removed the registry key "TargetVersionUpgradeExperienceIndicators" and re-ran.
We have the SDA on prem and the SMA is KACE as a Service so I have tried to get to the Samba share to try it as this a managed installed. But of course since it's not on prem I cannot do that either.
Answers (0)
Be the first to answer this question