Iso creation and website prompt to download

  • I was think you could possibly use the program called oscdimg for ISO creation, and it could be ran in the background on the server side. Might need its own random temp space to run, if multiple requests to create are prompted at the same time. After the building process the website would prompt to download or this could just be an admin task. The admin will give the ISO a name like as you would when creating a new image. It would be created and stored on the file share under a folder called ISO


    mkdir "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso"
    mkdir "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso\images"
    mkdir "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso\resources"

    xcopy /Y /E "C:\Program Files (x86)\clonedeploy\tftpboot\iso" "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso"

    xcopy /Y /E "C:\Program Files (x86)\clonedeploy\web\private\client_iso\output" "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso"

    "C:\Program Files (x86)\clonedeploy\web\private\apps\oscdimg.exe" -j2 -c -h -m -lCRUCIBLEWDS -b"C:\Program Files (x86)\clonedeploy\tftpboot\iso\boot\client-1.0.1.bif" "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso" "C:\Program Files (x86)\clonedeploy\web\private\client_iso\client.iso"

    rmdir /Q /S "C:\Program Files (x86)\clonedeploy\web\private\client_iso\new_iso"


  • yes, this is something that I would like to do, but keeps getting put on the backburner.
    @deployer actually recommended this a long time ago when CloneDeploy was CWDS.
    I compromised and made the solution that is currently generating the config files from the web.
    One thing that I don't want to do is differentiate CloneDeploy among different OS installs. The solution must be cross platform, but I do appreciate your efforts.

    I have so many ideas I want to get into CloneDeploy, but it's hard to find the time. My next area of focus will be completing the winpe imaging environment. That was my vision when I started over with CloneDeploy, to support multiple imaging environments to provide a single system that could be reliably used with all the major OS's. The multiple environments will provide a fallback in the event that one is not compatible. The final piece was to get all of those environments working together simultaneously without the need to change any config when booting to those environments. CloneDeploy Proxy DHCP will provide that. But enough on that, sorry for the tangent.

  • This is finally available in 1.3.0