Abnrangerx67

Understood, but with two different boot images, one with and without the startup command, how is that controlled in terms of which one comes down when imaging is initiated? Unless the idea is that one boot image can be used even with the startup command, but bypassed if the deploymentID is not input, then the process continues to the ones not hidden. Also, can the x64 boot image be used? I noticed in your tutorial you used the x86, not sure if that is a requirement or just your choice at that time. Thanks again for your response.

I gave this a try but it did not work. Not sure if it is because I used the x64. However, it did raise a concern that I was afraid would happen. When I PXE booted, the correct WIM did come down, but as mentioned in my other post, what if this was someone else and they wanted to access the visible TSes? Aside from assigning to a known collection, how do you use this on the unknown computers collection for baremetal imaging while still using the other normal boot images for traditional imaging?

Apologies, so with the boot image in place and used by our main TS. how would have an additional boot image for the hidden TS work or affect the unknown computers collection when it is time for OSD? My concern or wonder is what happens when a new/BareMetal computer is PXE booted, how is the "correct" boot image selected to be presented for the correct imaging process?

Great post, thanks will give this a try because now that we are deploying win11, but want to keep a win10 ts but have it restricted to "as requested". By hiding it, a ticket would need to be submitted and the deployment ID provided. Is there a way to use another form of "id" that we can rotate let's say monthly? Maybe overkill, but just trying to find a way to keep this as restricted as possible, because I suspect someone will get wise and know the deployment ID is not changing so they won't ask for it anymore. Now that I think of it, maybe we can just create a new deployment every month so the ID get changed. I will see how that works, but definitely open to some ideas.