by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    NuxRo
    @NuxRo
    Hi, does the Wimaging stuff work with 2012R2?
    Dmitry Kireev
    @kireevco
    Hi, needs to be modified, but should work
    NuxRo
    @NuxRo
    Do you know - roughly - what needs to be modified?
    It's a bit intimidating (for a linux guys at least). Very tempted to just use dd windows.raw from a linux live cd deployed by foreman
    Dmitry Kireev
    @kireevco
    There are conditionals checking for 2008r2 os
    Add 2008r2 in the same level
    And copy directories to 2012r2
    ** add 2012r2 I meant
    NuxRo
    @NuxRo
    thanks
    Dmitry Kireev
    @kireevco
    Il see i would have time to add it
    Dd would be terrible because of drivers and such
    NuxRo
    @NuxRo
    If dism ran on Linux I could do a dism /add-drivers after dd-ing it ... alas it does not. :)
    Or I could "dism" in a huge bunch of drivers that would probably cover most of our hw
    Dmitry Kireev
    @kireevco
    I like linux better, but I had to do it in powershell because of some integration that it has with dism
    there is imagex, that runs on linux
    but dism simply doesn't
    NuxRo
    @NuxRo
    I dont think you can add drivers using wimlib imagex alone alas
    Dmitry Kireev
    @kireevco
    you can’t...
    I was trying to run it via mono - same issue. also wine doesn’t work… (dism.exe)
    maybe some libs were missing. still, not open solution
    NuxRo
    @NuxRo
    thanks for the confirmation
    have a nice day
    Dmitry Kireev
    @kireevco
    you tool
    you too!
    Jan Wenzel
    @coffeelover
    hi, i'm trying to provision 2k12r2-x64-standard. it boots the generated boot.wim. when executing '10_init.cmd' an error message is displayed "x:\wimaging\deploy\wget.vbs: No such interface supported".
    Robert
    @graham1228
    Jan, you are getting that error because more than likely you do not have the right drivers installed into your Windows PE image for your NICs.
    Robert
    @graham1228
    Has any one else run into this issue? When provisioning a Win 2k12 image with foreman using vcenter compute resource the VM continues to reboot into Window's PE because foreman is setting the NIC as the first boot device on the VM at initial creation and the VM will always PXE boot. I'm using foreman discovery and with a Linux VM the PXE file is present so the Linux VM boots to local disk after the kickstart install; however this is not the case with Windows using the wimaging process.
    As a temporary fix I was able to comment out the line in "create_vm.rb" that set's the boot devices for the VM at creation, but would like the discovery image to keep track of the install process so the NIC can be the first device for re-provisioning purposes. Just wondering if I'm missing something and if others have had the same experience.
    hresto
    @hresto
    I've tried resolving this issue on my own, but still not able to figure out what's causing error. In Foreman 1.14.2 trying to deploy a win10x64 unattended, I'm getting a provisioning template error in preview: "Warning! There was an error rendering the Wimaging default provision template: "\xE6\x84" followed by "]" on UTF-8". Is this normal, or should this be resolve before I can continue?
    magarvo
    @magarvo
    Having a go with this on Foreman 1.13.2. Wish me luck ;)