Systems Management

just a small work around:

What we do...

We have a custom windows 11 23H2 (or 22H2) iso extracted, then we remove all unwanted indexes (home, student versions etc..) so we only have the 1 version we want (Pro in our case)

https://answers.microsoft.com/en-us/windows/forum/all/remove-multiple-indexes-with-dism/b57d2169-47a2-41f6-b667-af2c8ef44b06

Then we also apply some custom settings with NTLite (to make task bar more like windows 10 etc..) to the install.wim file

Then we zip the folder structure up into Win11_23H2.zip

We then use the client drop feature of Kace to upload the large 5gb file into to a custom software

Next, we setup a File synchronization to get the win11_23H2.zip file copied to the targets into folder c:\files\win11

Once the file is on the device(s) we run a script (running as a custom script user) that does a few things...

1. it rechecks if the device meets the hardware requirements with the "HardwareReasiness.ps1" from "https://aka.ms/HWReadinessScript"

2. it then extracts the Win11_23H2.zip to c:\files\win11_23H2 folder...

3. if capable, we then run a command that disables bitlocker if enabled, then runs command "c:\files\Win11_23H2\setup.exe /auto upgrade /eula Accept /quiet /noreboot /CompactOS disable /DynamicUpdate disable /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable"

4. we then use the KUserAlert.exe to create our own custom pop up message:

*   The computer was upgraded to Windows 11         *

*  The next time the computer restarts the upgrade *  

*              will install.                                                          *    

*                                                                                          *     

* The next restart will take a little bit longer.            *   

*                                                                                         *  

*      PLEASE DO NOT DISRUPT THE UPDATE...         *   

***************************************

5. if no one is using the PC, we can then force a reboot.. if user is using they will see the message and upon next restart the update will finalize..

This is similar to how we did the updates from windows 7 to windows 10, it seemed to be easier that the k1000 feature updates, especially since in k1000 you can NOT go from windows 10 22H2 to windows 11 23H2

Hope that helps anyone with any issues..

Jct

Striving for an answer on Feature update Windows 11 2`1H2 To Windows 11 22H2, as well. 

Dell 7420 fleet:  The systems were purchased to handled Windows 11 so they meet all standards.  

When running PC Health check you get a message your corporation manages your updates, despite having the regedit keys applied that allow Windows Updates/Feature Updates.   The panther files also confirm that the PC Health is okay and should update.  The clients have all Dell Updates Firmware patches, and at each try over the last two months were at the latest patch release.

Note:  reverting the Windows regedit keys allows directly patching/feature update using Windows 11 native process, however these same settings do not help K1000 feature update deploy/complete.  Continually getting the error code 0,0x0 when trying to deploy a feature update.  Windows Feature Update fails 0,0x0 

Quest has had a ticket for over two months with no resolution or movement to resolve K1000 feature update not working.  We are at the K1000 13.1.80 latest release.  Is this an issue introduced by Microsoft Windows new managed deployment process, blocking or interfering with the 3rd party tools like K1000 for updates.     | pending confirmation if Beta 13.2 resolves the issue.

Appreciate any insight.