OSDBuilder
OSDBuilder copied to clipboard
OSDeploy
Support for Windows 11 23h2
Does anyone have any workarounds for building the Windows 11 23h2 image as the latest version of OSDBuilder does not support it?
https://github.com/OSDeploy/OSDBuilder/pull/97
Waiting for @OSDeploy to merge, and update PSGallery with latest builds of OSDBuilder, OSDSUS, etc...
@Mattnicko Workaround as long as merge was not done: manually load the files from pull request locally https://github.com/OSDeploy/OSDBuilder/pull/97 and if you need multilanguage image as well https://github.com/OSDeploy/OSDBuilder/pull/94
For the moment, base should not newer than October 2023 ISO file.
Or use Win11 22H2 Image, also not newer than October 2023 - then do a built and capture with MDT and WSUS for which you can either just install November CU or also the enablement package for switch to 23H2.
For your information, David aka @OSDeploy is very busy and it's difficult to keep OSD or even OSDBuilder up to date (see the second pull request for reference) - that's why OSDBuilder will properly stop soon or later :( So I'm also looking for alternatives, but in general the direction is to consider AutoPilot and as MS also changed the format for CU they also want us to stop offline imaging ...
@Simsi1986 Help has been offered to maintain the module by several of us, we've asked David to provide documentation on the process he follows to update catalogs etc.. AutoPilot isn't going to help when the machine is toast.
Still working on it ... but been tied up the last week. I just pushed an update for OSDSUS, but does not have 23H2 yet included. ETA this weekend when I have some more time after Thanksgiving
@xe0n11 You're right - but at some level it can be already difficult to approve pull requests. If too much is on your desk, even small things can become big.
And of course AutoPilot is not the solution for everything, I also prefer the proven ways to get a clean image which can be used for bare metal deployment. And with a few adjustments it's even possible to complement both wonderfully. I don't protect the decisions made in Redmond, I just try to understand where the add. challenges are coming from.
@OSDeploy Much appreciated, hopefully you can then also finally approve/include https://github.com/OSDeploy/OSDBuilder/pull/94 - but before that I wish you a nice Thanksgiving with your loved ones.
@OSDeploy Thanks for continuing to contribute to this project when you have the time.
I pushed an update to OSDSUS this week, but for Windows 11 23H2 I still need to do some testing. My apologies, but I've been spending much time off over the holidays
I pushed an update to OSDSUS this week, but for Windows 11 23H2 I still need to do some testing. My apologies, but I've been spending much time off over the holidays
If it helps at all. I have been using my MDT daily with the changes I made in my pull request without fail. Works on all latest images
Is there any update on this? I did a OSD import with the 23H2, no errors so far?
I'll have to do some more testing. I had a chat with Gary on the 23H2 OS files and will be working on them this week.
Thanks David. 🍻
Side note: have you given much thought about writing the documentation on how to generate the catalog files for OSDSUS? I've noticed the last few releases are lacking the LCUs, several of us have put our hands up to assist you with producing the monthly catalogs.
I'll have to do some more testing. I had a chat with Gary on the 23H2 OS files and will be working on them this week.
Did you go ahaed with testing ? I have a lot of people anxiously waiting for the new version to be released :) Thanks in advance for all the hard work you put into this :)
For anyone that desperately needs this. Just manually load the files from my pull request. I deploy about 20 machines a day and update the image every Tuesday to get latest patches. Still works flawlessly on latest builds of windows
For anyone that desperately needs this. Just manually load the files from my pull request. I deploy about 20 machines a day and update the image every Tuesday to get latest patches. Still works flawlessly on latest builds of windows
Can confirm working as expected. Thanks @lufkin87 🍻🦘
Thanks @lufkin87, hopefully this gets merged soon! I was looking into preparing for Windows 11 deployment for my company, and we still run things old-school w/MDT + WDS, and this is exactly what I needed! 😁
@xe0n11 , when i run "OSDBuilder -Download OSMediaUpdates" i see 2024-02 Cumulative Update for Windows 11 Version 23H2 but i dont see the 2024-03 one.
@Whereamnow - the latest OSD module catalogs haven't been pushed to PSGallery so you won't see 2024-03. Once that's done, should be business as usual.
Yup, sorry I was out of town last week and didn't get back until late Saturday night. I'm doing some work for the job that signs my checks first, and should be able to do some pro-bono work on Patch Tuesday testing in the next 1-2 days. Stand-by.
FYI @OSDeploy - https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2022#3271msgdesc
OOB incoming, may need to update OSD catalogs again, haha.
@Mattnicko Workaround as long as merge was not done: manually load the files from pull request locally #97 and if you need multilanguage image as well #94
For the moment, base should not newer than October 2023 ISO file.
Or use Win11 22H2 Image, also not newer than October 2023 - then do a built and capture with MDT and WSUS for which you can either just install November CU or also the enablement package for switch to 23H2.
For your information, David aka @OSDeploy is very busy and it's difficult to keep OSD or even OSDBuilder up to date (see the second pull request for reference) - that's why OSDBuilder will properly stop soon or later :( So I'm also looking for alternatives, but in general the direction is to consider AutoPilot and as MS also changed the format for CU they also want us to stop offline imaging ...
Where does one find the October 2023 build of 23H2 Enterprise if it's no longer in VLSC?
@Mattnicko Workaround as long as merge was not done: manually load the files from pull request locally #97 and if you need multilanguage image as well #94 For the moment, base should not newer than October 2023 ISO file. Or use Win11 22H2 Image, also not newer than October 2023 - then do a built and capture with MDT and WSUS for which you can either just install November CU or also the enablement package for switch to 23H2. For your information, David aka @OSDeploy is very busy and it's difficult to keep OSD or even OSDBuilder up to date (see the second pull request for reference) - that's why OSDBuilder will properly stop soon or later :( So I'm also looking for alternatives, but in general the direction is to consider AutoPilot and as MS also changed the format for CU they also want us to stop offline imaging ...
Where does one find the October 2023 build of 23H2 Enterprise if it's no longer in VLSC?
Sorry to say, but not on "my.visualstudio.com" (old MSDN).
The build must be 22631.2506 or older 22631.2428? https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information
Newer media works fine, OS import in my setup is Windows 11 Enterprise x64 23H2 22631.3007 (en-us_windows_11_business_editions_version_23h2_updated_jan_2024_x64_dvd_12855bc9.iso).
^ Generated yesterday.
@xe0n11 Yes, newer images are working well.
@jespinoza84 Sorry for the confusion - my comment in November '23 was related to the situation at that time. In the meanwhile I could investigate the possible root cause for some issues.
My experience is, that OSDBuilder is only working well, if the imported ISO is at least one step behind of the available update during offline imaging. I could observe strange behaviour even in the build and capture after offline imaging. This also explains some issues I had previously in combination with MUI Image creation etc.
So the recommendation is to not use latest ISO (in terms of patch level, not release) before next Patch Tuesday. At the moment, latest Iso (2023-03) should work fine with latest CU (2024-04). Maybe I will have some time during maintenance to update our OSD and Upgrade Images as they are still on patchlevel 2024-02.
@xe0n11 Yes, newer images are working well.
@jespinoza84 Sorry for the confusion - my comment in November '23 was related to the situation at that time. In the meanwhile I could investigate the possible root cause for some issues.
My experience is, that OSDBuilder is only working well, if the imported ISO is at least one step behind of the available update during offline imaging. I could observe strange behaviour even in the build and capture after offline imaging. This also explains some issues I had previously in combination with MUI Image creation etc.
So the recommendation is to not use latest ISO (in terms of patch level, not release) before next Patch Tuesday. At the moment, latest Iso (2023-03) should work fine with latest CU (2024-04). Maybe I will have some time during maintenance to update our OSD and Upgrade Images as they are still on patchlevel 2024-02.
How do I use your updated files from the pull request? Do I just run them like regular ol' ps1 files or do I need to put them somewhere so that they take presedeence over the current ones that don't work with 23H2
@nolageek
Download the PR, overwrite files in the following directory - C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\23.2.21.1
@OSDeploy Can you merge this into the main branch\update PS Gallery soon? May help others.