3 Replies Latest reply on Aug 6, 2014 10:59 AM by Newton Nyante Branched to a new discussion.

    Provisioning a SysPreped WIM image of W2k8 R2

    Steffen Kreis



      up until today we only slipstreamed patches into our WIndows WIM images and deployed them using the Unattend Setup via BSA (8.3.2)


      Our Windows Engineering guys now want to move to a SysPreped WIM Image that would already contain additional stuff and settings to reduce deployment time.


      So far so good, in order to get things going i created a System Package Type with the options ticked like that:




      When we deploy such a package

      • the Drivers are laid down to the disk
      • and the image is applied via imagex.


      Then BSA reboots the target and we get a bootmgr error saying that winload.exe is missing or corrput.




      We already identified the reason for that, which is caused by the fact that the boot configuration is set to a "unknown device" after the image is applied (we aborted the script to check)


      The issue is described a lot in the web and the common solution is to run something like this after the image is applied


      bcdedit /set {default} device partition=c:

      bcdedit /set {default} osdevice partition=c:

      bcdedit /set {bootmgr} device partition=c:

      bcdedit /set {ntldr} device partition=c:

      The only problematic part is that we are unable to inject such commands into BL's provisioning sequence.


      So my questions are:


      Is anybody successfully deploying syspreped WIM images of W2k8 R2 using BladeLogic?

      Did somebody face a similar issue and was able to resolve this ?