OSDeploy
Feature for Offline Scenario (no network check)
No wait for Network in Offline Scenario (Initialize-OSDCloudStartnet.ps1)
I would like a option to disable search/wait for network (inside Initialize-OSDCloudStartnet.ps1) while using OSDcloud
Otherwise user's have to wait if network search/check goes in timeout
Do you have a proposed solution? How long of a delay is this consuming and what is the threshold for users waiting too long? I'm going to be honest, if this is only going to save a few seconds and its a minor inconvenience, I'm probably not going to invest 30-60 minutes of my time designing a solution.
I'd suggest if the wait is too long, you can always overwrite the startnet.cmd completely with Edit-OSDCloudWinPE with your own solution. This is the workaround I added because not everyone is going to want the same method.
We have a scenario were we only install custom install.wim's from D partition - without network.
Ok, but you didn't answer the "How long of a delay is this consuming and what is the threshold for users waiting too long?"
So if I understand this, the process works as intended, meaning you're able to use OSDCloud, as intended, but your users have to wait X additional seconds because of a timeout looking for a network. Is that accurate? If that's it, and without knowing the value of X, its quite possible I'll spend more time resolving this then it will save.
I'm happy if OSDCloud works for 75%, 85%, or 95% of people as expected, but I don't believe it will get to 100%, and that's ok. I believe this is a fringe enhancement that's really for a small benefit. I mean it has "Cloud" in the name, so its really designed for Cloud first. Local Only is secondary as a bonus, but that's not the design.
I'm sure the added X seconds is far less than the amount of time and effort that OSDCloud probably saves per deployment. I'm not going to commit to taking this up, but if you're going to go the distance and provide a solution, I'll review.
Finally, I proposed a solution which you didn't even comment on. "I'd suggest if the wait is too long, you can always overwrite the startnet.cmd completely with Edit-OSDCloudWinPE with your own solution. This is the workaround I added because not everyone is going to want the same method."
David