RELATED IDEAS
continuation of -imagefileURL
I hope this switch manages to make its way into V2 once we can start calling via CLI again. Very useful to us thank you!
I hope this switch manages to make its way into V2 once we can start calling via CLI again. Very useful to us thank you!
Our working model uses OSDCloud v1.0 in a wrapper script, made to be a sort of quasi-MDT worklow to deploy windows/configuration/applications as selected by a Tech and limiting use of internet including hosting the current ESD on a webserver alongside an SMB share. This avoids 30 laptops bringing the office internet to a crawl or a schools connection when they are building a new IT suite on-site. I noticed a PR for utilising MCC to pull the ESD by a third party, but after spinning up one i never managed to get it to work on 1.0 at least.
With our ConfigMgr task sequence integrated OSDCloud v1 we need this in two scenarios.
Sometimes the latest Microsoft esd files have included bug that have broken some functionality that we run during setupcomplete.cmd. Has mainly been issues with installing language packs with powershell. At least couple of times we have needed to bypass the esd version that osdcloud uses with -imagefileurl and target for previous esd version
Some of our clients use custom wim instead of esd from Microsoft. Using -imagefileurl we can target OSDCloud to use wim file hosted in Azure
Still reviewing, will need more votes and comments on use case. This is a big uplift for only 4 votes. 😁
In OSDCloud V1 we leverage the custom .wim functinality. For prod enviornments is good to test new monthly releases and make sure MS hasn't broken part of the build process. MS OOBE changes for example sometimes lead to unexpected Autopilot results, so not having to be on the bleeding edge is useful :o)
Likewise we may desire to create a custom WIM that includes some pre-installed apps as well.