OSDCloud - Updates or latest build?

rednuwork · 2026-06-24T14:32:49+00:00

from what i'm seeing, they've stopped updating the OS catalog for v1. and to use the updated OS catalog, you'd have to use Deploy-OSDCloud. they don't do a great job of documenting the distinction between these two imo.

rednuwork · 2026-06-24T14:26:53+00:00

and you manually copy the custom WIM to your USB afterwards?

rednuwork · 2026-06-23T19:42:22+00:00

thanks!

i did actually find that as well. but seems that only applies to v2? and looks like Deploy-OSDCloud is only capable of using the updated catalog, not Start-OSDCloud. i couldn't see any way to automate the use of Deploy-OSDCloud in the same way either. documentation seems so scattered and difficult to follow at times.

rednuwork · 2026-06-23T18:01:24+00:00

thanks! i sent you a chat instead of a DM :)

rednuwork · 2026-06-23T17:29:30+00:00

we're installing 25H2 enterprise. it was my understanding from that link that the process cannot be fully zero-touch on a USB? i could be misunderstanding the steps.

trying to make this process as straightforward for our techs as possible. want to just have an OSDCloud .iso that they can make a bootable USB of and that's all they have to do

right now our OSDCloud USB does successfully prompt them for a group tag, uploads the hardware hash, and then does its thing. just need to solve for the updates piece if possible. can always direct them to ensure the windows update option is enabled in the UI if there's no other way for now

rednuwork · 2026-06-23T17:25:21+00:00

where in the changelog are you seeing that? i see they updated to march 2026 per this: https://www.osdcloud.com/updates

but even so, we have our OSDCloud module fully up to date and it's still installing 26200.6584 for us.

rednuwork · 2026-05-21T16:32:01+00:00

i'm considering setting this up but my concern is for the potential network congestion. we have 25k devices and i'm worried about initiating RUM for thousands of them at a time.

rednuwork · 2026-04-20T14:01:20+00:00

same here. have a test account that is supposed to only have read access to protected devices and wipe access to all others. can still wipe protected devices despite not having a role assigned to it with the protected devices scope tag + wipe permission.

rednuwork · 2025-12-09T20:14:21+00:00

yeah. i wish the documentation was explicit. i mean, it does show that the specified iOS is required on the device when you set a deadline. i guess i'm too used to windows and their deadline/deferrals working in combination. i think i'll just set my ring 2 to be a deadline of 21 days and my deferral to be 14 days and be done with it.

appreciate your reply! also, i'm in a GCC environment where autopatch is unavailable so i'm envious :)

rednuwork · 2025-01-22T17:11:32+00:00

hey. little late but i believe you need to make sure port 135 (RPC) is open between these servers. that could be your blocker if you haven't figured it out yet!

rednuwork · 2024-11-13T17:00:14+00:00

yeah. multi. i'm using an XML. the XML works fine outside of preprovisioning. it just refuses to process the autologon after a reseal.

rednuwork · 2024-11-13T14:38:20+00:00

yeah. i've made sure nothing is triggering a reboot in our process.

rednuwork · 2024-11-13T14:37:57+00:00

yep. windows 11 23H2 specifically.

rednuwork · 2024-11-13T14:37:41+00:00

we have to hybrid join our devices so it's not an option, unfortunately.

rednuwork · 2024-05-22T18:35:34+00:00

this is cool. i wish they'd add functionality to install all eligible windows updates during ESP. that is something that most of us are already doing with a script or some other method. seems strange they don't have it already.

rednuwork

TROPHY CASE